Ian Klosowicz
Working full time while trying to break into data analytics is harder than doing it without a job. That's just true. You have less time, less energy, and less ability to do intensive study sprints. What you have instead is a stable income, which makes it easier to be patient about the timeline and selective about how you spend your time outside work.
The good news is that the skills you need to get an entry-level analytics role are learnable in a few hours a week, over several months, if you're consistent. You don't need to quit your job. You don't need a bootcamp. You need a realistic plan and the willingness to stick to it.
Be honest with yourself about how much time you actually have. Most people working full time can reliably protect 1-2 hours per day on weekdays, more on weekends. Some can do more; many can do less. The number matters because it determines your timeline.
At 1 hour per day, 5-7 days per week, you're putting in 30-50 hours per month. Learning SQL from scratch to an employable level takes roughly 60-80 hours of practice. Learning Excel pivot tables and basic formulas takes maybe 20 hours. Building a dashboard in Power BI or Tableau takes another 20-30 hours. Portfolio projects take 10-20 hours each.
That's roughly 150-200 hours of focused work before you're ready to apply seriously. At 40 hours per month, that's 4-5 months. At 20 hours per month, that's 7-10 months. Neither of those is fast, but both are achievable without quitting your job.
The biggest mistake people make is being inconsistent. Five days at 2 hours is better than three weeks off followed by a marathon weekend. Consistency over intensity.
The sequence matters. Building skills in the wrong order means spending time on things you're not ready to use yet.
Start with SQL. SQL is the most commonly required skill for data analyst roles and the one most people lack coming from non-technical backgrounds. Mode Analytics has a free SQL tutorial that's as good as anything you'll pay for. SQLZoo is another option. Spend the first 6-8 weeks here, doing real practice on actual datasets rather than just reading.
Then Excel or Google Sheets. If you already use Excel at work, this might go quickly. Focus on pivot tables, VLOOKUP/XLOOKUP, IF/IFS, and basic data cleaning. If you don't use it at all, add a few weeks here. This skill also has immediate payoff in most current jobs.
Then a BI tool. Power BI and Tableau are both reasonable choices. Power BI is more common in corporate environments and integrates with Microsoft tools most companies already use. Tableau has a stronger job market presence in tech and consulting. Pick one and build something with real data rather than tutorials alone.
Python is optional for entry-level. Don't let Python become a reason to delay building a portfolio. A lot of entry-level data analyst roles don't require it. Add it after you have the core skills if you want to, but don't treat it as a prerequisite.
The portfolio is the thing that gets you interviews. Without it, the skills don't show up on paper. With it, you have something concrete to talk about.
You don't need a large portfolio. Three solid projects are enough. Each one should use a real dataset, answer specific questions, and be documented clearly enough that someone else can understand what you did and why.
Good project sources:
Keep each project on GitHub. Even a basic README explaining what the project is and what you found is enough. The goal is to give a hiring manager something to look at that isn't just bullet points on a resume.
Your current job is a resource, not just a constraint. A few ways to use it:
Volunteer for anything involving data. Even if your role doesn't involve analytics, there are often reporting tasks, data cleanup projects, or one-off analysis requests that nobody wants to do. Take those. They build real skills and often produce work you can reference (though not show in detail) in interviews.
Find out what tools your company uses. If your company uses Power BI, learn Power BI. If they use Tableau, learn Tableau. Matching your learning to your company's stack creates opportunities to use your new skills immediately and gives you concrete examples to reference.
Look for ways to quantify things you're already doing. Can you build a tracker for something your team cares about? Can you automate a report that someone's building manually? Small wins at your current job are resume bullets.
Not every job will have these opportunities, but most will have some version of them if you look.
The job search while employed is slower than searching full time, but it has advantages. You can be selective. You don't have to take the first offer. You can wait for a role that's a real step up rather than a lateral move.
Practically, this means:
Should I tell my current employer I'm looking?
No. Not until you have an offer. Even if your relationship with your manager is good, telling them you're job searching creates risks with no upside. Keep it quiet.
Is it okay to use work time for studying?
Use your own judgment here. Using your lunch break to do a SQL tutorial is reasonable. Using company time during the workday to study is not. The distinction matters both ethically and practically -- you don't want to be distracted from your actual job in ways that affect your performance review.
How do I explain gaps in my learning during busy work periods?
You don't have to explain them. Learning timelines are rarely linear. If you have a stretch where you can't study because work is intense, that's fine. Pick it back up when you can. The total hours matter more than whether they came in a straight line.
What if my current job has nothing to do with data?
The portfolio is more important in that case. If your day job gives you no data-adjacent experience to reference, then the projects you build independently have to carry more weight. That's fine -- they can. Focus extra effort on making those projects specific, well-documented, and genuinely interesting rather than generic tutorial reproductions.
