|
Hi fellow data professional! Once thought to be a purely back office role, data engineering is undergoing a radical transformation and gaining a new responsibility: Front-end deployment. The folks already deploying applications in this capacity are known, incidentally, as forward deployed software engineers or forward deployed engineers (FDEs). Before you worry about needing to learn JavaScript or other web programming paradigms, know that I’m referring to the preparation, deployment and stakeholder/customer support of AI products. That last bit about stakeholder support defines the FDE role, which "focus[es] on enabling many capabilities for a single customer or business unit environment", according to Ariel Jalali CEO of Paragon. And increasingly the capabilities customers want enabled and accelerated revolve around everyone's favorite buzz acronym: AI. An October 2025 study found that, increasingly, “data engineers are stepping out from behind the scenes to help AI strategy and influence business decisions.” And before you think this is simply good PR speak for data engineers, I’ve observed this firsthand. This year, my team gained a new engineer exclusively dedicated to creating data-oriented products and infrastructure to service AI initiatives. Their contributions are by far the most visible out of anyone on our team since leadership is salivating over anything AI-related. The type of data engineering required to build and scale quality AI integrations is a bit different than source data that might pass through a batch pipeline. To yield the most accurate output, AI demands two qualities: Recency and volume. This means data engineers creating the infrastructure for AI deployment will be feeding real-time and unstructured data to their integrations. Before you get confused and think you need to brush up on prompt engineering, the most competitive AI skillset you can develop is an understanding of the “big picture” of deployment.
Most importantly, realize that the best data engineers now are leveraging AI knowledge to work across the data spectrum, as one engineer acknowledges: “I’ve found that all of us have taken on the role of engineer at some point. All of us have taken on the role of data scientists. All of us have taken on the role of data analysts.” So as you master the technical side of the job, understand that the future of data engineering job responsibilities is as dynamic as the data you will mine. Thanks for ingesting, -Zach Quinn Medium | LinkedIn | Ebooks |
Reaching 20k+ readers on Medium and over 3k learners by email, I draw on my 4 years of experience as a Senior Data Engineer to demystify data science, cloud and programming concepts while sharing job hunt strategies so you can land and excel in data-driven roles. Subscribe for 500 words of actionable advice every Thursday.
Hi fellow data professional! Once, during a virtual interview, I had to nod politely as my interviewer apologized for coughing after their cigarette. Oh, and to make this situation even more cringe—they were driving. Some industries design stressful interview processes to psychologically test a candidate’s poise under pressure. Luckily (for the most part) the software engineering field is not included in this basket of high-stress tests. Sure, we are subjected to moderate stress in the form...
Hi fellow data professional! On a recent holiday, a family member and I were strolling along a beach, talking about AI disruption (relaxing, I know). He, an attorney, assured me his job was AI-proof and jokingly offered to hire me when AI takes my data engineering job. If you ask executives at most companies, they’d find several flaws in that argument. Over 80% of technical executives, including Chief Data Officers and Chief AI Officers, consider data engineering to be an essential role...
Hi fellow data professional! Ken Jee, who you heard from last week, drops some sobering career advice in one of the earliest editions of AI Survival Guide: Making a senior-level tech role is no longer about advancement; it’s about survival. The post talks about the growing moat or "wall" between those breaking into the industry, those in entry-level roles and those in a mid-career phase. In the spirit of AI Survival Guide’s advice to bridge the gap separating the early and mid-career...