How Real People Switch to Data Engineering (And What It Actually Takes)

Two people decided to become data engineers around the same time. Matt Chang was teaching English at a cram school in Taichung, Taiwan — no programming background, no data experience, no obvious on-ramp. Brian Leong was already analyzing data at Transurban in Australia, surrounded by the tools and the team. Both got there. Matt's path took about 9 months of studying, roughly 50 failed job applications, and a community meetup he built himself just to stay sane through the rejections. Brian made a quiet internal move, built one portfolio project, cultivated the right hiring manager relationship, and barely experienced the cold-application grind at all.

The useful part of their stories isn't that they succeeded. It's that their starting points were completely different — and both paths worked. Yours is probably somewhere between them.

Data engineering has become one of the more realistic mid-career pivots into tech. The tools are freely available to practice at home, no CS degree is required, and entry-level US salaries now start between $80,000 and $110,000, according to Kore1 and 365datascience's 2026 data. People have made this transition from English teaching, food product development, chemistry research, and computational biology. The prior job title is not the bottleneck.

But knowing the destination is reachable doesn't tell you which road to take — or how long it actually runs. The first thing to understand is what skills transfer, and which ones you'll have to build from scratch.

What You Already Bring (More Than You Think)

Most career changers underestimate what they already have. The skills that transfer aren't always the ones that look technical on a resume.

Mamduh Zabidi spent seven years in genomics research — a PhD in Austria, a postdoc in Malaysia — before joining Roche as a Data Engineer. His assessment of the transition wasn't that he had to start over. It was the opposite: "Practices I learned in computational biology are helpful and bring a fresh perspective to my data engineering role." His academic toolkit — bash scripting, reproducible pipelines, variant-classification workflows — translated almost directly into AWS Lambda, Terraform, and SageMaker work. He didn't start from zero. He reframed what he already had.

Matt's edge wasn't technical either. It was his teaching background: structured explanation, patience with complex material, an instinct for building community. He used that to land an analyst role at an ESL kindergarten as his deliberate on-ramp, not to cold-apply to data engineering roles directly.

Tools and applications are a mechanism towards a solution. Standing out requires non-technical skills like problem-solving, stakeholder management, and communication.
— Brian Leong, Data Engineer at Transurban

The hard skills you'll need to build are SQL (non-negotiable), Python (non-negotiable), and at least one cloud platform — AWS, GCP, or Azure. Everything else — domain knowledge, structured thinking, documentation habits, the ability to explain complicated things to people who don't want to hear them — can accelerate you if you treat it as an asset rather than irrelevant backstory. Teachers bring pedagogical clarity. Accountants bring data validation instincts and quantitative discipline. Scientists bring pipeline thinking and reproducibility habits. Marketers bring domain knowledge that data teams serving marketing analytics functions increasingly need.

None of those are soft advantages. In the research, they show up repeatedly as explicit differentiators once the technical bar is cleared.

The Timeline Nobody Advertises

Knowing what transfers helps you scope the gap. But scope isn't the same as timeline — and the timeline is where most career-change plans break down.

Dataquest's 2026 roadmap estimates 8–12 months to job-ready for candidates with some data-adjacent foundation — existing SQL exposure, some analytical work, basic Python. That number extends to 18–24 months for a pure career changer with no data domain background at all. One practitioner who made the transition described it bluntly in an r/dataengineering thread: "It took me 2 years, and I was immediately hired by a financial institution." The two years felt slow at the time. The immediate hire on the other side suggests the preparation was real.

The study sequence inside those 18–24 months matters. Python appears in 70% of 2026 data engineering job postings, SQL in 69%, Apache Spark in 38.7%, Snowflake in 29.2%, and Airflow in 15.8%, according to 365datascience's March 2026 posting analysis. That's a study sequence, not a buffet. The first 8 months should focus almost entirely on the top two. Spark and orchestration tools come later, once you have something to orchestrate.

Mike, a chemistry scientist who lost his job in 2020, spent several quarters in depression and burnout before eventually landing a data engineering role. His retrospective is worth sitting with: "Success is extremely difficult to obtain when pretending to be something you simply aren't." The psychological cost of a forced or premature pivot is real. Plan a financial runway of at least 4–8 months of reduced income — more if you're leaving a tenured position.

Career changers who budget for a 3-month sprint and expect a job offer are systematically underestimating the gap. Those who budget 18 months and hit it at 14 feel like they succeeded early. The direction of error matters more than the number.

Three Paths In — Which One Fits Your Starting Point

Timeline and financial planning are necessary inputs. But they don't answer the question career changers wrestle with most: which path actually gets you hired?

The answer depends entirely on where you're starting.

