Latest / The Career Change Podcast with Fexingo: Switching Fields, Bootcamps, and Reskilling / How Bootcamp Grads Can Transition Into Data Engineering
Transcript
- Lucas: So you finished a coding bootcamp. You know how to build a React front end or spin up a Node API. But you're looking at job postings and wondering — where's the demand that's not oversaturated? Data engineering is one of those roles where supply of qualified candidates is still low relative to demand. Luna: I've seen that too. A lot of bootcamp grads default to front end or full stack, but data engineering pays well and has less competition, especially for people who didn't study computer science. Lucas: Exactly. And the misconception is you need a math degree or years of Hadoop experience. But the reality is a lot of data engineering work today is about moving data from point A to point B, cleaning it up, and making it accessible. If you're comfortable with Python and SQL, you're already partway there. Luna: Let's talk about the stack. What are the key tools a bootcamp grad should learn to be credible? Lucas: I'd focus on three things. First, SQL — and I mean beyond basic joins. Window functions, CTEs, query performance. That's table stakes. Second, a workflow orchestrator like Apache Airflow. Understanding how to schedule and monitor data pipelines is a huge differentiator. And third, a transformation tool like dbt — data build tool — which lets you write SQL to transform data in your warehouse. Luna: So less about big data frameworks like Spark? Or do those matter? Lucas: Spark is still important, especially at larger companies. But for a first role, I'd say get comfortable with processing data on a single machine using Python and Pandas, then learn the distributed concepts. Many junior data engineering roles at mid-size companies don't require Spark day one. They want someone who can write clean pipelines and debug when something breaks. Luna: What about cloud? AWS, GCP, Azure — is that a must? Lucas: It's a strong plus. If you can demonstrate basic familiarity with S3, Redshift, or BigQuery, that helps. But you don't need a certification. One approach: build a portfolio project using the NYC Taxi dataset. It's publicly available, has millions of rows, and you can build an end to end pipeline — ingest data from a CSV, load it into a Postgres database, transform it with dbt, and visualize with a simple dashboard. Luna: That's a concrete example. And it shows you understand the full lifecycle. What about the interview process itself? How is it different from a front-end interview? Lucas: Data engineering interviews often have a sql heavy coding round, sometimes on a whiteboard or a shared document. Expect questions like 'write a query to find the top three products by revenue per region.' Then there's a system design round where they ask you to design a data pipeline. For example, 'how would you build a system to ingest clickstream data from a mobile app and make it available for analytics?' Luna: That sounds intimidating if you haven't done it before. Any tips for preparing? Lucas: Practice by describing a pipeline you've built in your portfolio. Use the STAR method — situation, task, action, result. And be honest about trade-offs. For the NYC Taxi project, you might say you chose to batch load daily because real-time wasn't required, and you used dbt for transformations because it's testable and documented. Luna: So the key is building something real and being able to talk through your decisions. Lucas: Exactly. And there's a growing community around dbt and Airflow with free tutorials. You can learn the basics in a weekend. The barrier to entry is lower than most people think. Luna: I've also noticed some bootcamps are adding data engineering tracks. But I think self-directed learning still works if you're disciplined. Lucas: Yeah, and honestly, a lot of hiring managers I've talked to value a GitHub repo with a well-documented project over a certificate. Show them you can build a pipeline that actually runs. Luna: One more thing — networking. How do you find these roles? They're not always labeled 'junior data engineer.' Lucas: True. Look for titles like 'analytics engineer' or 'data analyst' with a pipeline focus. Also, join the dbt or Airflow Slack communities. People post jobs there, and you can ask questions. Being active in those communities signals genuine interest. Luna: On that note, a lot of the advice we give on this show comes from talking to people in the industry. And we're able to keep doing that because some listeners chip in monthly through buy me a coffee. Lucas: Yeah, we don't run ads, and we don't have a corporate sponsor. The show is listener-supported. If you've gotten value from episodes like this one, throwing a few dollars into the tip jar at buy me a coffee dot com slash fexingo helps us keep the lights on. Luna: It's at buy me a coffee dot com slash fexingo. And thank you to everyone who already contributes — it genuinely makes a difference. Lucas: All right, back to data engineering. One more thing I want to mention: the salary range. For a junior data engineer in a mid-sized US city, you're looking at $80,000 to $110,000. That's competitive with front-end roles, and the growth path is solid — senior roles can go up to $150,000 or more. Luna: And the skills are transferable across industries. Finance, healthcare, e-commerce — every company needs data pipelines. Lucas: Exactly. So if you're a bootcamp grad feeling squeezed on the front-end side, data engineering is a viable pivot. The learning curve is real but manageable, and the demand isn't going away. Luna: Great episode. Next time we'll talk about how to transition into technical program management — another path that's less obvious but rewarding. Lucas: See you then.