Latest / The Career Change Podcast with Fexingo: Switching Fields, Bootcamps, and Reskilling / How Bootcamp Grads Can Transition Into Data Engineering
Transcript
- Lucas: So we talk a lot on this show about roles where bootcamp grads can make a strong pivot — product management, UX research, cloud architecture. But there's one role that's been quietly exploding in demand, and most bootcamp grads don't even consider it. Luna: Let me guess — data engineering? Lucas: Exactly. And I say 'quietly exploding' because it's not as flashy as data science or machine learning. But the Bureau of Labor Statistics projects data engineering roles to grow by 35 percent over the next decade. That's faster than the average for all tech jobs. Luna: Right, and the barrier to entry is actually lower than people think. You don't need a math PhD. You need to be good at building pipelines, cleaning data, and making sure things don't break at 2 AM. Lucas: Exactly. So today I want to focus on one specific path: how a bootcamp grad with web development or general programming skills can pivot into data engineering in six to nine months. And I'll use a concrete example — a listener named Maya who did exactly that. Luna: I love when we have real examples. What was Maya's background? Lucas: She graduated from a full-stack web dev bootcamp about two years ago. She got a job as a junior front-end developer at a marketing agency, but she found the work unfulfilling — too much CSS tweaking, not enough problem-solving. She started looking at data engineering after a friend mentioned it. Luna: And she made the switch in six months? That's fast. Lucas: It is, but she was strategic. She didn't just start applying. She identified three core skills she needed to build on top of her existing JavaScript knowledge: Python, SQL, and data modeling. And then she built a portfolio around a single end to end project. Luna: What was the project? Lucas: She built a pipeline that ingests public data from the NYC taxi trip record dataset, cleans it, and loads it into a PostgreSQL database. Then she created a simple dashboard using Metabase. That's it. One project, but it demonstrated every skill a junior data engineer needs: extraction, transformation, loading, and a bit of visualization. Luna: That's smart — hiring managers often say they'd rather see one well-executed project than five half-finished ones. And she used open-source tools, so no one could say 'you only know AWS.' Lucas: Exactly. And she learned Airflow for orchestration — that's the tool that schedules and monitors your data pipelines. It's one of the most sought-after skills in the field. She spent about four weeks just on Airflow, working through the official tutorials and then adding it to her project. Luna: So the project timeline — four weeks on Python and SQL basics, four weeks on data modeling, four weeks on Airflow, and then two weeks polishing the project? That's about 14 weeks. Lucas: Roughly, yeah. She was also working her front-end job full time, so it took her about six months total. The key was she didn't try to learn everything. She focused on the stack that's most common for mid-size companies: Python, SQL, Airflow, and a cloud data warehouse like Snowflake or BigQuery. Luna: And she didn't learn Spark or Kafka or any of the big data tools? Lucas: Not initially. She knew that for her first job, those would be nice to haves. She wanted to target companies that are data-mature but not FAANG. Think of it like this: if you're a bootcamp grad, you're not going to get a job at Netflix building real-time streaming pipelines. But you can absolutely get a job at a mid-size fintech company that needs someone to maintain their nightly batch ETL jobs. Luna: That's a really important point. The companies that are most open to non-traditional backgrounds are often the ones that have data but haven't built a world-class data infrastructure yet. They need someone who can roll up their sleeves and get the data from point A to point B without breaking everything. Lucas: Exactly. And bootcamp grads are actually well-suited for that. Because bootcamp trains you to be scrappy and build things quickly. You're not going to over-engineer a solution. You're going to get it done. Luna: I want to talk about the 'bridge job' strategy. Because Maya was working as a front-end developer while learning data engineering. Did she use that job in any way to help her pivot? Lucas: She did, and this is the smartest thing she did. She volunteered to help her agency's data team with a small project — cleaning up a client's CRM data. It wasn't glamorous, but it gave her a line on her resume that said 'data engineering' and a reference from someone inside her own company. Luna: That's genius. So she didn't quit her job and go all-in on learning. She used her current role to get adjacent experience. And then when she applied externally, she had that experience to point to. Lucas: Exactly. And she applied to about 80 jobs over three months. She got five interviews, two onsites, and one offer. The offer was from a fintech company called LendUp — it's a mid-size lender that processes millions of transactions a day. They hired her as a data engineer I, and she started at $95,000. Luna: That's a great salary for a first data engineering role. And it's a path that's very replicable. Let's break down the exact skill stack for our listeners. Lucas: Sure. First: Python. You don't need to be an expert. You need to be comfortable with pandas, reading and writing files, and basic scripting. Second: SQL — and I mean intermediate SQL, not just SELECT * FROM. You should know window functions, CTEs, and how to optimize a slow query. Luna: And then data modeling — understanding star schemas, fact and dimension tables. That's the part most bootcamp grads skip, but it's crucial because data engineers are the ones designing the warehouse schema. Lucas: Exactly. And then orchestration with Airflow or Prefect. And finally, a cloud data warehouse — Snowflake is the most common, but BigQuery and Redshift are also fine. You can learn Snowflake for free using their trial credits. Luna: And for the portfolio project, what would you recommend someone build today? Because the NYC taxi dataset is great, but it's a bit played out. Lucas: I'd say pick a dataset you're personally interested in. Maybe sports data, or real estate listings, or public company financials. The goal is to show you can take raw data, clean it, and make it queryable. Bonus points if you can show you handled errors and scheduled the pipeline to run daily. Luna: And one more thing — when you're interviewing, be ready to explain trade-offs. Why did you choose Airflow over Prefect? Why did you use PostgreSQL instead of MySQL? Those questions show you understand the decisions you made. Lucas: Totally. And speaking of trade-offs, I want to talk about something that's been on my mind. This show is completely ad-free, and we want to keep it that way. If you've found this episode useful — if you've ever thought about making a career change or you've shared an episode with a friend — the best way to support us is to buy us a coffee. It's the smallest possible ask, and it genuinely helps us keep the lights on. Luna: Yeah, it's at buy me a coffee dot com slash fexingo. And if today's episode was worth a coffee to you, that's the link. No pressure, seriously. Lucas: Alright. Back to data engineering. So you've built your project, you've learned your tools. What's the next step? The job search itself. Luna: And this is where bootcamp grads often trip up. They apply to 'data engineer' roles and get rejected because they lack experience. But there are job titles that are more accessible. Lucas: Right. Titles like 'analytics engineer', 'data operations analyst', or 'junior data engineer' are much more common than 'data engineer' at the entry level. And the responsibilities overlap significantly. Analytics engineering, in particular, is a great entry point because it focuses on transforming data within the warehouse using SQL and dbt — a tool that's very popular right now. Luna: And dbt is something you can learn in a weekend. It's basically a templating tool for SQL. So that's another low-hanging fruit for bootcamp grads. Lucas: Exactly. So to summarize: pick your tool stack, build one end to end project, leverage your current job for a bridge role, and target job titles like analytics engineer. That's the playbook. Luna: And if you're a bootcamp grad listening right now, you have a huge advantage: you're used to learning fast and shipping code. Data engineering is just another stack. You can do this. Lucas: Yeah. And if you have questions about the specific tools or the job search, we'll be answering them in future episodes. Until next time.