The same nine years, argued four different ways.
A job title is a lens, not a person. These pages take one role family at a time, read how the market actually writes that job, and answer it line by line — with the honest ramps named rather than buried. If you already have a specific posting in hand, the applied pages map individual job descriptions instead.
One family, mapped against the market's own words.
Forward Deployed Engineer
Embed with the customer, build it in their stack, and hand over something their team keeps shipping.
Argued elsewhere on the site, not yet written up here.
These families already have real applications behind them on the applied pages — they just don't have their own composite job description yet. No link here until they do.
A CV lists what happened. It doesn't tell you whether the shape of the work fits.
The same nine years read differently depending on what you're hiring for. Embedding with a customer, architecting a solution before the contract, running a team, building the agentic system — those are four different jobs drawing on overlapping evidence, and a single résumé flattens them into one paragraph. So each page here picks a family, reads how the market actually writes that job, and answers it in the market's own words. The ramps get named in the same table as the strengths, because a claim you can't check is worth nothing to you.