Unfortunately, Landing A Job In Data Just Changed Forever

Have you ever felt like applying for data analytics roles in 2026 feels more like a humiliation ritual instead of a fair assessment of your skills and qualifications? Well, if you're trying to break into data right now but struggling to land a job, you're not alone. That's because the way people are getting hired in 2026 is changing fast. Now, if you're new here, my name's Kedeisha, and over the past 5+ years, I have placed hundreds of people into data roles worldwide, and I've watched in real time as applications are getting harder and harder to be seen. So in this video, I'm going to show you what's actually changed in the job market and what to do if you actually to get hired today. So what's actually changed? Because if you've been applying lately and thinking, why does this job market feel so difficult? You're not imagining things. When I was first pivoting into analytics during the COVID era, breaking into tech and data was hot. Back then, you can get away with doing significantly less than you can today. You could take a Coursera certificate, spend a weekend following someone else's Tableau and Power BI tutorial, put Excel, SQL, and a few other tools on your resume and start applying. And for a lot of people, that was enough to at least start getting interviews. The problem is I still see people using this outdated strategy Today, they finish a cert, recreate a tutorial project, make one generic resume, and then send out the same resume to 200 to 500 different jobs. And then a few weeks later, almost no one has responded to them. And then they assume the answer is simply to apply to another 300 jobs. And that is where I think people are getting stuck, because the issue isn't necessarily that you're not applying enough, you're just using outdated tactics. The number of candidates has gone up while the number of open roles isn't the same as the pandemic era level where companies were overhiring. Companies are still hiring, don't get me wrong. I'm not saying that data is dead. There are definitely jobs, but the balance has changed. There are more people competing for those jobs. And on top of that, AI has made it easier than ever to flood an application with little friction. A few years ago, you didn't have people using AI tools to auto-apply to hundreds of jobs every day. You didn't have the same volume of AI-generated resumes hitting a job portal within hours. So getting someone to notice your application has become harder. And that's why if you come to me today and said, Kedisha, I've applied to 150 jobs and I'm still not getting interviews. I wouldn't immediately tell you to get that number to 300. I would ask you how targeted those 150 applications were, because that is the game now. Not just volume, but quality volume. Let's say you find 2 data analyst roles. One is clearly focused on Tableau. The other keeps mentioning Power BI, DAX, and Microsoft tools. I would not send the same exact version of my resume to both. Now, I'm not saying you need to rewrite your entire resume every single time. Usually the changes are pretty subtle, but they do matter. For the Tableau role, I'm making sure my Tableau experience is easy to find. If I have relevant dashboard work, I'm bringing that forward. If Tableau Server appears somewhat in the job description and I have experience with it, I'm making sure it's not buried somewhere at the bottom of the resume. And then for the Power BI role, I'm going to do the same thing with the skills that matter there. It's the same person, same experience. You're just making it easier for that specific employer to see why you fit that specific role. And this is actually one of the places where I think AI can actually be useful in your job search. You can give a job description to ChatGPT, Claude, or my favorite, Manus, and ask it to identify Identify the most important skills and responsibilities and keywords, then compare those against your resume. Not so it can completely rewrite your experience into something that isn't true, but so you can spot where relevant experience you already have isn't being communicated clearly enough. That's a much better use of AI than trying to automate 500 generic applications. And the reason I want you to understand this shift is because jobs themselves are changing too. The analyst role is becoming more full stack. A few years ago, you could learn some Excel. Some basic skills, and that would be enough for a lot of entry-level roles. But today, teams are leaner, so companies increasingly want analysts who understand more of what happens before the dashboard ever gets built. If someone gives you a messy data source, can you understand how that data gets clean? Can you transform it? Can you build a simple pipeline that might involve Python, or it might involve Power Query or Databricks? The specific tool is less important than understanding what's happening to the data. Now, I'm not saying you need to become a data engineer. You do not need to know every database, every cloud tool, and every pipeline technology. But if you're the deciding where to expand your skills after learning the basic analyst stack, I would personally put more emphasis on data engineering foundations before jumping into any machine learning. A few years ago, everyone wanted to be a data scientist. Data science was hot, machine learning was hot. The boom has flattened out though. Meanwhile, companies still have very real problems around dirty data, data quality, and getting reliable data from one place to another. So if you're a data analyst who understands the business side, can analyze the data, and can also understand some of the engineering underneath it, you become way more useful than the pack. So yes, the market has changed. It is more competitive. The role itself is asking more of you, but that doesn't mean there's no opportunity. It just means you cannot use COVID-era 2020 job search strategies in a 2026 job market. Now, once you understand that the old application strategy isn't enough anymore, the next question becomes, how do you actually separate yourself from everyone else? And this is where I think we've moved into what I call the proof economy. You need proof today because one of the easiest traps to fall into when you're struggling to get hired is thinking that the answer is always another credential. You get your bachelor's degree, you're still not getting the results that you want. So maybe you get a master's degree, then you get a SQL certificate, then a Python certificate. And before you know it, you have spent years proving that you can study analytics without proving that you can actually do analytics. And that becomes a problem the moment someone in the interview says, walk me through a real analytics problem that you've solved end to end. Because a credential just tells me what you studied. It doesn't automatically tell me that you can use it. And I've seen this happen in real life. I had a student who had both a bachelor's and a master's degree from my alma mater, Emory University, one of the top schools in the country. So this wasn't someone with weak education. He had the credentials, but he was still working security jobs and struggling to make that transition. What made the biggest difference was developing his actual analytics skills and building work he could show with a portfolio. So when he got into an interview, he could pull up his portfolio and walk the hiring manager through what he had done. An actual demonstration. He could show the work and he ended up landing a 6-figure role. That is why I keep saying proof. This is the proof economy because that portfolio was doing something his degrees alone could not do. And I know the obvious question here is, well, how am I supposed to prove I can do real work if no one's going to hire me without experience? And this is where I think you have to stop waiting for a company to officially give you permission to solve a real problem. One of the things I always recommend is doing short volunteer analytics projects with your local nonprofits or small businesses. And when I say free work, I'm not saying go work somewhere indefinitely for no money. I mean a very defined engagement. 30 days, maybe 45 days. And because these organizations can move slowly, I would reach out to more than one. Sometimes it takes a week just to get a response, and sometimes it could take another week just to get the data. That's normal though. But once you finish one of these projects, notice how differently you can talk about your experience. The beginner version would sound like, I built a sales dashboard using a Kaggle dataset. Okay, that shows me what you practice. But compare that with, I worked with a local nonprofit that had donation data spread across inconsistent spreadsheets. I cleaned and standardized the data, then built a dashboard so the team could understand donation trends and recurring donor behavior. Now I'm hearing about a real stakeholder, real data, and a real business problem with an actual outcome. That is a completely different conversation in the interview. And this whole idea of proof also explains why hiring processes can feel so ridiculous now. People see 5 to 6 interview rounds and immediately think, why would a company need this many conversations just to hire an analyst? And look, I understand the frustration. No one likes to do these interviews, but I think you have to understand what the company is trying to protect itself from. Hiring is risky and expensive. Hiring the wrong person is even more expensive. If a company hires someone and 60 or 90 days later realizes they can't actually do the work, which happens a lot, that mistake costs time, money, and productivity. And now companies are trying to evaluate candidates in an environment where looking impressive on paper is easier than ever thanks to AI. So employers are trying to answer a harder question today that they didn't really have to answer before. Is this person actually as good as they look? That is what all of those checkpoints are just trying to figure out. And while you can't control how many rounds they create, you can control how much uncertainty is around you. That is why I would front load as much proof wherever as possible. If you have a portfolio, use it. If you have a real project, talk about it. And don't just show the final dashboard. Be able to explain what went wrong. Tell me where you made certain decisions and tell me what you would change if you can do the project again and what trade-offs you had to make. Because the deeper you can go into your own work, the easier it becomes for an employer to believe that you actually did it. And once you start thinking this way and shift your mentality, it also changes which applications deserve your time. If I see a job that's been sitting there for months and keeps getting reposted, and gives me no real indication that someone is actually hiring, I'm probably not going to spend an hour tailoring my application for that job. But if something was posted recently, I can understand the team, the requirements make sense, and I can clearly see the connection between my experience and what they need, that is where I'm going to put my effort into. Because standing out isn't just about making every application equally good, it's about recognizing which opportunities are worth doing more for. So your new strategy becomes find better opportunities Make my application relevant and show enough proof that the employer can picture you doing the work. And that is how you stand out in the proof economy today. Even if you do all of that well, there's still another problem. Most job seekers are competing in the exact same places. They go to LinkedIn, they type data analyst, and they apply to all the well-known companies, or they hit easy apply, and then they're surprised when they're competing with thousands of people. That is the front door. And if that's the only way you're trying to get hired today, I think you're making the job search harder than it needs to be. I would still apply to jobs normally, but I would start asking, where are fewer people looking? That question alone changes a lot because instead of automatically chasing the company everyone recognizes, you start noticing industries where actual analytics work is strong, but the competition is not as intense. Government, for example, local government, state government, especially government contracting. I still get LinkedIn DMs today regularly about government contracting roles for data analytics jobs. Consulting is another great area people overlook, particularly boutique consulting firms. And then there are industries like healthcare, health insurance, supply chain, transportation, logistics. These Companies have the data, they have the decisions to make, and they need analysts, but they're not necessarily in the places everyone on social media is telling you to apply. That is what I mean by the side door. It's not about finding some magical hidden company. It's about changing where you're looking. And the same thing applies to job titles. If you're only searching for data analysts, you're choosing to compete in the most obvious search possible. That is why I keep coming back to this idea that the job description matters more than the job title. You need to be able to recognize the work itself, and once you do that, you can start widening your keyword searches, using Boolean searches on LinkedIn and Google, and checking company career pages and finding jobs that may never appear when you search for that exact title. And ideally, you want to find those jobs early. If you can build a personal job alert system or even use AI to help create a custom job search board for yourself, now you're going to be notified about relevant job roles within 24 to 48 hours of them being posted. That puts you in a completely different position than finding the same role 30 days later. But the side door isn't only about where to find the job. It's also about how you get connected to the people around it. And this is where networking gets a bad reputation, because most people imagine the most cringiest possible version of networking. You don't find a random stranger on LinkedIn and say, hey, can you refer me? That's always going to be awkward, and most people are still doing that. And if you are doing that, please stop. But if you went to college, for example, you have a much more better natural place to start— your alumni network. You go to your school's LinkedIn page, go to the alumni who work in analytics or at companies you're interested in, and start a normal conversation. I did this personally when I was pivoting in, and I probably talked to like 20 people. And not every conversation needs be a meeting. Some of them can just be conversations in the DM because you always want to respect people's time. So entering through the side door isn't just one tactic. It's just a different way of approaching your job search. You widen where you look and you widen what you call the job and you build relationships instead of immediately looking for favors. And when someone actually does give you their attention, you make sure your work communicates something useful. The side door is not a secret website. It's just learning how to look where everyone else is not looking. All right, quick pause. Now, if you want to land your first job in data analytics and avoid the lengthy mistakes that I did, click the link in the pinned comment where you can find the exact steps that my students use to land their job in data analytics without going back to school. All right, now let's get back to it. And now this brings me to the final question, which is probably the question underneath all the other questions people ask me. How do I know when I'm actually ready to apply? Because usually people don't phrase it like that. They ask, how much SQL do I need? Do I need Python? Do I need another project? Do I need another certification? But really what they're trying to figure out is whether they're good enough to start applying for jobs. And I think the easiest way to answer that is to stop measuring readiness by how many tools you've studied. Instead, ask yourself, can I take proper ownership of a real analytics problem without getting my hand held and without getting the instructions? Because if you can do that, a lot of the other pieces start falling into place. Very often people show me their portfolio projects, and then when I ask them why they use a certain chart, they don't really know. I ask them why you clean the data a certain way, and they're not really sure. Why'd you approach your SQL query with this certain approach? And they can't explain it. Eventually, I and anyone else would realize that you didn't really own that project. Maybe you blindly followed a tutorial without taking any notes. Maybe AI made most of the decisions. Maybe you just copied an approach without understanding why it worked. That is very different from being able to defend your own work. And a good way to break out of this is a test that you can do with SQL. SQL is still one of the most heavily tested technical skills in analytics interviews. So rather than asking whether you've completed enough SQL lessons, I teach my students something what I call the whiteboard method. You can take a piece of paper or a blank Word doc. Draw a couple tables, give yourself a business question, or even ask AI to do it. Write a query without autocomplete and without immediately asking ChatGPT what to do. Can you reason through it? Can you write pseudocode? Can you figure out how the tables relate? Can you aggregate properly? Can you recognize when to use a CTE or a subquery or a window function when the problem calls for it? And more importantly, do you understand why you're choosing your approach? Because knowing what a window function is and knowing why you're using it are 2 completely different things. And use that same standard and test across the rest of your skills. So if you're trying to figure out whether ready to apply, I would stop waiting for the moment when you know everything, because that moment's never going to come. Instead, test yourself on whether you can take basic analytics problems and move it from end to end without any directions, and test yourself in front of another person so you can defend your choices that you made. When you can do all of that, you're probably closer to job ready than you think. And if there are parts you cannot do yet, that's useful too, because now you know the gaps that you need to work on instead of trying to work on everything. You know, these specific things to focus on. But whichever route you choose to follow to get hired, you're still going to have your resume reviewed by a human. And unless you know how to write one for the 2026 job market, none of what I mentioned matters. And that's exactly why I reviewed over 2,000 resumes to find out exactly what gets analysts hired. That's this video right here, and I want you to watch it next. I'll see you there.