Forward Deployed Engineer

The problem we've solved

Selling has always run on a brutal ratio. A salesperson spends barely a third of their day actually selling. The other two-thirds goes to the work around the customer: the research, the lists, the notes, the CRM, the follow-up. Two-thirds of every sales payroll dollar buys administration instead of revenue. The manager's ratio is worse. Coaching is the highest-leverage thing a sales manager does and it's structurally impossible to do at scale, so they sit in on one call a week and guess at the rest while the quiet underperformers repeat the same mistakes on real customers every day.

We built the platform that ends both ratios. One system: the humans get coached on every call they make, and an AI coworker absorbs everything that comes with selling but isn't selling, wired into the CRM, the phones, and the calendar the business already runs on. The hours come back, every conversation gets better, and every outcome feeds back into what gets coached and absorbed next. More time, spent better, measured against revenue.

The thing worth understanding before you apply: the call itself is about to be free. Within a year every voice model will hold a competent conversation. What lasts is what happens after the agent hangs up, the messy conversation turned into clean structured data, landed in the system the customer already works in, with the reasoning attached and proof it was done right. Anyone can make the call. Almost nobody does the finishing. That finishing is the product, it's deep, unglamorous, customer-specific work that doesn't get copied over a weekend, and it's already running. It's also most of what this role extends into every new account.

The role

We need one person to own the technical customer journey end to end: first serious conversation to live in production. Demo, discovery, pilot design, CRM and telephony integration, launch, and support. You'll go into the codebase when a deployment demands it, tuning and extending what's already there so it fits each new customer, and turning what you learn in the field back into the product.

This is the hire that stands up our go-to-market motion. You won't inherit a process. You'll build one, run it on our first accounts, and make it repeatable enough that the tenth deployment is dramatically easier than the first.

Why this role exists

The product is built and it works. The two founders ship production code across the platform, and it's live and running today. What we don't yet have is someone who has run an enterprise technical sales cycle and can deploy that product into outside customers reliably. That's the gap this hire fills, and it's the difference between a product that works and a company that sells. We're not looking for a cog. We're looking for the person who owns the commercial engine and teaches the founders the cycle along the way, so the motion lives in the company and not in one person's head.

The unfair advantage you're walking into

We own and operate a mid-sized business in our beachhead vertical. The platform is deployed and running inside that operation right now, with real reps, real call volume, real CRM, and real revenue on the line. It was battle-tested against a business we own before it ever went near an outside account. You are not selling vapor and you are not cold-starting in an empty category. You're taking something proven in production into a market we know cold.

The size of it

The beachhead is one vertical, deliberately. But the architecture doesn't care which vertical it's in. The same system, humans coached on the calls that stay human, a coworker taking the volume and the routine events, wired into whatever stack the customer already runs, applies to any floor where the phone is where the revenue happens: distribution, staffing, mortgage, real estate, dealer groups, legal intake, and beyond. And it runs in two directions. On the floor it's the best software a sales team has ever used. On the wire it's infrastructure the customer's own systems call over API when an event fires. That second direction is where the ceiling stops tracking headcount and starts tracking transaction volume. You'd be deploying the first outside proof of a motion that's meant to stamp across an entire market.

Where we are

The product is live and proven inside our own operation. Outside customers are the frontier you'd be hired to open, so you're employee-level early, with the ownership and the upside that implies. If you want a mature pipeline handed to you, this isn't it. If you want to be the person who builds it on top of a product that already works, it's exactly it.

What you'll own

• Win the customer. Lead demos and technical discovery with sales leaders, RevOps, and executives. Turn "we use Salesforce and RingCentral" into a real deployment plan. A good demo leaves them thinking this understands how our team actually works.
• Deploy the customer. CRM integration and write-back, telephony setup, configuration, end-to-end validation. A phone number that shows connected is not enough. You own the test call. An API that connects is not an integration. It's done when the right data lands in the right place and the customer trusts it.
• Design pilots that answer business questions, not pilots that succeed because people liked the demo. Baseline metrics, instrumentation, clear success criteria, escalation path.
• Tune and extend the product in the field. Fix the CRM sync, trace the voice defect, close the integration gap, adapt the finishing to a new customer's stack. You own problems through the stack, not up to the edge of a title.
• Turn the field into product. When three customers need the same thing, the job isn't to configure it three times. It's to see the pattern and help turn it into a platform capability.
• Transfer the motion. Part of this role is teaching the founders to run discovery and demos without you in the room. Making yourself repeatable is a measure of success here, not a threat to your seat.

The stack

Next.js, React, TypeScript, Node, Supabase/Postgres, Inngest for durable async workflows, Electron for live-call experiences. Voice runs over PSTN with realtime AI: ASR, LLM reasoning, TTS, warm transfers, escalation. You don't need every piece on day one. You need to move through the stack without a tour guide and know where the deterministic boundaries have to sit around the AI.

What we look for

• You've run enterprise technical sales cycles: discovery, demos to executives, pilots, RFP responses, real integrations.
• You can ship production code (TypeScript/Node/React/Postgres) and own a deployment end to end.
• You've put AI into production and can reason about agents, tools, evaluation, state, and human escalation.
• Strong judgment under incomplete information, and the credibility to tell a customer "we don't support that reliably yet, here's what we do, and here's how we'd prove the next step."
• Comfort talking to engineers, operators, RevOps, sales leaders, executives, and security teams in the same week.

Especially valuable: Salesforce architecture and write-back, telephony provisioning and routing, realtime voice AI, and freight/logistics/TMS experience.

What this is not

Not pure engineering. Not classic sales engineering that ends at signature. Not implementation consulting. You win the customer, deploy the customer, and improve the product because of what you learned doing both. If you're happiest with a hard problem instead of a detailed ticket, and your instinct after solving something is "how do we turn this into a capability we can use everywhere," this is the seat.

Pay: $201,674.00 - $256,432.00 per year

Benefits:

• 401(k)
• 401(k) matching
• Dental insurance
• Health insurance
• Paid time off
• Retirement plan

Application Question(s):

• Why do you want this job?
• How do you tell the difference between a bug, a missing feature, and a customer who's using the product wrong?
• What's a strong opinion you hold about building AI products that you think most engineers get wrong?
• How are you using AI coding agents in your own work right now, and where have they burned you?

Work Location: Remote