Breaking Into Data Engineering in 2026: Standout Resumes, Career Changes, and more w/ Chris Gambill
TL;DR
Soft skills are still the biggest career lever in data engineering — Chris Gambill says the new engineers who stand out aren’t just good at Python or Spark; they can explain tradeoffs, talk to the business, and avoid becoming the stereotypical engineer “put into a corner” in big orgs.
Career switchers from finance often make the best junior data engineers — after coaching future data engineers, Chris says finance people already understand messy systems, SQL, ERP relationships like AP and GL, and where “all the skeletons are buried,” which makes the jump into engineering surprisingly strong.
A standout junior resume should lead with projects, not a giant tool list — Chris recommends moving work history down, putting projects near the top, linking to GitHub, and building at least three realistic end-to-end projects on messy data instead of recycled Titanic or COVID datasets.
AI is changing the job, but not removing the need to understand code — Chris has students use Databricks Assistant, Codex, Claude Code, and other tools, but then forces them to walk through code line by line so they can catch bad outputs instead of blindly accepting generated scripts.
The hiring game is increasingly about relationships, not ATS roulette — both Joe Reis and Chris emphasize recruiters, former coworkers, and long-term professional relationships as the real path through a crowded market, especially when applicant tracking systems feel like a “physical black hole.”
The modern data engineer is drifting toward orchestration and AI-adjacent work — Chris expects more roles to blend engineering, product thinking, and agent management, with traditional data engineering branching into AI engineer, ML, architect, and broader “data generalist” paths.
The Breakdown
Chris Gambill’s lane: enterprise operator turned coach
Chris introduces himself as a data strategy and engineering leader who’s been in the field since 2000, with 14 years at AT&T and a stint leading data and analytics for the cybersecurity business that became Level Blue. These days he does fractional consulting, runs a YouTube channel, writes on Substack, and coaches mostly aspiring data engineers and a few senior ICs trying to move into management.
Why consulting beats big-company “cheerleader meetings”
Chris says he prefers consulting because he feels more useful and spends less time in what he politely calls “cheerleader meetings.” His current consulting work is less about flashy builds and more about helping teams stop creating silent failures, get data into shape for AI, and learn how to actually communicate with other humans.
The underrated skill: talking to people
A big thread early on is that many engineers in large organizations get rewarded for technical skill by being isolated from the business, so their communication muscles atrophy. Chris’s whole edge, and the reason former AT&T colleagues now bring him in, is that he can bridge the technical-business divide — something he traces partly to starting his career in customer service.
What Chris tells new data engineers: don’t ignore transferable skills
For career switchers, especially from sales, marketing, finance, or PM roles, Chris spends a lot of time pushing back on impostor syndrome. His advice is simple but practical: expect failure, build resilience, focus on a few tools instead of the whole ecosystem, and start writing code early so the IDE stops feeling scary.
AI is compressing everything, but adaptability still wins
Joe and Chris riff on how the timeline of change has collapsed — what used to take a decade now feels like six months. Chris thinks data engineers may increasingly become orchestrators of AI-driven work, while Joe frames the broader moment as a “Mexican standoff” between software engineers, product managers, and everyone else suddenly empowered by AI tools.
What companies are actually doing with AI right now
Chris says one of his biggest clients is going all-in this year: Copilot for the business side, Claude Code and Cursor for engineering. But he’s skeptical of splitting tool stacks because different models produce different answers, and he worries business users will confidently circulate AI-generated nonsense the same way they already export Power BI dashboards into misleading Excel files.
How to use AI without letting it hollow out your skills
Chris likes Codex right now and also points students toward Databricks because the free tier is robust and won’t surprise them with a huge bill. But he’s strict: if a student uses AI to generate Python, they still have to explain every line back to him, because being employable means knowing when the model gave you something inefficient or just wrong.
What makes a junior resume and job search actually work
His resume advice is concrete: don’t lead with a “bajillion technologies,” lead with projects that feel real, tied to the industry you want, and show messy-to-clean transformations such as getting raw data into a usable silver layer. He also recommends recruiters more than most people do — especially agencies like TEKsystems — because thoughtful outreach and real relationships beat tossing resumes into ATS systems and hoping to escape the void.
The best candidates, the real motivation, and where careers go next
Chris says finance backgrounds are especially strong for data engineering, while people chasing the field only for money tend to struggle because they won’t put in the reps. On career paths, he sees multiple branches — analyst to engineer, IC to architect, engineer to leadership, even sideways moves into software, ML, or AI orchestration — and closes by sharing that the most rewarding part of his work right now is seeing coaching students land genuinely good jobs.