This is the last email you’ll get while Analyst Hive is still $19 a month.

Tomorrow it’s $39.

Not a flash sale, not a fake countdown that resets when you refresh. The price goes up on September 1st and it stays up. If you’ve been sitting on this, today is the day the sitting stops being free.

So instead of another teardown, I’m going to tell you exactly what the $19 buys you and why waiting a week costs you more than $20.

Here’s the situation most of you are in.

You’ve got 400 open tabs. A half-finished Coursera cert. A SQL course you started in March. A folder called “portfolio” with nothing in it. You’re not lazy and you’re not dumb. You just don’t have an order to do things in, so every day you pick the tab that feels most urgent and make almost no progress on any of it.

That’s the whole problem. It was never a knowledge problem. Every SQL concept you need is free on YouTube. The gap is that nobody self-teaching has a sequence, and without a sequence you spend 8 months learning things in the wrong order and quit before the part that actually gets you hired.

1. You stop deciding what to learn next.

Analyst Hive is a 90-day, day-by-day system. Every day has one thing. You open it, you do the thing, you close it. Day 14 knows what Day 13 taught you. Day 60 knows you can already write a join.

You’re not building the curriculum and taking the course at the same time anymore. That’s the part that quietly kills people. Deciding what to learn is harder than learning it, and you’ve been doing both alone.

This is literally what the first three weeks walk you through, before you touch a single “impressive” project.

Join Analyst Hive

2. The tool fight is already settled.

SQL. Excel or Google Sheets. One BI tool, Tableau or Power BI. Used together, in one project, end to end.

That’s the stack that gets junior analysts hired. It’s been the stack for years. But every roadmap online buries it under 15 things you’ll never open again, and you end up half-learning a bloated pile of tools instead of getting fluent in the 3 that matter.

You don’t need the giant toolkit. You need the boring stack, used well, on something real.

3. You build one project a hiring manager actually finishes reading.

Most self-taught portfolios are 6 disconnected notebooks that each answer a question nobody asked. A hiring manager clicks one, sees the Titanic survival predictor for the 15th time that week, and closes the tab.

Inside, you build one project that runs the full pipeline. Pull messy data with SQL, clean and model it, put it in front of a decision in a dashboard. It looks like a job because it is the job. That’s the thing that makes someone email you back

4. The outcome range is real, and the gap to it is a plan.

Analysts coming out of this land in the $70K to $187K range. That’s not a typo and it’s not the ceiling reserved for people who already had a computer science degree.

The distance between you and that number isn’t talent and it isn’t a bootcamp loan. It’s 90 days of doing the right thing in the right order instead of another year of doing everything in no order. Talent gets wildly overrated by people who haven’t watched a stubborn person with a plan beat a smart person without one.

5. The math on waiting.

You can join tonight at $19 or join in October at $39.

Same system either way. The only variable is whether you locked the price in while it was open. $19 a month is less than one takeout order. $39 is still cheap for what it is, but there’s no reason to pay double for the exact same thing because you needed one more day to think about it.

Twelve months at $19 is $228. Twelve months at $39 is $468. Waiting a day to “decide” costs you $240 over a year. That’s the whole decision.

Here’s the part I actually want you to sit with.

Every month you spend “getting ready” to start is a month you’re not in a role earning. The cost of waiting was never the price of the program. It’s the salary you’re not collecting while you circle the runway. The price going up tomorrow is small. The 6 months you’ll lose if this becomes another thing you meant to do is not.

Analyst Hive is the day-by-day system that takes you from 400 open tabs to a hired analyst in 90 days. SQL, Sheets, and one BI tool, one real portfolio project, one thing to do each day, no guessing about what’s next. It’s built by someone who taught himself this with no degree, so it’s ordered the way it should’ve been handed to me. Tonight it’s $19 a month. Tomorrow it’s $39. Lock it in here:

Join Analyst Hive

What’s the actual thing keeping you from starting? Not the polished reason. The real one. Reply and tell me, I read every one.

Talk soon,
Ian

P.S. If you’re going to join at some point anyway, joining tonight and joining in three weeks are the same decision except one costs $20 a month more forever. That’s it. That’s the P.S.

Then you hit submit and never heard back.

This happens to most no-degree candidates. And it keeps happening because nobody tells them what actually occurs on the other end of that application.

Here’s the sequence, from the moment your resume lands to the moment it gets a call, or gets closed.

A hiring manager at a mid-size company posts a junior analyst role on LinkedIn at 8 a.m. By noon she has 60 applications. By end of day, 140. She is not reading 140 resumes. She is screening them.

Screening is a discard process. She’s looking for reasons to close a tab, not reasons to open a calendar invite. The average screen takes 6 to 10 seconds. A resume either survives that window or it doesn’t, and the pile she’s calling from on Friday usually has 4 to 6 names in it, down from 140.

Your resume either cleared the screen or it didn’t. Here’s how that decision actually gets made.

1. The ATS runs it first, before any human sees it

Most companies above 50 employees use an applicant tracking system. The ATS parses your resume, pulls out keywords, and ranks applicants before a human reviews a single one.

The keywords it’s looking for come directly from the job posting. If the posting says “SQL,” your resume needs to say “SQL,” spelled exactly that way, somewhere above the fold. “Database querying” doesn’t match. “Structured Query Language” doesn’t match. SQL matches.

No-degree candidates lose here in two specific ways. They either dump every tool they’ve heard of onto a skills line hoping one sticks (which dilutes the signal), or they describe their skills in plain language that doesn’t match the exact phrasing in the posting.

The fix is mechanical: read the posting, find the exact tool names, make sure those exact names appear on your resume. That’s ATS optimization. It takes 10 minutes per application and most people skip it.

2. The 6-second screen happens top-down

If your resume makes it past the ATS, a human opens it. That person starts at the top left and moves right and down. The first 4 to 5 inches of your resume determine whether she keeps reading.

What she’s looking for in those first seconds: a job title or summary that makes sense for the role, recognizable tools, and some signal that you’ve done something with data rather than just listed tools you’ve studied.

What she usually finds on no-degree resumes: a generic objective statement (”Seeking an opportunity to grow in a data-driven environment”), a company name she doesn’t recognize, and a skills list that starts with SQL and ends 11 tools later.

She closes the tab.

The candidates who survive this window have something at the top that describes work, not credentials. A project. A result. A real business question answered with real data. One sentence is enough if it’s the right sentence.

3. The education filter is real but it’s not where you think it applies

Hiring managers do notice the absence of a degree. But most of them notice it around the third or fourth section of the resume, not the first.

If your resume leads with a strong summary and a project that demonstrates the actual work, a recruiter is already forming a picture of what you can do before she gets to education. That picture either survives the education field or it doesn’t.

If your resume leads with “Education: High School Diploma (2018)” followed by a Relevant Coursework block, she’s already categorized you before she reads anything else.

Move education to the bottom. Every time.

4. The project question is the only thing that changes the outcome at the interview stage

If your resume clears the screen and you get a phone call, the first 10 minutes of that call will include some version of this question: “Tell me about a project you’ve worked on.”

Most no-degree candidates either don’t have a project they can speak to specifically, or they describe something so vague that the interviewer can’t evaluate it. “I analyzed some sales data in Excel” tells a hiring manager nothing.

A candidate who built one end-to-end project, can name the dataset, explain the business question, describe the tools used and why, and walk through a finding with a specific number, clears this question every time.

Analyst Hive’s 90-day sequence is built around exactly that: one project, three tools, documented end to end so you can answer this question on any call. Members who finish the sequence have something specific to talk about.

Join Analyst Hive

5. The callback list is shorter than you think

A hiring manager screening 140 applications calls 4 to 6 people. That’s a 3 to 4 percent callback rate, not because the other 96 percent were unqualified, but because most resumes look the same.

Same 12-tool skills list. Same generic summary. Same bullet points about “assisting with” and “supporting” data tasks. Same absence of any project that proves anything.

The resumes that make the callback list are the ones that look different on paper. Specific tools rather than a full catalog. A summary that describes actual work. A project with a real question and a real answer. One link that a recruiter can click and see something.

That’s the whole game. Being different on paper at 3 to 4 percent scale is the margin between getting calls and never hearing back.

The resume is a screen, and most people are designing it to answer a question nobody’s asking (”what have you studied?”) instead of the question that actually gets you past the screen (”what have you built?”).

A hiring manager screening 140 resumes on a Thursday afternoon is not rooting for you. She’s looking for a reason to close the tab. Give her a reason to keep it open instead.

Analyst Hive is a 90-day, day-by-day program for people breaking into data without a degree. It walks you through the exact resume structure above, the three-tool stack that shows up in every junior analyst posting, and one portfolio project built end to end that you can speak to specifically in any interview. Membership is $19/month through August 31 and goes to $39/month September 1.

Join Analyst Hive

If you’ve been applying and not hearing back: which part of the resume do you think is the problem? The top section, the skills list, or something else?

P.S. The 3 to 4 percent callback number isn’t a reason to give up. It’s a reason to make sure your resume is in the top 3 to 4 percent of the pile, which is a much lower bar than it sounds.

Talk soon,
Ian

They add a “Relevant Coursework” section under Education. They list every tool they’ve touched. They write “Proficient in SQL, Excel, Tableau, Power BI, Python, R” across a single line and hope a recruiter connects the dots.

Then they wonder why no one calls.

Here’s what a hiring manager sees on the other end of that application: a candidate who learned a lot of things shallowly and can’t prove any of them work in a real business context.

A recruiter screening 40 resumes this week doesn’t stop to give yours the benefit of the doubt. She sees no degree, no recognizable company, no project that means anything, and moves on in 6 seconds. The coursework section doesn’t save you. The tool list doesn’t save you. The generic summary paragraph about being “detail-oriented and passionate about data” really doesn’t save you.

The candidates getting calls from that same pile look different on paper. Here’s the difference.

1. Lead with what you built, not what you know

Your summary is the first thing a hiring manager reads. Most no-degree candidates use it to say the same 3 things: they’re passionate about data, they’re a self-starter, and they’re eager to learn.

Write it differently. Lead with the project, the tools, and a result.

Something like: “Self-taught analyst. Built an end-to-end sales dashboard in Power BI using 3 years of revenue data. Identified a seasonal drop pattern that would’ve been worth $40K if applied to a real inventory decision.”

You’re not listing credentials. You’re describing work.

2. Build 1 project and document it like it’s a case study

This is where most no-degree resumes fall apart. Candidates either list no projects at all, or they list something vague like “Personal project: analyzed Airbnb data.”

That tells a hiring manager nothing. What question were you answering? What tools did you use and why? What did you find?

A single project, described with specificity, does more work than 5 generic bullet points combined. Pick a dataset that maps to a real business problem. Run the analysis in SQL. Build the dashboard in Tableau or Power BI. Write up what you found and what a business would do with it.

That’s your portfolio. 1 project, done end to end, explained clearly.

I help you step-by-step in building the write-up for your projects AND help you directly with bullet points on resume or on your portfolio in Analyst Hive.

Join Analyst Hive

3. Put the education section at the bottom and stop apologizing for it

No-degree candidates consistently put their education section at the top, list their high school diploma or an incomplete degree, and add a Relevant Coursework block hoping to pad it.

Stop.

Move Education to the bottom of the resume. List whatever you have, nothing more. No coursework, no “expected graduation,” no list of YouTube courses.

The top of your resume should be your project, your tools, and your skills section. The education question will come up in the interview if it comes up at all. A hiring manager who gets to your project before your education section is already evaluating you differently.

4. Your skills section should be 5 things, not 15

“SQL, Excel, Google Sheets, Tableau, Power BI, Python, R, SPSS, Looker, Databricks, dbt, pandas, NumPy, matplotlib, Jupyter Notebooks.”