If you're already in a data-adjacent role — analyst, BI, finance with real SQL depth — Brian Leong's path is the template. Build one end-to-end pipeline project, cultivate the hiring manager relationship internally, and target an internal transfer or a BI Engineer title before jumping to a formal DE role. The analyst-first ladder (Data Analyst → BI Engineer → Data Engineer → Senior Data Engineer) is the most documented successful arc in the research. One practitioner who ran it across six years at multiple US employers put his advice simply: "Change jobs every 1.5 years. Have a personal GitHub. Write a public blog." Internal moves can happen faster, but the compounding logic is the same.

If you're coming from a non-technical background — teacher, marketer, accountant, customer service — Matt Chang's path is closer to your reality. Do not apply to data engineering roles first. Target a Data Analyst role as the deliberate on-ramp and expect 40–60 applications before meaningful traction. Matt built a local meetup while he was studying, which kept him in motion through the rejection stretch. The ESL kindergarten analyst role that hired him wasn't glamorous. It was the bridge that made everything after it possible.

What has carried me this far is purely my persistence.
— Matt Chang, Data Engineer and former English teacher

If you're a scientist, engineer, or researcher with existing pipeline or scripting experience, Mamduh Zabidi's path applies. Skip the analyst step. Reframe your existing work — bash scripting, reproducible experiment pipelines, statistical modeling — as portfolio artifacts. Target ML-platform or data engineering roles that intersect with your scientific domain. Build AWS or cloud skills on top of what you already have rather than treating your background as a liability.

Every branch converges on the same 2026 hiring signal. According to a May 2026 analysis of 20 live data engineering job postings, engineers who are struggling "have built their identities around skills that AI has made cheap and continue to price themselves as if those skills are still scarce." What gets someone past the resume screen now is a publicly visible artifact — a deployed dbt project, a GitHub pipeline, a documented postmortem — not a certification list. One well-chosen certification is worth having; the AWS Certified Data Engineer Associate is the most cited in current job posting analyses. More than two certifications without shipped projects is signal loss, not signal gain.

What Happens Inside Your Head (And How Not to Let It End the Search)

Knowing your branch tells you where to start. What it doesn't answer is the one question that derails even well-prepared career changers: what do you do when the rejections arrive and start to feel like a verdict?

Senior data engineers on r/dataengineering are direct about this: "Ultimately, I've found that imposter syndrome won't just go away, so try your best to manage it." This isn't a beginner problem. It's an industry-wide feature that persists past the first hire and into senior roles. Naming it as normal is the first step to not letting it stop you.

Ivanna Ditlevsen Jurkiv, who transitioned from data analyst to Senior Data Engineer at NNE, a Danish pharma engineering firm, credits something most career-change guides underemphasize: "It was my motivation that got me the data engineer job." When candidates have similar technical baselines — which they increasingly do — visible, genuine engagement is the differentiator. The hiring manager is reading hunger as much as they're reading the resume.

Mike's retrospective from the chemistry side adds the essential qualifier: "Success is extremely difficult to obtain when pretending to be something you simply aren't." These aren't contradictory. Ivanna's "show hunger" and Mike's "don't fake it" are both warnings against performance over authenticity. The candidate who genuinely wants to build pipelines and shows that clearly beats the candidate who memorized the right answers and telegraphed that they're tolerating the process.

The documented failure modes worth knowing in advance: trying to learn every tool before applying (paralysis); self-rejecting on job descriptions where you meet 60–70% of requirements (most working data engineers meet similar percentages); mistaking certification accumulation for progress; and faking enthusiasm for roles that don't genuinely interest you. Hiring managers sense that last one faster than candidates expect.

Where Both Stories End Up

Matt's path was longer and harder — roughly 50 applications, 9 months of study, a community he built himself to stay in motion through the rejection stretch. Brian's was quieter — an internal move, one portfolio project, a hiring manager he already knew. Both arrived at the same title. The difference wasn't talent or timing. It was which path fit their starting point.

The 2026 data engineering market hasn't closed, but it has raised the visible-proof bar. The candidate who gets hired is the one who can point to something real: a deployed pipeline, a postmortem on a broken one, a GitHub repo that moves data from somewhere to somewhere else. One of those artifacts, completed in public, does more for an application than two certifications completed in private.

This week's concrete move: pick one public dataset — weather data, transit data, sports stats — and write three SQL queries against it that answer a real question. Publish the queries and your interpretation in a public GitHub repo or a free blog. That is the first artifact. Every subsequent step builds on it. The goal this week is not to become a data engineer. It is to have one thing that exists in public that did not exist yesterday.

The 18-month timeline that feels like too long is also the reason this field hasn't been flooded with people who watched a tutorial. Slow is durable. Start slow, start this week.

Recommended Tools & Resources