Shownotes
Help us become the #1 Data Podcast by leaving a rating & review! We are 67 reviews away!
There's a lot of advice online on breaking into data. Here's what I'd tell a beginner.
💌 Join 30k+ aspiring data analysts & get my tips in your inbox weekly 👉 https://datacareerjumpstart.com/newsletter
🆘 Feeling stuck in your data journey? Come to my next free "How to Land Your First Data Job" training 👉 https://datacareerjumpstart.com/training
👩💻 Want to land a data job in less than 90 days? 👉 https://datacareerjumpstart.com/daa
👔 Ace The Interview with Confidence 👉 https://datacareerjumpstart.com/interviewsimulator
⌚ TIMESTAMPS
00:00 – The Reddit post
01:09 – Companies interested in you
04:12 – Analysis is about money
07:00 – Bad tool advice
09:42 – My advice
🔗 CONNECT WITH AVERY
🎵 TikTok
💻 Website
Mentioned in this episode:
🔍 Find Your Next Data Job at FindADataJob.com
This episode is brought to you by FindADataJob.com — the #1 job board for aspiring data analysts. It's my own job board, where we post dozens of new data analyst roles every single day. Every listing comes with the stuff other boards leave out: salary reports, skill reports, and a seniority score, so you know exactly what you're applying to before you hit submit. Stop scrolling through a hundred irrelevant postings and go find your next data job faster at FindADataJob.com.
Transcripts
The data analyst role is changing,
and it can be a little bit scary,
2
:especially if you're thinking about
someone breaking into the field.
3
:It honestly feels pretty daunting
and honestly probably impossible.
4
:But it's not impossible, and in
today's episode, I wanna break down
5
:what people are saying online, what
people are saying on Reddit on how
6
:the data analyst role is changing
and what you should do because of it.
7
:So recently on the subreddit
DataAnalyticsCareers, someone posted this,
8
:and I want to actually react and see if
this person's giving sound advice or not.
9
:So let's go ahead and get into it
10
:So the first thing that they say is
to start top-down, not bottom-up.
11
:Most people start with tools.
12
:They open up a SQL course,
memorize syntax, and then
13
:wonder what to do with it.
14
:That is backwards.
15
:Before you learn a single tool, research
requirements and responsibilities
16
:of data analyst positions in
companies you want to work at.
17
:List the skills they ask for, list
the responsibilities, and then try to
18
:understand what the job is actually for.
19
:Ask yourself which industries
actually industry interest me,
20
:what does a day-to-day look like in
the companies that I am targeting?
21
:What problems does the analyst
solve for the business?
22
:What is the goal of the role?
23
:This will give you a global
view and the idea about the job.
24
:This is more for the private sector
companies, but in the public sector,
25
:some things will still be applicable.
26
:Okay.
27
:I totally agree with the idea of we're
not doing data analytics to analyze data,
28
:and you shouldn't just learn data skills
and data tools to learn data tools.
29
:Like, they should always be used to solve
business problems in some sort of a way.
30
:So we don't wanna just like
memorize syntax, we don't
31
:wanna just write SQL queries.
32
:We're always writing SQL queries
to solve business problems.
33
:And the quicker you get that
in your mind, the better.
34
:So I agree with that.
35
:I do think it is a little interesting
here that they're saying, "Hey,
36
:go look at the companies you're
actually interested in, and list…
37
:look at what skills they're requiring."
38
:And I think that's important to like
actually look at job descriptions
39
:and see what is actually being in
demand, 'cause you might think, "Oh,
40
:Python's really important to learn."
41
:Guys, it's really not.
42
:Uh, like I think it's only like 80% of
data analyst jobs don't require Python.
43
:So if you're gonna spend so much time
learning Python for only apply for those
44
:20% of the jobs, it might not be worth it,
and that's my, you know, my take on it.
45
:I've done a bunch of episodes
in the past about what skills
46
:you should actually learn.
47
:You know, you can go to finddatajob.com
48
:and click on our s- uh, skills
report to actually see what
49
:skills are in demand right now.
50
:But I think that's important to do,
but I wouldn't necessarily just do it
51
:for the companies you're interested in,
because that might change over time,
52
:and also it's like a small subset.
53
:Like let's say you really wanna
work at Meta, and their data
54
:analysts might use Python.
55
:I don't know.
56
:If you're really set on working for Meta
or a certain company, that makes sense.
57
:But if you're open to like working
for any company really, like I
58
:think instead of just looking at a
few companies you're interested in,
59
:you should look at the aggregate.
60
:And so I think that's why our, um,
skills report at finddatajob.com
61
:is really useful, 'cause that's like on
average what skills should you actually
62
:learn, and the answer is Excel, SQL, and
one BI tool like Power BI or Tableau.
63
:That's basically the, the short
answer, but you can go check it out,
64
:the long answer, on our website.
65
:Also, like what industries actually
interest me, I think that's one way
66
:to look at it, but also I would say
what industries are interested in me.
67
:Because it's like a lot of us, I mean
not a lot of us, but me for example,
68
:and I know I've talked to a lot of you
guys, are interested in sports analytics.
69
:Like, "Oh, I love sports.
70
:It'd be so fun to be, you know, one
of these analytics guys for the NBA or
71
:for the NFL or something like that."
72
:And that would, would be fun, but the
truth is, those positions are so rare
73
:and they're so in demand that they're
impossible to land, and they don't pay
74
:particularly well most of the time.
75
:So it's like, yes, you would be interested
in those jobs, but it's probably better
76
:to reverse it and think, "Well, what
industries would be interested in me?"
77
:And usually it's what
industry you're coming from.
78
:Like what's your domain and what's
your degree, and those types of things.
79
:So when I was a chemical lab technician,
it's like, oh yeah, I could have
80
:tried to land a sports analytics
jobs and that would've been great.
81
:You know, maybe their job description say
you have to learn R, and I would've spent
82
:all this time learning R, but the truth is
they would probably never be interested in
83
:me, and so I just wasted a bunch of time.
84
:And so I think it's actually better to
reverse this and start with the, you know,
85
:what companies and what industries are
interested in me, and then try to focus
86
:on that, unless you're really set on,
like, a specific j- company or industry.
87
:But I think most of us
aren't really that case.
88
:Also, this is more true for the private
sectors versus the public sector.
89
:I don't know what they're saying there.
90
:Like, I don't feel like there's that
big of a difference between the two.
91
:Uh, like they both post jobs online.
92
:Like, I don't get why making the company
public or private, that actually changes.
93
:But I don't know.
94
:So overall, I'd give this b-
advice maybe like a B plus.
95
:I think for the most part it was
right on, but there were some small
96
:things I would make some changes on.
97
:Let's move on to their next paragraph.
98
:"Learn how businesses make money before
you learn how to query a database.
99
:This is the whole thing nobody teaches,
and it is the thing that separates
100
:analysts who get promoted from analysts
who stay stuck executing requests."
101
:We have that classic AI line right
there, right, with the double dash.
102
:I forget…
103
:Em dash is what that's called.
104
:Also, I thought this was for people
who are pivoting in and not for
105
:people who are getting promoted.
106
:But okay, I'm gonna…
107
:I'm getting distracted here.
108
:"Every business runs on the
same fundamental loop: attract
109
:customers, convert them, deliver
value, retain them, grow revenue.
110
:The department you work for
determines which part of the loop
111
:you spend most of your time on.
112
:Your analysis will always serve
one or many of these stages.
113
:Once you understand that, you
can think about data as numbers.
114
:You can stop thinking about data
as numbers and start thinking
115
:about as evidence for decisions."
116
:I do like that line.
117
:That is a great line.
118
:"Four questions to ask
before any piece of analysis.
119
:What is the business
actually trying to achieve?
120
:The real goal, not the metric.
121
:Who will use the analysis?
122
:A CEO and product manager need completely
different things from the same data.
123
:What decision does this
analysis need to support?
124
:Analysis without a decision
attached is just exploration.
125
:What action will they take
after seeing these numbers?
126
:If the answer cannot change anything,
the question is not worth asking.
127
:Build this thinking into every project
from day one, and you'll be ahead of
128
:most junior analysts within six months."
129
:I think this is pretty solid advice,
especially those four questions that they
130
:listed there, like what are we actually
trying to solve with this analysis?
131
:Who is this analysis for?
132
:How much level of detail do
we need to have in there?
133
:I think that makes a lot of sense,
and he or she is right that the
134
:quicker you understand that,
the better analyst you will be.
135
:I think trying to study how businesses
make money is an interesting concept.
136
:I don't necessarily think every
business runs on the same fundamental
137
:loop of attract customers, convert
them, deliver value, retain them, grow
138
:revenue, or at least those stages are
very convoluted, and I think that's an
139
:oversimplification of how businesses work.
140
:Like, yeah, like for instance, if
you do like a D2C, direct to consumer
141
:brand, and like I'm selling, you know,
water bottles, like that makes sense.
142
:But like I've worked for companies who
don't care about growing their revenue.
143
:They just want to be acquired someday,
and that's how they're going to make
144
:money is eventually via an acquisition.
145
:And so they're not concerned
even about revenue.
146
:Like that, that's a real thing,
and that's, you know, there's
147
:lots of companies like that.
148
:Also, like I worked for ExxonMobil, like
one of the biggest oil, uh, producers or
149
:gasoline producers in the world, and In
terms of like, you know, this method that
150
:they're talking about here, I don't know.
151
:I was so far away from that.
152
:Like, I was in research and development.
153
:Like, I guess research and development
maybe would be like in deliver
154
:value stage, but I think this is an
oversimplification of how business works.
155
:But it is important to remember
that we're only doing analytics
156
:to help the business usually make
money, and I hate to say that.
157
:Like, it could be to save lives, it could
be to help people improve their lives,
158
:but most of the time it is to make money.
159
:And so you always need to tie your
analysis back to a dollar bill.
160
:That's really important, and the
quicker you figure that out, the better.
161
:So if you're trying to land a data job
and, you know, you're unable to tie
162
:what you've done historically to dollar
bills, that is difficult to perform well.
163
:So the quicker you can kind of
bridge that gap, the better.
164
:Moving on to point number
three: learn tools to answer
165
:questions, not to memorize syntax.
166
:Once you understand the business
context and the types of questions
167
:you'll be asked, tools become obvious.
168
:I don't think there's any way for you
guys to be able to predict what, what
169
:questions you'll be asked, unless,
unless from the job description.
170
:Sometimes from a job description, you
can actually pull out what type of
171
:questions you would be asked, but I
would say that every job description and
172
:every role is so unique that, like, you
can't just b- be like, "Oh, these are
173
:the type of questions I'll be asked,"
you know, different types of roles.
174
:Like, it's so different
every place you go.
175
:That being said, like, there
are some analyses that are very
176
:common depending on where you go.
177
:So like, for example, if you're gonna
work for Google or you're gonna work for
178
:Amazon or you're gonna work for Meta, like
one of the things they're always thinking
179
:about is AB testing or hypothesis testing.
180
:Like, if we change this on our
website, do we get better results?
181
:Yes or no?
182
:If you work for one of those
companies, you will probably face
183
:some sort of question like that.
184
:So there are some generic questions
like that, but every other role
185
:I've worked at has been so unique.
186
:It's kind of hard to predict
just off of a job description.
187
:Okay, you learn SQL because you
need to query customer data.
188
:You learn Python because you need to
clean a dataset or automate a report.
189
:Uh, okay, this is dumb.
190
:Like, no.
191
:I could clean a dataset and create
an automated report in Excel.
192
:I could cr- clean a
dataset and do it in SQL.
193
:Like, okay, I don't think
that's sound advice.
194
:Like, you learn Power BI because a
stakeholder needs to interact with
195
:a trend, not just read a table.
196
:Once again, I could do that
in Python, so I don't know.
197
:"Learning a tool without a question
to answer is why most people plateau.
198
:The syntax does not stick because
there is nothing to attach to it."
199
:I don't know, that sounded
like an AI-generated sentence.
200
:"Use AI and Kaggle to find datasets
that match your target industry."
201
:I like that advice.
202
:It's always good to find unique datasets.
203
:"Build projects around
real business questions."
204
:I like that advice.
205
:"What is driving churn in a subscription
business is a better starting place
206
:than let me practice SQL joins."
207
:That is probably true.
208
:Like, I think that is sound advice
that, like, if you can actually do
209
:real-world projects with real-world
data, that's, that's better than just
210
:doing pointless exercises online.
211
:That's one of the reasons we created
the accelerator, and we do the
212
:different projects that we do with
real-world datasets to kind of get
213
:you in the habit of doing this.
214
:All right, next point here.
215
:"Talk to people already doing the job.
216
:There is more useful information in
one honest conversation with a working
217
:analyst than in 10 hours of tutorials."
218
:Eh, debatable.
219
:"Threads, LinkedIn, Reddit, you
will find those willing to help
220
:you if you ask a specific question
rather than a generic one."
221
:I mean, that is true.
222
:Like, the more specific
you can ask, the better.
223
:Like, the more specific
advice you're going to get.
224
:Like, the more context you
give someone, the better.
225
:I can't tell you how many, like,
"How should I break into data?"
226
:questions I get, and it's
like, "Okay, well, who are you?
227
:What do you do?
228
:What do you want to do?"
229
:and those types of things.
230
:So the more specific you are, the better.
231
:"Prepare in advance, though."
232
:And, uh, that's the whole post, and that
got 500 upvotes on, uh, this subreddit.
233
:I mean, I think it's sound advice,
but it's not really even that amazing.
234
:It's like, okay, you need to
make sure that you're tying
235
:your analysis to dollar bills.
236
:Okay, I agree.
237
:And do real-world projects
with real-world data.
238
:I mean, that's sound advice.
239
:Like, you can't go wrong with that advice.
240
:But what does that actually mean to you
guys who are trying to land a data job?
241
:Like, you guys aren't
even in the role yet.
242
:Like, how is this
actually going to change?
243
:And one important thing I think
this person's really missing out on
244
:is why this is actually changing,
and the truth is it's 'cause of AI.
245
:AI is changing so many different
things, the way we analyze data,
246
:the way we interact with data.
247
:And I still think it's really important
to learn the fundamentals first because
248
:otherwise I think it's going to haunt you
down the road where you can't actually
249
:fix things on your own if AI gets
really expensive, or you can't actually
250
:catch, like, any errors that AI makes,
'cause AI does make errors all the time.
251
:So I think it's first important to
learn the fundamentals of the business
252
:and actually, you know, like, okay,
how does this business operate?
253
:How does data support business?
254
:That's great.
255
:Then make sure you know the fundamentals
of data, like columns, rows, how we
256
:actually analyze data, when to use
a line chart versus a bar chart, why
257
:we don't really like pie charts in
the data visualization community.
258
:The basics of all things
data fundamentals.
259
:And then I think it's really important
on top of that to learn how to do things
260
:in AI, because I do think the future is
very AI-focused, and that's one of the
261
:things that I'm trying to talk a lot about
on this episode and on this platform.
262
:So if you guys want to learn
more, I try to talk about AI every
263
:single week in my newsletter.
264
:You can go to
datacareerjumpstart.com/newsletter
265
:and subscribe for absolutely free.