Every word after the first 5 on a list like that tells a hiring manager you’re not sure what you actually know.

Pick the stack you can prove: SQL, Excel or Google Sheets, and 1 BI tool. That’s it. If you built your portfolio project with those tools, you can talk about them specifically in an interview. The 12 other tools you added because they appeared in job postings will get you nowhere if someone asks you to walk through a Power BI model on a whiteboard and you haven’t touched it in 3 months.

5. Quantify what you can, but stop making up numbers

Every resume guide tells you to quantify your impact. The problem is, most no-degree candidates are coming from jobs that had nothing to do with data: retail, food service, warehouse, customer support.

You can’t say “increased revenue by 23%” if you were a barista.

What you can do: find a number somewhere in that job. Volume (”processed 150+ customer transactions per shift”), scale (”managed inventory for a store with $2M in annual product flow”), or time (”reduced X from Y to Z minutes by doing A”). Real operational details beat fake impact numbers every time.

If you’re working with pure portfolio projects, be precise about the dataset: how many rows, how many variables, what time range, what business question you were answering.

6. Link to something a recruiter can actually click

GitHub, a Tableau Public dashboard, a Notion page with your case study writeup. One link, working, at the top of the resume next to your name.

Most no-degree candidates don’t do this because they don’t think their work is ready. Get it ready. A recruiter who clicks a link and sees a real dashboard is no longer looking at your education section.

That link is the whole application.

The degree question is real. Hiring managers do see it. But it’s a filter, and filters have workarounds.

A candidate with a portfolio project, a narrow and defensible skill set, and a resume that leads with work instead of credentials clears that filter regularly. The candidates who don’t clear it are the ones who looked indistinguishable from 30 other self-taught applicants with generic summaries and a 15-tool skills list.

The resume doesn’t get you the job. It gets you the interview. Make it do that job and stop asking it to apologize for what you don’t have.

Analyst Hive is a 90-day, day-by-day program for people breaking into data without a degree. It covers the exact resume structure above, the 3-tool stack that shows up in real job postings, and 1 portfolio project built end to end. Membership is $19/month through August 31 and goes to $39/month September 1.

Join Analyst Hive

P.S. The candidates I see struggle most aren’t underqualified. They’re indistinguishable. The resume is usually the first place that shows up.

Talk soon,
Ian

They finish a SQL course. They upload a Kaggle dataset about avocado prices. They call that their portfolio and wait.

Then they wonder why nobody’s calling.

Here’s what’s actually happening on the other side of that application.

A hiring manager is looking at 40 resumes. Half of them have the same Titanic survival predictor. A quarter have the same bike-sharing analysis. The rest are blank because people uploaded a one-page resume with no projects at all.

What almost none of them have is a section showing the candidate used data to do anything in a real job, a real business, or a real problem they actually owned.

Not because they didn’t have that experience. Because they never looked for it.

Data experience doesn’t come exclusively from data analyst jobs. It comes from any job where you tracked something, measured something, reported something, or made a decision based on numbers. Most people reading this have done all four. They just never wrote it down that way.

1. Track what you tracked

If you’ve worked in retail, food service, logistics, a call center, or a warehouse, you were sitting next to data every single day.

How many units moved. What the daily average was. Which shift hit quota and which didn’t. How long orders took. Return rates. Shrink. Downtime. Complaints per hour.

You weren’t called a data analyst. But you were tracking operational data, noticing patterns, and operating inside a system that ran on numbers.

Write it down. “Monitored daily throughput metrics across a 12-hour shift and flagged deviations to floor management” is a real bullet. Not invented. Not stretched. Just named properly.

2. Find where you made a decision with numbers

This one is the most underused.

You didn’t need a dashboard to make a data-informed decision. You needed a number and a choice.

Did you ever look at inventory levels and decide to reorder? Did you look at foot traffic and decide when to schedule staff? Did you price something, quote something, or bid on something based on costs you calculated? That’s it.

Take that decision, name what data you used, and state what the outcome was. “Adjusted staffing schedule based on weekly foot traffic patterns, reducing overtime costs by roughly 15%” isn’t a lie if that’s what happened. It’s just described at the right level of specificity.

3. Inventory every report you’ve ever built

Spreadsheet. Weekly email summary. Shift log. Inventory count. End-of-month number roll-up. Damage report. Ticket queue summary.

If you built it, owned it, or maintained it, you built a reporting process. That counts.

What to write: the cadence (weekly, monthly), who received it, what decisions it informed, and what happened when the numbers looked off. Four answers. That’s a portfolio artifact that already exists because you already did the work.

This is what most of the 90-day sequence inside Analyst Hive is built around: not just SQL and dashboards, but how to find and document the experience you’ve already accumulated so it reads as analyst experience to a reviewer.

Join Analyst Hive

4. Look at your side projects

If you’ve ever run an Etsy shop, managed a social media account for a business, tracked a household budget in Google Sheets, or done anything that required comparing one number to another over time, you have a data project.

Not a polished one. But one.

The bar for a portfolio project isn’t “built a production pipeline.” It’s: defined a question, gathered data, analyzed it, found an answer. If you tracked your Etsy conversion rate for three months and changed your listing strategy based on what you found, that’s a complete analysis. Write it up. Put it in a repo.

5. Map your work history to the job description

Pull up three real entry-level data analyst job postings. Look at the requirements section.

They’re going to say: “comfortable working with data,” “ability to track and report on KPIs,” “strong Excel skills,” “build reports for stakeholders,” “translate data into insights for non-technical audiences.”

Now find the closest match in your actual work history. You don’t need to have done it in a data analyst context. You need to have done it.

If you’ve explained a number to a manager who didn’t understand it, you’ve translated data for a non-technical audience. If you’ve built any spreadsheet other people used, you’ve built a report for stakeholders. If you’ve tracked anything on a recurring basis, you’ve worked with KPIs.

Write it that way. Not because you’re inflating your background, but because you’re finally describing it accurately.

6. Be honest about the level

Don’t claim you’ve built a star schema or maintained a warehouse if you haven’t. Show that you’ve worked around data and are actively building the technical layer on top of it.

“I’ve done these work-adjacent tasks with data” combined with “here’s the portfolio project where I built the SQL and dashboard version of that same problem” is more compelling than a resume full of tutorials with no real-world context underneath.

Entry-level hiring is a signal-detection problem. Reviewers aren’t asking “did this person have the title.” They’re asking “does this person think like someone who can do the job.”

Most people have more documented-able data experience than they think. They just never wrote it down at the right level of specificity.

The candidate who gets the call made their real experience legible, built a project that demonstrates the technical piece, and didn’t bury the actual signal under a list of tools they learned over a weekend.

Experience doesn’t appear on a resume automatically. You have to name it.

If you want a structured system for doing this, Analyst Hive is a 90-day, day-by-day membership for aspiring analysts serious about landing a role in the $70K–$187K range. It covers the technical side and the job-search strategy side at the same time, including how to document the experience you already have so it reads correctly. The price goes to $39/month on September 1. It’s $19/month right now.

Join Analyst Hive

Question for you: What’s one task from a past job that involved data, even informally? Drop it in the comments and I’ll tell you how I’d write it on a resume.

P.S. The most common issue I see when people share resumes is a work history that contains real data experience described as if it had nothing to do with data. The rewrite usually takes two sentences.

Talk soon,
Ian

The strategies inside are what I’ve used to help students land $70K–$187K data roles. It’s a 90-day, day-by-day system. Do day 4 on day 4, day 15 on day 15, no guessing what comes next.

If you’re sending resumes into a void right now, that’s the exact thing it fixes.

Lock in $19/month before 9/1 here: Join Analyst Hive

Now for the single biggest reason your resume isn’t turning into interviews.

You spend a Saturday making your resume look good.

Two columns. A little skills bar with proficiency dots. A splash of color, an icon next to your email. You export it from Canva as a PDF, apply to 40 jobs, and wait.

Then nothing. Not a rejection. Not a call. Silence.

Here’s what happened to that resume. It never reached a person.

Most companies push every application through an Applicant Tracking System before a recruiter opens a single file.

The ATS reads your resume, pulls it into a database, and ranks it against the job description automatically. For a data analyst posting with 300 applicants, nobody reads 300 resumes.

The recruiter opens the ATS, filters for the skills the role needs, and looks at the 15 that surface. If your resume didn’t parse cleanly, or didn’t contain the words they filtered for, you’re not in those 15. You’re not in the pile at all.

The whole game is two things: getting parsed correctly, and matching the posting. That's it. The best-looking resume on earth scores a zero if the software can't read it, and a plain resume that mirrors the job description will beat it every time.

Most people spend their effort on how the resume looks to a human who's never going to see it.

1. YOUR TWO-COLUMN TEMPLATE IS WHY YOU’RE INVISIBLE

ATS parsers read a page like a book. Left to right, top to bottom, one column. The second you split the page into two columns, text boxes, or tables, the parser tries to flatten it and scrambles the order. That skills sidebar you’re proud of gets shredded or dropped entirely.

Same story with headers and footers. A lot of parsers ignore them, so if your name, email, or phone number lives up in the header, it can vanish. The recruiter gets a resume with no way to contact you.

Kill the design. One column, top to bottom, plain text. It’ll feel too simple. That’s the point. Simple is what survives the machine.

2. MATCH THE POSTING WORD FOR WORD

The ATS ranks you on how closely your resume matches the job description. Not the spirit of it. The literal words.

If the posting says “SQL,” your resume needs the string “SQL,” not “wrote queries against relational databases.” If it says “Tableau,” write Tableau, not “data visualization tools.” If it says “stakeholders,” use the word stakeholders. You’re not dumbing it down. You’re speaking the exact language the filter is scanning for.

Read the posting, pull out every hard skill and tool it names, and make sure each one appears on your resume in the same words, as long as it’s actually true for you. Do this per application. A resume tuned to the posting will always outrank a generic one, and it takes 10 minutes.

3. MAKE THE 3 TOOLS FINDABLE IN FIVE SECONDS

For an entry data role, the filter is almost always looking for the same short list: SQL, a spreadsheet tool (Excel or Google Sheets), and one BI tool (Tableau or Power BI). That’s what gets screened. Put those in a clean, plain-text Skills section near the top where both the parser and a skimming recruiter hit them immediately.

Don’t bury them at the bottom under hobbies. Don’t dilute them with 15 other tools nobody asked for. Three tools, stated plainly, backed up by a project that used them.

This is the whole spine of what we build inside Analyst Hive: the exact 3-tool skill set, and the portfolio projects that prove you can use it, mapped over 90 days so you’re not guessing what to learn next. Join Analyst Hive

4. USE THE SECTION NAMES THE SOFTWARE EXPECTS

Parsers look for standard headings to sort your resume into fields. “Experience.” “Skills.” “Education.” “Projects.” When you get clever and label a section “Where I’ve Made An Impact,” the parser doesn’t know what that is, and the content underneath can get misfiled or lost.

Boring headings win. And save the file as a .docx or a text-based PDF, not an image and not a flattened Canva export. A quick test: open your PDF and try to highlight and copy the text. If you can’t select it, neither can the ATS.

5. EVERY BULLET SHOULD END IN A DECISION, NOT A TASK

Once you clear the filter, a human reads the top few. This is where task-lists die. “Built dashboards in Tableau” tells them nothing. Every recruiter has read that line a thousand times.

Show what the analysis changed. “Built a Tableau dashboard that flagged the 3 regions driving 60% of churn, which shifted where the retention team spent Q3.” Now there’s a decision attached to your work, and a number attached to the decision. That’s the bullet that gets you the call.

You don’t need a big-name employer for this. A portfolio project counts, as long as the bullet ends in a decision someone could’ve made off your work.

For most data analyst roles, a human never decides you’re a no. The software filters you out before anyone gets the chance to.

