AI Front Desk
AI Front Desk

Forward Deployed Engineer

New York CityOn-siteSeniorFull-time

Posted Aug 19, 2026

The role in short

Own complex enterprise deployments by embedding with customers to build custom integrations and AI workflows, then generalize these solutions into reusable product primitives.

New York City · In Person · Travel Required

ABOUT FRONTDESK

Frontdesk is building AI workers that run customer operations across voice, text, email, and chat.

Over the last year, the size of the contracts we've been closing has increased roughly 10x, with several enterprise deals now reaching six figures and beyond.

At that scale, deployment stops being simple.

Our largest customers need custom integrations, complex workflows, outbound orchestration, legacy systems connected, and dozens of edge cases handled before AI can actually run meaningful parts of their business.

We're looking for the person who wants to own that problem.

THE ROLE

We're hiring our Forward Deployed Engineer.

You will take our hardest enterprise customers from:

"We want Frontdesk to do this" → "It's live in production."

There won't always be a playbook.

You might fly to a customer's office, sit with their operators, understand a workflow nobody has documented properly, design the solution, and then build the missing integration or product capability yourself.

You won't throw requirements over the wall to another team. You'll work directly in the codebase and own the outcome.

And once it works, you'll ask the most important question:

How do we make sure we never have to build this from scratch again?

You'll take what you learn in the field and turn it into reusable Frontdesk product, infrastructure, and deployment primitives.

WHAT YOU'LL DO

  • Own our largest and most technically difficult enterprise deployments.
  • Work directly with customers to understand how their businesses actually operate.
  • Build integrations, workflows, internal tooling, and product capabilities needed to get them live.
  • Travel onsite when being in the room helps us solve the problem faster.
  • Work across voice, SMS, email, chat, APIs, data, LLMs, and workflow orchestration.
  • Debug whatever is blocking a deployment, even when the problem sits outside Frontdesk.
  • Identify patterns across customers and turn one-off solutions into scalable product.
  • Work closely with the founders and engineering team on what Frontdesk should build next.

BUILD AND LEAD THE FUNCTION

We expect this to become a major function inside Frontdesk.

At first, you'll be extremely hands-on. You'll write code, work with customers, and personally own deployments.

As we scale, we expect you to build and eventually lead the Forward Deployed Engineering organization.

That means defining how we deploy enterprise AI, hiring the team, building the playbooks, and determining how Forward Deployed Engineering works with Product, Engineering, Sales, and Customer Success.

We're looking for someone who doesn't just want a job.

We're looking for someone who wants to build something from zero, own a massive surface area, and eventually lead the organization they create.

YOU MIGHT BE A FIT IF YOU

  • Are a strong software engineer who wants more ownership than a traditional engineering role provides.
  • Love talking to customers and solving real problems, not just working from tickets.
  • Are comfortable jumping across the stack and learning whatever is necessary.
  • Have strong product intuition and naturally think about how to generalize what you build.
  • Thrive when the problem is ambiguous and there is no existing playbook.
  • Move extremely quickly and take personal ownership over outcomes.
  • Would rather own an entire problem than a small piece of a large system.
  • Could see yourself starting a company someday, or already think like a founder.

Prep for this interview

4 questions likely to come up at AI Front Desk, each matched to a line in this posting.

  1. 1Integrations and APIs
    They wrote: “Our largest customers need custom integrations, complex workflows, outbound orchestration, legacy systems connected, and dozens of edge cases handled before AI can actually run meaningful parts of their business.”

    Walk me through connecting our product to a customer's internal system that has no documentation.

    How to answer

    Why they ask: This happens weekly in the job. They want a calm, step-by-step method.

    1. Find who owns the system and get read access to a test environment
    2. Watch real traffic or logs to learn the data shapes
    3. Build a thin adapter with logging around every call
    4. Agree on how failures get reported, and who fixes what

    Tip: Talk about finding the owner of the system first. The code is the easy part.

  2. 2LLMs, RAG and agents
    They wrote: “Work across voice, SMS, email, chat, APIs, data, LLMs, and workflow orchestration.”

    A customer wants a chatbot over their internal documents. How do you build it?

    How to answer

    Why they ask: RAG is the most common first project. They want the whole path, from messy files to answers people trust.

    1. Collect and clean the documents; handle permissions per user
    2. Split them into chunks, embed, and store with source links
    3. Retrieve, then answer with citations; say “I don't know” when retrieval is weak
    4. Build a test set of real questions with expected answers before launch

    Tip: Spend more time on the data and on testing than on the model.

  3. 3Ownership and working with customers
    They wrote: “Are a strong software engineer who wants more ownership than a traditional engineering role provides.”

    Tell me about something you shipped that broke in production.

    How to answer

    Why they ask: Everyone has broken production. They want to hear you own it and change something afterwards.

    1. What broke and who it affected
    2. How you found out and what you did in the first hour
    3. The root cause, said plainly
    4. What you changed so it can't happen the same way again

    Tip: Pick a real one with a cost. Spend most of the answer on what you changed.

  4. 4Travel
    They wrote: “Travel onsite when being in the room helps us solve the problem faster.”

    How do you handle being on the road with customers for weeks at a time?

    How to answer

    Why they ask: Many FDE roles involve regular travel. They check you know what you're signing up for.

    1. Your past travel or on-site experience
    2. How you stay productive away from the team
    3. What travel level works for you, said plainly

    Tip: Be honest about what works for you. A mismatch here hurts both sides later.

Not the one? Get the next one by email

New roles land here every day. Pick what you want to hear about.

FDE Info

Want the job, not just the posting? Learn how FDEs work.

FDE Info is our free weekly newsletter for forward deployed engineers: tools, field notes from real deployments, and how FDE teams hire and pay.

Free. One email a week. Unsubscribe in one click.

Similar roles at other companies

AI Front Desk

On-site

Apply