Artwork for podcast Data Career Podcast: Helping You Land a Data Analyst Job FAST
181: I Got 285 Data Analyst Applications. Here's Who I Hired.
Episode 18114th October 2025 • Data Career Podcast: Helping You Land a Data Analyst Job FAST • Avery Smith - Data Career Coach
00:00:00 00:12:51

Share Episode

Shownotes

Help us become the #1 Data Podcast by leaving a rating & review! We are 67 reviews away!

I'll walk you through the exact data analyst job hiring pipeline from a hiring manager's perspective & show you how to NOT get rejected.

💌 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


🔗 CONNECT WITH AVERY

🎥 YouTube Channel

🤝 LinkedIn

📸 Instagram

🎵 TikTok

💻 Website

Mentioned in this episode:

✨ Try Julius!

This episode is brought to you by Julius – your AI data analyst companion. Connect to your database and/or business tools, pull insights in minutes–no coding required. Thanks, Julius, for sponsoring this episode. Try Julius at https://landadatajob.com/Julius-DCP

https://landadatajob.com/Julius-DCP

Transcripts

Speaker:

285 people applied for

this data analyst position.

2

:

Only one got hired.

3

:

I'm going to walk you through the

brutal six step hiring funnel that

4

:

eliminated 99% of candidates and

show you exactly how to survive it.

5

:

Now, here is what the hiring

process looked like for a

6

:

real data analyst job posting.

7

:

They got about 285 applicants

in about a week, 12.

8

:

Made it to a phone

screen with a recruiter.

9

:

Seven passed the sequel assessment.

10

:

Six got an interview

with the hiring manager.

11

:

Four, made it to the final round

with the entire technical team,

12

:

and only one person got the offer.

13

:

So what happened at each one of these

stages, and more importantly, how do

14

:

you make sure that you're not one of

those 284 people who got rejected?

15

:

Well, let's break it down step by step

16

:

let's dive into stage one, which

is application reviews stage.

17

:

And in this stage there was 285

applicants, and that's quite a bit,

18

:

but not uncommon in today's job market.

19

:

And you remember that only

12 made it to stage two.

20

:

So what the heck happened in this stage?

21

:

Well, usually I tell you that the

majority of applications are never

22

:

even seen by the hiring manager at all.

23

:

Instead, they're filtered by the applicant

tracking system or a TS for short.

24

:

But this hiring manager ensured me

that she looked at every single resume.

25

:

Now, I think this is the exception versus

the rule, and it really goes to show how

26

:

cool this hiring manager is in particular.

27

:

But that's also why they took the job down

after a week when they got 285 applicants.

28

:

Many companies would honestly just leave

this job up for a long time, collecting

29

:

maybe double or triple the candidates.

30

:

And honestly, you'd probably have

a low chance of being considered

31

:

if you applied pretty late.

32

:

And that's actually my first set of

advice and that is to apply early.

33

:

The earlier you apply, the more chance

you have of actually getting noticed.

34

:

Next, I'll tell you that if you're

not getting into stage two, which

35

:

is a recruiter screen, we'll

talk about that here in a second.

36

:

It's likely because of

your resume at this point.

37

:

That's all the company

really knows about you.

38

:

That's all they have on you.

39

:

So you probably need to change

something about your resume.

40

:

Now, I don't know exactly what that is.

41

:

There's lots of places you

could be going wrong here.

42

:

But here is a quick checklist to consider.

43

:

Is your resume a TS compliant?

44

:

The biggest mistake here I see with

like most job applicants is they

45

:

put tables or multiple columns in

their resume, and that's a no-no.

46

:

A lot of ATSs can't read

those properly at all.

47

:

So you could be getting your

resume rejected right away.

48

:

Next, are you missing keywords?

49

:

If the job description wants someone with

Tableau skills and you don't have Tableau

50

:

listed anywhere on your resume at all.

51

:

The a TS will probably auto reject you,

but even if you do get past the a TS,

52

:

the hiring manager isn't going to spend

much time on your resume if you don't

53

:

have those Tableau skills on your resume.

54

:

In fact, this is exactly what

the hiring manager told me.

55

:

She said, quote,

56

:

"If only half of applicants have

experience with Tableau (which is what

57

:

we listed in the job description),

I'm going to talk to the half with

58

:

Tableau skills before I talk to the

other half with Power BI or Looker.

59

:

You have to prioritize on the

things just because there's a

60

:

lot of people coming through."

61

:

So there you have it

from the horse's mouth.

62

:

Lastly, you could just be

overqualified or underqualified.

63

:

If you're too experienced with

this role, they'd probably get

64

:

worried that you're going to get

bored and leave in like six months.

65

:

And if you have absolutely no experience,

well, they're worried that you're going

66

:

to need to require too much training and

it's gonna be too much of an investment.

67

:

And that's really how 96%

of the applicants may be

68

:

including you get rejected.

69

:

But before you feel very sad and utterly

depressed, let me just tell you a

70

:

secret tidbit that never gets talked

about hiring manager said this quote,

71

:

"Honestly, when I looked at them,

probably 70% of the applicant pool

72

:

could have been successful in this role.

73

:

So that makes it really

hard to narrow down."

74

:

Guys.

75

:

Let this soak in for just a minute.

76

:

You may not be getting rejected

because you're unqualified.

77

:

You might just not be the best candidate.

78

:

So please, guys, I implore

you pretty please do not take

79

:

these rejections so harshly.

80

:

I know it's tough.

81

:

I know it doesn't feel good, but

realize often it's saying less about

82

:

who you are, what your skills are,

your capabilities are, and more to

83

:

do with your resume and maybe someone

just had a better resume than you.

84

:

That's it.

85

:

Don't take it so personally.

86

:

Avery Smith-3: So in stage two,

which is the recruiter stage, this

87

:

is where you're going to be talking

to someone from human resources.

88

:

This person usually isn't super technical.

89

:

They're not going to grill you on SQL

or statistics or anything like that.

90

:

They're usually checking for

things like, is this applicant

91

:

actually a real human being?

92

:

Which I know sounds crazy, but

it's:

93

:

important in today's day and age.

94

:

There's lots of scams out there.

95

:

Number two, can this

person communicate clearly?

96

:

Are they able to express

themselves thoroughly?

97

:

Three, do they actually have any of

those key skills listed on their resume?

98

:

Once again, this is nothing

super technical here.

99

:

Just making sure you don't list every

skill possible on your resume, even

100

:

though you know nothing about those

skills, that would be a huge red flag.

101

:

So that's what they're checking for here.

102

:

Number four, does this person

actually seem like they're

103

:

going to be a good cultural fit?

104

:

Are there any red flags?

105

:

Obviously the recruiter doesn't

wanna waste the hiring manager's

106

:

precious time with an applicant

that's just kind of a jerk, right?

107

:

And wouldn't fit in the team

anyways, so check in for that.

108

:

Number five, they wanna make sure

that the location and work style that

109

:

you want to have is a fit for you.

110

:

If the job description is in person

in Houston, but you live in Dallas.

111

:

That might not work.

112

:

Or maybe you want to commute

three hours a day, I don't know.

113

:

Uh, or if you're looking for remote

work and this job is actually

114

:

hybrid, it just might not be a fit.

115

:

So they're checking for that as well.

116

:

And lastly, what are your salary

expectations and do they match

117

:

what the company had in mind?

118

:

And this is a big one.

119

:

If the budget for the role is 70,000 to

85,000 and you're looking for a world

120

:

that pays like $130,000, it's likely

that they're not going to really.

121

:

Interview you any further.

122

:

So due to candidates not responding or not

having a salary, a location, or work type

123

:

fit, the applicant pool went from 12 to

seven applicants that made stage three.

124

:

Avery Smith-4: Stage three is the

technical assessment part, and

125

:

this is where the team is actually

looking at your technical capability.

126

:

They're trying to get a feel

for your technical skills.

127

:

Now, most of the times these

technical assessments are in Excel,

128

:

sql, or some other coding language.,

129

:

Because these tools are used the

most in industry, but also because

130

:

they're the easiest to evaluate skill

quickly and in a standardized way.

131

:

For our hiring manager in particular,

she chose SQL because it's one

132

:

of the core skills to the team

and it's really easy to test for.

133

:

Now, I will say I've seen a lot

of entry-level roles, have more

134

:

of a take home assessment that you

can do in like a 72 hour window

135

:

than doing like a pressured test.

136

:

And I'm a big fan of the

take home assessments because

137

:

they're a lot less pressure.

138

:

These technical assessments can be

really scary and high pressure because

139

:

it's like taking a live test that

may or may not determine your salary

140

:

for the next decade of your life.

141

:

That isn't fun, right?

142

:

So with all that pressure aside,

what can you do to perform well

143

:

in this stage and get past it?

144

:

The number one thing

you can do is practice.

145

:

Like you guys, there are so many different

data interview practice platforms out

146

:

there that you can try and it's a cliche,

I know, but practice makes perfect.

147

:

Now you might be wondering, well, what

do I practice, what might be included

148

:

in this particular SQL assessment?

149

:

And for this one in particular,

they asked two questions.

150

:

Number one was a group by question,

and the other one was a little bit

151

:

more advanced and it was a window.

152

:

Function question, sql.

153

:

So make sure you know both of those.

154

:

Uh, but luckily or maybe less

lucky and more skill for our

155

:

candidates, all seven of them

actually passed the SQL assessment.

156

:

Uh, but one candidate did end up taking

on a different offer and bowed out.

157

:

So we're moving into step

number four with six candidates.

158

:

Avery Smith-5: So in stage four, we

are now down to six applicants, which

159

:

is crazy from 2 85 to six, and this

is the hiring manager round here.

160

:

The hiring manager is meeting you

face-to-face for the first time.

161

:

So you're going to be doing some