So stop optimizing for the human and start optimizing for the filter standing in front of the human. Plain formatting, the posting’s exact words, the 3 tools up top, decisions on every bullet. Do that and you stop losing at a stage you didn’t even know you were playing at.

Quick reminder since it’s close: Analyst Hive is $19/month until 9/1, then $39/month. If getting past the ATS and into actual interviews is the thing you’re stuck on, that’s what the community is built to fix. Join at $19 before the 1st: Join Analyst Hive

How many data analyst jobs have you applied to, and how many actually got back to you? Reply with both numbers. I want to see the real ratio people are dealing with right now.

P.S. If your resume is a PDF you exported from Canva with icons and a skills bar, that’s the first thing to kill tonight. Plain, one column, .docx. You can rebuild it in 20 minutes and it’ll outperform the pretty one on every posting you send it to.

Talk soon,
Ian

They open a roadmap, see 14 things on it, and decide the plan is to learn all 14. SQL, Python, R, Tableau, Power BI, statistics, machine learning, a cloud certification, some Git, maybe Spark because a job posting mentioned it once. They spend 8 months grinding through tutorials for tools they’ll never touch in an entry-level role.

Then they apply, get nothing back, and assume they need a 15th tool.

Here’s what’s actually happening on the other side of that application.

A hiring manager has 300 résumés for one junior analyst opening. She’s not reading them. She’s scanning them for 15 seconds each, looking for a reason to say no. Half the candidates list 11 tools and can’t demonstrate real fluency in any of them. She’s seen the same 4 Coursera certificates 200 times this month. Nothing on the page tells her you can actually do the job on day one.

The gap isn’t that you know too little. It’s that you spread yourself across 12 tools when the job runs on 3. Depth in the 3 that matter beats a surface tour of everything. That’s the whole game, and almost nobody plays it.

Here are the 3 things, and how to prove each one.

1. SQL is the tool that gets you past the résumé screen.

Pull up 20 junior analyst postings right now and count how many require SQL. It’ll be close to 20. This is the one non-negotiable technical skill in the field, and it’s the first filter most companies apply.

You don’t need advanced SQL. You need to join tables, filter, group, aggregate, and write a subquery without looking it up. That’s a few weeks of real practice, not 8 months.

2. Excel or Google Sheets is the tool they actually watch you use.

People skip this one because it feels too basic to list. That’s the mistake. The technical interview for a lot of junior roles is somebody sharing their screen and asking you to build a pivot table, write a VLOOKUP or XLOOKUP, and clean a messy dataset live.

You don’t need both. Pick the one the companies you’re targeting use and get genuinely fast in it. Fast enough that you’re not thinking about the keyboard while someone watches you work.

3. One BI tool. One.

Tableau or Power BI. Not both. Learn one well enough to connect a data source, build a dashboard that answers an actual business question, and explain why you chose each chart.

The reason “one” matters: a candidate who knows Power BI cold reads as competent. A candidate who lists Tableau, Power BI, and Looker but can’t build a clean dashboard in any of them reads as a tutorial-follower. Hiring managers can tell the difference in about 30 seconds.

This is exactly the sequence we run inside Analyst Hive, one tool at a time, in the order that maps to how you actually get hired. Quick heads up on that, the price goes up soon. It’s $19/month right now, and that ends. Starting 9/1/26 it’s $29/month. If you’re going to join, join before then.

Join Analyst Hive

4. The 4th “thing” isn’t a tool. It’s proof you can use the first 3 together.

Three tools listed on a résumé is still just a list. What converts is one project where a hiring manager can watch you use all 3 in sequence: SQL to pull and shape the data, Sheets or Excel to clean and check it, a BI tool to turn it into something a decision-maker would actually read.

Not 6 disconnected portfolio pieces. One end-to-end project that looks like the job. That single artifact does more than any certificate on the page.

5. Every extra tool you add is working against you.

This is the part people get backwards. Listing Python, R, Spark, and 3 cloud platforms on a junior application doesn’t make you look more qualified. It makes you look like you learned the roadmap instead of the job.

Python shows up on every bloated curriculum, and for entry-level analyst roles it’s mostly noise on the résumé. It signals you spent months on something the job screen isn’t asking for while you were thin on the 3 things it is asking for. Depth reads as competence. Breadth reads as anxiety.

Cut the list to the 3 that matter and let each one be undeniable.

The candidate who gets hired isn’t the one who knows the most tools. It’s the one a hiring manager can picture doing the job on Monday.

Three tools, used together, proven once. That’s a Monday-ready candidate. Fourteen tools and no project is a roadmap-follower, and there are 300 of those in the stack already.

Analyst Hive is the community and step-by-step path for exactly this: SQL, then Sheets or Excel, then one BI tool, then the single portfolio project that ties them together and reads like a real job. No bloated roadmap, no 14-tool detour. One thing before I let you go: the $19/month price is ending. Starting 9/1/26 it becomes $29/month. Lock in $19 before 9/1 here:

Join Analyst Hive

What’s on your current “to learn” list that you now suspect is on there for no reason? Reply and tell me the tool. I’ll tell you straight whether a hiring manager cares.

P.S. If your résumé lists more than 5 tools right now, that’s not a flex. That’s the thing quietly getting you filtered out. Cut it to 3 and watch what happens.

Talk soon,
Ian

You’ve watched enough YouTube to explain what a window function does. You know what a star schema is. You could hold your own in a conversation about any of it.

Then Monday comes and you open a SQL tutorial you’ve already finished twice.

Take anyone 8 months into “learning data analytics” and ask what they worked on last Tuesday. You’ll get a specific, confident answer. A Python course. A joins refresher. A video comparing data analysts to data engineers.

Then ask how many applications they’ve sent. Usually zero. Sometimes three, all submitted in one evening, all to the same two companies, all about 6 weeks ago.

Now take someone 4 months in with a worse skill set. Weaker SQL. An uglier portfolio. Two projects instead of five. They’re employed. Months 3 and 4 got spent applying, getting rejected, fixing the one thing that caused the rejection, and applying again.

The order the steps ran in is the entire difference.

Every free resource in this space answers what to learn. Almost none answer what to do on Tuesday morning at 6am before work. That’s why people with a decade of curiosity and 200 bookmarked links still aren’t data analysts.

Courses always pay out. Applications usually don’t.

Opening a course has a guaranteed outcome. You’ll finish the video. You’ll feel sharper than you did an hour ago. Nobody tells you no.

Sending an application has a high chance of silence and a real chance of rejection. So every morning you’re choosing between a task that always pays and a task that usually doesn’t.

You’ll pick the course. Everybody picks the course. People do that when nobody’s told them what today’s job is.

The tell is how you talk about it. “I’m not ready yet” is a statement about how the last rejection felt, or how the first one might.

Roadmaps have no dates on them.

Pull up any data analyst roadmap. SQL, Excel, Python, Power BI, statistics, portfolio, communication skills. All of it’s correct and none of it tells you what today is.

It lists every skill and leaves you to work out where to start, how long to spend there, and when you’re allowed to move on.

Most people start at the top and grind SQL for 4 months, because SQL’s on the list and grinding it feels safe. Meanwhile the resume they’d actually submit is the one they wrote for a retail job in 2019.

The resume is the bottleneck.

Most people run this order: learn everything, build a portfolio, fix the resume, start applying.

A recruiter spends about 6 seconds deciding whether the rest of you exists. If that document doesn’t clear, nobody finds out you can write a window function.

Fixing a resume takes a few focused days and has a clear finish line. Getting “good enough at SQL” takes months and has no finish line at all, which is why people pick it. You can’t fail a task that never ends. You can only keep doing it.

So the skill you spent 4 months on sits behind a document you spent 40 minutes on. It’s the cheapest thing on the whole list to fix.

“Fix the resume” means something specific. Rewrite your current job in the language of the job you want. Put numbers on things you already did, because “improved reporting” and “cut a weekly report from 4 hours to 20 minutes” describe the same work and only one of them gets read. Change the line at the top to say data analyst instead of whatever your last employer called you.

None of that needs a new technical skill. Most people could knock it out this weekend and never do, because it doesn’t feel like learning.

Rejection tells you things a course can’t.

No course can tell you your portfolio project reads like a tutorial someone followed. A recruiter can, by not calling.

20 applications will expose your real gaps in 3 weeks. You find out your resume gets no responses, or that it gets responses but you freeze in the screening call, or that you clear the screen and fall apart on the SQL assessment.

Three different problems with three different fixes. You can’t tell which one you’ve got until you’re in the process.

Track it and the answer shows up fast. 30 applications and zero responses is a resume problem. 5 screening calls and no second rounds means you can’t explain your background in a way that connects to the role. Second rounds that die at the technical is the one case where the answer is more SQL.

Most people assume they’re in that third bucket. Almost nobody is.

Motivation is a bad scheduler.

Any plan that depends on you waking up and deciding what to do that day falls apart on the first bad week. A kid gets sick. Work runs long. You skip two days, feel behind, and open a tutorial instead of the hard thing, because the hard thing got heavier while you were gone.

Delete the decision. You should be able to sit down, see one task, do it, and close the laptop without ever asking yourself what you should be working on.

That’s what Analyst Hive is. 90 days, one task per day, in the order that gets people hired: resume, then SQL, then portfolio, then applications, then interviews. You open it and do today.

Analyst Hive

Nobody gives away the order.

Free content stops at the roadmap for a reason. Telling you what to learn is easy and it gets shared. Telling you what to do on day 34 means somebody had to decide what day 34 is, and be wrong about it in public if they got it wrong.

So you get every skill listed and no order to run them in. Then when it doesn’t work, the story is that you lacked consistency.

You’ve had access to everything you need for the entire time you’ve been stuck.

What’s missing is a Tuesday. A specific one, with a specific task sitting on it, that you didn’t have to invent at 6am.

Analyst Hive is 90 days of daily tasks for breaking into data. Open it, do today’s task, close it. No lectures, no roadmap to interpret, no weekly decision about what matters most right now.

It’s $19 a month, less than most people reading this have already spent on courses they didn’t finish. Members have talked to multiple recruiters and landed foot-in-the-door gigs inside their first week, because week one is applications.

If you’ve been learning data analytics for more than 6 months and haven’t applied anywhere, this is the piece you’re missing.

Analyst Hive

Reply with the month and year you first decided you wanted to be a data analyst. Just the date. I want to see how far back this goes for people.

P.S. If you read all that and thought “yeah, but I actually do need to learn more SQL first,” that sentence is the problem. It’s been telling you that for months and it’ll keep telling you that for months more.

Talk soon,

Ian

They send me the Reddit thread. 600 comments, everyone agreeing that entry level is finished, that AI ate the junior roles, that you need a master’s now. Then they close the tab, buy another course, and decide they’ll start applying once they finish it.

6 months later they’ve got more skills and the same number of interviews.

Then they send me the thread again.

Here’s what’s happening on the other side of that application.

A hiring manager posts one junior analyst role on a Tuesday. By Friday it has 400 applicants. She’s not a recruiter. She’s an analytics lead with her own reporting due, and she gives the whole pile about 90 minutes on a Monday morning.

That’s roughly 13 seconds per resume.

In those 400 she sees the same Google certificate a couple hundred times. She sees the Titanic dataset. She sees a COVID dashboard. She sees “passionate about turning data into actionable insights” in 300 different fonts.

She picks 8 people to phone screen. Every one of them is someone she could describe out loud afterwards.

So here’s my honest take. 399 of those applications were interchangeable, and that’s most of the reason they got nothing back.

Which changes what you should do next. Every hour you spend on a 6th tool is an hour you didn’t spend becoming the one applicant she can describe to her boss in a sentence.

That’s the whole game right now.

The crowding is at the entry point and nowhere else

