Episode 147

full
Published on:

11th Feb 2025

147: The Surprising TRUTH About Data Science Careers (ex-Amazon data scientist Daliana Liu)

In this episode, I chat with Daliana Liu of The Data Scientist Show! She talks about her career journey, including her tenure at Amazon, and offers practical advice on making data science impactful in business. Tune in to discover what truly makes a great data scientist and check out Daliana's Data Science Career Accelerator course, designed to help data scientists advance their careers: https://maven.com/dalianaliu/ds-career

💌 Join 10k+ aspiring data analysts & get my tips in your inbox weekly 👉 https://www.datacareerjumpstart.com/newsletter

🆘 Feeling stuck in your data journey? Come to my next free "How to Land Your First Data Job" training 👉 https://www.datacareerjumpstart.com/training

👩‍💻 Want to land a data job in less than 90 days? 👉 https://www.datacareerjumpstart.com/daa

👔 Ace The Interview with Confidence 👉 https://www.datacareerjumpstart.com/interviewsimulator

⌚ TIMESTAMPS

00:00 - Introduction

13:55 - Focusing on non-technical skills

18:07 - The importance of communication skills

23:11 - How to have positive visibility in your company

28:25 - Data Science & ML Career Accelerators

🔗 CONNECT WITH DALIANA

🎥 YouTube Channel: https://www.youtube.com/@UCa0RTSXWyZdh7IciV9r-3ow

🤝 LinkedIn: https://www.linkedin.com/in/dalianaliu/

📸 Instagram: https://www.instagram.com/dalianaliu/

Website: https://www.dalianaliu.blog/

🔗 CONNECT WITH AVERY

🎥 YouTube Channel: https://www.youtube.com/@averysmith

🤝 LinkedIn: https://www.linkedin.com/in/averyjsmith/

📸 Instagram: https://instagram.com/datacareerjumpstart

🎵 TikTok: https://www.tiktok.com/@verydata

💻 Website: https://www.datacareerjumpstart.com/

Mentioned in this episode:

🔮 Try DataFairy.io 100% free

Want an AI assistant to help you in your data journey? Try DataFairy.io for free to help you with Excel, SQL, Python, cold messages, networking, LinkedIn, and more!

🧚‍♀️ Try DataFairy.io (the best AI tool)

Transcript
Daliana Lui:

I think a lot of times we think it's important to

2

:

constantly grow your technical skills,

but that only get you somewhere.

3

:

So basically, if you imagine the career

trajectory from junior data scientist

4

:

to senior data scientist and later staff

and principal scientist, you'll see the

5

:

requirement for technical skills slowly.

6

:

The increase is there.

7

:

Not that high.

8

:

And however, it requires more

communication skills, leadership

9

:

skills, influencing skills, higher

level you want to, um, become.

10

:

Avery: So Dalyana, you have almost

300, 000 followers on LinkedIn.

11

:

You're a LinkedIn top voice.

12

:

You're the host of the

data scientist show.

13

:

Uh, you've worked as a data scientist,

uh, at Amazon, and now you're kind of

14

:

doing your own thing, teaching other

people how to be data scientists.

15

:

Thank you so much for coming

on the podcast and, uh, I'm

16

:

so excited to have you here.

17

:

Daliana Lui: Yeah, thanks

for having me Avery.

18

:

It's been a long time coming.

19

:

Avery: Yeah, I've been on your show

and now you're coming on, on mine, but

20

:

I'm really excited for, for me to get

to know your story better and also for

21

:

our audience to know your story more.

22

:

And also just know more about

like what it actually takes to

23

:

be a data scientist, you know,

specifically at a company like Amazon.

24

:

So for those who maybe haven't

followed you in the past, can you

25

:

just give like a quick overview

of what your career has been like?

26

:

Daliana Lui: Yeah, so I started

studied applied math in college when

27

:

I lived in China, and then I felt it

was too much theories, and I wanted

28

:

to learn something more practical.

29

:

So that's when I started

to get into statistics.

30

:

Got my master in, um, University of

Irvine, University of California.

31

:

Uh, and then I got my job as a business

intelligence data, data analyst.

32

:

So at that time the word data scientist

wasn't invented, but I was basically

