Latest / The Career Change Podcast with Fexingo: Switching Fields, Bootcamps, and Reskilling / How Bootcamp Grads Can Break Into Data Engineering
Transcript
- Lucas: So there's this stat that's been stuck in my head for weeks — data engineering job postings are up about 40 percent year-over-year as of mid-2026. That's not AI hype, that's actual pipeline work, building the infrastructure that makes machine learning possible. Luna: Forty percent is huge. But I feel like every bootcamp grad I talk to still says 'data scientist' when you ask what they want to do. Data engineering barely gets mentioned. Lucas: Exactly. And that's the opportunity. Data science is saturated at the entry level. Data engineering is where the actual hiring demand is, especially at mid-market companies that have finally started collecting data but don't know how to move it around. Lucas: Today I want to look at one specific case — a woman named Maria Torres. She did a 14-week data bootcamp in early 2025, came from a marketing coordinator background, and landed a data engineering role at a company called Mosaic Goods — it's a mid-size e-commerce retailer — within six months of graduating. Luna: Six months is fast. What was her strategy that most people miss? Lucas: She didn't try to learn everything. Most bootcamp grads go wide — they want to learn Spark, Kafka, Airflow, Kubernetes, all at once. Maria focused on three things: SQL, Python for ETL, and one cloud platform — she chose AWS. That's it. Lucas: She told me she spent the first month after bootcamp just getting really good at window functions in SQL and writing Python scripts that cleaned and moved data between CSV files and a PostgreSQL database. No distributed systems, no real-time streaming. Luna: That sounds almost too simple. But I guess if you can actually do that in a real setting, you're already more useful than someone who's read about Spark but never built a pipeline. Lucas: Right. And here's the concrete move that got her interviews — she built a portfolio project using public data from the city of Austin. She pulled property tax records, crime reports, and school ratings, then built an ETL pipeline that loaded them into a Redshift data warehouse and created a dashboard showing which neighborhoods had the best combination of low crime and good schools. Luna: That's smart because it shows she understands the business question, not just the technical tooling. Lucas: Exactly. And when she applied to Mosaic Goods, the hiring manager told her that project was the reason she got the call. They had a similar problem — they needed to combine sales data from three different platforms and build a reporting pipeline. She had a concrete example of doing exactly that. Luna: So what does the actual learning path look like for a bootcamp grad who wants to replicate this? Lucas: Let me lay out a three-month roadmap. Month one: SQL and Python fundamentals with a focus on data manipulation. I'm talking about being able to write complex joins, subqueries, window functions, and common table expressions without Google. Lucas: In Python, you want to be comfortable with pandas and the built-in csv module. You don't need machine learning libraries at all. Luna: What about the cloud piece? Because I think that's where most bootcamps fall short — they teach the concepts but not the hands-on deployment. Lucas: Month two is all cloud, and you pick one. AWS is still the most common in mid-market companies, so I'd recommend that. You don't need the full data analytics certification right away — Maria started with the AWS Cloud Practitioner to understand the basics, then studied for the Data Analytics specialty while applying. Lucas: The key is to actually build a pipeline using S3 for storage, Lambda for processing, and Redshift or Athena for querying. There are free tiers for all of those. Luna: And month three is the portfolio project? Lucas: Month three is the project and the job search. The project should be something that answers a real question — not 'I built a pipeline that moves data from A to B', but 'I built a pipeline that shows X about Y'. Use open data from your city, or from Data.gov, or from the company you want to work for if they publish any. Lucas: And then you put that project on GitHub with a clear README that explains the business context, the data sources, the architecture diagram, and the results. That's your resume. Luna: One thing I've noticed in talking to data engineering managers — they really care about whether you understand the difference between batch and stream processing. Is that something a bootcamp grad should worry about early on? Lucas: Worry about it, but don't lead with it. Most entry-level data engineering roles are batch processing. Streaming is a nice to have for junior roles. Maria told me she got asked in one interview to explain the trade-offs, and she gave a simple answer: batch is for when you can wait a few hours for fresh data, streaming is for when you need it in seconds. That was enough. Luna: So don't overcomplicate it. Got it. Lucas: Exactly. And that's actually a theme across all the successful career changers I've talked to. They pick a narrow path and go deep. They don't try to learn the entire data engineering ecosystem. Luna: It reminds me of what you said about Maria — she didn't learn Spark, but she got the job anyway. Most companies just want someone who can build a reliable pipeline, not someone who can architect a distributed system from scratch. Lucas: Right. And the companies that need distributed system architects aren't hiring bootcamp grads anyway. They're hiring people with five years of experience. The sweet spot for a bootcamp grad is a company that's maybe 200 to 500 employees, has a data warehouse but no dedicated data engineering team, and needs someone to come in and build the first real pipeline. Luna: Mosaic Goods sounds like exactly that profile. Lucas: They had a data scientist who was spending 60 percent of her time cleaning data instead of building models. Maria came in and automated the data cleaning pipelines, which freed up the data scientist to do actual analysis. That's a clear win that shows up in a job interview. Luna: I want to ask about certifications. There are a bunch now — AWS, Google Cloud, Azure, and also the Data Engineering certificate from IBM and others. Do they actually help? Lucas: They help as a foot in the door, especially if you don't have a CS degree. Maria had the AWS Data Analytics specialty by the time she interviewed, and she said the hiring manager mentioned it gave them confidence she understood cloud data architecture even though she didn't have work experience. Lucas: But the certification alone won't get you the job. You still need the portfolio project. The certification signals you studied, the project signals you can build. Luna: And I assume networking matters here too, because a lot of these mid-market companies don't post on the big job boards. Lucas: Absolutely. Maria found the Mosaic Goods role through a meetup. She went to a data engineering meetup in Austin, talked to someone who worked there, and when they mentioned they were hiring, she applied the next day. She said that personal connection made her resume stand out from the 200 other applicants. Luna: That's the kind of specific advice that actually works. It's not 'go network more,' it's 'go to a meetup where the people who do the job you want are hanging out.' Lucas: Exactly. And meetups are also a great place to hear what tools companies are actually using in your area. If you go to three meetups and everyone's talking about dbt and Snowflake, that's a signal you should learn those instead of something else. Lucas: One more thing — when you're applying, don't ignore contract to hire roles. A lot of data engineering work starts as a six-month contract because companies are unsure about the need. Maria's first role was actually a contract position, and they converted her after four months. Luna: That's a good point. And I think for a bootcamp grad, a contract role can be easier to get because the bar is slightly lower and the company can try you out before committing. Lucas: Right. And on that note — I want to mention something that a lot of listeners might not realize. This show stays ad-free because a small group of listeners chips in monthly over at buy me a coffee dot com slash fexingo. That's literally what makes it possible for us to do deep-dive episodes like this one. Luna: Yeah, and it's not a big ask — it's just that if you've gotten value from the show, especially if it helped you think through a career move, that's the whole reason we keep doing them. Lucas: So — back to the roadmap. The last thing I want to emphasize is that the job search for data engineering is different from front-end or full-stack. You're not building a flashy portfolio site. You're showing that you can handle messy data and make it useful. Luna: And that's actually a huge advantage for bootcamp grads because you can demonstrate those skills with public data without needing a company's proprietary data set. Lucas: Exactly. So if you're a bootcamp grad thinking about your next move, data engineering is a field where the demand is real, the entry path is clear, and you can actually build the proof of your skills before you get the job. That's a rare combination in tech right now. Luna: It's also a field where the work itself is satisfying — you're building the foundation that everything else runs on. I could see it being a great long-term career. Lucas: Yeah, I think so too. And if you want to dig deeper into the technical side, we'll put links to the resources Maria used in the show notes — including the Austin open data portal and the AWS free tier setup guide.