Every one of those 400 applications exists because a company wanted an analyst badly enough to open a req and defend the budget for it. Demand is real. It’s just being met 400 times over on the first day.

Look at what happens 2 years further up. Roles asking for 2 to 3 years of experience sit open for weeks. Companies chase those people. Recruiters cold message them on a Sunday.

Same industry. Same tools. Completely different level of competition.

The first 18 months are the hard part, and after that the same market starts working in your favor. So everything you do right now should be pointed at getting through the door, not at looking impressive once you’re already inside.

More skills won’t fix a saturation problem

The instinct after a rejection is to assume you were underqualified. So you go add something. Python. Then a bit of machine learning. Then cloud. Then statistics, properly this time.

All 400 of those applicants had the same instinct.

The technical bar for a junior analyst hasn’t moved in years. SQL you can write under pressure, joins and window functions included, without a tab open. Excel or Sheets you know cold. One BI tool you can build in without a tutorial running on the second monitor. That’s the bar.

Most people who think they’re past that bar aren’t. They can follow a SQL tutorial and they’ve never written a query against a table they didn’t design, with 3 columns that mean the same thing and no documentation. That’s the version that gets tested.

Everything you stack on top of it just makes you later. An 11 item roadmap costs you 6 months and doesn’t change a single screening decision.

The people getting hired stopped learning at the right point and moved on to the part that actually gets judged.

Your project has to end in a decision

A project that ends with “here’s a dashboard” gives the hiring manager nothing to say about you. She’s seen a dashboard today. She’s seen 4.

A project that ends with “based on this, the business should stop spending on X and move that budget to Y, and here’s roughly what that’s worth” gives her a line she can repeat to somebody else. That’s the whole mechanism. Whoever she can quote in the hiring meeting is whoever gets the interview.

The difference shows up at the very start, in the question you pick. “Analyzing Airbnb listings in Barcelona” produces charts. “Which listings should raise their price and by how much” produces a recommendation, and it forces you into the messy parts on the way there: what counts as comparable, what you do about the 11% of rows with no review data, which assumption breaks the whole answer if it’s wrong.

Those are the parts an interviewer can actually question you on. Nobody asks a follow-up about a bar chart.

2 of those is enough. I’d take 2 where you can defend every assumption over 6 built from a tutorial that you can’t explain when someone pushes on them.

This is the part people get wrong most often, and it’s exactly what I walk through inside Analyst Hive: how to pick a question a real business would pay to have answered, and take it through to a recommendation somebody could act on this quarter.

Join Analyst Hive

Apply before you feel ready

Waiting until you feel ready is the most expensive decision available to you, and it’s free at the moment you make it, which is why everyone makes it.

Applying is its own skill with its own learning curve. Writing about your projects so a non-technical manager cares. Answering “walk me through a time you were wrong” without freezing. Handling a live SQL screen while somebody watches your cursor move. You get better at all 3 by doing them badly a few times.

6 months of applying while you learn beats 6 months of learning and then applying. Same calendar, and at the end of it you’ve got a rejection pile telling you exactly which gap to close.

There’s also a timing thing nobody mentions. That 400 applicant post is what a job looks like after it’s been sitting there 3 days. The same role on day one has 40. Being early is most of the edge, and you can’t be early to anything while you’re still finishing a course.

Start applying at the point where you can write SQL, use one BI tool, and defend 2 projects.

Pick an industry

Everybody differentiates on tools. Almost nobody differentiates on domain.

Being the person who understands how a subscription business loses money, or how retail inventory behaves in Q4, is worth more than any tool you could add this month. It changes what your projects are about, what your questions sound like in an interview, and which roles you’re the obvious fit for instead of the 200th option.

It costs you a decision and nothing else. Pick the industry you already know something about from a previous job, or the one hiring most where you live. Read a few of their quarterly reports and 3 or 4 job postings, and write down the 5 metrics that keep appearing. Churn, basket size, occupancy, whatever it is for that industry. Build your 2 projects around those metrics.

That’s a weekend of reading, and it puts you in a smaller pile immediately. You stop being applicant 200 for every analyst role in the country and start being one of maybe 20 people who applied to a logistics company already talking about on-time delivery rates.

That’s the difference between the 8 she screened and the 392 she didn’t.

Hiring at this level runs on whether one person can describe you in a sentence. Everything else is downstream of that.

A crowded market rewards going narrow and applying early. Everybody else is going wide and starting late, which is exactly why it works.

Analyst Hive is the community and the 90 day sequence I built for this problem. It cuts the roadmap down to the few things junior hiring actually turns on, walks you through building 2 projects that end in a real recommendation, and gets you applying while you’re still building instead of 6 months after. If you’re stuck in the loop of another course, another tool, another month, this is the way out. Join here:

Join Analyst Hive

Now I want a number from you. Reply with how many applications you’ve sent and how many first round interviews came back. Just the 2 numbers, not the story around them. I want to see what the real ratio looks like across this list.

P.S. If your first reaction to point 2 was “yeah, but Python”, notice that you argued with the skill list and skipped straight past the part about applying 6 months late. That’s the actual tell.

Talk soon,
Ian

You find a roadmap. It has Excel, SQL, Python, R, Tableau, Power BI, statistics, probability, linear algebra, machine learning, cloud, and Git on it. You start at the top. You promise yourself you’ll apply once you’ve worked through it.

Eleven months later you’re halfway down the list and you haven’t sent a single application.

Here’s what that looks like from the other side.

A hiring manager posts one junior analyst role and gets 400 applications in six days. First pass, she’s giving each resume about nine seconds, and she’s looking for two things: has this person written SQL against a database that wasn’t a tutorial, and can they explain a number to somebody who doesn’t care about the number.

She has seen the Titanic survival predictor at least 15 times this month. She has seen the same COVID dashboard closer to 30. Your machine learning section doesn’t move her, because the role has no machine learning in it and she knows the pipeline was copied

Nothing you learned in months four through eleven changed her decision.

And if you do get through, the interview is three SQL questions, one “walk me through a project,” and one “explain this result to a stakeholder who thinks it’s wrong.” That’s it. That’s the test you spent a year studying for.

The gap isn’t between what you know and what you should know. It’s between what gets taught and what gets tested.

A curriculum is built to be complete. An interview is built to be fast. Almost everything you study to feel prepared gets zero airtime in the 30 minutes that actually decide it.

That’s the whole game. So here’s the 20% I’d keep if I started over.

1. SQL UNTIL IT’S BORING, THEN STOP COLLECTING TOOLS

Learn SQL until joins, CTEs, and window functions are muscle memory. That’s the bar for most junior roles and it’s higher than people think, because “I know SQL” usually means “I can write a SELECT with a WHERE.”

Boring means you can write a query that ranks customers by spend within each region, without looking anything up and without going quiet about it on a screen share. Most candidates can’t. That one gap decides more junior interviews than every other item on the roadmap combined.

After that, one spreadsheet tool and one BI tool. Excel or Sheets, because the request will arrive as a spreadsheet whether you like it or not. Then Tableau or Power BI, whichever shows up more in the jobs you’re actually applying to. Learn it over a weekend and move on.

Not both BI tools. The second one takes four hours to pick up later, once you have a job and somebody’s paying you to sit through it. Adding it now buys you a bullet point nobody reads and costs you a month

2. SKIP 90% OF THE STATISTICS

You will not use calculus. You will not use linear algebra. You will not derive anything.

What you’ll use weekly: percent change, the difference between an average and a median, sample size, and the instinct to know whether a spike is a real move or a broken tracking tag.

The statistics that matters in a junior job is mostly the ability to say “that number looks wrong” and then be right. That gets built by staring at messy data, not by working through a probability textbook.

Here’s the version of that you’ll actually run into. Average order value jumps 40% overnight. The finance team is thrilled. You look, and it’s one B2B order of 900 units sitting inside a dataset of consumer purchases. The median didn’t move at all. Catching that in ten minutes is worth more to your team than anything you’d learn in a semester of probability.

Skip the semester. Learn the four things. Come back for the rest if a job ever asks, which it probably won’t for two years.

3. SKIP MACHINE LEARNING ENTIRELY

Every roadmap ends with machine learning because it’s the exciting part. It’s also the part junior analysts never touch.

Your first job is pulling numbers, cleaning them, and explaining to someone in marketing why last week was down. There’s no model in that. There’s a lot of “why do these two tables disagree.”

A random forest on your resume tells a hiring manager you followed a tutorial. A clean, documented query that answers a business question tells her you can handle a Tuesday.

The counterargument is always “but I want to become a data scientist eventually.” Fine. The fastest route there is two years inside a company with access to real data and people who’ll teach you, and you get in the door on SQL and communication, not on a notebook you can’t defend line by line.

4. TWO PROJECTS, BOTH ENDING IN A DECISION

Not eight projects. Two.

What separates a project that works from one that gets scrolled past is whether it ends in a recommendation somebody could act on. “Here’s a dashboard of Airbnb prices in Lisbon” gets scrolled past. “Here are the two neighbourhoods a new host should list in, here’s the nightly rate that breaks even, and here’s what it costs them if I’m wrong” does not.

Pull the data yourself so it’s messy. Write your assumptions down where the reader can see them. Say what you’d check next with another week.

This is the build the 90-day sequence in Analyst Hive walks you through, because the decision-led project is the one piece of a portfolio that survives contact with a real interview:

Join Analyst Hive

5. SKIP EVERY CERTIFICATE AFTER THE FIRST

One is fine. It gets you past the “does this person know what a database is” filter and gives you a structure while you’re starting cold.

The second one signals you got nervous and bought something. The fifth signals you’ve been studying for a year and hiding from the application form

Look at that enrollment number and then ask yourself how it differentiates you from the other 399 applicants. Certificates are the cheapest line on a resume to verify and the least interesting thing to ask about. No hiring manager has ever built an interview question around a Coursera badge.

6. SKIP THE “NOT READY YET” PHASE

This is the expensive one.

Most people spend months four through twelve learning, because applying is uncomfortable and learning feels like progress. Same energy as cleaning the kitchen instead of doing your taxes.

Apply at month three. You’ll be bad at it. That’s the point. Fail four interviews and you’ll learn more about what the job actually tests than any course will teach you, because you’ll hear the real questions in the real order from the people who make the decision.

Then you go back and study the specific thing you fumbled, which takes a week, instead of studying everything, which takes a year.

The rejections are the curriculum. They’re just free, so nobody sells them to you.

None of the 80% is wrong. That’s what makes it dangerous. It’s all real, useful, defensible knowledge that pays off eventually.

It just doesn’t pay off now, and you’re not being judged on eventually.

The curriculum is infinite. The hiring process is 30 minutes. Choosing what to ignore is the first analyst skill you’ll ever use, and it’s the one they’re actually testing.

Analyst Hive is a 90-day sequence built out of the 20%. SQL to the depth that gets used, two portfolio projects built around a decision, the interview answers written out, and an application process that starts in week three instead of month twelve. There’s no machine learning module, no statistics semester, no fifth tool, because none of it gets you the first job. If you’ve been learning for eight months and still haven’t applied to anything, this is the thing that ends that:

Join Analyst Hive

Reply and tell me the one thing you’ve sunk the most hours into that has never once come up in an interview. I read every reply, and those answers are usually what I cut next.

P.S. If your first reaction to this was “but what if they ask me about machine learning,” that reaction is the 80% talking. Go count how many junior postings you’ve seen this month that even mention it.

Talk soon,
Ian

So they add Python. Then dbt. Then a Tableau cert, then a cloud cert, then a machine learning course they abandon at week three.

Two years later the skills section is twice as long and the number on the offer letter hasn’t moved.

I want you to look at this from the other side of the desk for a second.

