Start Here
Getting hired is a skill, and it is not the same skill as data engineering. This short orientation reframes the job search as a process you can run deliberately — with a funnel, a timeline, and a strategy — instead of a frustrating game of submitting resumes into the void. Do this well and the months of learning you've put in turn into an offer.
The uncomfortable truth
Being good at the job is necessary but not sufficient to get the job. Every year, capable engineers stay unemployed longer than they should because they treat the search as an afterthought — applying randomly, with a generic resume, no portfolio, and no interview practice. Meanwhile, less skilled candidates who run a process get hired faster.
That's actually good news: the job-search skill is learnable and you're starting it deliberately. This course is the process.
You have something most bootcamp grads and self-taught applicants don't: a real, working, documented platform (your capstone) that you can demo and discuss in depth. Almost everything in this course is about putting that asset to work. If you haven't finished the capstone, do it before you start applying — it's your single biggest differentiator.
The hiring funnel
Every job search is a funnel. Understanding it tells you where to spend effort:
Each stage filters people out. The chapters of this course are organized to get you through each one — so when something isn't working, you can diagnose which stage is leaking and fix that specifically.
The map of this course
| Chapter | Funnel stage it serves |
|---|---|
| 01 · The Job Market & Roles | Targeting — which jobs to go for and how to read them |
| 02 · Portfolio & Presence | Top of funnel — being findable and credible |
| 03 · Resume & Applying | The screen — getting past the six-second look and the ATS |
| 04 · Interview I — SQL & Coding | Technical screens |
| 05 · Interview II — System Design & Behavioral | Onsite / final rounds |
| 06 · Offer & First 90 Days | Closing — and starting strong |
A realistic timeline
Set honest expectations so you don't quit at week three:
- Weeks 1–2: Polish the capstone and portfolio (Ch.02), write the resume (Ch.03), set up LinkedIn. Don't apply yet — apply with a weak resume and you burn opportunities.
- Weeks 3+: Apply steadily (quality over spray-and-pray) while drilling interviews (Ch.04–05) in parallel. Treat the search like a part-time job: consistent weekly effort.
- Reality: A first data role often takes two to six months of active searching, with plenty of silence and rejection along the way. That's normal, not a verdict on your ability. The people who get hired are usually the ones who didn't stop.
You will hear "no" — or more often, nothing — many times before a "yes." Every senior engineer has a graveyard of rejections behind them. Track your funnel, learn from each round, and keep going. Persistence is the single biggest predictor of landing the role.
Mindset for the search
- Run a process, not a vibe. Track applications, stages, and outcomes in a simple sheet. Data engineers, of all people, should instrument their own funnel.
- Quality beats volume. Ten tailored applications with a referral beat a hundred generic ones into the ATS.
- Interview skill is separate and practiceable. You can be a great engineer and a rusty interviewer. Drill deliberately (Ch.04–05).
- You're closer than you feel. Imposter syndrome is near-universal. Your capstone is real evidence you can do the work — trust it.
✓ Check yourself
Answer from memory before opening each one.
-
Six weeks in, your tracker shows 40 applications, one recruiter call and no technical screens. Which stage of the funnel is leaking, and which chapters of this course do you go back to?
Show answer
The resume screen: almost nothing is surviving the six-second look and the ATS, so interview drilling would fix a stage you are not reaching. Go back to Chapter 03 (the resume) and Chapter 02 (the portfolio it points to), and check how many of the 40 went in cold rather than through a referral. See The hiring funnel.
-
The chapter claims a less skilled candidate can be hired faster than a more capable one. What is the mechanism, and what asset does it say you hold that most self-taught applicants don't?
Show answer
Being good at the job is necessary but not sufficient: every funnel stage filters on something other than raw ability (a resume, a story, interview practice), so the candidate who runs a deliberate process gets through stages the capable-but-random applicant never reaches. Your asset is the capstone — a real, working, documented platform you can demo and discuss in depth. See The uncomfortable truth.
-
A friend finishes the curriculum on Friday and plans to start applying on Monday with the resume they already have, "to get the numbers up", polishing it as they go. What does the timeline say is wrong with that plan?
Show answer
Applying with a weak resume burns opportunities: a company that screened you out is not an opening you get back once the resume improves. The tempting idea is that volume compensates; the chapter's order is weeks 1–2 on the capstone, portfolio, resume and LinkedIn, and only then steady applications alongside interview drills. See A realistic timeline.
-
You are ten weeks into an active search with mostly silence and four rejections. What does the chapter say that pattern tells you about your ability, and what should you do with it?
Show answer
Nothing about ability — a first data role often takes two to six months of active searching, and silence is the normal response, not a verdict. Treat the rejections as funnel data: see which stage they cluster at, fix that stage, and keep the weekly effort consistent, because persistence is the biggest predictor of landing the role. See A realistic timeline and Mindset for the search.
-
You have ten hours this week. One plan sends sixty quick applications through job boards; the other sends eight tailored ones, three of them through people you know. Which does the chapter back, what decides it, and when does the volume plan have a point?
Show answer
The eight: ten tailored applications with a referral beat a hundred generic ones, because what matters is how many survive the resume screen, not how many you send. Volume only has a point once resume and portfolio are already strong and you have run out of warm routes — and even then the tracker should show whether the cold applications convert at all before you spend more hours on them. See Mindset for the search.
Exercise — Build your job-search tracker (10 minutes)
Create a simple spreadsheet with columns: company, role, date applied, source (referral/board), stage, next action, notes. This is your funnel dashboard — you'll add rows as you apply and move them through stages.
There's no single right answer, but the discipline matters: candidates who track their search apply more consistently, follow up more reliably, and spot which funnel stage is leaking. Treat your job hunt like a pipeline you're operating — because it is one.
Next
Before you can target jobs, you need to understand the landscape — the roles, the titles, and how to read what a posting is really asking for. → The Job Market & Roles