33

:

doing, uh, data science generalist work.

34

:

Uh, I'm doing.

35

:

Analysis for the marketing

team, build time series model.

36

:

And then I, uh, got into Amazon.

37

:

I moved from LA to Seattle.

38

:

Uh, my title was again, business

intelligence engineer slash statistician.

39

:

I think that's a.

40

:

Basically perfect kind of

role for a data scientist.

41

:

Uh, and later I work on experimentation,

AB testing, product analytics.

42

:

So that's the first few years in Amazon.

43

:

And then I got into machine learning

and deep learning and moved to,

44

:

um, Amazon web services and also

grow to a senior data scientist.

45

:

Avery: Very cool.

46

:

And I think it's so interesting that you

started your career as a data analyst

47

:

or like with that data analyst title.

48

:

Do you recommend that for others?

49

:

Like starting as a data analyst or was

that role already kind of a data scientist

50

:

role, but just had the title of data.

51

:

Daliana Lui: I think today, if you look

at what people do under a data scientist

52

:

or data analyst role, it's so different.

53

:

For example, at Facebook, there

are product data scientists.

54

:

Don't do much machine

learning and modeling.

55

:

And they write a lot of SQL and they

probably also use Python and in some

56

:

other companies, there might be a

data analyst also doing some modeling.

57

:

So I would say it really depends on

the company and what a role specifies,

58

:

but in general, data scientists do.

59

:

Use Python more, do a little bit more

automation compared to data analysts.

60

:

And some data analysts, they

work more as a business analyst.

61

:

They work closely, very

closely with, um, stakeholders.

62

:

I don't think there's a good or bad to

start your career where it really depends

63

:

on what you're interested in, what kind

of job, uh, market look like, and, uh,

64

:

uh, Regardless of where you get started,

you can grow and become either a manager

65

:

or a principal data scientist and analyst

in your, uh, in your career track.

66

:

Avery: I agree that there's probably

not a right or a wrong necessarily,

67

:

but one thing, one thing that is really

interesting is just that those titles

68

:

kind of being all over the place.

69

:

And I think that's true today.

70

:

I mean, I think it's

probably more true back then.

71

:

Then, but even today, like I see some

of the strangest titles, like I've

72

:

seen a data science analyst before,

uh, or data analytic scientists.

73

:

Yeah.

74

:

And I'm like, I don't know exactly

what, what those roles are.

75

:

So if I had to ask you,

what is a data scientist?

76

:

What would you say the definition

of a data scientist is?

77

:

Daliana Lui: Yeah.

78

:

I think the data scientist is someone

who uses data and some kind of framework.

79

:

Could be experimentation, could be,

uh, machine learning, or it could

80

:

be some kind of statistics analysis

to help their usually business, uh,

81

:

stakeholder make better decisions.

82

:

Um, and this decision could be one

decision could be you automate a million

83

:

decisions, making it into a machine

learning model and eventually have

84

:

some sort of business impact, meaning

it help your company make more money.

85

:

Uh, save more time, save money, et cetera.

86

:

Getting more customers.

87

:

Avery: I like that definition.

88

:

Do you, do you think that like, do

you think that there's a difference?

89

:

Cause like a data scientist is kind

of what you just explained, right?

90

:

And there's this whole field

of study called data science.

91

:

Do you think data scientists are

the only ones that do data science

92

:

or like, where do you see data

science versus data analytics?

93

:

Daliana Lui: Yeah, I think now everybody

does data science, not just data

94

:

analysts, product managers, they have

to know some data science, data science.

95

:

They might not be the one

that always writes SQL, but

96

:

they need to understand it.

97

:

And I've also seen a lot of automated

analytics or machine learning tools.

98

:

Maybe a product manager in the

future can easily use those

99

:

tools to create some analysis.

100

:

Engineers.

101

:

They need to know data science.

102

:

In fact, a lot of AI engineers these

days, they basically came from a

103

:

software engineering background

and then they learned machine

104

:

learning statistics on the go.

105

:

And of course, we'll

talk about the overlap.

106

:

I think the biggest difference is

in general, I would say, See the

107

:

data scientists, the people with

a data scientist title, um, some

108

:

of them work on machine learning.

109

:

Some of them don't, but the ones who

work on machine learning, deep learning

110

:

have more engineering element in it.

111

:

See them more often in

a data scientist title.

112

:

And for a data analyst.

113

:

I think the data analysts today also do

a lot of automation, but it probably lies

114

:

in, uh, some of them might do some data

engineering work or creating a dashboard,

115

:

new automated dashboard, but it doesn't

mean their work is easily automated.

116

:

Need to communicate a lot with

their stakeholders to find out

117

:

what is the most important thing.

118

:

What's the story you need to

tell from their, uh, dashboard.

119

:

Uh, so they probably use more

SQL and some data analysts.

120

:

I know they use a lot of

Excel as well because their

121

:

stakeholders are not technical.

122

:

Avery: I think that's like a good

definition because really at the day.

123

:

There is so much overlap.

124

:

Um, and it really, like you

said, depends on the company.

125

:

So it, it's, it's quite difficult

to, to actually draw a line on, uh,

126

:

let's talk about some of the work

that, uh, you've done in your career.

127

:

So as a data scientist, you, you mentioned

the term machine learning, which, which I

128

:

think is a term that a lot of people hear,

but maybe don't know the definition of.

129

:

For, for me, it's basically just

using some sort of, of math to

130

:

accomplish some business problem.

131

:

The biggest one probably is predicting,

uh, what's going to happen in the

132

:

future, but there's obviously other

things like, you know, separating

133

:

things into groups and stuff like that.

134

:

Would you say that's kind of a fair

definition of machine learning?

135

:

Daliana Lui: Yeah, I think so.

136

:

It's basically learning machine learning

is basically learning patterns from data.

137

:

If you think about a pattern of

let's just say you drink coffee on

138

:

Monday, Wednesday, Friday, but don't

drink coffee on the rest of the day.

139

:

So if I have enough data, if you

follow those patterns, say 90

140

:

90 percent of the time, I'm able

to use a model to learn that.

141

:

So I think that's the.

142

:

Simplest machine learning probably

just have like one parameters,

143

:

which is the day of the week.

144

:

Uh, and today, when we think about

machine learning, it's more complicated.

145

:

We're probably some models.

146

:

If you think about the open AI had

GPT probably have, uh, I don't know,

147

:

millions, billions of those parameters.

148

:

Avery: Yeah, that that's pretty

complicated stuff, but you've also

149

:

worked on some pretty complicated stuff.

150

:

I would imagine at Amazon, one of

the things that I saw that you, you,

151

:

you'd kind of co published with Amazon

was essentially a soccer project,

152

:

which I played soccer growing up.

153

:

So I was a big fan.

154

:

Yeah.

155

:

And I think a lot of people listening

really, really enjoy sports.

156

:

Maybe they've seen the movie Moneyball

or read the book Moneyball kind

157

:

of highlighting the Oakland A's

and how they used analytics to,

158

:

to, you know, win a championship.

159

:

Uh, can you talk a little bit about

what you kind of did at Amazon

160

:

with, with this soccer project?

161

:

Daliana Lui: I was at Amazon Web

Services and, uh, our team at that

162

:

time was called ML Solutions Lab.

163

:

So basically we're a group of consultants.

164

:

We help AWS customers, um, implement a

machine learning, deep learning solution.

165

:

So this customer came to us.

166

:

They are a sports betting company.

167

:

They have a lot of soccer game data

and they want to see whether they

168

:

can predict whether there will be a

soccer goal in the next few seconds.

169

:

for joining us.

170

:

And so this is the first computer

vision project I worked on.

171

:

And it's a very complicated project

because we need to analyze the videos.

172

:

Uh, we basically, um, used a few different

frameworks to chop the data, um, into

173

:

kind of five second, five seconds, seven

second clips, and then we have to manually

174

:

Manually label the data into whether this

moment is a goal, whether it's not a goal.

175

:

And if you watch soccer, you

know, sometimes a very intense,

176

:

uh, how do you call it?

177

:

Uh, attack.

178

:

It looks very similar to a goal.

179

:

So we also need to label that to train

a model, to learn this is attack.

180

:

This is not a goal.

181

:

So a fun story is because