Picture a director of analytics with four analysts. Same warehouse access, same BI tool, roughly the same SQL. Her intake board takes about 60 requests a quarter and all four of them close their tickets on time.

Three of those analysts she sends tickets to. The fourth one she pulls into the planning meeting before the tickets exist.

That fourth analyst is not better at window functions. He’s in the room because when someone asks him for a churn dashboard, he asks what they’re going to do differently depending on what the number says. Roughly half the time, that one question kills the dashboard and replaces it with a smaller piece of work that answers what the person actually wanted to know.

He saves her thirty hours a quarter of building things nobody opens. That’s why he’s in the meeting, and that’s why he got promoted twice while the other three got cost of living adjustments.

The gap between a $60k analyst and a $150k analyst is not technical. Both of them can write the query. One delivers a number, and the other changes a decision.

Everything a company pays a premium for lives in that space: taking a vague request, working out which decision it feeds, and answering the decision instead of the request.

That’s the whole game. Here’s what it actually looks like day to day.

1. THEY FIND THE DECISION BEHIND THE REQUEST BEFORE THEY OPEN THEIR EDITOR.

“Can you pull churn by region for last quarter?” is never the real question. The real question is closer to “should I keep funding the West team?” or “do I have a product problem or a sales problem?”

Two questions get you there. What are you going to do with this? And what number would change your mind?

The second one is the one nobody asks. It tells you the threshold that matters, which tells you the precision you need, which usually tells you the four-hour version is fine and the two-week version was never necessary.

Junior analysts think this makes them look slow. It does the opposite. It’s the single fastest way to sound like the most senior person on the thread.

It also protects you from the worst outcome in this job, which is delivering exactly what was asked for and watching it get ignored. That happens when the request was a guess at what would help and you treated it as a spec.

2. THEY CONVERT EVERYTHING INTO DOLLARS.

“Conversion dropped 3%” gets a nod in a meeting. “Conversion dropped 3%, which is about $180k a quarter at current traffic” gets budget, headcount, and your name attached to the fix.

Nobody funds a percentage. Percentages are trivia until someone does the multiplication, and the person who does the multiplication is the person the room turns to next time.

You don’t need a finance background for this. You need the average order value, the traffic number, and a willingness to say “roughly” out loud. Directional and stated beats precise and unsaid, every time.

This is also the exact skill that fixes a resume, which is why almost nobody’s resume works. “Built dashboards in Tableau” is a percentage-level bullet. “Rebuilt the ops dashboard, cut weekly reporting time from 6 hours to 40 minutes across a 12-person team” is a dollar-level bullet, and it’s the same project. Month 1 of Analyst Hive has you rewriting every bullet you own this way, with a metrics bank so you’re not staring at a blank page trying to invent numbers you don’t have.

The fastest way to break into data no matter where you’re at (built by me!)

Join Analyst Hive

3. THEY LEAD WITH THE ANSWER AND BURY THE METHOD.

The $60k version of an update walks through the process. Where the data came from, what got cleaned, which joins were involved, what got excluded, then the finding at the bottom like a reveal.

The $150k version is one line at the top: here’s what I found, here’s what I’d do, here’s what I’m not sure about. Everything else goes below, for the two people who’ll actually read it.

The tell is the first sentence. If it starts with “so I pulled” or “I joined the” or “after filtering out,” you’re writing for yourself. If it starts with a recommendation, you’re writing for the person who has to act.

Nobody skips your methodology because they don’t respect it. They skip it because they have nine minutes before their next meeting and they need to make a call. Structure for that and you start getting invited to the calls where decisions get made.

This is what I used to send

What I send now

4. THEY NAME THE HOLES IN THE DATA BEFORE ANYONE ELSE FINDS THEM.

Analysts hide caveats because they think a caveat looks like weakness. Then someone in the meeting spots the double-counted refunds, and now every number that analyst produces gets a second look forever.

Say it first. “Heads up, this excludes trial accounts, and if we counted them the number is closer to 8%.” Thirty seconds of admitting limits buys you months of people accepting your numbers without checking.

There’s a version of this that goes further and it’s the one that gets people promoted. Tell them what the data can’t answer at all. “This tells you where churn happened. It won’t tell you why, and if why is what you need, I’d rather call ten of these accounts than build you another cut of this.”

Trust compounds faster than skill does. An analyst everyone trusts at 80% accuracy gets pulled into strategy. An analyst nobody trusts at 99% accuracy gets sent tickets.

5. THEY GO BACK AND CHECK WHETHER THE DECISION ACTUALLY CHANGED.

Almost nobody does this. The analysis ships, the ticket closes, and everyone moves on with no idea whether the work mattered.

Two weeks later, ask. Did you end up shifting the budget? Did the West team change anything? What happened?

It costs you one message. It is also the only way you ever find out whether your instincts are good, because otherwise you’re guessing at your own accuracy for your entire career.

Half the time the answer is that nothing happened, which is genuinely useful information about which of your work is decorative. The other half, you now own a real outcome with a real number on it, and that outcome is what you say in your next interview, your next review, and your next negotiation.

That’s the difference between “I built dashboards for the sales org” and “my analysis moved $400k of spend out of a channel that wasn’t converting.” Same job. One of them is a story with an ending.

There is no salary band for producing numbers. There is a very large one for being the reason a decision was right.

The query is the cheap part. The question is the job. Every tool on your list is a way of executing an answer, and executing answers is the part that gets cheaper and more automated every year. Deciding which question was worth answering is the part that doesn’t.

If you’re stuck at the ticket-closing tier and you don’t know what to do next, that’s what Analyst Hive is for. It’s a 90-day sequence with a task for every single day: what to build, what to rewrite, who to message, how to talk about your work so it reads as decisions instead of dashboards. No course to binge and no curriculum to guess your way through. You open it, you see today’s task, you do it, you close it.

There’s nothing like this in the data world

Join Analyst Hive

Now I want one from you. Reply with the last request you got that you should have pushed back on. What did they ask for, and what did they actually need? I read every reply and the best ones usually turn into future issues.

P.S. Quick way to find out where you currently sit. Count how many of your last ten requests you asked a single follow-up question about before starting. That number is closer to your salary band than your skills section is.

Talk soon,
Ian

You’re still not getting interviews. Or you’re getting them and freezing anyway.

So you go back and grind more SQL, because clearly the problem is you don’t know enough.

The problem is you’re studying the wrong 80%.

Here’s what an actual SQL screen looks like from the other side of the table. I’ve watched enough of these to know the pattern. Three questions. Two of them are a JOIN and a GROUP BY with a filter. The third is a slightly harder aggregation, maybe a window function if the company is fancy. That’s the whole test.

The candidate who spent two months on recursive CTEs and pivot logic sits down, gets asked “pull total revenue by month for customers who signed up in Q1,” and stares at it. Not because they can’t write a GROUP BY. Because nobody ever made them turn a sentence like that into a query. They practiced answering SQL questions. They never practiced answering business questions with SQL.

That gap is the entire job. The syntax is the easy part and everyone treats it like the hard part. Knowing SQL and using SQL to answer a question someone actually asked are two different skills, and only one of them shows up on your resume screen.

Let me break down how much you actually need.

1. The job runs on about six things, and you already half-know them.

SELECT. WHERE. JOIN, mostly LEFT and INNER. GROUP BY with aggregates like SUM, COUNT, and AVG. A couple of window functions, usually ROW_NUMBER and a running total. CTEs to keep long queries readable.

That’s the core. That combination handles the overwhelming majority of real analyst work. Not 60% of it. Closer to 90.

The stuff you’re intimidated by lives in the last 10% and you will Google it the two times a year it comes up, same as every senior analyst does.

2. Advanced SQL is a lookup, not a prerequisite.

Recursive queries. PIVOT and UNPIVOT. Correlated subqueries. Performance tuning. Every one of these is real, and every one of them is something you look up when a specific problem demands it.

You do not need to hold them in your head to get hired. No hiring manager is quizzing a junior candidate on query execution plans. If one does, that’s a signal about the company, not about you.

The senior people you’re trying to become do not have this memorized either. They have it bookmarked. The difference between them and you isn’t recall. It’s that they know a recursive CTE is the right tool for the org-chart problem in front of them, then they go look up the syntax.

Let’s take a real example and break it down: "Show me the top 5 customers by revenue in the last 90 days, excluding refunds."

The query to answer this is…

Seems a bit long for a simple questions but let’s do this together.

• “top 5” is answered by the ORDER BY total_revenue DESC + LIMIT 5

• “customers” is answered by the JOIN customers c ON … (the revenue lives in orders, the names live in customers, so you join!)

• “by revenue” is answered by SUM(o.amount) AS total_revenue + the GROUP BY c.customer_name

• “in the last 90 days” is answered by WHERE o.order_date >= CURRENT_DATE - INTERVAL '90 days'

• “excluding refunds” is answered by AND o.status != ‘refunded’

3. The actual test is translation, and almost nobody practices it.

Here is the skill that separates people who pass SQL screens from people who don’t: reading a vague, half-specified business question and knowing which tables, joins, and filters it maps to.

“Which products are underperforming this quarter” is not a SQL question. It’s a question you have to interrogate first. Underperforming compared to what. Which quarter. Do returns count. Is a product a SKU or a category. By the time you’ve answered those, the query writes itself. The SQL was never the hard part. The thinking in front of the SQL was.

You can drill this. Take a schema, generate business questions against it, and write the query for each one out loud before you touch the keyboard. Do that fifty times and interview questions stop feeling like traps.

This is literally what the SQL block of the 90-day sequence walks you through, one business question mapped to one query at a time, so translation becomes automatic instead of the thing you freeze on.

Join Analyst Hive

4. Depth on the core beats breadth across the syntax.

Knowing JOINs cold beats knowing forty functions at surface level.

Most people who “know SQL” fall apart the moment a query needs three joins and one of them is a LEFT JOIN where the null handling actually matters. They can name every join type. They can’t reason about what happens to their row count when the join fans out.

That’s the depth that shows. An interviewer can tell in one question whether you understand what a JOIN is doing to your data or whether you just memorized the keyword. Go deep on the six core things until you can predict the shape of the output before you run it. That’s worth more than another twenty functions you’ll never use.

5. On the job, you inherit SQL. You rarely write it from scratch.

This is the part no tutorial prepares you for. Day one at a real job, you’re handed a 200-line query someone wrote two years ago and told to figure out why the numbers look off.

You will spend more time reading other people’s SQL than writing your own. Messy SQL, undocumented SQL, SQL with a CTE named “temp2.” The skill is following someone else’s logic and spotting where it breaks, not composing an elegant query on a blank page.

• At the left join order_items oi line → “This is where the number breaks. Joining to order_items multiplies every order row by its number of line items. An order with 4 items now counts its revenue 4 times.”

• At sum(t.amount) → “So this SUM is inflated. It’s adding the same order amount once per line item, not once per order.”

• At the temp2 CTE → “temp2 does nothing. It’s a copy of temp1. Dead code you inherit and have to read past anyway.”

• At where order_date >= '2024-01-01' (optional) → “No upper bound. Is this supposed to be one year or everything since? Nobody documented it.”

Practice reading SQL, not just writing it. Pull real queries off GitHub or dbt project repos and trace what they do. It’s unglamorous and it’s exactly what the job is.

6. Knowing when your answer is wrong is the senior skill.

Anyone can write a query that returns a number. The number being right is a separate question.

A junior analyst runs the query, sees 4,812, and reports 4,812. A good analyst runs it and immediately asks whether 4,812 is even plausible. Should this be in the thousands or the millions. Did that LEFT JOIN just double my rows. Is this suspiciously round.

That instinct, sanity-checking your own output before anyone else has to, is what makes people trust your work. It is also completely absent from every SQL course, because courses give you problems with known answers. The job gives you problems where you’re the only check.

