Forward Deployed Engineer

Forward Deployed Engineer Take an enterprise prospect from first technical conversation to a live, adopted deployment: scoping what is genuinely buildable, building the demo, the custom agents, and the skills yourself, and being personally accountable for the first moment the customer's own team sees the product do something real. What you'll own Pre-sale, technically. Sit in discovery, work out the minimal viable setup for this prospect, then build and run the demo yourself. You decide what is feasible; nothing enters a proposal without your scoping behind it, and your "no" blocks the line item. The demo and the setup, hands-on. Configure the workspace, wire the data sources and connectors, seed the brand knowledge, and get the outputs looking like this customer's brand. Not a spec you hand to someone—an environment you stand up. Custom agents and skills, for the whole life of the account. Most enterprise requirements don't land as a feature request—they land as "our category model isn't yours," "this claim needs a compliance check we do differently," or "this report has to arrive in our format." You build the agents and skills that close that gap: writing them, wiring them to the customer's sources and connectors, testing the output quality, deploying them into their workspace, and maintaining them as the requirement moves. This runs from the pre-sale demo through onboarding and continues once they're live—it is not a one-time setup task. Onboarding through go-live. Run the POC and the training with the customer's day-to-day users, not just the executive buyer. Gather custom requirements directly, and be honest about which are configuration and which need engineering—the second kind gets flagged as roadmap evidence and never committed to a date. The requirements trail. Enterprise onboardings run on daily standups where asks arrive informally, one at a time, for weeks. Keeping that legible—what was asked, by whom, what we agreed, what the customer still owes us—is a core part of the job, not admin around it. The wow moment, as a number. You own the success metric for the journey from pre-sale to go-live. It has to be measurable, falsifiable, and meaningful to the people using the product daily—a dashboard only the buyer ever opens is a failed deployment. Escalations inside your window. A blocked demo, a stalled data-access request, a POC going quiet: yours. Post-launch product issues route to Product; you stay involved only to settle what was actually promised. Your day-to-day toolkit This is the seat's actual working surface—what an ordinary Tuesday looks like. We run AI-native internally, not as a talking point: the expectation is that you drive these tools yourself rather than asking someone to run them for you. For What you'll live in Building agents, skills, and demo setups Claude Code and equivalent agentic dev tools—writing skills, wiring MCP connectors, scripting against our APIs, automating the repetitive parts…