the data came to us.

182

:

We're not labeled.

183

:

So me and my coworker spent two days.

184

:

Just looking at those clips to label

whether this is goal or it's not a goal.

185

:

So over the two days, I think I probably

watched hundreds of soccer goals.

186

:

I don't want to watch soccer

for the next couple of years.

187

:

So that's the unexpected

part of data science.

188

:

Sometimes you need to do a lot of those

type of data quality check, labeling.

189

:

But you have to do those type of things

because we, we label it in a very specific

190

:

way that we know how to train a model.

191

:

Eventually, uh, we used, uh,

we experiment that on a few

192

:

different, uh, video analysis,

uh, modeling called, uh, um, I3D.

193

:

So basically it's an inflated 2D.

194

:

Using, uh, inflated 2D modeling to

analyze, uh, the data and the way,

195

:

how to simplify the business problem.

196

:

Because like I mentioned, after

tech, there could be a goal.

197

:

It could be not a goal,

maybe ended in like a corner.

198

:

For example, we'll just simplify

that into a binary problem.

199

:

That's also, um, important way to tackle

a very ambiguous, complicated problem.

200

:

Sometime you might not, you

might need to reduce the scope.

201

:

Uh, for example, this, in this case,

we reduce the problem space from a

202

:

multi class classification problem

into a binary classification problem.

203

:

And then we train a model.

204

:

When we came out with a classifier, uh,

with a classifier, we Use a classifier

205

:

to run through the entire game.

206

:

Every five seconds, we run through that

classifier and then see whether there

207

:

will be a goal in the next few seconds.

208

:

We also created a very fun demo.

209

:

Basically, in real time, you can see a

Uh, likelihood score of whether there

210

:

will be a goal in the next few seconds.

211

:

It can make the viewing

experience more exciting.

212

:

Avery: Yeah.

213

:

I saw, I saw the demo actually, and

maybe I'll, I'll insert a little

214

:

recording because it was pretty cool.

215

:

Um, but what, what a cool project.

216

:

Uh, and I think.

217

:

Uh, there's so many

different, different things.

218

:

I think that listeners can, can learn

from that one companies like Amazon.

219

:

And honestly, a lot of companies are act

as consulting companies a lot of the time.

220

:

Uh, and so what, like a gambling

company in this case, or any other

221

:

sort of manufacturing company,

or I don't know, whatever.

222

:

Company that exists a lot of the times

they like kind of outsource their

223

:

analytics and data structure stuff to

smarter companies like, like Amazon.

224

:

And I think that's, that's good to know.

225

:

And I think that's a cool role to sit

in is basically you get to do analytics

226

:

for, for multiple, multiple companies.

227

:

I think that's really cool.

228

:

And then the other thing I love that

you said was, you know, I didn't seem

229

:

like you were too much of a soccer fan

necessarily, and you to become one.

230

:

Uh, and that's sometimes what you

have to do is like, you maybe don't

231

:

have the domain experience, but.

232

:

You can kind of need the domain

experience when you're building machine

233

:

learning models a lot of the time.

234

:

Daliana Lui: Yeah, exactly.

235

:

And I also worked on a football, American

football project when I was on the team.

236

:

I knew, I mean, I, I know a little

bit of soccer, of course, but I knew

237

:

nothing about American football and I

have to buy a book to read how football

238

:

work, uh, to, to, you know, to our

point, to understand the context.

239

:

Avery: It's crazy because yeah, it's

just, there's the cool thing about

240

:

analytics and data science and machine

learning is it's really industry agnostic,

241

:

which really means that you can take

the principles, the machine learning,

242

:

um, models and the machine learning

algorithms and apply them to really

243

:

so many different business problems.

244

:

And so you could probably spend your

whole life just learning about different

245

:

industries and how to apply just one model

to those, those different industries.

246

:

Uh, which I, which I think is fascinating

and one thing I want to give you

247

:

credit for in your LinkedIn content.

248

:

A lot of the times you're,

you're obviously very technical.

249

:

Like you use a lot of very fun buzzwords,

uh, when you're kind of explaining that

250

:

and you've obviously worked for Amazon.

251

:

So you're obviously very technical, but

one thing I really appreciate about your