So how much SQL do you actually need? Enough to answer a real question and enough to know when your answer is lying to you. That’s a much smaller pile of syntax and a much bigger pile of judgment than the tutorials sold you.

The people getting hired aren’t the ones who know the most SQL. They’re the ones who can sit down in front of a messy schema and a vague question and produce a number they’d stake their name on.

If you want the version of this that’s already sequenced, Analyst Hive is a 90-day daily-task system that takes you from tutorial SQL to job-ready SQL, one task a day, built around exactly the translation and depth work above instead of another list of functions to memorize. It’s for people who are tired of grinding syntax and still freezing in interviews. If that’s you, start here:

Join Analyst Hive

What’s the SQL question that tripped you up in an interview or on the job? Reply with the actual prompt, I want to see which ones are still catching people.

P.S. If you’re currently three window functions deep into a course and quietly panicking that it’s not enough, close the tab. You’re past the point of diminishing returns. Go write ten queries against a real dataset instead.

Talk soon,
Ian

Forty people answer. Half say it changed their life. Half say it’s a scam. Almost none of them have ever screened a resume for an analyst role.

So here’s the version from the other side of the table.

The standard path looks like this. You enroll. You watch the videos at 1x. You take six months because life happens. You finish the Cyclistic case study, you add the badge to your LinkedIn banner, you flip on Open to Work, you apply to 200 jobs.

Then you wonder why nobody’s calling.

Picture the person on the other end of those applications. One open entry-level analyst req, 300 applicants in the ATS, and about seven seconds per resume before a decision gets made. In that stack, the Google certificate shows up again and again. So does the same bike-share case study, the same three charts, the same conclusion about casual riders versus annual members.

By resume 40 she isn’t reading the certificate line anymore. Her eye has learned to skip it the same way you skip a cookie banner.

That’s not a knock on the course. It’s arithmetic. Anything a few hundred thousand people can complete on the same schedule stops being a differentiator the moment it gets popular.

Here’s the actual gap. The certificate teaches you a curriculum. Hiring is a comparison.

Finishing a curriculum proves you can follow instructions for six months. It says nothing about whether you’d be useful on a Tuesday when two dashboards disagree and somebody has to figure out which one is lying.

That gap is the whole game.

1. IT’S A SYLLABUS, NOT A CREDENTIAL.

Treat it as a reading list and it’s genuinely useful. Treat it as a qualification and you’ve handed your job search to a line that four other people in the same stack already have.

The tell is where people put it. If the certificate sits at the top of your resume, above your projects and above your work history, you’ve told the reader it’s the strongest thing you own. She will take you at your word and rank you accordingly.

Move it to one line at the bottom. Nothing about your candidacy changes. What changes is what the first seven seconds land on.

The comparison she’s making isn’t “certificate versus no certificate.” It’s you versus everyone else who finished the same one, and that gets settled entirely by what sits above the certificate line.

2. IT WEIGHTS THE TOOLS WRONG FOR THE JOBS YOU’RE APPLYING TO.

The course spends heavy time on spreadsheets, heavy time on Tableau, and a full course on R. SQL gets a fraction of the runtime.

Go open 20 real entry-level postings and tally the tools yourself. Not the ones you wish existed. The 20 in your metro or remote that you would actually apply to today. SQL will be on nearly every one. R will show up on a handful, mostly in research and biotech. Excel and a BI tool will be everywhere.

The proportions inside the course and the proportions in the market do not match, and the market is the thing interviewing you. Nobody has ever been asked to open R or Python in an entry-level analyst interview. People get asked to write a join under time pressure constantly.

Look at the course list. Nine courses, and none of them are named after SQL.

That doesn’t make the course bad. It makes it incomplete in a way that’s invisible while you’re inside it, because everything feels productive when a progress bar is moving. You can spend three weeks on R and finish further from a job than when you started, and nothing in the interface will tell you.

3. THE CAPSTONE IS THE PART THAT ACTUALLY HURTS YOU.

Most of the certificate is neutral at worst. The shared capstone is negative.

When you submit the same case study, on the same dataset, answering the same questions the course handed you, you’re submitting evidence that you can execute someone else’s assignment. The reviewer has already seen the answer. She knows which decisions were yours and which ones the course made for you, and the honest count is close to zero on the first list.

The fix isn’t a harder dataset. It’s owning the question. Pick a topic you can get genuinely messy data on, write the question yourself, and be ready to explain why you cut the rows you cut. A scrappy project on a boring subject you scoped yourself beats a polished one you were handed, because only one of the two shows judgment, and judgment is the entire thing being hired for.

If you keep the capstone anyway, don’t lead with it, and never present it as your best work. It’s a homework assignment with good branding.

The test for any portfolio project is simple. Can you name a decision you made that a reasonable person would have made differently, and defend it? If the answer is no, the project isn’t yours yet.

4. SIX MONTHS OF LEARNING WITH ZERO APPLYING IS THE REAL PRICE.

The tuition isn’t the money. It’s the six months you spent as a student while telling yourself you were preparing.

The people who get hired run both tracks at once. They’re sending outreach in week two, not after graduation. They rewrite the resume in month one, then again in month two once they’ve seen what the postings actually ask for. They’re getting rejected early enough that the rejections still have time to teach them something.

Waiting until you feel ready is the most expensive habit in this whole field, and a course with a completion certificate at the end is perfectly designed to feed it. There’s always one more module.

That’s the reason I built Analyst Hive as a daily sequence instead of another course. One task a day for 90 days, and outreach and applications start in the first week, not after some finish line.

Join Analyst Hive

5. WHEN IT IS ACTUALLY WORTH IT.

Here’s the fair version, because the certificate does have a real use.

If you’re starting from absolute zero, if you don’t know what a join is or what a dashboard is for or what an analyst does between 9 and 5, the course gives you vocabulary and a map. That’s worth something real. Vocabulary is what lets you read a job posting and understand what’s being asked of you, and you can’t fake your way past that step.

So use it that way. Four to six weeks, not six months. Watch at 1.5x. Skip the reflection prompts. Do the SQL sections twice and everything else once. Replace the capstone with your own project. Put it on one line at the bottom of the resume and don’t bring it up in an interview unless someone asks.

Used like that, it’s a month-long head start. Used the other way, it’s a six-month waiting room with a certificate at the exit.

Same course. Same content. The difference is entirely in what you do with the calendar around it.

The certificate is the syllabus. The interview is the exam. Nobody grades attendance.

Every entry-level analyst who gets hired had to prove one specific thing: that they can take an unclear question, get their hands into imperfect data, and come back with an answer somebody can act on. No course does that for you. The best one can do is put you in a position to demonstrate it, and then you have to go and actually demonstrate it.

Analyst Hive is a 90-day daily-task operating system for people trying to break into data analytics. Not a course, not a bootcamp, not another video library. One task a day, in order, covering SQL, portfolio, resume, LinkedIn, outreach, applications, and interviews, so you never open your laptop wondering what to work on. It exists because the certificate ends and leaves you standing in the parking lot holding a badge. This is the part after.

Join Analyst Hive

If you finished the certificate, hit reply with two numbers: how many months it took you, and how many interviews you’ve gotten since. I want to see the real spread, not the testimonials.

P.S. The people defending the certificate hardest in comment sections are almost always still in it. The ones who got hired talk about their projects.

Talk soon,
Ian

They buy another SQL course. They watch three hours of it. They tell themselves this is the year, then open a new tab and start the exact same thing they abandoned in March.

Ninety days later they’ve learned a little more SQL and applied to nothing.

I’ve watched this loop from the inside, and I ran it myself once. I broke into analytics with no degree and no permission, and the thing that finally worked wasn’t more learning. It was a sequence. So here’s the real question people should be asking: if I had to wipe my progress and start completely over in 2026, knowing what I know now, what would I actually do for 90 days?

Not what would I learn. What would I do, day by day, to be employable by the end of it.

Here’s the exact plan.

1. WEEK ONE IS RESUME AND LINKEDIN. NOT SQL.

Everyone gets the order backwards. They spend two months learning tools before anyone can find them, then wonder why the skills never turned into interviews.

If I started over, day one is a resume that survives an ATS scan and a LinkedIn profile that reads like an analyst instead of “aspiring data enthusiast on a journey.” Because the moment I start building projects in week three, I want a place to put them that’s already set up to be seen.

This is boring and unglamorous and it’s why most people skip it. It’s also the part that decides whether any of the later work gets looked at. A perfect portfolio pointed at a dead profile is a tree falling in an empty forest.

2. I’D LEARN SQL BY BUILDING, NOT BY WATCHING.

I would not touch a 12-hour SQL course. I’d learn the joins, the aggregations, and the window functions I actually need, then immediately point them at a real messy dataset and answer a real question.

The difference between someone who “did the SQL course” and someone who can do the job is that the second person has queried data that didn’t come pre-cleaned in a tutorial. Nobody hands you a spotless table at work. You get duplicate rows, nulls where there shouldn’t be nulls, and a column called “date” that stores dates in four different formats. The whole skill is dealing with the mess.

So every concept I learned, I’d apply the same day to something ugly. Watch a 20-minute explanation of window functions, then go rank real customers by real spend in a real dataset before I close the laptop. Learning and doing collapse into one step. That’s the pace that gets you hired in months instead of years, because you’re not accumulating knowledge you can’t demonstrate. You’re accumulating things you’ve actually done.

3. ONE PORTFOLIO PROJECT THAT ISN’T THE TITANIC DATASET.

A hiring manager who’s screened 40 portfolios this month has seen the Titanic survival predictor at least 15 times. It signals one thing: this person followed the same free tutorial everyone else did. Same with the Iris flowers and the stock-price line chart. The moment they recognize the dataset, they stop reading.

If I started over, my portfolio would have one project built around a question someone would actually pay to answer. Pick an industry, find its real data, and answer something a manager in that industry would nod at. Why do customers churn after month three. Which store locations are quietly losing money. One strong project built around a real business question beats five copy-paste notebooks, every time.

And I’d write it up like I’m explaining it to a non-technical boss, because that’s the actual job. Lead with the answer, then show the work. The analysis is half of it. Communicating what it means to someone who doesn’t care about your code is the half that gets you promoted.

4. I’D APPLY BEFORE I FELT READY. ON PURPOSE.

The instinct is to wait until the portfolio is perfect and the skills feel complete. That day never arrives. The people who wait are still waiting a year later, more skilled and just as unemployed.

Applying early does two things. It tells you exactly which skills the market wants right now, from real job descriptions instead of a course syllabus from 2021. If every posting in your city asks for Power BI and your portfolio is all Tableau, you want to know that in week five, not week fifteen.

And it gets you reps at the part everyone’s worst at: the interview. Your first interview is going to be rough no matter when you take it. Better to spend that roughness on a job you’re lukewarm about than on the one you actually want three months from now.

This is exactly what the middle stretch of the 90 days walks through, day by day, so you’re not guessing when to pivot from building to applying. It tells you which day to start sending applications and what to send.

Join Analyst Hive

5. NETWORKING, BUT NOT THE CRINGE KIND.

I would not send “I’d love to pick your brain” messages to strangers. Those get ignored, and they should. I’d post what I’m learning, publicly, consistently. That’s networking that scales while you sleep.

Every project, every thing that clicked, every ugly dataset I wrestled into shape becomes a short post. Do that for 90 days and you’ve built an audience of people in the field who now recognize your name. Some of them do the hiring. A few of them will message you about a role before you ever apply to it.

I built my entire path on this. The posts weren’t self-promotion and they weren’t polished. They were proof of work, in public, on a schedule. People don’t refer strangers. They refer the person whose learning they’ve been watching for two months.

6. MONTH THREE IS INTERVIEW REPS, NOT MORE TUTORIALS.

