The Rise of the Backwards Deployed Engineer | Sagiv Ofek

Skip to main content<br>TL;DR: Embed with your own company instead of a customer. Replace bloated SaaS with custom tools, get paid a commission on what you save, and skip the salary band entirely.

The forward deployed engineer has become a fixture of modern enterprise sales. You take a sharp engineer, embed them with a prospective customer, let them absorb the workflows and pain points, and have them build a custom solution that closes the deal. Companies like Palantir built empires on this model, and now everyone from AI labs to infrastructure startups is copying the playbook.

But there's a mirror image of this role that almost nobody is talking about - and it might be the single biggest untapped opportunity for ambitious engineers right now. Call it the backwards deployed engineer. Same idea, but pointed inward: instead of embedding with customers to drive revenue, you embed with your own company's departments to eliminate cost. Specifically, the millions of dollars hemorrhaging out the door every year to bloated SaaS contracts.

Here's the pitch, and it's a beautiful one: walk into your CFO's office and propose a new compensation structure. Forget the salary band. Forget the level ladder. Pay me a commission - ideally 100%, but negotiate - of whatever I save the company in SaaS spend during the first year. Then go replace the tools. A motivated engineer could pull in a seven-figure paycheck on this model without breaking a sweat, and the company still comes out ahead.

This kind of arrangement is completely normal everywhere except engineering. Sales reps live and die by commission. An account executive might take home 10% to 80% of the contracts they close, and the best ones have genuinely uncapped upside because their contribution is easy to measure: did the deal close, and for how much? Engineers, meanwhile, get slotted into salary bands defined by level, with comp that barely flexes regardless of impact. The standard defense is that engineering value is hard to quantify - engineers don't fully control the product, they don't determine PMF, and their business contribution gets diffused across a dozen other functions. Fair enough. But cost savings? Cost savings are trivially measurable. You can put them on a spreadsheet. You can wire them to a paycheck.

And the timing has never been better, because AI has collapsed the cost of cloning SaaS tools to something close to zero. The category of software that used to require a team of twenty and eighteen months to build can now be vibe-coded by one good engineer over a few weekends. Meanwhile, the SaaS bills keep arriving. I've seen companies pay over a million dollars a year for Workday and use it as an employee directory. I've watched ten-million-dollar contracts with "advanced analytics" vendors get burned to power dashboards a junior analyst could have built in Retool. I once worked somewhere that paid Oracle north of fifty million a year to host a database of food menu items that, as far as anyone could tell, no production system actually read from.

This is the gap the hungry 10x engineer has been waiting for. Your company is bleeding money to legacy SaaS - and even the modern, well-marketed SaaS isn't safe, because most companies use maybe 10% of what they're paying for. The proposal writes itself: I'll go department by department, identify the tools that are overpriced or underused, replace them with custom internal software tailored exactly to how your teams actually work, and you compensate me as a percentage of what I save. From the company's perspective it's close to a free option. They get an engineer to clone, replace, and upgrade their stack, and they only pay out of savings that wouldn't exist otherwise.

It won't suit everyone. The backwards deployed engineer has to actually go sit with HR, with sales ops, with marketing, with finance. They have to learn what tools are in the stack, where the contracts are buried, which workflows are real and which are theater, and where the gaps are. Then they have to build - fast, scrappy, and tuned to the specific company rather than the generic market. It's part anthropologist, part contractor, part founder. But for the right kind of engineer, it might be the most leveraged role in tech right now.

The forward deployed engineer made companies money. The backwards deployed engineer is going to make engineers rich.