139: The TRUTH About Landing a Data Job (Hiring Managers Tell All)
Help us become the #1 Data Podcast by leaving a rating & review! We are 67 reviews away!
It’s not just about skills; find out what makes hiring managers say, “You’re the one we’ve been looking for.” Featuring hiring managers like Alex The Analyst, Megan McGuire, Jesse Morris, and Andrew Madson, the episode provides actionable tips and behind-the-scenes looks at what it takes to stand out in the data job market.
💌 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
Subscribe to Our Newsletter: Join the Data Career Jumpstart Newsletter
Prepare for Interviews: Try the Interview Simulator
⌚ TIMESTAMPS
00:25 Alex The Analyst: The Importance of Personality in Hiring
08:01 Megan McGuire: The Hiring Process from Start to Finish
17:06 Jesse Morris: Storytelling and Tenacity in Data Roles
23:21 Andrew Madson: The Value of Projects and Team Fit
26:27 Conclusion and Additional Resources
🔗 CONNECT WITH GUESTS
Alex Freberg: https://www.linkedin.com/in/alex-freberg
Megan McGuire: https://www.linkedin.com/in/megan-s-mcguire
Jesse Morris: https://www.linkedin.com/in/jessemorris1
Andrew Madson: https://www.linkedin.com/in/andrew-madson
🔗 CONNECT WITH AVERY
🎵 TikTok
💻 Website
Mentioned in this episode:
⭐ Enjoy the show? Leave a rating
We are 57 reviews away from becoming the #1 data podcast in the world! If you haven't already, please take 30 seconds and leave us a rating!
Transcript
As the host of the number one data podcast on Spotify, I've
2
:had the opportunity to interview
a lot of cool people, including
3
:a lot of data hiring managers who
you'll hear from in this episode.
4
:And they've given really great advice
on how to get hired in the data space.
5
:In this episode, you'll hear the best
snippets from those hiring managers
6
:and get actionable advice on how
actually to land a data job straight
7
:from the hiring manager's mouth.
8
:Let's get into it.
9
:Our first hiring manager you
may have seen before on YouTube.
10
:It's Alex, the analyst or Alex Freyberg,
and he has really great hiring experience
11
:from when he was at his corporate job.
12
:And in this example here, I want you
to pay attention to what he thought
13
:mattered most when getting hired.
14
:It's probably going to surprise you
when you were hiring people, like what
15
:was important in a candidate for you?
16
:Like what was the first few
things you were looking at?
17
:Alex: Yeah.
18
:I'm going to be like brutally honest
because I think people tend to sugarcoat
19
:this process and the hiring process is.
20
:A lot of people on like LinkedIn
or YouTube will tell you like
21
:the sugar coated version.
22
:I'm going to tell you
what I truly looked for.
23
:I was on a hiring team
when I was a data analyst.
24
:I was the one who gave
the technical interviews.
25
:And so that was my part
of the hiring team.
26
:And then you're right.
27
:I became a hiring manager.
28
:And so then as the hiring manager, I did
the whole process and usually brought
29
:in like my boss as well for some like
the final interviews during the hiring.
30
:The, when I was on the hiring
team during that process, we
31
:were mostly hiring data analysts.
32
:I eventually started when I was a
hiring manager was doing developers,
33
:database engineers, or data engineers,
and then data analysts as well.
34
:So that was a little bit different,
but on the hiring team, just for
35
:data analysis, we always looked for
someone who had a good personality
36
:and most people will tell you.
37
:I've seen it online.
38
:They're like, well, you know, as long
as you have the right skills and you get
39
:in there and you smile, you know, that's
a good, that's what you need to do.
40
:I, I think when you're on a team,
you really do look for someone who's
41
:going to fit well with your team.
42
:And so, yeah.
43
:So, I always kind of gravitated
towards people who are more outgoing,
44
:and is that 100 percent fair?
45
:No, I don't think so, but hiring,
the hiring process isn't super fair.
46
:And so, the people who are more
outgoing, I tended to gravitate
47
:to, and so did my whole team.
48
:Our whole team was very outgoing, very
social, and so we didn't want to, someone
49
:come in and have a very different flow
to them, or, or personality to them.
50
:And so that's just like a brutal
truth, you know, people always
51
:say diversity is like crazy good,
but for personality, I think.
52
:The, the, that piece of it is actually
the flow of the team and how that, uh,
53
:people gel together is really important.
54
:The second thing we looked for is, uh,
being able to articulate well, their
55
:skills, abilities, and their experience.
56
:And so oftentimes we'd have people
come in and SQL is really important.
57
:When I was a, on the hiring team, SQL was
the most important skill because we used
58
:it like really in depth for a lot of our
processes and so people would come in and
59
:I was like, well, tell me how you've done.
60
:You know, data cleaning or
tell me how you use SQL.
61
:And if people can articulate really
well, like here's how I use it.
62
:They were just like, Oh, well, you know,
I've, I've taken a few courses in my job.
63
:I use SQL, but I don't
really use it that much.
64
:And they would kind of
beat around the bush.
65
:And I'd be like asking
really pointed questions.
66
:They couldn't articulate those
questions that I would think is if
67
:you've really used SQL well, you
should know how to answer those
68
:questions because I can tell you.
69
:Even at that time, I could be
like, well, here's the process
70
:that I would take to clean data.
71
:Here's how I do that in SQL.
72
:Here are, you know, here
are the exact steps.
73
:That's what you need to be saying
and people would beat around the
74
:bush and wouldn't want to say things.
75
:And that was always a big red flag.
76
:And then the last thing that I
think we would look for is someone
77
:who is technically proficient.
78
:So I was the one
conducting the interviews.
79
:We would always do some type of
whiteboarding and then some type of
80
:general technical interview question.
81
:So the whiteboarding,
you know, um, Uh, um, uh.
82
:Uh, um, it really is the number
one thing that I, like this
83
:is straightforward stuff.
84
:And we were hiring at like the mid level.
85
:So mid level SQL on their
resume for three years.
86
:This should be a no brainer.
87
:Like, like, This is like super simple,
like, like just aggregating something with
88
:a group by nothing crazy or just a simple
joint, just combine these two tables
89
:and people would have trouble with it.
90
:And that was an immediate red flag.
91
:Like we couldn't hire them.
92
:And so those three things I
would say are the biggest things
93
:that we look for and like really
ranked on during those interviews.
94
:But if I'm being like completely
honest, the personality thing
95
:was like 50 percent of it.
96
:If you have a good personality, then
that like really puts you higher up.
97
:And it's not just like I don't know,
personality is very objective and so
98
:it's hard to describe, but just somebody
who's more outgoing, very friendly.
99
:That is like kind of
what we were looking for.
100
:The being able to articulate and the
technical interviews is the other 50%.
101
:So those two things were still
very important, but if they looked
102
:like they were very teachable.
103
:If they looked like they were like
really driven and we were like, you
104
:know, they may not be where we want
them today, but I was like, that
105
:person will be good in like a month.
106
:We would still hire them.
107
:And we did that for one of our
business analysts who we hired, um,
108
:who were, he kind of knew SQL, but
his job wasn't as intensive as Eagle
109
:for his, that, for that position.
110
:So we were like, Hey, let's,
Let's hire him cause he would
111
:fit really well with our team.
112
:And we trained him like I, he was my
mentor, my, my, my mentee on my team.
113
:So I trained him in SQL and he,
within like a month he was up and
114
:running and I didn't really have
to help him that much anymore.
115
:So again, it was like that trainability
piece, the, um, the attitude,
116
:the, uh, how driven they were did
play a big role in who we hired.
117
:So I know I was long winded
on that, but they, you know,
118
:that's a, that's a really tough.
119
:Process to our to talk about, you know,
120
:Avery: it is I think you did.
121
:I think you did really well And I don't
I mean although it was you know, you did
122
:talk about maybe the extrovert versus the
introvert I don't think it was too brutal
123
:I think I think it's like an opportunity
you have a good personality and you
124
:maybe aren't the best technical person
on planet Earth You still have a chance.
125
:Alex: Yeah.
126
:Well, I talked to a lot of people who
give me that feedback They're like,
127
:well, I'm a really big introvert I
get really nervous and it's true and
128
:they're like, how can I get past that?
129
:and so So there are
things that you can do.
130
:I really believe in practicing
before interviews, mirror, looking
131
:in a mirror and practicing smiling.
132
:Cause believe it or not, I was
that person back in interviews.
133
:Um, I used to be very, very nervous
and very scared for interviews.
134
:Um, I used to be much more
introverted than I am now.
135
:I've worked through a lot of that as I
got into the workplace just by having
136
:to, in order to like succeed on teams.
137
:But I used to be very, very, very nervous.
138
:And, and so what I would do is
I'd practice in a mirror and then
139
:my, I'd practice with my wife.
140
:And so she'd be like, Oh,
you're doing that weird, you're,
141
:you're doing this weird thing.
142
:And she'd be really honest with me.
143
:And so I needed somebody who
could give me that feedback.
144
:And that helped immensely in interviews.
145
:So I'm kind of, I feel like I can
point even to myself as like a
146
:testament of someone who, who got over
that and was able to push through.
147
:And then I was really able to.
148
:Understand, like I have to
do that in order to really be
149
:successful in an interview.
150
:Avery: All right.
151
:So maybe not exactly what you expected.
152
:Personality really matters.
153
:And I think that's
actually a positive thing.
154
:Of course you have to have the skills
that is like the bare minimum, but your
155
:ability and your personality can actually
set you apart from other candidates.
156
:Now you might be thinking,
well, that's great.
157
:And like I said, I think it's a positive
thing because it means that there's
158
:room for all of us in the data world.
159
:Some of you guys will be thinking
like Alex said, Oh, I'm introverted.
160
:I don't have that great of
a personality or I'm kind of
161
:scared to share my personality.
162
:And I don't think you have
to become extroverted.
163
:I'm actually an introvert,
believe it or not.
164
:But I think really practicing in
those interviews and at least just
165
:coming off very personable in the
interviews is really important.
166
:I love what Alex said about the mirror.
167
:I actually built a software.
168
:It's called Interview Simulator
that lets you practice.
169
:Interview questions, uh, with the
hiring manager in front of you, like a
170
:mirror, and you actually record yourself
and get feedback on your responses.
171
:If you want to check that out,
it's at interview simulator.
172
:io or I'll have a link in
the show notes down below.
173
:Okay.
174
:Our next hiring manager is Megan McGuire.
175
:In this snippet, she's going to
walk us through what it's like
176
:to actually hire someone in the
data world from beginning to end.
177
:She'll talk about posting the job,
how many applicants she got, how many
178
:people The recruiter talked to how
many people she talked to as the hiring
179
:manager and kind of what the next
steps and how they ultimately hired
180
:someone who actually didn't have all
that traditional of a data background.
181
:Let's take a listen.
182
:Okay.
183
:So you write this job
description, you hand it over HR.
184
:They, they post it somewhere
on the internet somewhere and
185
:applications start to come in.
186
:So can you walk us through how
many applications, how long you,
187
:maybe you guys have the job open
and how many applications you got?
188
:Megan: Yeah, I think we had this
role listed for like a week.
189
:We didn't give it long, because we
got 285 applications within a week.
190
:Honestly, when I looked at them, and
I looked at every single one of them,
191
:like, looked at every resume, probably
about 70 percent of that applicant pool
192
:could have been successful in the role.
193
:Again, it's an entry level role.
194
:A lot of this is about what you're
able to learn and like what you've
195
:shown some promise in so far.
196
:So yeah, most of these people honestly
could have done pretty well in the role.
197
:So that makes it really
hard to narrow down.
198
:Honestly, when I hire a senior analyst,
that's a lot easier because I can go
199
:through and see that like, you don't
have the body of experience to support
200
:that you've done this for a long time.
201
:You don't have the portfolio.
202
:You don't have the projects.
203
:When I'm looking at a junior
analyst, I assume you're not
204
:going to have those things.
205
:So I have to parse out on a
lot more stringent criteria.
206
:So if you don't have experience in
the tech stack that I'm looking for,
207
:285 applicants, if only half of those
have experience with Tableau, which
208
:is what we use as our visualization
tool, I'm going to talk to the half
209
:with Tableau before I talk to the
other half with Power BI or Looker.
210
:You have to prioritize on these
things just because there's a
211
:lot of people coming through.
212
:So out of that 285, I think we
had 12 talk to our recruiter.
213
:That's our next stage is
we do our recruiter screen.
214
:I'm a big believer in the hiring process.
215
:Like I'm not going to ask you to
do a technical screen before we've
216
:put some time forward to you.
217
:We need to have that
sort of give and take.
218
:So you talk to our
recruiter at that stage.
219
:After that, we had.
220
:Five candidates exit because they
either didn't respond, or location,
221
:or salary requirements didn't line up.
222
:So then we had seven candidates
take our code assessment.
223
:We do a SQL test on CodeSignal
to review candidates skills.
224
:I really enjoy having something,
like, technically grounded, where I'm
225
:able to see the code you can write.
226
:It doesn't really work well to do, like,
a quick Tableau assessment, but SQL's
227
:such a core skill, and it's really easy
to test with a lot of SQL questions.
228
:We're doing some grouping.
229
:I think.
230
:There might be a window
function question on there.
231
:So at that stage, actually everybody
passed our SQL interview, but we
232
:did have one candidate accept a
different offer at that stage and exit.
233
:Yeah.
234
:Our average completion time
on that stage was 24 minutes.
235
:My goal is also to keep
that stage pretty short.
236
:I don't want to ask you
for like a six hour test.
237
:You're applying for lots of jobs,
especially at the entry level.
238
:I'm not trying to keep
you for many, many hours.
239
:The stage actually that we moved
to was my hiring manager interview.
240
:And in that stage, I'm asking usually
some more problem solving questions.
241
:So I'm going to ask you about something
in your portfolio, something that you've
242
:gone deep on, and ask you things like,
how would you expand that project?
243
:What else are you curious about
this project that you might've
244
:worked on in your portfolio?
245
:If you were rebuilding it, like, what
would you do differently this time?
246
:What other data would be
helpful for driving decisions?
247
:Those sorts of questions to dive deep.
248
:Again, like, I'm not asking you about
all of your experience in data analytics.
249
:I assume that you don't have that
applying for an entry level role.
250
:I talked to six in the higher edger
state and four of them went through.
251
:The biggest gap for the two candidates
who exited there, I think was like
252
:visualization and data exploration skills.
253
:So then we moved into the team
technical interview where I have two
254
:of the senior analysts on my team go
through much more technical questions.
255
:So in that stage, you're going to
see like, let's walk through your
256
:portfolio project and talk about like.
257
:How you build this in Tableau, you put
something on Tableau public, we're going
258
:to talk through the stages of building it.
259
:So they're going to be vetting your
technical skills with a lot more detail.
260
:This shouldn't be a scary stage.
261
:Just feel confident speaking to the
stages of not only how you did things,
262
:like we're not going to ask which
button did you push, but think about
263
:the methodology and why you chose
to build something a certain way.
264
:So like, if you chose to do
a calculation in SQL versus
265
:in a data visualization tool.
266
:Why did you do that?
267
:And how did you go
about figuring that out?
268
:Those are going to be the sorts
of questions to talk to there.
269
:Avery: Okay.
270
:Awesome.
271
:So then you're, you're analysts, you're
kind of doing this like team interview.
272
:Now let me ask you this.
273
:I mean, they've done this probably a few
times, maybe in their careers, right?
274
:Do you give them questions?
275
:Do they come up with their own questions?
276
:Megan: They come up with
their own questions.
277
:I talk to them primarily about the goals.
278
:This is very similar to my management
style in general is I want to
279
:talk to them about the goals.
280
:What are we trying to find out?
281
:To bring it all back into the data world,
interviewing is a form of getting data.
282
:This is a means of data collection.
283
:So I talk to them about like,
what do we want to learn about
284
:the candidates at this stage?
285
:And I will help them with writing
questions if they need it.
286
:But for the most part, I'm
telling them like, I want to learn
287
:about their technical skills.
288
:I want to learn about how they
go about solving problems.
289
:I want to learn about how
comfortable they feel in this system.
290
:And you should be able to
come back and tell me about.
291
:After that, that's
actually our last stage.
292
:So we do that technical interview and
then I'm reviewing all of the feedback.
293
:So our system.
294
:As we collect scorecards after
every interview, and then I have
295
:access to review all of them.
296
:So I can see something that's been
scored relatively objectively across
297
:every interview and every candidate
and sort of evaluate how that adds up.
298
:So that'll be scoring on
things like technical skills.
299
:How are your SQL skills?
300
:How are your Tableau skills?
301
:But it'll also include things like
problem solving and other soft skills.
302
:How are you as a communicator?
303
:And I can evaluate against all of that.
304
:In this case, I had two candidates
that I was sort of debating
305
:between in the final stage.
306
:And then I made the call on
who to extend an offer to.
307
:Really the differentiator for
the candidate who got the offer
308
:is we're an education company.
309
:We're here to help people upskill,
learn data analytics, was that she
310
:had prior experience in education.
311
:So all of her technical skills were great.
312
:Her communication skills were great.
313
:Her portfolio was great, but I had
multiple candidates who met all of that.
314
:So her differentiator was really
that education experience that
315
:was really helpful for us.
316
:It was something that set
her apart and made her like
317
:the perfect candidate for us.
318
:Avery: And I want to emphasize that here.
319
:I work with a lot of teachers who
want to get into data analytics
320
:and a lot of them are fearful.
321
:Hey, I don't have a technical background.
322
:I come from an unusual background,
but in this case, that non technical
323
:background, the unusual background
was actually kind of the superpower
324
:that got her the job or him the job.
325
:Megan: Yeah, like it's
super, super helpful.
326
:I can combine that portfolio,
combine all the things that you've
327
:learned about data analytics with
the other things that you know.
328
:Somebody out there is making
ed tech software that needs
329
:to be sold to teachers.
330
:Like you understand teaching, you
understand the education world.
331
:You can apply that knowledge to
data analytics in that setting.
332
:Be the perfect candidate for that
company rather than a pretty good
333
:candidate for a whole sea of companies.
334
:And the same could be applied again for
like, if you've got retail experience
335
:or customer service experience, you
might look at a customer service
336
:analytics role, which there are plenty.
337
:Take your prior experience in customer
service and apply that to analytics.
338
:I did it myself.
339
:Like that's how I got into
analytics was I studied healthcare
340
:in my undergraduate program.
341
:And I took an analytics role
at a healthcare company.
342
:So when you can sort of combine
those things, it makes a much
343
:more powerful profile, makes
you a much stronger candidate.
344
:Again, like you don't have
to be okay for everybody.
345
:Okay.
346
:For everybody will get you a lot of like
looks, but you'll get the offer more when
347
:you can find a way to make yourself like
just right for one company, those things.
348
:Avery: Okay.
349
:How awesome was that behind the scenes?
350
:I'm going to it's like to actually
hire someone in the data space.
351
:285 applicants just erased half of
them because they didn't know Tableau.
352
:That's why it's so important to
list all data skills pretty much
353
:on your resume and your LinkedIn.
354
:12 spoke to a recruiter and
out of those 12, only 7 made
355
:it to the next stage, which was
actually a SQL little coding test.
356
:Everyone pretty much
passed the coding test.
357
:One person got offered a
job and so dropped out.
358
:So six people talked to the
hiring manager, which was Megan
359
:in this case, kind of a behavioral
interview like you heard.
360
:Out of those six, she kicked two
out after that and finally had
361
:four interview with her team.
362
:The team was part of the process,
which I think is really neat.
363
:And it goes back to what Alex was
talking about earlier, how you
364
:really do need to mesh with the team.
365
:Well, out of those four, two of them
kind of stood out, but that couldn't
366
:really choose between the two.
367
:And the benefit of the doubt went to
the person whose domain experience,
368
:like their past experience that wasn't
data related would help the team.
369
:In this case, it was someone
with an education background, and
370
:this was an education company.
371
:And so that's who they ended
up hiring, which is awesome.
372
:And I think for you, you should
really be thinking about.
373
:You know, how can I use my
domain and my previous experience
374
:to help me land my next job?
375
:Hopefully your hiring manager is as
good and as kind as Megan, because I
376
:think she hired very well in this case.
377
:The next hiring manager we are
going to hear from is Jesse Morris.
378
:And I want you to pay attention to
what he thinks is most important
379
:in the hiring process, because once
again, I don't think you're going
380
:to be able to guess what it is.
381
:When you've hired some of those entry
level people, what stood out the most
382
:to you in those hiring processes?
383
:Jesse: Yeah, that's a great question.
384
:And I think, you know, if you take
anything from today's conversation,
385
:I think it's around this.
386
:And, you know, again,
I think it gets lost.
387
:You've got to be the most technical in the
room or, you know, your ability to build
388
:a dashboard and make it a work of art.
389
:You know, that's like the most important.
390
:I actually don't think that's the case.
391
:And I actually think, Avery, you and
I talked about this about, like, how
392
:a lot of teachers make great analysts.
393
:And I think there's a lot of truth
to that because ultimately when I
394
:think when it boils down to it Really?
395
:It's it's a couple of key things one
It's the ability to tell stories and be
396
:succinct and that is not that's not just
a data skill set That's a life skill set
397
:You know If you look actually my original
background is in sales like I actually
398
:I should say my second job My first
job was I was a data analyst and then
399
:I realized I needed to get presentation
skills and the ability to tell stories
400
:So I went into sales for a few years.
401
:And so I think, you know, that skillset,
the ability, but I think you can get
402
:that in a myriad of ways, you can
be a great writer, you can, there's,
403
:there's so many different ways you
can get that skillset, but I think
404
:that's such a big one, especially.
405
:You know, a lot of my time is spent
communicating to executives and
406
:to leadership teams and to boards.
407
:Like I spent a lot of time telling
stories to the board and that's really
408
:key is that ability to kind of boil
things down and to here's the most
409
:important and then you can work back.
410
:Ultimately, like people, when they get
curious about data, that's when they
411
:start asking kind of your next layer
of questions and you, you can make
412
:that, you can bring that curiosity
of the life through storytelling.
413
:The other one, which is
probably a little bit.
414
:Less common you want here, but this is
something that just continues to even
415
:today even with senior analysts It
doesn't matter what level of analysts
416
:you are but tenacity and mental
toughness Wow, so that's a really funny
417
:one I tenacity to me like in my world.
418
:I work in these smaller called
startup type Uh, technology companies.
419
:And so we're moving at really
fast pace, but we don't get
420
:weeks to work on projects.
421
:So if you work in any large corporate
companies, you're going to get that.
422
:And that's okay.
423
:I think ultimately it's good
to know, like, what are, what
424
:type of environment you're in?
425
:And so if you don't work necessarily
well under pressure and some of these
426
:things I'm about to talk about, that's
okay, then you're probably maybe better
427
:designed to work at larger companies
where you're given the freedom to like,
428
:sit down and work on things for weeks.
429
:The environment I work in,
we're not given that time.
430
:And so the ability to, you know,
change prioritization on a dime, to
431
:juggle nine different projects at once.
432
:If you talk to my data analyst
today, like this is the reality.
433
:Like we, this week, we came into the
week with a plan and by Monday afternoon,
434
:you know, it was Monday morning during
our standup and by Monday afternoon,
435
:that plan got halfway derailed, right?
436
:And so it's a reprioritization
game and that's not for everybody.
437
:I mean, I think ultimately.
438
:You know, that's a tough thing to wrap
your head around and not get frustrated.
439
:And, and I think you and I talked about
this before, but it's that like knowledge
440
:of, I understand what perfect looks like
or really phenomenal looks like, but
441
:I also understand what good enough is.
442
:And I think that skill set,
that's a really important one.
443
:And that's not like, you know, I'm going
to learn this by watching X, Y, and Z.
444
:I think that's something that you
actually have to work towards and
445
:build up that, that mental toughness.
446
:I actually think failure, you know,
it's easy to look at a resume and be
447
:like, Oh, all this stuff went great.
448
:I was a founder, you
know, at a tech company.
449
:Good for me.
450
:I also failed at that tech company.
451
:Right.
452
:I learned a lot of things through
trial and error and that I think
453
:it's the same for all of us.
454
:And so those would be some of the
things I think that really stand out
455
:to me when you boil it down to like
some of the key pieces behind it.
456
:It's an attitude, right?
457
:Like it's that willingness to say,
Hey, I messed up here and that's okay.
458
:Like, cool.
459
:What'd you learn from it?
460
:How do we make it better?
461
:How can I help?
462
:But I think, you know, those
are ultimately some of the, when
463
:you boil it down to some of the
things that I look for, no matter
464
:what stage you're at within it.
465
:And then I think.
466
:You know, on the specifically on the
starting out analyst in particular, you
467
:know, I think just a, again, perspective
is an interesting one, but did you have
468
:a sales background or did you work for,
I mean, maybe you're working in retail.
469
:Did you work for Banana Republic
during college where you were
470
:like, all of those things,
perspective and data is everything.
471
:And what I mean by that is like your
ability to speak into it from the
472
:person who's asking the question
or the departments or the leaders
473
:that are asking the questions.
474
:Right.
475
:Because as long as you've got just
that various perspective, that
476
:actually has a lot more value.
477
:I think sometimes the technical even does.
478
:Avery: Yeah.
479
:And I hope people just heard what
you said, because I think that's
480
:very impactful, you know, just
to kind of rehash them a bit.
481
:It's not necessarily how technical
you are that lands you the job.
482
:Because I think you said this
phrase when we first originally
483
:talked that the technical stuff.
484
:It's kind of expected.
485
:That's like you, you have
it or you kind of don't.
486
:Right.
487
:And it's really your storytelling,
your grit, your attitude that separates
488
:you, which I think for all of you
guys listening who want to be aspiring
489
:data analysts, that should be really
rewarding because you can have grit.
490
:You can be, you know,
you can be authentic.
491
:You can try hard.
492
:You can have passion.
493
:You can become a good,
you know, storyteller.
494
:Those aren't like necessary, like you
have to be spending 25 years of your life
495
:in SQL to know how to master everything.
496
:Right.
497
:That's really, in my opinion, enlightening
and refreshing to hear because it can be
498
:like, I think most people take the data
career job hunt way too skill heavy.
499
:Of course, skills are important.
500
:Right.
501
:But like, they're not everything.
502
:And I think you kind of just said that
basically, they're not everything.
503
:All right.
504
:Hopefully you're catching
the drift at this point.
505
:It was a pretty similar theme
here that your technical skills,
506
:of course, they're important.
507
:It's the bare minimum.
508
:It's actually things like your
storytelling, the ability to be
509
:succinct that sets you apart.
510
:And that's something you're
probably thinking, Avery,
511
:you're not very good at that.
512
:I've listened to your podcast episodes.
513
:I've watched your YouTube videos
and you're not very succinct.
514
:And it's true.
515
:It's something I'm still working on.
516
:And I think it's a lifelong journey, but
once again, this is like Jesse said, a
517
:life skill, not necessarily a data skill.
518
:And so that's something that we can
practice and we can get better at.
519
:And no matter how technical
or how non technical you are.
520
:It's something that you can
improve on every day and work at.
521
:Jesse also brought up tenacity
and mental toughness, and this
522
:is something that we can all do.
523
:One thing that I do is I actually
take ice cold showers and baths to
524
:try to increase my mental toughness.
525
:Kind of weird, but it works for me.
526
:The last hiring manager we are
going to hear from is Andrew Madsen.
527
:I want you to pay attention to what
he says because he kind of repeats
528
:what has already been said, but he
adds one really important point.
529
:Part, uh, that the other ones
haven't talked about as much,
530
:and that is projects, which is
the P part of the SBN method.
531
:Let's take a listen.
532
:I wanted you to walk us through the
idea of when you're hiring a data
533
:analyst, you know, what's really
important to stand out as a candidate.
534
:What can these listeners do to To stand
out and the data analyst job search.
535
:Andrew: Yeah.
536
:My thoughts on this
have evolved over time.
537
:So the data analyst position has
just grown and grown and grown as
538
:our needs for quality data analysts
have really permeated every industry.
539
:So there's a lot of opportunity
there before when I was new at
540
:hiring data analysts and I was
new into data myself, I really was
541
:focused on the technical skills.
542
:I was looking at whatever my stack was,
like we use Tableau, whatever it is.
543
:And I was looking for applicants
who match that data stack.
544
:That's how I began looking for applicants.
545
:Now what I look for if I was hiring a data
analyst, I focus much more on the person.
546
:I look for somebody who's curious.
547
:I look for somebody who's resilient.
548
:I look for somebody who's going
to mesh well with the team because
549
:data analytics is a team sport.
550
:You know, one person who just isn't
a team player can really throw off
551
:the whole dynamic and ultimately
the work and the business insights
552
:that we're trying to drive.
553
:So less important to me is your
specific technical skill set.
554
:You know, if you know Tableau
really well and we're using Power
555
:BI, that's totally fine with me.
556
:But you're demonstrating
that ability to learn.
557
:And some of the ways that you
can do that, like Avery always
558
:talks about, are projects.
559
:I love to look at projects.
560
:I love to see interesting projects.
561
:We've all seen the Titanic dataset,
and I don't mind if you use that, but
562
:I want to see something that you're
interested and passionate about, and
563
:I want to learn about that with you.
564
:And then if we're interviewing, I
really want you to tell that story,
565
:because the ability to communicate
as a data analyst is so important.
566
:You know, I don't want to have
to go to the stakeholders and
567
:explain what you were doing.
568
:I want you to go and represent
yourself and present your insights
569
:and build those relationships.
570
:So if you can have something you're
passionate about, you uncovered some
571
:insights and you can communicate those in
a story and a narrative that's engaging.
572
:Those are so important.
573
:Those will really set you apart.
574
:Avery: Okay.
575
:That's awesome.
576
:A lot to unpack there.
577
:I think we, as data analysts,
candidates often over index.
578
:On how much, you know, the
technical skills matter and
579
:the technical skills do matter.
580
:There's people who are willing
to take a chance on you and you
581
:have to show them that you're more
than just, you know, some NPC.
582
:I don't even know what that
even, what that means right now.
583
:What does that mean?
584
:A non role playing, I don't even know
what it means, but it's like a non player
585
:Andrew: character.
586
:Yeah.
587
:Avery: Non player character.
588
:You have to show some sort of passion,
some sort of personality, some sort of
589
:drive, some sort of like, And that can
be even your grit, your communication,
590
:you know, what you like about projects.
591
:And it's just interesting that we've
had a couple of different data hiring
592
:managers on the podcast now, and they've
all let off with a very similar message.
593
:There you have it, folks, advice
straight from hiring managers on
594
:how to land your next day at a job.
595
:If you want even more On how to
land a data job, I highly suggest
596
:checking out my newsletter.
597
:Every week I send you a tip that helps you
take the next step in your data career.
598
:You can subscribe at datacareerjumpstart.
599
:com or in the show notes down below.
600
:And if you want even more help on
your data journey, consider joining
601
:the data analytics accelerator,
which is my ten week bootcamp to
602
:help you land your first data job.
603
:You can find that link in
the show notes down below.