By the final stretch I wouldn’t learn a single new tool. I’d drill the interview: the SQL live-coding, the STAR stories, the “walk me through a project,” and the salary conversation people fumble and leave real money on the table over.

Most candidates prepare for interviews by doing more of the thing that’s comfortable, which is learning. Then they get in the room and can’t explain their own project out loud. They freeze on a query they’d have written easily at home, because they never practiced writing it while someone watched.

The reps that matter in month three are performance reps, not knowledge reps. Say your project story out loud until it’s smooth. Rehearse the number you’ll give when they ask about salary. The offer doesn’t go to the most skilled person. It goes to the person who was clearly the least risky hire in the room.

The point of all of this

Notice what’s missing from these 90 days: there’s no month spent “getting the fundamentals down” before anything real happens. Every single week produces something a hiring manager could see.

Learning isn’t the bottleneck. It never was. The bottleneck is turning what you learn into evidence, fast enough that you’re employable before you burn out and quit again in March.

You don’t need another course. You need a sequence that tells you what to do today.

That’s the entire reason Analyst Hive exists. It’s not a course and it’s not a community you scroll for motivation. It’s the exact 90-day sequence above, broken into a task for every single day, so you never open your laptop and wonder what you’re supposed to be doing. Stop buying information. Buy the sequence, and spend the next 90 days executing instead of guessing.

Join Analyst Hive

If you were starting over in 2026, what’s the one thing you’d refuse to waste time on this time around? Reply and tell me. I read every one.

P.S. The reason week one is resume and not SQL is that I did it in the wrong order myself the first time. Spent months getting “ready” for a stage nobody had invited me to yet.

Talk soon,
Ian

Half say the field is saturated and AI is coming for it. Half say demand has never been higher and now is the perfect time to start. Almost every one of them is written by someone selling a course.

So you read all forty. Then the Reddit threads. Then two YouTube videos with opposite conclusions and the same thumbnail. Then you decide you’ll start once you have a better read on where things are heading.

That was six months ago.

Here is what “saturated” actually looks like from the other side of the desk.

A hiring manager posts an entry-level analyst role on a Monday. By Wednesday there are 400 applications. She opens the first forty. Thirty of them have the same certificate, the same three-dashboard portfolio, and the same summary line about being passionate about turning data into insights. Four analyzed the same Netflix dataset. Two used the same Tableau template, down to the color palette.

She is not rejecting those people because the field is dead. She is rejecting them because she cannot tell them apart and she has 360 more to get through.

That is the whole issue in one scene. The field is fine. The on-ramp broke. And it broke because it got easy, not because it got hard.

That distinction decides everything you do next. If demand collapsed, the correct move is to leave. If supply exploded, the correct move is to stop looking like the supply. Same headline, opposite responses.

Here is what actually changed.

1. THE DEMAND SIDE NEVER MOVED

Companies did not stop needing people who can answer questions with data. The Bureau of Labor Statistics projects 34% growth for data scientists and 7% for market research analysts between 2024 and 2034. The World Economic Forum’s 2025 Future of Jobs report put data roles at five of the fifteen fastest-growing jobs. Glassdoor puts the average US data analyst salary around $82,000 in 2026. 365 Data Science

Those are not the numbers of a dying field. Nobody writes “is welding still worth it” posts about a job paying $82,000 with a decade of projected growth ahead of it.

If you are waiting for demand to come back, it never left. Nothing in the last two years suggests a company somewhere decided it would prefer to run on vibes.

What people are actually noticing when they say the market is dead is that they applied to 60 jobs and heard nothing. That is real. It is also not a demand signal. It is a sorting signal.

2. WHAT EXPLODED WAS THE SUPPLY

Search volume for data courses peaked in 2025. Bootcamps, certificates, university programs, and AI-generated learning paths all did exactly what they promised. They lowered the barrier to entry. Analythical

That worked. That is the problem. The result is that a hiring manager now opens hundreds of applications that look nearly identical, and a good chunk of them were tailored to the posting by the same AI tool. Analythical

You are not competing against a shrinking number of jobs. You are competing against a much larger number of people who took the same free path you took and produced the same artifacts you produced.

This is why the advice that worked in 2021 stopped working. It did not become wrong. It became universal. Advice that everyone follows is not advice anymore, it is a description of the pile.

3. AI DID NOT TAKE THE JOB. IT TOOK THE PROOF.

Around 70% of analysts report that AI automation makes them more effective at work. That is not the profile of a role being replaced. That is a role getting a power tool. 365 Data Science

But here is the part nobody says out loud. AI did not eliminate the analyst. It eliminated the evidence you used to rely on.

Writing a JOIN used to be proof you could do something most people could not. It is not anymore, because the laptop of the person interviewing you writes JOINs too. Every skill that a model performs on demand has stopped functioning as a credential. What is left is the part the model cannot do for you in a 45-minute conversation: knowing which question was worth asking, and being able to defend the answer to someone who disagrees.

This is good news if you are willing to hear it. The skills that got commoditized are the ones that took the longest to learn and proved the least. The skills that still count are the ones you can start practicing this week, on a project you already have, in a conversation you can rehearse.

4. THE BAR MOVED FROM CREDENTIALS TO EVIDENCE

Roughly 85% of data analyst job postings do not specify any required years of experience. 365 Data Science

Read that twice, because it sounds like the best news you have heard all year, and it is not charity. The filter did not get deleted. It moved. When a posting refuses to screen on experience, the screening happens later and less visibly: at the resume, at the referral, at the interview where you either explain a real decision you made or you do not.

The bar did not get lower. It got less legible. That is worse for people waiting to be told they qualify, and much better for people who can show something.

I broke into this field without a degree and without permission from anyone, and the mechanism was not that the requirements were soft. It was that a specific person became convinced I could do a specific job. That mechanism has not changed. It has just gotten harder to hit by accident, because there are more people in front of it.

Actual job listing for an entry-level position with no years of experience required.

5. THE COST OF THE QUESTION IS THE CALENDAR

Every version of this question has the same hidden price. You are not weighing a career. You are buying time to not start.

Six months of research produces a person who knows more about the job market than most people employed in it, and who has not written a resume. Ninety days of unglamorous sequence produces a person interviewing. Both of those people asked the same question in January. Only one of them stopped asking it.

The first week of Analyst Hive is deliberately not exciting for this exact reason. Resume rewritten. LinkedIn fixed. Trackers built. Learning blocks on the calendar. SQL started. It is the boring version of the answer, in the order that works, so nobody spends month one deciding what month one should be.

Join Analyst Hive

So, is it worth it in 2026?

The field is worth it. It was worth it in 2024 and it will be worth it in 2028, because businesses will still be making expensive decisions with incomplete information and paying people to reduce the guessing.

The question is worth nothing. “Is it worth it” is a question about the market. “Am I going to do the work” is a question about you. Only one of those two is actually up for debate, and it is not the market.

Analyst Hive is a 90-day daily sequence for getting hired as a data analyst. Not a course, not a bootcamp, not a community with a Discord nobody opens. You get told what to do each day, in order, for 90 days, so the six months you would have spent reading conflicting takes gets spent building the thing that gets you interviews. If the market is crowded, the answer is not more information. It is a sequence, executed.

Join Analyst Hive

If you are on the fence right now, reply and tell me the specific thing you are waiting to see change before you start. Not “the market.” The actual thing. I want to know if it is something that can happen, or if it is a way of staying where you are.

P.S. Every article arguing about whether this field is dead is competing for the same search term you typed. Think about what that tells you about how many of your competitors are also reading instead of starting.

Talk soon,
Ian

Then they wonder why nobody’s calling.

A hiring manager who’s screened 40 candidates this month has seen the Titanic survival predictor at least 15 times. Same dataset, same three charts, same “insights” about women and children first. It doesn’t prove you can do the job. It proves you can follow instructions, which is a different skill entirely, and not the one they’re hiring for.

That gap between “I built a project” and “this project got me interviews” is the whole game. Most people spend weeks on the first thing and never figure out the second. Here’s what actually separates the two.

1. The dataset choice already tells them you copied a tutorial

If your dataset is Titanic, Iris, MNIST, the Ames housing set, or anything pulled straight off the front page of Kaggle, a hiring manager can guess your entire project before opening it. Not because those datasets are bad. Because everyone uses them, which means the dataset itself signals “I searched ‘beginner data project’ and picked the first result.”

The fix isn’t complicated, it’s just more work: scrape it, pull it from a public API, or find a niche dataset nobody’s touched a thousand times. A messy, self-sourced dataset with actual missing values and weird edge cases does more to prove you can operate independently than a perfectly clean CSV ever will. Messy data is the job. Clean tutorial data is the opposite of the job.

2. Documentation is the actual product, not the notebook

Most portfolios are a Jupyter notebook full of code and charts with zero explanation of why any decision was made. That’s a proof of syntax, not a proof of thinking.

What a hiring manager actually wants to know: what was the business question, why did you choose this approach over the obvious alternative, what tradeoff did you make and why, what would you do differently with more time or better data. That’s not a notebook. That’s a README that reads like you’re explaining your reasoning to a coworker, because that’s exactly the skill they’re hiring for.

3. End-to-end beats “just modeling”

A project that starts at “here’s a CSV” and ends at “here’s a chart” skips the two-thirds of the job that actually separates junior from mid-level: getting the data in the first place, and getting the answer in front of someone who can act on it.

The stronger version touches the whole chain: pull or ingest the data yourself, clean and transform it, analyze it, and put the output somewhere a non-technical person could actually use it, a dashboard, a one-pager, a short writeup. You don’t need to be an engineer to do this. You need to stop stopping at the modeling step because it’s the part every tutorial covers and the rest isn’t.

This is the single biggest reason most portfolio projects flop, and it’s exactly what Day 15 of the Analyst Hive walks you through step by step, how to build a GOOD project before you’ve written a single line of “insights.”

Join Analyst Hive

4. Generic questions get generic projects. Specific questions get you hired.

“Predict house prices” is a modeling exercise. “Which zip codes in this metro are undervalued relative to school ratings and commute time, and would that actually change where a first-time buyer looks” is a business question with a defensible answer and a point of view.

Pick a vertical that’s either close to the job you want or close to something you actually know something about. Recruiting funnels, real estate pricing, subscription churn, staffing placement rates, whatever. Specificity is what makes a project sound like it came from someone who understands a business, not someone who ran .fit() on a CSV.

Even the scoping step should look like real work, not a template.

5. If nobody can find it, it didn’t happen

A great project sitting alone on a GitHub repo with three commits and no context is invisible. Post the decision-making, not just the finished thing. A short LinkedIn post walking through why you picked the dataset, the one decision you almost got wrong, and what you’d do differently does more for your visibility than the project itself, because it’s the part people actually read.

The project isn’t the assignment. It’s the audition.

Nobody’s grading whether you can technically complete a project. They’re asking whether they’d trust you with an ambiguous, half-defined business problem and a messy dataset, because that’s what the actual job is on day one. Every choice in the project, the data, the documentation, the scope, the question, is either proving that or proving you can follow a tutorial. Pick one.

If you’re staring at a blank portfolio wondering where to even start, that’s the exact problem Analyst Hive is built to remove. It’s not a course you sit through, it’s a 90-day sequence where the project work, the resume, the LinkedIn presence, and the applications all move together instead of you guessing what to work on next. Day one tells you exactly what to build first, no guessing which dataset or which tutorial to trust.

Join Analyst Hive

What’s the worst portfolio project you’ve seen (or built)? And if you’ve landed interviews off a project, what made it different from the rest of your applications? Curious what patterns show up in the replies.

[P.S.] The five things above took me way longer than 90 days to figure out on my own. That’s the whole reason the sequence exists, so you don’t have to learn it the slow way.

Talk soon,

