The Forward-Deployed Engineer Is the New Shape of Building
AI turns one capable person into a whole team.
AWS just committed $1 billion to a dedicated forward-deployed engineering unit, and demand for the role has grown 42x in two years. If you were at the last two AWS Summits — New York and Washington, DC — you felt it. It was the biggest conversation in the room.
Most of that conversation treats it as a staffing model: embed engineers with customers. That misses the deeper shift.
For two decades, building software was a relay race. A product manager defined the work. A frontend engineer, a backend engineer, a data engineer, and an ops team each ran their leg. We split it that way for one reason: the whole thing was too big for any one person to hold.
AI removes that reason.
When an agent can write the query, generate the fix, and explain the tradeoff, the specialist boundaries stop being load-bearing. One person — a product owner who understands the goal — can now go from problem to shipped solution without a chain of handoffs. That person is the forward-deployed engineer: product judgment and engineering execution, married, because AI does the specialized labor underneath.
Nowhere is this clearer than the cloud. Understanding an AWS environment used to take a FinOps analyst for cost, a security engineer for posture, an SRE for observability, and an architect to tie it together — plus a different tool for each. Four specialists, four dashboards, and no one who could see across them.
That’s the exact gap we built Sherpa to close. Sherpa is the agent that does the specialist labor. You talk to your AWS cloud in plain English — cost, security, observability, inventory, migration — and it answers, grounded in a live Knowledge Graph of your actual environment. It doesn’t just surface a finding; it proposes the exact fix, and a human approves before anything runs. One capable person, plus Sherpa, can now own what used to take a team of four.
That’s why we hire forward-deployed engineers. Each one owns a domain end to end — they talk to the customer, shape the product, and ship the outcome — because the agent underneath them collapses the specialist work.
The org chart of the next decade won’t be frontend, backend, PM, and ops. It’ll be fewer people who can hold the whole problem, with AI as the team below them. AWS just put a billion dollars behind that thesis. We’ve been building for it.
Want Sherpa hunting waste in your AWS?