Latest / The Career Change Podcast with Fexingo: Switching Fields, Bootcamps, and Reskilling / How Bootcamp Grads Can Transition Into Data Engineering
Transcript
- Lucas: So you've finished a coding bootcamp, you know your React or your Rails, you can spin up a basic web app, but the job market for junior full-stack developers is crowded — really crowded. You're looking at hundreds of applicants per role, and it's tough to stand out. But there's a path that a lot of bootcamp grads overlook: data engineering. Luna: Data engineering. We talk a lot about data science on this show, but data engineering feels like the infrastructure behind it all. What exactly does a data engineer do day-to-day? Lucas: Great question. At its core, data engineering is about building and maintaining the systems that collect, store, and process data so that data scientists and analysts can actually use it. Think ETL pipelines — extract, transform, load — data warehouses, data lakes, all that plumbing. It's less about building predictive models and more about making sure the data is clean, reliable, and accessible. Luna: And I imagine that's a huge need. Companies are drowning in data, but if it's not organized, it's useless. Lucas: Exactly. And that's why data engineering roles have been growing fast. According to LinkedIn, data engineering job postings grew over 35 percent year-over-year in 2025. And the salary range for a mid-level data engineer in the US is typically between one hundred and twenty and one hundred and fifty thousand dollars. It's a strong career path. Luna: That's solid. And it's a field where bootcamp grads can genuinely compete because it's more about practical skills than academic pedigree. Lucas: Right. I want to talk about a specific example. A listener named Priya reached out — she graduated from a twelve-week full-stack bootcamp in early 2025, couldn't land a front-end role, but then pivoted to data engineering. She spent about three months self-studying after the bootcamp, focused on SQL, Python for data, and cloud basics on AWS. She built a project that simulated an e-commerce data pipeline, and that project landed her an interview at a mid-size online retailer. She got the job. Luna: That's exactly the kind of story we want to hear. What were the key skills she picked up in those three months? Lucas: First and foremost: SQL. I cannot overstate how important SQL is in data engineering. It's the lingua franca of data. You need to write complex queries, understand window functions, know how to optimize for performance. Priya said she spent two weeks just drilling SQL on LeetCode and HackerRank. Luna: And Python — she already had that from bootcamp, but did she need to learn specific libraries? Lucas: Yeah, she focused on Pandas and NumPy for data manipulation, and then she picked up basic PySpark for handling larger datasets. Also, she learned the basics of Airflow — that's an orchestration tool for scheduling pipelines. And cloud: she got the AWS Certified Cloud Practitioner certification, which is entry-level but shows you understand services like S3, Redshift, and Lambda. Luna: And the project — what did it involve? Lucas: She built a simulated ETL pipeline. She generated mock sales data using Python, stored it in an S3 bucket, used AWS Glue to transform it, and loaded it into Redshift. Then she wrote a simple dashboard query to show daily sales trends. It wasn't production-grade, but it demonstrated she understood the full workflow. That's what got her the interview. Luna: I love that. It's concrete, it's replicable. And I think for our listeners who are thinking about this, it's important to know that you don't need a computer science degree to build that kind of project. Lucas: Absolutely. And speaking of resources, there's a free online course called the Data Engineering Zoomcamp by DataTalksClub — it's fantastic. It covers data warehousing, batch processing, streaming, the works. Priya said she completed that course in about eight weeks, and it gave her the vocabulary and confidence for interviews. Luna: That's a great tip. And on that note, we should mention that the reason we can keep recommending free and low-cost resources like that is because listeners like you support the show. A couple of dollars a month is genuinely what keeps these episodes going — buy me a coffee dot com slash fexingo, if you've gotten something out of them. Lucas: Yeah, it really makes a difference. No ads, no sponsors — just the community. And every bit helps us keep producing content that's practical and specific. Luna: Alright, back to the data engineering path. So beyond the technical skills, what do interviews look like for a bootcamp grad applying for a data engineer role? Lucas: They vary, but there are common themes. You'll almost always get a SQL screen — maybe a live coding exercise where you have to write queries against a sample database. Then there's usually a system design question, but at the junior level, it's more about data modeling. Like, 'Design a schema for an e-commerce platform' or 'How would you structure a data warehouse for a subscription service?' Luna: And for a bootcamp grad who hasn't worked in a large-scale data environment, how do you prepare for that? Lucas: Practice. There are resources like the 'Data Engineering Cookbook' by Andreas Kretz, which is free online. Also, the website DataLemur has SQL interview questions tailored to data engineering. And for system design, I'd recommend reading about star schemas, snowflake schemas, and slowly changing dimensions. You don't need to be an expert, but you need to show you understand the concepts. Luna: What about tools like dbt? I've heard that mentioned a lot in data engineering discussions. Lucas: dbt, short for data build tool, has become incredibly popular. It lets you transform data in your warehouse using SQL, and it handles dependencies and testing. Priya said she learned dbt basics from a free online tutorial, and it came up in her interview. The interviewer was impressed that she knew about it, because it shows she's keeping up with modern tooling. Luna: So the key takeaway is: you don't need to be an expert in everything, but you need a solid foundation and some project experience that demonstrates you can do the work. Lucas: Exactly. And for bootcamp grads, the bootcamp itself gives you the programming fundamentals and the discipline to learn fast. Data engineering is a natural extension because it's still coding, but it's more about data logic and infrastructure than UI. Plus, the barrier to entry for building projects is low — you can spin up a free tier on AWS or Google Cloud and start building. Luna: And the demand is there. I saw a report from Burning Glass that said data engineering job postings grew 50 percent between 2020 and 2025, and the average time to fill a data engineer role is shorter than for data scientists. Companies need people who can actually handle the data. Lucas: That's a great stat. And it underscores why bootcamp grads should consider this. You're not competing against PhDs; you're competing against people who have learned on the job. If you come in with SQL proficiency, Python, a cloud cert, and a project, you're already ahead of many applicants. Luna: What about the non-technical side? Are there specific soft skills that matter for data engineers? Lucas: Communication is huge. You have to talk to stakeholders — product managers, analysts, sometimes executives — about data requirements. They might not know the technical details, so you need to translate business needs into technical specs. Also, documentation. Data pipelines are complex, and if you don't document them, six months later no one knows how they work. Luna: That's a good point. And for bootcamp grads who are used to pair programming and agile workflows, those collaboration skills transfer directly. Lucas: Absolutely. And one more thing: data engineering is a field where you can grow quickly. After a year or two, you can move into senior data engineer, then data architect, or even machine learning engineering if you're interested. The ceiling is high. Luna: So for someone listening right now, maybe they're frustrated with the job search for front-end roles, what's the first step you'd recommend this week? Lucas: Start with SQL. No money needed. Go to SQLZoo or LeetCode, do the easy and medium SQL problems. Spend a week on that. Then pick a cloud platform — AWS is the most common — and do their free tier tutorials on S3 and Redshift. Then build that ETL project. You can do all of that in a month if you're dedicated. And if you have questions, the Data Engineering subreddit is very active and welcoming. Luna: And once you have that project, put it on GitHub with a clear README, and add it to your LinkedIn under 'Projects'. That's your portfolio. Lucas: Exactly. Priya told me that her project got her the interview, but her ability to explain the design decisions she made — why she chose one approach over another — that got her the job. Be ready to talk about trade-offs. Luna: That's great advice. Data engineering might not be the first thing bootcamp grads think of, but it's a smart pivot with real demand and real opportunity. Lucas: And the best part is, you're building a skill set that's only going to become more valuable as companies generate more data. It's a long-term career move. Luna: Alright, that's all for today. Thanks for listening, and we'll see you next time. Lucas: Take care, everyone.