Ian

Not because the person lacks experience. Not because they’re unqualified.

Because the resume is structured like a diary instead of a decision-making tool.

I see this constantly. Someone has real skills like SQL, Excel, maybe even a project or two but their resume buries all of it under vague job history and a “Skills” section that reads like a word cloud.

Recruiters spend seconds, not minutes, on a first pass. If your resume doesn’t answer “can this person do the job” almost instantly, it doesn’t matter what you actually know.

Here’s the section order I have every Analyst Hive member use:

1. Contact Information

2. Professional Summary

3. Experience

4. Projects

5. Education

6. Skills

7. Certifications

Notice where Projects sits. Above Education. Above Skills.

For anyone transitioning into data without a technical degree, your projects carry more weight than almost anything else on the page. They’re proof, not a claim. A hiring manager can’t verify that you “know SQL.” They can look at a project and see it.

Most people get this backwards. They lead with a skills list and bury the one section that actually proves they can do the work.

The other mistake I see constantly: people write their experience section as a list of duties instead of outcomes. “Responsible for reporting” tells a recruiter nothing. The version that gets interviews is specific, such as the tool, the action, the result.

Inside Analyst Hive, this isn’t a one-time exercise. The resume section includes the exact AI prompts I use to turn scattered work history into results-driven bullet points, the project framework that makes a portfolio piece actually count on a resume, and the full breakdown of free vs. paid resume tools plus which one to skip entirely.

Your resume isn’t something you finish once. It’s something that evolves every time you complete a project, earn a certification, or gain new experience, and the roadmap is built to update it at exactly the right moments.

Founding Member pricing closes [Saturday, July 11] at midnight.

After that, the price goes up and not just for new members, but permanently for anyone who didn’t lock it in. There’s no grandfathering in after the deadline. If you join now, your rate is frozen for as long as you’re a member. If you wait until Monday, you’ll pay more than the person who joined this week, for the exact same program.

If you want the structure, the prompts, and the exact system for building a resume that gets interviews and not just a document that looks nice — I’d love to have you inside.

Join Analyst Hive

As always, thanks for reading.
Ian

They upload a new headshot.

Change their headline.

Add a few skills.

Maybe rewrite the About section after reading three different articles telling them exactly what keywords recruiters are looking for.

Then they move on.

The profile is “finished.”

The problem is that most LinkedIn profiles aren’t actually built to accomplish what their owners want them to accomplish.

They read like resumes.

A LinkedIn profile isn’t a resume.

It’s a landing page.

Every section should answer one simple question:

Why should someone keep reading?

Recruiters aren’t opening your profile because they have twenty minutes to study your career.

They’re deciding, often within a few seconds, whether you’re worth learning more about.

That changes how you should think about every part of your profile.

Your headline isn’t your job title

One of the biggest mistakes I see is treating the headline like an HR database.

Instead of helping someone understand where you’re headed, people write something generic.

Instead of:

Customer Service Representative

or

Student

or

Looking for Opportunities

Try giving people context.

For example:

Data Analyst | Building SQL, Excel & Tableau Projects | Documenting My Journey

Notice the difference.

One tells people where you work.

The other tells people where you’re going.

That immediately makes your profile more interesting.

Your About section should tell a story

Most About sections sound like they were written by AI in corporate mode.

“I am a highly motivated professional with strong communication skills...”

Nobody talks like that.

Instead, tell people why you’re making this transition.

What sparked your interest?

What are you learning?

What kinds of projects are you building?

Where do you hope to end up?

People remember stories far longer than they remember buzzwords.

Don’t leave your Featured section empty

This is probably the most underused section on LinkedIn.

Think about what happens when someone visits your profile.

You say you’re learning SQL.

Great.

Can they actually see anything?

Your Featured section is where you prove it.

A portfolio website.

A Tableau dashboard.

A GitHub repository.

A LinkedIn post explaining a project.

A YouTube video.

Even one project immediately makes your profile more believable than simply listing “SQL” under Skills.

Your activity matters more than most people realize

Imagine two candidates.

The first has an excellent profile.

The second has a good profile but spends a few minutes each day commenting thoughtfully on data-related posts.

Which one is more likely to be seen?

The second.

Every comment is another opportunity for someone to discover your profile.

Every post demonstrates that you’re actively learning.

Every interaction slowly builds familiarity.

I’ve watched complete strangers connect with aspiring analysts simply because they consistently showed up and added value to conversations.

In fact, one of the members inside Analyst Hive shared something with me just a few days after joining.

One of the early action items in the roadmap is to begin leaving thoughtful comments on LinkedIn.

Within days, one of those comments caught the attention of another content creator, and shortly afterward, a lead software engineer at Salesforce connected with them without them even sending the request.

Nothing magical happened.

They simply became visible.

That’s what LinkedIn rewards.

Your profile should evolve with you

One mistake people make is trying to build the perfect LinkedIn profile before they’ve built anything else.

You don’t need the perfect profile.

You need an accurate one.

As you complete projects, add them.

As you learn new skills, update them.

As your confidence grows, your profile should grow with it.

LinkedIn isn’t something you finish.

It’s something you continuously improve.

One of the first things we do inside Analyst Hive is optimize your LinkedIn profile.

Not because a better headline gets you hired.

Not because a better banner magically attracts recruiters.

But because your LinkedIn profile becomes the foundation for everything else you’ll build over the next 90 days.

Your projects need somewhere to live.

Your networking efforts need somewhere to point.

Your comments need somewhere to send curious people.

And your story deserves to be told before your resume ever reaches someone’s inbox.

A great LinkedIn profile won’t get you a job on its own.

But it can absolutely open the door to conversations that never would have happened otherwise.

This is actually Day 1 inside Analyst Hive.

We don’t just tell you to “optimize your LinkedIn.”

We walk through every section of your profile together, explain why it matters, provide examples, and help you build a profile that supports the rest of your job search.

From there, each day builds on the last.

You’ll learn SQL, build portfolio projects, improve your resume, grow your network, prepare for interviews, and follow a structured roadmap designed to remove the guesswork from becoming a data analyst.

Only 25 founder slots available before prices increase.

If you’ve been looking for a step-by-step system instead of another collection of disconnected resources, I’d love to have you join us.

Join Analyst Hive

See you next time!

-Ian

Before we wrapped up, I asked a simple question.

“What did you work on yesterday?”

There was a long pause.

Eventually they laughed and admitted that they had spent most of the day trying to decide what to work on next.

That conversation has stayed with me because, over the years, I’ve had some version of it hundreds of times.

Most aspiring analysts don’t begin their journey lacking motivation. Quite the opposite. They begin with excitement. They discover a career that offers interesting work, remote opportunities, and a clear path toward building a better future. Naturally, they start collecting resources. Within a few weeks they’ve accumulated enough material to keep themselves busy for years.

Their bookmarks are full of:

• SQL tutorials

• YouTube playlists

• Portfolio inspiration

• Resume advice

• LinkedIn posts

• Interview guides

None of those resources are bad. In fact, many of them are excellent.

The problem is that collecting resources slowly becomes a substitute for making progress.

Every morning starts with the same decision: What should I work on today?

It seems like an innocent question, but I’ve watched that question quietly derail months of progress. Instead of building a project, someone watches another tutorial. Instead of applying for a job, they redesign their resume for the fourth time. Instead of publishing their first portfolio piece, they spend another evening comparing datasets because they’re convinced they haven’t found the “right” one yet.

From the outside, it looks like they’re working hard.

From the inside, it feels like they’re stuck.

The people I’ve watched successfully transition into data rarely had access to better information. What separated them was that they removed as many daily decisions as possible. They knew what today’s objective was before they ever opened their laptop. One completed task led naturally into the next, and before long they had built something that couldn’t be created in a single weekend: momentum.

That’s the lesson I keep coming back to.

Momentum isn’t created by one extraordinary day. It’s built through dozens of ordinary ones. A SQL exercise becomes a project. A project becomes a portfolio. A portfolio becomes a conversation with a recruiter. Looking back, every milestone feels connected, but while you’re living through it, each day feels almost insignificant.

Helping aspiring analysts has changed the way I think about learning. Technical skills certainly matter, but I’ve become far more interested in helping people build consistency than helping them find one more resource. Once consistency takes over, everything else starts to compound.

That realization is ultimately what led me to build Analyst Hive.

I didn’t want to create another collection of videos or another community where people hoped to find the next step. I wanted to build something that removed the daily uncertainty altogether. Every day has a purpose. Every action builds on the one before it. Instead of wondering what deserves your attention, you simply focus on completing today’s objective and let the momentum take care of tomorrow.

Founder pricing is still available for a little while longer before membership increases.

Join Analyst Hive

If you’ve been looking for a structured way to stop planning and start making measurable progress, I’d love to have you join us.

See you next time!

-Ian

They struggle because they don’t know what to do next.

There are thousands of SQL tutorials, Excel courses, dashboard walkthroughs, resume templates, interview videos, and portfolio guides available online. None of those are difficult to find.

The difficult part is turning all of those resources into a plan you can actually follow.

That’s why so many people spend six months “learning” but still don’t have a portfolio, haven’t networked, and haven’t applied for many jobs.

A resource isn’t a roadmap.

Over the last several weeks, that’s exactly what I’ve been building.

The first month of Analyst Hive is now fully mapped out with daily lessons that tell members exactly what to work on each day. Instead of wondering whether you should practice SQL, build a project, improve your LinkedIn profile, or network, the program removes that decision entirely.

Every lesson has one objective. Complete it, then move on to the next day.

As I’ve been putting everything together, it’s reinforced something I’ve believed for a long time.

A structured system is more valuable than another course.

Most courses teach a single skill. Coaching calls can be helpful, but once the call ends you’re left deciding what to do on your own.

My goal with Analyst Hive is different. I wanted to build the program I wish existed when I was trying to break into data—a practical system that combines technical learning, projects, networking, portfolio building, LinkedIn, and job searching into one place.

The response so far has honestly exceeded my expectations. We launched Early Access this week, and we’ve already welcomed our first founding members.

Founding Member pricing is still available, but it will increase once Month 1 of the program is complete. Anyone who joins before then keeps their price for as long as they remain a member.

If you’ve been looking for a structured path into data analytics instead of another collection of disconnected resources, I’d love to have you inside.

Join Analyst Hive

As always, thanks for reading.

Ian

Over the last several months, I’ve been quietly building something I’ve wanted to create for a long time.

A step-by-step program for aspiring data analysts.

If you’ve followed my content for a while, you’ve probably noticed a common theme.

I don’t believe most people struggle because they can’t learn SQL or Tableau.

I think they struggle because they don’t know what to do next.

There are thousands of courses, YouTube videos, certifications, and roadmaps available, but very few resources that actually give you a structured path from where you are today to becoming a competitive data analyst.

That’s exactly what I wanted to build.

Instead of piecing everything together yourself, you’ll simply follow the program one day at a time.

Inside you’ll find:

• Daily lessons and action items

• SQL, Excel, Tableau & Power BI learning paths

• Portfolio projects

• Resume and LinkedIn optimisation

• Networking systems

• Interview preparation

• Templates, trackers, and playbooks

Everything is designed to help you build skills, gain experience, and make consistent progress without wondering what to work on next.

Early Access Is Now Open

I’m opening the program to founding members before announcing it more broadly.

As a founding member, you can join today for $9/month and lock in that price for life.

As the program continues to grow with new lessons, videos, playbooks, rewards, and resources, pricing will increase for future members—but your membership price will never change.

This has been a passion project for me, and I’m excited to finally share it with you.

If you’ve been looking for a structured path into data analytics, I’d love to have you inside.

Join Analyst Hive

Join Analyst Hive

Thanks for all of your support over the years.

I can’t wait to see what you build.

Ian