The Job Market & Roles
Before you apply to anything, you need a map: which roles actually exist, what they really mean behind the title, who's hiring, and how to read a posting without being scared off by an inflated wish-list. Targeting the right jobs — and recognising the ones you're already qualified for — is the difference between a search that converts and one that drains you. This chapter makes you fluent in the market you're entering.
The data job landscape
Back in Course 1, Chapter 01, you met the data team as a set of overlapping responsibilities rather than tidy boxes. The job market reflects exactly that messiness: the same work shows up under five different titles, and two companies can mean opposite things by the same word. Here's the spectrum, laid out from "closer to the raw infrastructure" on the left to "closer to the business question" on the right:
The boundaries are blurry on purpose — most real jobs straddle two of these. A "Data Engineer" at a small startup may do everything from spinning up infrastructure to writing the analytics models. The same title at a big tech company may be a narrow, well-defined slice. Don't take the label at face value; read the actual responsibilities (we'll do exactly that below).
| Role | Core job | Typical tools | Overlaps with |
|---|---|---|---|
| Data Engineer (DE) | Build and operate the pipelines that ingest, move, and transform data reliably. | Python, SQL, orchestration (Airflow), warehouses, cloud | Analytics Eng, Platform Eng |
| Analytics Engineer (AE) | Turn raw data into clean, documented, trusted tables analysts can use. SQL-and-dbt heavy. | SQL, dbt, the warehouse, BI tools | Data Engineer, Analyst |
| Data Platform Engineer | Build the internal tools, frameworks, and self-serve platforms other data engineers use. | Python, IaC, CI/CD, orchestration internals | Data Engineer, Infra |
| Data Infra / Platform (SRE-flavoured) | Run the underlying clusters, storage, and reliability of the data stack. | Kubernetes, Terraform, monitoring, cloud | DevOps/SRE, Platform Eng |
| ML Engineer (MLE) | Build pipelines and serving systems for machine-learning models in production. | Python, ML frameworks, feature stores, MLOps | Data Engineer, Data Scientist |
Your curriculum and capstone map most directly onto Data Engineer and Analytics Engineer roles — building reliable pipelines and clean, modelled data. Knowing that lets you filter the firehose of postings down to the ones you can actually win, instead of spreading yourself across five different role types and underperforming on all of them.
Titles & seniority
On top of the role, every posting carries a seniority level. The ladder is roughly the same everywhere, even when the words differ:
| Level | What's expected | Realistic for you now? |
|---|---|---|
| Junior / Associate / I | Execute well-scoped tasks with guidance. Learn the codebase and tools. You're expected to grow. | Yes — your primary target. |
| Mid / II | Own features end to end, work independently, need less hand-holding. | Sometimes — reachable with a strong capstone and a sharp interview, especially if you have prior work experience to lean on. |
| Senior / III | Own systems, make design decisions, mentor others, handle ambiguity. | Not yet — but a clear destination 2–4 years in. |
| Staff / Principal | Set technical direction across teams; deep, broad influence. | A long-term horizon, not a first-role concern. |
Let's be honest and encouraging at the same time. A realistic first role from this curriculum is a junior-to-mid Data Engineer or Analytics Engineer. That's not a consolation prize — it's the front door of a field where mid-level engineers are in real demand and senior compensation climbs steeply. You're not trying to land "Staff Data Engineer" out of the gate; you're trying to get in, do good work, and let the ladder do the rest.
Postings list the ideal candidate, not the minimum. If a role looks like a stretch but you can do most of it, apply anyway — many "mid" roles hire strong juniors, and the worst outcome is a polite no. Reserve your "I'm clearly overqualified to be rejected here" energy for roles asking for things you've genuinely never touched.
Who hires data engineers
"A data job" can mean wildly different day-to-day experiences depending on the kind of company. For a first role, the type of employer matters as much as the title, because it shapes how much you'll learn, how much support you'll get, and how forgiving the environment is while you find your feet.
| Employer type | Scope / what you'll do | Mentorship | Pay | Stability | Good first role? |
|---|---|---|---|---|---|
| Early startup | Very broad — you touch everything, often alone. Fast, messy, high ownership. | Often thin (you may be "the data person") | Lower base, equity lottery | Lower | Great learning if you're scrappy; risky if you need guidance |
| Scaleup | Defined-but-growing scope; real data team forming; modern tooling. | Usually solid — peers to learn from | Competitive base, meaningful equity | Moderate | Often the sweet spot for a first role |
| Big tech | Narrow, deep, well-defined slice; mature systems and process. | Strong, structured onboarding | Highest total comp | Higher | Excellent if you can pass the bar; hardest to get into |
| Non-tech enterprise (banks, retail, healthcare, insurance) | Stable, often older stack; lots of data, slower pace, real impact. | Varies; can be very supportive | Solid, steady base; little/no equity | Highest | Underrated entry point — many open roles, less candidate competition |
Career-changers often fixate on glamorous tech-company logos and overlook banks, hospitals, retailers, and insurers — which collectively hire enormous numbers of data engineers, face less applicant competition, and frequently offer the steady, well-mentored environment that's ideal for a first role. The stack may be less trendy, but the skills transfer and the paycheck clears.
How to read a job description
Most beginners read a job description as a pass/fail checklist and disqualify themselves on sight. That's a mistake. A JD is a wish-list written by a committee, not a contract. Your job is to separate the genuine must-haves from the aspirational padding — and to recognise the postings that are red flags in disguise.
The classic trap is the inflated JD: "5–8 years experience, expert in Spark, Kafka, Airflow, dbt, Snowflake, BigQuery, Kubernetes, Terraform, and 12 other tools." Almost nobody on Earth matches that. It's a wish-list, and the team would happily hire someone who's strong on the fundamentals and knows a few of those tools well. Here's how to decode the language:
| What the JD says | What it usually means | How to treat it |
|---|---|---|
| "Required" / "must have" | The real, non-negotiable core (e.g. SQL, Python, a warehouse). | Take seriously — be able to demonstrate these. |
| "Nice to have" / "bonus" / "a plus" | Genuinely optional. Padding. | Ignore as a filter; mention if you have it. |
| "Experience with X, Y, Z, …" (long list) | The team's tooling. They don't expect all of it. | Match 50–60% and apply. |
| "5–8 years of experience" | An anchor, not a gate — especially at mid level. | Don't auto-disqualify; experience is often flexible. |
| "Familiarity with data modelling / testing / quality" | A team that cares about doing it right. Good sign. | Lean in — this is your curriculum's strength. |
| "Strong communication / collaboration" | Real and underrated. They mean it. | Have a story ready that shows it. |
Mapping a JD to your skills. Print (or paste) the posting and mark each requirement: ✓ I can demonstrate this, ~ I've touched it, ✗ never seen it. If you hit most of the ✓ on the genuine must-haves and the ✗ items are all in the "nice to have" pile, you're a fit — apply. Your capstone gives you a concrete answer for most of the core items, which is exactly why it's your biggest asset.
Some JDs reveal a role you don't want. Watch for: a single role that wants a data engineer and data scientist and ML engineer and BI developer (the "do-everything unicorn" — usually understaffed and chaotic); no mention whatsoever of data quality, testing, or reliability (suggests an immature, firefighting culture); vague responsibilities with grandiose buzzwords; or a posting that's been open for many months (something's off). A demanding-but-specific JD is healthy; an everything-to-everyone one is a warning.
How compensation works
Pay in this field has three components, and understanding the structure matters more than chasing any single number:
| Component | What it is | Notes |
|---|---|---|
| Base salary | Guaranteed cash, paid regularly. | The part you can count on. Prioritise this for a first role. |
| Bonus | Variable cash tied to company/individual performance. | "Target" bonus is not guaranteed; treat it as upside. |
| Equity | Stock or options — a slice of company ownership that vests over time. | Public-company stock has clear value; startup equity is a bet that may be worth a lot, or nothing. |
Here's the honest part: compensation ranges vary enormously by country, city, cost of living, company size, industry, and seniority — by multiples, not percentages. Any specific number you read online is a snapshot of one context and can mislead you badly in another. So this chapter deliberately won't quote dollar figures as fact. Instead, learn to research comp for your own situation:
- Level-comparison sites (levels.fyi-style aggregators): strongest for big/public tech companies, where employees self-report base, bonus, and equity by level. Treat the data as indicative, not gospel — samples skew toward higher-paying firms.
- Glassdoor / Indeed / LinkedIn Salary: broader coverage including smaller and non-tech employers, but noisier and often self-selected. Use the range and median, not a single point.
- Public salary data: some regions and many job boards now require posted salary ranges — read them directly off the postings in your market.
- Ask real people: the most accurate source. Communities, alumni, and contacts in similar roles and locations will often share ranges privately. A polite "what does a junior DE in [city] typically make?" goes a long way.
The eye-popping numbers you see online are usually senior engineers at a handful of elite firms in expensive cities. They are real, but they are not your baseline. Build your own picture from several sources filtered to your role, level, and location — then you'll know a fair offer when you see one. We'll cover actually negotiating it in Chapter 06.
Where the jobs are
Not all channels are equal. The single biggest mistake job-seekers make is pouring all their energy into the lowest-yield channel — blasting applications into job boards — while ignoring the one that actually converts. Here's the realistic picture:
| Channel | What it is | Yield | How to use it well |
|---|---|---|---|
| Referrals | Someone inside the company submits or vouches for you. | Highest | Build relationships before you need them; ask warmly and specifically. Worth disproportionate effort. |
| Company career pages | Applying directly on the employer's site. | Medium | Target companies you actually want; pair with a referral if you can find one. |
| Communities (Slacks / Discords) | Data-focused groups that post roles and make warm intros. | Medium–high | Be a genuine participant, not a job-spammer. Many roles are shared here first. |
| Recruiters | Internal or agency recruiters who source candidates. | Medium | Respond, be clear about what you want; good ones become allies. Harder to engage as a junior. |
| Job boards (LinkedIn, Indeed, niche boards) | Open postings anyone can apply to. | Lowest (but high volume) | Use as a discovery tool to find companies, then route through a warmer channel. |
A referred application is dramatically more likely to get a real human look than one that arrives cold through a board. This is why the next chapter — building your portfolio and online presence — matters so much: being visible and credible is what generates referrals and recruiter interest in the first place. Spend a meaningful share of your search building relationships, not just clicking "Apply."
✓ Check yourself
- Can you name the main data roles and explain how a Data Engineer differs from an Analytics Engineer?
- What seniority level is a realistic first-role target for you, and why?
- Given an inflated JD, can you separate the genuine must-haves from the wish-list padding?
- Which job-search channel has the highest yield — and are you investing in it?
Exercise — Find and decode 3 real postings (30 minutes)
Open a job board and find three real Data Engineer or Analytics Engineer postings in your target market. For each one: (1) note the role and seniority; (2) list every requirement and mark it ✓ (I can demonstrate this), ~ (touched it), or ✗ (never); (3) separate the genuine must-haves from the nice-to-haves; (4) rate your fit as strong / stretch / not yet. The point isn't to find perfect matches — it's to train your eye so postings stop intimidating you.
Here's a worked example of decoding one posting:
POSTING: Data Engineer · Scaleup · 3–5 yrs experience
REQUIREMENTS (✓ can show / ~ touched / ✗ never):
✓ Strong SQL -> capstone models + drills
✓ Python for data pipelines -> capstone ingestion code
✓ A cloud data warehouse -> built on one in capstone
~ Airflow / orchestration -> used it; not expert
✓ Data modelling & testing -> dbt + tests in capstone (GREEN FLAG: they care about quality)
✗ Kafka / streaming -> listed under "nice to have"
✗ Kubernetes -> listed under "bonus"
"3–5 yrs" -> anchor, not a gate
MUST-HAVES (real): SQL, Python, a warehouse, data modelling/testing -> I hit all 4
NICE-TO-HAVES: Kafka, Kubernetes, Airflow depth -> partial / optional
RED FLAGS: none — specific, quality-aware, defined scope
FIT VERDICT: STRETCH-but-apply.
I match every genuine must-have. The ✗ items are all optional.
Plan: apply, and in the cover note connect my capstone's testing
work to their "data modelling & testing" line. Try to find a referral.If you can produce a decode like this for three postings, you've turned the scary wall of requirements into a clear, honest read of where you stand — and you'll apply to the right roles with confidence instead of self-disqualifying.
Next
You know which roles to target and how to read them. Now let's make you findable and credible so those roles — and the referrals that unlock them — start coming to you. → Your Portfolio & Online Presence