252

:

LinkedIn posts is, you know, sometimes

they're technical, but other times they're

253

:

like, Hey, you as a technical person

actually kind of get more done when

254

:

you focus on your non technical skills.

255

:

Has that been true for you in your career?

256

:

Daliana Lui: Yeah, absolutely.

257

:

Uh, I think a lot of times we

think it's important to constantly

258

:

grow your technical skills, but

that only get you, um, somewhere.

259

:

And after that, uh, I wish

I could show you a plot.

260

:

So basically if you imagine the career

trajectory from junior data scientists

261

:

to senior data scientists, and later

staff and principal scientists, you'll

262

:

see the requirement for technical skills.

263

:

Slowly, the increases.

264

:

Not that high, and however you require,

it requires more communication skills,

265

:

leadership skills, influencing skills,

higher level you want to become.

266

:

And I think once we get into the

reality, there's no homework anymore,

267

:

and there's no, uh, perfect data.

268

:

And a lot of times the stakeholders are

not even clear about what they want.

269

:

And so it is essential to know.

270

:

You know, from the beginning of the

project, how to ask the right questions,

271

:

how to work with the right people,

how to find a project that actually

272

:

have the high impact that can get you

a promotion and later on, how do you

273

:

influence the right stakeholders to

get your solution in the right place?

274

:

Avery: It's a, it's a crazy concept

because I think we, we like to think

275

:

as technical people, the, the more

technical you are, the more you'll get

276

:

paid, the more desirable you'll be, the

more influence you'll have at a company.

277

:

And, and to be honest, it's just not true.

278

:

Even if you're not junior levels,

even when you're trying to get hired.

279

:

It's not like the smartest person or

the best person at SQL lands the job.

280

:

There's often these soft skills, these

people skills, these communication

281

:

skills, uh, that come into play and,

and really kind of make the difference

282

:

between maybe a good data analyst, a

good data scientist, and a great one.

283

:

Um, one of the ones that you posted about

recently, and I think you kind of just.

284

:

Hinted at it just barely.

285

:

And your answer was sometimes

these stakeholders don't have

286

:

a clue, uh, of what you want.

287

:

And so one of the things you

posted recently was like, one thing

288

:

that can make you a great data

scientist is getting feedback early.

289

:

Can you expound on that?

290

:

Daliana Lui: Uh, when I started,

uh, in Amazon, I wanted to show

291

:

my manager where my stakeholders,

my work only one is perfect.

292

:

Otherwise I would feel embarrassed.

293

:

But reality is.

294

:

Sometimes you think you understand

their request, but you don't.

295

:

Or during the time when you're working

on a project, their preference,

296

:

their priority have changed.

297

:

So it's important to constantly

align with your stakeholders to make

298

:

sure you understand their needs.

299

:

And also, there's only It's very

limiting what you can communicate

300

:

three words, especially you're

working on a data science project,

301

:

whether you need to turn that into a

dashboard or machine learning model.

302

:

So you have to show them your demo.

303

:

Um, I, in my career growth

course, I always talk about

304

:

show them a ugly demo first.

305

:

Even if it's just in your, um, Jupyter

notebook or in your, you know, SQL,

306

:

uh, you know, editor, show them to let

them know what's the, uh, what does

307

:

the MVP look like, it's even better

if you can create a very small UI

308

:

so they can play with, they can get

excited for, and when they see what.

309

:

It might look like it gave them more idea.

310

:

So it's not a bad thing when they tell

you, Hey, this is not what I want.

311

:

If you're only 20 percent of the

project, but it will be a huge problem.

312

:

If you're already at 80 percent

of projects, actually you want to,

313

:

uh, have those small tweaks and ask

them, Hey, is this what you want?

314

:

Or I have a few other ideas that

I think that might help you.

315

:

This is my proposals.

316

:

What do you think?

317

:

So have those conversations

early can save you a lot of time.

318

:

When you're towards

the end of the project,

319

:

Avery: I'm sure, I'm sure you've seen

this now as you've grown in your career.

320

:

And I've seen it as I've grown in my

career to the point now where I, you

321

:

know, I code a little bit, but a lot

of what I do is, is directing other

322

:

people to code and stuff like that.

