Jobs in Arlington, VA

About the role

We are a hybrid company with a focus on in-person collaboration when necessary. Employees are expected to be available to work from one of our office hubs at least two days per week, or eight days per month. Our US hub locations include: Austin, TX; New York City, NY; San Francisco, CA; and the Washington, DC metro area. If this is a role based in Europe, our Europe hub locations are London, UK and Amsterdam, NL. Please ensure you can realistically commit to this structure before applying. Our largest customers no longer decide on the demo. They decide on what happens after: whether their HR systems connect, whether provisioning works, whether coaching shows up inside the tools their people already have open, whether our AI behaves the way their risk team needs it to. Forward Deployment is the function that owns that work. This role takes the accounts nobody has solved. One is an eight-figure decision waiting on a commercial model that doesn't exist yet. On another, the champion left, the last co-creation attempt damaged trust, and we have never been able to see their usage data. On a third, an executive told us the platform is strategic and 2% of the seats have been assigned. On those accounts there is no charter to execute. You write it. That means deciding what technical success even means here, what we'll commit to, what we'll refuse, and whether a squad belongs on this account at all. Some of these problems are commercial or political rather than technical, and part of the job is recognizing that early, saying so plainly, and not spending engineers on it. You'll do this with a squad of engineers beside you, inside the customer's environment, on a handful of accounts whose outcomes our executive team tracks by name.

What you'll bring

• 7+ years in product management, solutions architecture, or a forward deployed role, including several years owning the technical relationship on enterprise accounts where the contract value ran into seven or eight figures.
• A record of turning around an account that was going badly: trust damaged, a previous attempt failed, or a competitor already in the building.
• Enterprise deployment experience and the scars that come with it.
• You've shipped against someone else's HRIS, argued your way through a security questionnaire, waited on procurement, and watched a rollout stall because 40% of the licenses were never assigned.
• Enough technical depth to be useful.
• You don't need to write production code, but you should read an API doc without help, reason about a data pipeline, configure an LLM's context and guardrails yourself, and tell an engineer when an approach won't survive the customer's security review.
• Credibility with executives on both sides of the table.
• You've briefed a customer's leadership team and your own, and you've delivered bad news to both without losing the room.
• Experience in B2B2C, where you sell to an enterprise buyer and build for the people that buyer serves.
• The two want different things and you've had to hold both.
• Relentless agency.
• When something isn't working, you own it and fix it instead of naming the team that should have.

Benefits

Locations