π Follow this roadmap w/ The Data Analytics Accelerator (My Bootcamp): https://datacareerjumpstart.com/daa
β TIMESTAMPS
00:19 - Step 1: Skills
02:33 - Step 2: Data Roles
06:38 - Step 3: Projects
10:22 - Step 4: Portfolio
13:20 - Step 5: Resume & LinkedIn
17:59 - Step 6: Job Hunting
21:12 - Step 7: Interviews
22:53 - The SPN Method
π Join 30k+ 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
Here's exactly how I would become a data analyst if I had to start all over again in 2026. Now I'm low key, pretty lazy, and I'm also very impatient. So I'd want to choose the fastest roadmap with the least amount of work required to actually land a data job. That roadmap is called the SPN method, but it still has a lot of work. Step one, I'd wanna figure out exactly what skills are required because there's literally. Thousands of different data tools and skills that you could possibly be learning. And if you're gonna master them all, it's gonna take you so long. It's gonna take you decades before you even feel close to ready. Once again, remember, I'm very lazy and I'm very impatient. So I want to learn the bare minimum of skills required to land my first data job. So which skills and what tools would I focus on? Ideally, I choose the skills that have the biggest bang for your buck, the lowest hanging fruit. So basically what that means are the ones that are used the most in industry. But also the ones that are the easiest to learn, so I can learn them quickly. That way I could have employable in-demand skills really, really, really fast. Uh, so what are those skills? You're probably wondering, well, you can do the research for yourself by going through like hundreds, thousands of different job descriptions and keeping tallies and track of what data tools are mentioned the most often. But obviously that's gonna be a lot of work. The good news is I already did all that research and work for you, so here you go. The most in demand tools that are also pretty easy to learn are Excel. Tableau sql. Literally, that's it in that order. These are the top three data skills that you should be learning when you're just starting out in data analytics. And if you need any help remembering that I came up with something called a pneumonic, I think is what it's called to make it kind of easy. It's every turtle swims. E for Excel, T four Tableau and S four sql. And that's where I'd personally start. If I had to start all over, I wouldn't really study anything else until after landing that first data job. Now I can hear everyone in the comments already. Well, what about Python and what about Power bi? And here's the truth, I love Python. It's literally my favorite data tool. But honestly, there is a little bit of a steep learning curve, and it's only required in like. 13% of data analyst jobs. It just takes so freaking long to learn. And remember, I'm not trying to be in this job hunting mode forever. I'm trying to land a data job quickly. So learning Python, it's gonna take a freaking long time. And to me, it's just not worth the time investment at the beginning because it's not the most in demand skill and it's not the easiest. So it makes sense for me to leave it till later, and at that point I can probably learn it. On the job, so I'm gonna be getting paid to learn and I'm all about that, so sign me up for that. In fact, I did a video in the past about how to get paid to learn stuff in data analytics. You can check that out right there. Step two, I'd wanna make sure I understand all the different data jobs available. Obviously there's data analyst and that is a great place to start. In fact, I think it's the best place to start, but there's actually so many more jobs than just. That they all have slightly different names and slightly different responsibilities, but a lot of the times they're doing pretty similar stuff to what you'd be doing as a data analyst. So the first two I wanna talk about are data scientists and data engineer. If you're just getting started, I would not try to get those jobs because it is hard to land those roles. It requires a lot of programming knowledge and math knowledge land, those roles. And I just think they're really hard to land. So instead, I'd focus on things like data analyst, financial analyst, healthcare analyst, marketing analyst. Almost anything that has the word analyst in it, or that might have the word data in it, I would at least consider. Now, there's so many different jobs here and I can't possibly tell you every single one, but let's just start with the big one. So financial analyst and business analysts are two of the most common analyst roles I've been seeing on job boards quite a bit. In fact, I run my own data job board. We'll talk about it here in a second, but on that job board. Financial analyst and business analyst roles are pretty much more common than data analyst roles. The financial analyst roles you're going to be dealing with, like p and ls, a little bit more profit and loss statements, uh, a little bit like more kind of data plus accounting, e uh, a little bit about forecasting and just like how much cash you have on hand. A business analyst role, that's like half business, half data analyst kind of meet in the middle, so their jobs can be quite varied, um, in what they're actually doing. But a lot of the times they're just like. Approaching business problems with like Excel or with Tableau or with SQL or something like that. The next most common one is healthcare analyst, and it is kind of self-evident, but basically you're doing data analytics with healthcare data. A lot of the times you'd think that this is like looking at medical charts and. Different medicines and procedures and stuff like that. But honestly, unfortunately, a lot of the healthcare analyst roles are more about the operations of healthcare, like appointments and billing, uh, and scheduling and stuff like that. There's a huge demand for healthcare analyst roles, and I don't see that demand going away anytime soon. So this is a great role, especially if you have healthcare experience in the past, if you've worked maybe as a nurse or some sort of. Medical tech, this could be a great fit for you. Marketing analyst, once again, very self-evident in the name, but basically you're doing data analytics on marketing data. If you've ever worked as a marketer, if you know anything about ads, if you know anything about social media or like website analytics, this is a great place to. For you to start now. There's so many more jobs I can't even talk about right now in this video. So here's a big list on the screen right here, and if you're listening to the audio version, I'll have a link in the show notes down below. But there's so many different data jobs you guys. So pause this video, take a screenshot of this, and start looking for these jobs. The reason you wanna start looking for these roles instead of data analyst roles is one less people know about these roles, so they're going to have less applicants. And two, a lot of the time. Your domain experience is going to be very valuable for these roles. So for example, if you've been an accountant before, a financial analyst role is a really good fit for you because you already have that accounting experience. So when you go to apply to financial analyst jobs, they can look at your resume and be like, oh, this person's already been an accountant. They're gonna understand this data set better than most. And that's something that I'd have to take in as well. So in my previous life, I was a chemical lab technician, so I'd be probably looking for data jobs that maybe have to do with laboratory data or companies that deal with some sort of chemicals. Now there's also a bunch of like these in-between jobs that are like half data jobs, half domain jobs, um, and they're a little bit more entry level. They require less skills. Maybe they only require Excel, for example. You've probably never heard of these jobs and that's totally okay. I made a whole separate video, so you can watch that on YouTube right here, or we'll have a link to it and the show notes down below. And that will basically explain these roles that are a little bit more entry level than even a data analyst role. They don't pay as well as data analyst role, but you could probably land them today if you know Excel. So once again, check that out. And honestly, if I had to start all over again, I might go for one of these roles first because when I was a chemical lab technician, I was making like $15 an hour, and these roles are like closer to $25 an hour. So I might wanna start with one of these roles, get the word data on my resume, and then start applying for data analyst jobs after I get data on my resume. Step three is I need to figure out a way to convince a hiring manager to actually hire me. Why would anyone wanna hire me? I'm a chemical lab technician. I've never been a data analyst. I don't have very many data skills, like why on earth would someone hire me? Um, and you've maybe felt this way before. I call it the circle of doom. It's basically like I can't get data experience because I can't get a data job because. I can't get data experience. And so this never ending cycle of doom where it's like, how the heck am I ever supposed to get a job when I don't have experience, but I can't get experience? 'cause no one's gonna gimme a job. And honestly, it's the absolute worst. If you're in the circle of doom right now, let me know in the comments and I'm so sorry. That is not a fun place to be. But here's the truth, is you could actually create your own experience and you do that by building projects. Now a project is basically. A real world life example of you analyzing data. It's almost like you have some sort of proof that like, hey, not only does my resume say that I can do Excel, that I can analyze data in sql, that I can make a Tableau dashboard, but here's some tangible proof via project that I can. And it's one thing to know the skills. It's another thing to show that you know the skills. And those are different things. So think about it, if I'm like interviewing with a hiring manager and I'm. Tell the hiring manager, Hey, yeah, I know sql, I've been learning sql. They're gonna be like, well, can you prove it to me? Right? And if I can have a project where like, I'm like, yes, I can look it. Here's some healthcare data that I analyzed. You know, here's some financial transactions that I analyzed. Here's some manufacturing sensor data that I actually analyzed, and I created this dashboard for you in Tableau. See how powerful that is. All of a sudden, the hiring manager is like on the defense at the beginning, like, I don't know if this person actually can do what we need them to do. Two, oh my gosh, this person already has done what I need them to do. Here's the evidence. I like this person. I mean, it's hard to do, but put yourself in the hiring manager's shoes. Let's say that you were a hiring manager. For like the next Fast and the Furious movie that's coming out and you need to hire a stunt double. Let's say you get two applicants. Applicant, a, you know, on their resume it says that they can jump over a car. Great. Uh, applicant B'S resume also says they can jump over a car. Fantastic, but they also send a video of them jumping over a car. Who are you more likely to hire? Uh, option A or option. It's option B, right? Why? Think about it for a second, because they gave evidence that they can do what the job description says. They took the risk out of it because now that I'm on the other side of, I hire people, right? I'm a hiring manager now and I hired some wrong people this year and it has bit me in the butt. It has cost me honestly thousands of dollars, uh, because I didn't hire correctly. And so when you are, you know, trying to convince a hiring manager that you are the right person, if you can lower that risk with projects. All of a sudden you're breaking the circle of doom. You have experience and you're letting the hiring manager know in a undeniable way, Hey, I've got this. Don't worry about me. So I would need to start building projects. And if I didn't know where to go or how to start building projects, you always gotta start with a dataset and you gotta find a dataset somewhere online. So one of the best places you can find data sets, well, there's a bunch of different options. I actually did a whole nother video about it right here, you can find in the show notes. Um, but the short answer is Kaggle. Kaggle is a great place to find, uh, a data set like. 90% of the time, and usually that's like good enough. So that's where I'd start. And then in terms of like what to do in the project, first pick, should you do it in Excel? Should you do it in sql? Should you do it in Tableau? Uh, just pick whatever one you're maybe the best at, and then start to answer some business questions about the data set. Think about how many, what's the max, what's the average? What's the relationship between these two columns? What happens over time? Those are some of the questions that you can ask at the beginning, and you can just answer maybe two or three or four of 'em, and all of a sudden you have a project. You have evidence, all of a sudden you have experience. And I would be qualified, or at least I would be able to talk to a hiring manager with like some sort of defense like, no, I am good. You should hire me. So I need to build projects. Step four, I would need to create a home for these projects, right? Because if you do these projects. But they're not tangible, then. They're not tangible. And how are you gonna convince the hiring manager that you're the person, right? So if your project is just in your head, it doesn't really count. If it's just on your desktop, it doesn't really count. That doesn't do you any good. You need this to be public. You need this to be easily shareable. You need this to look good and look pretty and make yourself look good, right? This is really key to have a portfolio. So a portfolio is basically a home. For your projects, and you'll want to have maybe one to, I don't know, 10 different projects that that's a big order. It depends on the, the quality of your projects. One really, really, really good project could be better than like seven mediocre projects. It really just depends. So where should you build your portfolio? There's a couple different options. And I teach all these different options inside of my program, the data Analytics accelerator, and I actually give them templates to just do this really easily. Probably the most common place to have a portfolio is GitHub. Uh, but I don't like GitHub as a portfolio for data analysts. Um, I can hear you guys in the comments. Oh, GitHub's awesome for data scientists and data engineers and programmers. Yeah, I get it. Okay. But a lot of you guys at the beginning. You're not gonna be writing code. GitHub is literally meant for code. Now you can kind of reverse engineer, hack it and make it for anything, and it, it could work as a good portfolio, but it's really hard to navigate and it's really hard to look good inside of GitHub. Just trust me on this and try one of these other things instead. I really like to use LinkedIn. LinkedIn. That's a great place where recruiters are right? Like it's like 97% of recruiters are actively using LinkedIn every single day. So why not be where they are? Right? Because those are the people that can change your life. Those are the people that can all of a sudden reach out to you and offer you a job. So I like using LinkedIn. There's a featured section on there. There's a project section on there. We like to use LinkedIn articles too, to make these projects go. And that's what I suggest. That's one of the things I teach inside of my bootcamp. The next thing I also do inside the bootcamp is card dot, uh, co. I think. I'll, I'll put a link, uh, right here and in the show notes down below. But basically it's just a website builder, a simple website builder. Um, I think it costs like nine to $20 a year and it's so worth it. You guys, your portfolio looks, looks so good and you can build it pretty quickly. So, uh, our students inside of our bootcamp actually just get. This template from us right here, that they can literally just fill in the blanks with their information so it doesn't take them like the, I don't know, couple hours that it might take you to set up. But, uh, I really like card. I really like LinkedIn. You could do it on Medium, you could do it on any sort of Squarespace or Wix or other website builder. Also, if you like GitHub, there is an alternative called GitHub pages. GitHub realize, Hey, people are using this as a portfolio. We're not really built to be a portfolio, so let's build a like separate product that makes portfolios really well, and that's called GitHub pages. And I really recommend that it's just a little bit of a steep learning curve if you're not really. Knowing about GitHub or you don't know about markdown, markdowns kind of like a programming language. It's kind of not, but uh, regardless it's a little bit more technical, so I'd wanna make sure I have a portfolio. Ideally in LinkedIn or card step five, I'd need to make sure that my resume and LinkedIn are working for me. And these are really the only two tools you get when you're trying to land a data job and you need to invest in them. They need to be like little mini. Employees running around working for you. Okay. And let me talk about what I mean by that. Number one, when you're applying for jobs, your resume either is going to pass what's called the a TS, the applicant tracking system, or it's not every time, it does not pass the a TS. There's kind of two scenarios. One, your resume couldn't really be read very well, and it's not. A TS compliant, meaning there's some formatting issues on it, or two, you didn't fit what the job description or the a TS was looking for. Number one, you wanna just make sure that you have a really good a TS friendly resume. We give our students all a bunch of templates that they can choose from, but the key here is basically no pictures, one column, no tables, and make sure it's like pretty simple, like don't try to do too much with your resume. Next, these ATSs, they're honestly not very smart. Even with ai, they're kind of dumb. Basically what they're looking for is they're looking at your resume and they're looking at the job description, and they're trying to figure out if you're a match or not. Now, what would make you a match? Think about it. Whatever's on the job description should match your resume, and so if you're applying for a data analyst role. Well, I'm sorry. You live in a world where they want to hire someone with experience. There is no non-zero experience jobs anymore. The lucky thing is we talked about earlier how to create experience. So if you're applying for data analyst jobs and you don't have the term data analyst. On your resume anywhere, you're probably not gonna pass the a s, so you can kind of hack the system here. You can put it next to your name at the top of your resume. You can put it in like your objective statement at the top and or you can put it in your experience section and have a data analyst job. That could be one that it's just you making projects on your own. You could hire yourself, start your own company. All of a sudden you're doing data, freelance, data analytics, just you need to have the word data analyst, or whatever role you're trying to apply for financial analysts, marketing analysts, business intelligence engineer. You need to have that somewhere on your resume. And if you don't, you're not likely to get called back. So I'd wanna make sure that my resume said data analyst like three or four different times. Now, on a similar note, if the job description is asking for sql, I'll wanna make sure that I have SQL on my resume multiple times. So once again, I wanna put it in my skill section. Maybe I put it in my statement, my objective at the top, uh, maybe I tried to put it in my bullet points in my experience section. Maybe I have a project section now on my resume. I'd want to put it there. You want to add as many keywords as you can. If you don't have the word Excel, the word sql, the word Tableau, power, bi, python, whatever, whatever terms you're trying to go for, if those aren't on your resume, you're not gonna get interviews. So I wanna make sure that I put SQL, Tableau in Excel, and in many places I possibly can. On my resume along with a data analyst tile. Next, I'd wanna do the same thing with LinkedIn. I wanna make sure that all of my experience section on LinkedIn is filled out. I wanna make sure it has bullet points. I wanna make sure I have a really good about section. I have a really good headline, a clear profile picture, a good cover photo on LinkedIn, and make sure every single part of my LinkedIn profile. Has information. Why? Because once again, 97% of recruiters, these are the people who hire you, are on LinkedIn every day. And if they're on LinkedIn every day, I think I should probably be on LinkedIn every day as well. I can't tell you how many times people go through my program and they do our LinkedIn section, they update their LinkedIn, and all of a sudden they have people reaching out to them, recruiters, Hey, would you be interested to interview for this role? Would you be interested to interview for that role? And all it does is take some LinkedIn optimization. Once again, you want to keyword stuff on your LinkedIn in as many places as you possibly can. Add skills, add whatever's in the job description, put that on your LinkedIn. The other thing to kind of consider on your resume in LinkedIn, and this is a little controversial, so uh, if you don't like it, I'm sorry, but this honestly helps you. Can you change any of your previous titles? Can you go through your titles and can you make them sound more data analyst? Can you add the word analyst anywhere? Can you add the word data anywhere? The more that you have data and analyst on your resume in your title section of your experience? The better. So maybe you are a program specialist. Can we substitute the word analyst for specialist? Would that be the end of the world? The term analyst is pretty broad, so I feel like it's safe to do. And honestly like most titles are all over the place. Like a title at one company does not mean the same as what it would be at another company. They're all made up. There's no such thing as like real titles, to be honest. So I think if you can do this. You should, and I honestly, I would elect to do that. So chemical lab technician, maybe I'd be chemical lab analyst. That feels like a little bit of a stretch, but here's the key. If it feels like a stretch, just remember you're just tricking the a TS. You could explain it to a human. Oh, that was actually more of like, uh, lab like technician role. But I did do a little bit of Excel analysis on that job. Humans can understand nuanced computers, ATSs cannot, so I'd probably update my LinkedIn and resume those ways. Step six is I would need to start applying for jobs. Um, obviously this might be really obvious, but I'm not going to land a job if I don't apply for jobs. And the same is true for you. So if you're applying to only a few jobs and you're not getting any bites and you're like, why can't I land a job? The answer is apply for more jobs. Now, I hate saying that because I'm also not a fan of just the spray and pray method where you're literally, you know, bombing your resume out to hundreds of thousands of people. Like I don't think that is a good method either. I think that there is kind of a middle ground where you're applying, probably unfortunately, in today's economy for hundreds of roles. But you're doing so in a targeted manner with human-centric motion in mind. And what I mean by that is 67% of jobs come from being recruited or referred. So that's why I really wanted to update my LinkedIn earlier. Right. So I can get recruited, but let's talk about referrals, referrals. Are amazing. This is when someone at a company will refer you to a role at that company and hiring managers and recruiters love that because if your friend's at a company and they're doing good work, they probably like your friend and they would probably be glad to hire more people like your friend, and hopefully you're just as good as your friend. So. Networking is really key here. You need, you need, you need to be networking. If you're not networking, your job hunt will take, I'm not even being dramatic here, 10 times longer. Networking is literally the key to landing a data job quickly. Now, how do you do that? We talked about updating our LinkedIn profile. That's a great start. I would also tell you to start documenting your journey on LinkedIn via posts and comments. Um, that's what we teach our students. I know that's scary for a lot of you. But I've literally seen it work wonders for so many students who had zero job experience and they were able to land a data job because of that. If that sounds scary, no worries. You can go to your neighbor, you can go to your cousin, you can go to your mom's friend's aunt and just be like, Hey, what do you do for work? Pull out your phone. Go through every contact in your phone. Write down what every single person does for work and where they work, and then ask. Would they ever hire a data analyst? Do they, do they have data analysts working at their company now? If so, send them a message. Start with the people who in your network already are in the data world or in the tech world. They can be really good resources for you and if they're actually your friends, if they're actually your family, they're willing to help you. They will be willing to help you. You just need to ask the right way. So a really easy way to not be intrusive, it's just to be like, Hey, I know that you're, you know, a program manager. At IBM, do you enjoy it? Just start the conversation that way. Oh, like, yeah, it's great. Yeah, it's awesome. You can be like, yeah, cool. I'm like looking to become a data analyst. Do you know any data analyst at IBM? Oh yeah, I know this guy. That's very cool. I can introduce you if you'd like. Oh yeah, that'd be great. See, I didn't even ask, I didn't even ask for anything right in that scenario, but I got what I wanted. So if you're not networking, it's gonna be hard. You need to be applying for jobs. Also I recommend varying where you apply for jobs. LinkedIn, great place to apply for jobs, maybe check your local listings. Those will don't get as many applicants and could be really, really easy to land interviews. Also, try other job platforms. I'm not gonna list them all, but I'm biased. You can try find a data job.com. This is my free data job board where I post a lot of different data jobs. I also have another one that is premium. It is paid. It's called premium data jobs.com. Those ones. Always have a recruiter or hiring manager that you could reach out to today. So that's why it's a little bit special. That's why it's paid. Check out both those, but just make sure you're going to different job boards and trying different application methods because it is a little bit of a luck, a little bit of a numbers game. Now, if I've done steps one through six, I'm probably ready for steps seven, which is start landing and preparing for interviews and. Interviews are how you seal the deal. That's how you actually get job offers, right? But you shouldn't be stressed. I shouldn't be stressed about interviews until I start landing them because there's two different separate skills here. The skills and the process of landing interviews, and then the process of passing interviews, and those are two different things, and you should prepare for them and work on them at different times and in different ways. So I would not be stressed about an interview until I've landed an interview. Once I landed an interview, I will cram. Uh, and there's lots of different things you have to think about in an interview, but basically most data interviews have two main parts, the behavioral part and then the technical part. The behavioral part. They're gonna be asking questions that usually start with, tell me about a time, tell me about a time you. Had to be a leader. You had an issue with a coworker, and these questions are basically like, let's look in their behavior in the past to predict what they might do in the future. It's like, once again, the recruiter and hiring manager here are trying to figure out how risky you are and hopefully not how risky you are once you've. You've shown that, hey, I'm a normal human being. I can work. They might ask more technical questions, and a lot of the times this will be maybe Excel specific questions or SQL specific questions. It kind of just depends on the role and the company. There's so many platforms you can try to prepare for these, these technical interviews. Just to list a few analyst builders, strato, scratch, uh, data lemur. There's like so many different data analyst prep, interview prep courses and classes and online things that I don't wanna talk about it right now and you shouldn't worry about it. I'm not worrying about it until I land interviews, but once you do. Those are right there for you to practice. So that's how I would hopefully land my first data job if I was starting from absolute scratch this year. And if you joined this method, we call it the SPN method. And what it means is it is not just learning skills, that's the s part of the SPN method. If you're just learning skills. You're not gonna land interviews, you're not gonna land jobs 'cause you're missing out on the other two thirds of the equation for landing your first data job. The P in the N, the P stands for projects in a portfolio. So that's what we talked about earlier. You need to have projects, you need to have that proof and have it in a portfolio. And the last part is the N, which is the networking, which is if, like I said, if you're not networking, you're not gonna land a job. So if you like this roadmap and you actually wanna follow it, please watch this video over and over again until you can finally figure out exactly what I said. If you'd like a hand by hand guide. Walking you through all the steps, literally giving you step-by-step instructions on this is how you network, this is what your LinkedIn should look like. Here's a bunch of projects that you can do. Here's a template for the resume and for the portfolio. Then consider joining the data analytics accelerator. This is my all-inclusive data analytics bootcamp, where I'll take you from zero to data analyst. Literally, this has worked for so many different people in my program from so many different backgrounds. We've helped teachers, truck drivers, Uber drivers, warehouse workers, accountants, therapists, music therapists, like whatever your current role is, we can probably help you transition into a data analyst if you wanna check that out. I have a link in the show notes down below. It's called the Data Analytics Accelerator. I'll be your coach and my team will help you land that First Data job. We're super excited to help you.