323

:

And I realized that, you know, now I'm

the stakeholder and I've become the, a

324

:

bad stakeholder where I don't even know

what I want half the time, what I'm

325

:

asking, or when I do know what I want, I

kind of stink at explaining what I want.

326

:

Um, and so when people.

327

:

You know, who, who are working

under me, are able to come back

328

:

with something quickly and be like,

Hey, is this what you're asking?

329

:

Uh, especially like in a meeting or in

a demo, like a loom video, uh, because

330

:

I like, like what you said, you,

you can only say so much with words.

331

:

It's almost like, like

internet speed, right?

332

:

That's basically like how fast information

can transfer words is like, I don't know.

333

:

15 megabytes per second, but

like an in person meeting,

334

:

we're talking like gig speed.

335

:

Um, there's just so much

more communication, which is,

336

:

which is, which is awesome.

337

:

And that ultimately leads to

what, what's called like adoption

338

:

and people using your analysis.

339

:

Um, and that's another thing that you've

mentioned, uh, on LinkedIn that like.

340

:

You can't really do data

science just for, for funsies.

341

:

You have to get it adopted.

342

:

Can you talk a little bit more about that?

343

:

Daliana Lui: I think there was a data

point a few years ago, probably over 80

344

:

percent of machine learning models fail.

345

:

I think part of it is natural

because there's a research or

346

:

discovery nature in data science.

347

:

Not everything has to

be put in production.

348

:

But a lot of times if What

you have done become useless.

349

:

Then from the company perspective,

they wasted their time.

350

:

You don't have direct impact.

351

:

And from a personal growth perspective,

if you don't have the impact, it's

352

:

hard to define your contribution

to the team, to our growth.

353

:

And how do you advocate?

354

:

Yourself for that promotion, when

you build something, a lot of data

355

:

scientists and also engineers, they want

to just build something that they think

356

:

is important or they think is cool.

357

:

They just learn some model

from a Coursera course.

358

:

They want to implement that.

359

:

I think that's a great way to learn.

360

:

By doing, but when it comes to, um, doing

work for a, most of the time for profit

361

:

company, you need to think about is what

I'm working on aligned with my team goal.

362

:

I'm not helping my stakeholder

or, um, this is the five goals.

363

:

My manager tried to achieve.

364

:

I'm not helping my manager.

365

:

I might be a team player.

366

:

It's better if you can align

your passion to the impact.

367

:

And sometimes the passion and

impact might be a separate thing.

368

:

There is one thing maybe you can exercise

your passion for, for learning on your

369

:

own time or take 20 percent of, you know,

your, your work time, but make sure the

370

:

80 percent of your time, you're actually

solving the useful business problem.

371

:

And a lot of time, it

could be a little bit, um.

372

:

Boring and repetitive.

373

:

Um, I think that's also an opportunity

for you to create more impact, to

374

:

see how can you, um, automate this?

375

:

How can you also, sometimes you need to

motivate yourself that again, aligning

376

:

with the stakeholders, with the customer's

pain point, stakeholder's request.

377

:

Sometimes if you see how does that

implement it, how it solve even

378

:

just one person's problem, it can.

379

:

Also make you feel more motivated

to work on projects like that.

380

:

Avery: It's hard because in, in data,

especially like in school, right?

381

:

Let's just take like a normal, you know,

college, maybe like a master's degree

382

:

or maybe even an undergrad degree.

383

:

Your master's was in what again?

384

:

What did you say your master's was in?

385

:

Daliana Lui: In statistics.

386

:

Avery: Okay.

387

:

And yeah, and my master's was in,

was in data analytics technically.

388

:

Right.

389

:

Um, but like, I would imagine it

was the same in your master's, but

390

:

my master's was very theoretical.

391

:

Um, and it was all about like, like, for

instance, you, you might be interested in

392

:

statistics of, of like getting a P value

less than, you know, zero point or 0.

393

:

05.

394

:

And you might be interested in like, okay.

395

:

Like, can we make the P value lower?

396

:

I know we can't really make P values

lower, but like you might be interested

397

:

in really low P value or, or in

like my masters, it might be like,

398

:

Hey, we're like 79 percent accurate,

