Ship It Weekly - DevOps, SRE, Platform and Cloud Engineering News · Hands-On Engineering Podcasts · November 2026
Asked how the analytics engineer's job changes when agents write most of the SQL, Handy says the same shift is coming for SREs and software engineers. The valuable work moves to designing the loops and evals the agents run in.
…typically you move more slowly. And that final check is done in the same way that when you build a software factory today, you have this decision to make who merges the pull requests. And some people say the human does, and some people say that the agent does. And so you get to make that decision.
Yeah. Okay, so let's move on to like analytics engineering. So DBT helped make data transformation look more like software engineering. AI Agents write more SQL and consume more data, how does the analytics engineer's job change?
My general guidance here is really not about analytics engineers or SREs or software engineers. It is all of these very technology knowledge work fields are going to be systematized in a way that they haven't been before. And you as a professional will either be operating inside the system or you'll be operating on the system. And from my perspective, the more interesting work to do is to be operating on the system, to be designing the loops, the evals, et cetera, as opposed to having tickets assigned to you. I think that this is true of all of the different types of jobs that I just mentioned and many more. And so for analytics engineers, that really looks like not how do I really cleverly model this data to solve this kind of thorny quantitative problem. It turns out that Astra 6 is going to be able to solve that problem as well as you can, if not better. And instead, you should be thinking about the system holistically and saying, what evals do I have? What evals do I need? How do I see the things that are unseen, like the latent business needs in the…
Yeah, so it's moving up a layer, essentially. 100%.
One of our values that I now authored 10 years ago is we believe in moving up the stack. And I think this is a big moving up the stack moment. We've all been very identified with our own set of technical skills because we've spent a long time building those technical skills. And it turns out that…
Yeah, I think you're right. When you were building DBT, what made practitioners trusted enough to put it into their production workflow? How did you make that happen? How did you build that trust with the community?