pleasantries, some small talk, and

162

:

then some background questions.

163

:

Uh, and then eventually you're going to be

getting into more of the problem solving

164

:

questions like, for example, what's a

cool project you've worked on before,

165

:

either at work or in your portfolio?

166

:

What would you do

differently in that project?

167

:

Maybe like what type of data would've

been helpful for making decisions?

168

:

Hey, how do you use data

in your personal life?

169

:

These are just some examples

of questions they may ask.

170

:

In this stage, our hiring

manager dropped two of our six

171

:

remaining candidates from six.

172

:

To four.

173

:

And the reason, well, the hiring manager

felt that two of them had a bit lower

174

:

data visualization and data exploration

skills than the remaining four.

175

:

That's just from those questions

that we talked about earlier.

176

:

The best way to not get left behind

here in the dust is to make sure

177

:

that you have an awesome portfolio,

projects, and multiple if you can.

178

:

The hiring manager told me that

they don't have to be big projects

179

:

or use millions of rows, but if you

can make them novel and personal

180

:

to you, that would be really good.

181

:

And so I made an episode recently on the

five Best Project Ideas that you can start

182

:

today if you're just getting started.

183

:

So you can watch that on a YouTube card

up here or in the show notes down below

184

:

if you don't know how to get started.

185

:

But once again in this interview,

you're just gonna try to be yourself.

186

:

Just try to explain not

only the what, but the why.

187

:

Think out loud and try to

show that you are a go-getter.

188

:

So those four candidates are now

entering what we call team interview,

189

:

and that is stage number five.

190

:

Avery Smith-6: The fifth stage is

the technical team interview, and

191

:

this is where the hiring manager and

herd team of two senior analysts went

192

:

through some more technical questions.

193

:

It's almost like a combination

of the hiring manager interview

194

:

and the technical assessment.

195

:

Put together.

196

:

So they'd probably ask you things

like, Hey, explain a project

197

:

you've worked on step by step.

198

:

So that's very similar to the

hiring manager, but it'll also

199

:

focus more on your thought process.

200

:

Well, why did you choose

this instead of that?

201

:

So if you chose to do a calculation

in sql, well, why didn't

202

:

you just do that in Tableau?

203

:

Why did you choose that way?

204

:

And hey, how did you end up deciding

that this honestly shouldn't

205

:

be that scary at this point.

206

:

They already like you a lot.

207

:

They've already invested a

lot of time in you, and that's

208

:

because you're a great candidate.

209

:

They're just trying to figure out

which of the four candidates left

210

:

is the best fit for the team.

211

:

And after this, well, it's the last

stage, and that is the hiring decision.

212

:

At this point, the hiring manager and her

team get together and collect scorecards

213

:

of the team, interview each interviewer.

214

:

Gives a score based on how technical you

are with SQL and with Tableau, but also

215

:

how good of a problem solver are you?

216

:

How clear of a communicator are you?

217

:

How weird are you?

218

:

Just kidding.

219

:

Hopefully you're really normal and at

this point our hiring manager was able to

220

:

narrow it down to two front runners that

scored slightly higher than the other two.

221

:

So after cutting 283 other candidates,

how did the hiring manager go

222

:

from first to second place?

223

:

Well, honestly, she flipped a

Coin Hez Candidate One tails.

224

:

Candidate two.

225

:

Nah, just kidding.

226

:

She went to candidate who had a closer

domain related to the company's industry.

227

:

You know, both candidates,

they were both great at sql.

228

:

They could write good SQL code.

229

:

Both candidates could create

awesome dashboards in Tableau.

230

:

Both candidates were pretty clear

communicators, and both candidates

231

:

were pretty fun to talk to.

232

:

They could get along with the team.

233

:

So what was the differentiating factor?

234

:

It was, well, what have

you done previously?

235

:

What do you know about this domain?

236

:

What do you know about this industry?

237

:

What do you know about our

company, what we actually do?

238

:

So to all my career pivoters out

there, I hope this gives you hope,

239

:

and I hope it gives you confidence

because it should what you studied

240

:

in school, it can be really helpful.

241

:

The job that you are leaving, that you've

had for the last 10 years, it could

242

:

honestly give you the edge in the end.

243

:

So that is my advice to you guys.

244

:

Your domain matters if you

land an offer, celebrate it.

245

:

You've earned it.

246

:

If you don't get the offer, just

know that you are close and move on.

247

:

Don't get depressed.

248

:

Don't dwell on it.

249

:

It's not the end of the world.

250

:

I promise.

251

:

Your next offer is right down the road.

252

:

So there you have it, the full

data hiring process with tips

253

:

on how to pass each stage.

254

:

If you want a copy of this diagram or

you just want me to explain it via text,

255

:

I'll have a link in the show notes down

below where I'll send you all of this

256

:

and hey, if you enjoyed

this video, hit subscribe.

257

:

Keep going, you guys, you've

got this, I believe in you.

Follow

Links

Chapters

Video

More from YouTube