can I get to 81 percent accurate?

399

:

So we're thinking in like

P values and percentages.

400

:

But really, like you said, most

businesses are pro for profit.

401

:

So they think in dollar signs and

usually pretty much dollar signs only.

402

:

Uh, so if we can't relate our

analysis and our work that we've

403

:

done into dollar signs, and it

doesn't have to be dollar signs.

404

:

It can be time saved.

405

:

It could be lives saved.

406

:

It could be.

407

:

You know, people promoted, I don't

know, whatever, whatever the,

408

:

the key units, yeah, more users.

409

:

That's, that's another good one.

410

:

Whatever your team is focused

on, you have to figure out how

411

:

to get your analysis there.

412

:

Otherwise you're not really

helping the team out one and two.

413

:

Like you said, your, your career

growth is going to struggle because.

414

:

Especially these bigger companies,

like your promotions are kind of tied

415

:

to the work you've done for the impact

you've had for the business, basically.

416

:

Daliana Lui: Yeah.

417

:

Avery: Yeah.

418

:

Okay.

419

:

I, I agree with you there.

420

:

I think that that makes a lot of sense.

421

:

Another thing I think you, you

mentioned in a LinkedIn post is like.

422

:

Maybe you are trying to do that, right?

423

:

But you're like, you're kind of struggling

to, to like advocate for yourself.

424

:

You're kind of struggling talk to

your, to make, to make your work clear.

425

:

Do you have any advice on like

how to like make your, your work

426

:

more known like in the company?

427

:

Daliana Lui: Um, yeah, so.

428

:

Uh, you meant, uh, making, having

more visibility in a company?

429

:

Avery: Yes.

430

:

Daliana Lui: Yeah.

431

:

If you already work on a high

impact project, you probably will

432

:

work on sometime directors or VP.

433

:

So I don't think you need to be kind of

quote unquote famous in your company.

434

:

Of course it helps, right?

435

:

If you did deliver a high impact

project and you give a talk.

436

:

You have more visibility.

437

:

Maybe there are other people come to,

um, invite you to for collaboration.

438

:

For example, when I published a blog

post on the soccer project, which is

439

:

talking about there are other teams

reaching out to me, asking questions,

440

:

looking for collaborations, but a lot of

times you only need to be visible to a.

441

:

In their circle of people, for example,

the people who actually decide the road

442

:

map of the team or the person who might be

on the committee of your promotion review,

443

:

I think a great way to do this is to.

444

:

See if you can build a relationship

with them to collaborate with them.

445

:

And the first step is, uh, if you,

again, don't know how to build a

446

:

relationship with, you can go from a

perspective to just learn from them,

447

:

to get feedback and show them what's

something you have been working on.

448

:

Kind of similar to, we talk about

getting stakeholder feedback.

449

:

Um, if you want to bring more awareness

for your project, for example, you're

450

:

building a new tool that will improve.

451

:

You aim to improve your team's

productivity, maybe talk to the key

452

:

users, potential users of this tool or

some other stakeholders and show them

453

:

a quick demo, um, ask them what's their

pain point and get, get a user feedback.

454

:

So when someone is.

455

:

Involved when they, uh, give you

ideas and you implement them, they

456

:

feel they're part of the project.

457

:

So later on, when they have some similar

project, they're aware, Oh, there is

458

:

someone I can talk to on that team.

459

:

They're expert in this.

460

:

So in a company, you don't

have to be an expert.

461

:

You don't need to work on one project for.

462

:

10 years and have a PhD

in it to become expert.

463

:

Sometimes if you deliver project end to

end, you, you know, a lot of the domain

464

:

knowledge and the business contact,

you are an expert, let people, uh, by

465

:

collecting feedback, um, talk to people

one on one, um, sometimes help them.

466

:

People know that you are

the expert on this domain.

467

:

And when you finish the project,

share your work through an internal

468

:

blog post, or you can schedule a

lunch and learn session, et cetera.

469

:

And, uh, I know we all

have our own priorities.

470

:

We're busy, but sometimes also need to,

you can set aside some time to host.

471

:

Office hours or, um, Q and a

sessions, be generous with your time.

472

:

Sometimes also goes a long way.

473

:

Avery: Very cool.

474

:

And I think, I think that is

awesome advice on, on increasing

475

:

availability, uh, sharing your work.

476

:

It's such a, seems, seems like you

shouldn't have to do that because

477

:

you're at work and it's like, why

do I have to share this with anyone?

478

:

Uh, but it can be such a big,

uh, impact to your career.

479

:

And, and others as well.

480

:

Uh, well, Dalyana, this is the

Data Career Podcast, and obviously

481

:

you've shared a lot of good things

about growing your data career.

482

:

Uh, I want to ask you if you had to

give someone who, you know, is listening

483

:

to this episode, any sort of advice on

advancing their career to the next level.

484

:

What would you give them?

485

:

Daliana Lui: I have so many devices,

very hard to come down to one.

486

:

Yeah, I would say.

487

:

There is, of course, it's important

to understand how to create more

488

:

impact for your company, uh,

how to advocate for yourself.

489

:

We are, um, in this kind of system,

there's promotion, there's annual review.

490

:

It's important to know

how to play that game.

491

:

Uh, but at the same time, it's

also important to look inward.

492

:

To know what do you enjoy, what is your

goal, uh, what's your life goal beyond

493

:

your, the, the next level of the promotion

or the raise, I think is helpful for

494

:

you to play the long game, um, when

you know yourself better, so maybe.

495

:

Uh, every quarter or every year said,

uh, we're at the end of the year,

496

:

maybe during the holiday season said,

uh, one afternoon, just write down how

497

:

do envision your life will look like.

498

:

And then think about how could

your career, your family, your

499

:

friends play a part of it.

500

:

So at the end of the day, the career

is only one aspect of our life.

501

:

Avery: I think that's important to

remember because it it's really easy to

502

:

get lost in, uh, all in it all because.

503

:

It's like, why do we work?

504

:

We work to live.

505

:

And sometimes it feels

like we live to work.

506

:

Um, so I think that is sage advice.

507

:

Uh, Dalyana, thank you

so much for coming on.

508

:

We'll have all of Dalyana's, uh,

links in the show notes down below.

509

:

She's been working on

something really cool as well.

510

:

Dalyana, you want to talk about

what you've been doing recently?

511

:

Daliana Lui: Yeah, so I'm working

on, uh, more career coaching.

512

:

So one course I recently

launched is called the data

513

:

science career accelerator.

514

:

So we talked about how to, uh, improve

your stakeholder management skills.

515

:

How to be a great communicator.

516

:

So all the soft skills we just talk

about and how to build a relationship

517

:

with our manager, how to create more

impact and get a promotion you deserve.

518

:

So basically we teach you all the

required soft skills, leadership

519

:

skills, communication skills

that school didn't teach you.

520

:

And this course requires you

to be a data scientist for,

521

:

you know, at least one year.

522

:

Um, and, uh, a lot of, uh, the senior

data scientists take this course too.

523

:

They want to learn how to

continue to expand their scope.

524

:

So, um, I will share the

link with, um, Avery.

525

:

Avery: Yep.

526

:

We'll have the link in the

show notes, uh, down below.

527

:

We'll also have links

to your social as well.

528

:

So make sure you're

following Dalyana already.

529

:

Dalyana, thanks so much

for being on the show.

530

:

Daliana Lui: Thanks Avery.

Listen for free

Show artwork for Data Career Podcast: Helping You Land a Data Analyst Job FAST

About the Podcast

Data Career Podcast: Helping You Land a Data Analyst Job FAST
The Data Career Podcast: helping you break into data analytics, build your data career, and develop a personal brand

About your host

Profile picture for Avery Smith

Avery Smith

Avery Smith is the host of The Data Career Podcast & founder of Data Career Jumpstart, an online platform dedicated to helping individuals transition into and advance within the data analytics field. After studying chemical engineering in college, Avery pivoted his career into data, and later earned a Masters in Data Analytics from Georgia Tech. He’s worked as a data analyst, data engineer, and data scientist for companies like Vaporsens, ExxonMobil, Harley Davidson, MIT, and the Utah Jazz. Avery lives in the mountains of Utah where he enjoys running, skiing, & hiking with his wife, dog, and new born baby.