Aron
Aron

Forward Deployed Engineer

San Francisco, CAHybridMidFull-time

Posted Sep 9, 2026

The role in short

Embed with manufacturing and industrial customers to build production integrations, customize agentic workflows, and deploy AI solutions for procurement spend analysis.

About NegotiateAI (Menlo Ventures Backed)

Today we're building AI for category managers at manufacturing and industrial companies, taking the grind out of indirect spend and delivering enterprises millions in savings.

That's the starting point. Where we're going is general procurement AI that spans the entire function.

About this role

Procurement data is a mess, and every enterprise's mess is different. Part numbers don't match, supplier names are spelled four ways, and the ERP is a decade of customizations on top of SAP. Our platform has to work inside that reality on day one, not after a six month cleanup project.

You'll be the first Forward Deployed Engineer at NegotiateAI: embedded with our earliest customers, building until the product delivers measurable savings against their real data, then pushing what you learned back into the core platform. This is an engineering role, not a solutions or consulting role. You write production code and you own what you ship.

What you'll do

  • Embed with customer procurement and IT teams to map how spend actually flows: intake, approvals, category taxonomies, supplier master data, and where the savings are hiding.
  • Define crisp success metrics with the customer before you build. Realized savings, categorization accuracy, cycle time, coverage. Then instrument them so nobody has to argue about whether it worked.
  • Build integrations into customer systems: SAP, Ariba, Coupa, Oracle, NetSuite, data warehouses, SSO and identity, and the inevitable SFTP drop. Navigate read-only versus write-back postures and design for whichever one the customer will actually approve.
  • Go from a raw spend extract to a working pipeline fast: entity resolution on suppliers, part identifier normalization, category mapping, and ground truth you can defend in a room full of skeptics.
  • Model customer spend in ClickHouse, which backs our analytics and benchmarking layer, and keep queries fast as datasets grow from one customer's category to an enterprise's full indirect spend.
  • Customize the agentic workflows at the core of the product for each deployment: retrieval sources, tools, prompts, and guardrails, then harden them for reliability and observability.
  • Build per-customer evals against their own data so we can prove accuracy, catch regressions, and show progress week over week.
  • Drive adoption. Run training, write runbooks, and hand off something durable to a champion inside the account instead of becoming the single point of failure.
  • Be the technical voice in front of prospects: lead demos on sales calls, scope pilots against a prospect's own data, and handle security reviews, data handling questions, and SOC 2 questionnaires.
  • Feed patterns back into the platform. Recurring integrations, failure modes, and workflows should become product, not a folder of one-off scripts.

Must haves

  • 4+ years of professional software engineering experience with a track record of shipping production systems end to end.
  • Real comfort working directly with customers, from scoping an ambiguous problem with a category manager to running a training session to answering a hard question from a chief procurement officer or CIO. You treat time with stakeholders as part of the engineering work rather than a detour from it.
  • Hands-on experience building with LLMs in production: agentic workflows, tool use, retrieval, structured outputs, and evaluation.
  • Strong backend and integration skills. API design, data pipelines, and working against systems whose documentation is wrong. Depth matters more to us than experience in any particular language.
  • Experience shipping against messy real-world data: cleaning, normalization, entity resolution, and establishing ground truth.
  • Judgment about what stays bespoke and what becomes product. Custom work is how we learn, but a deployment that only works for one customer is a liability.
  • Comfort with early-stage ambiguity: a small team, shifting priorities, and shipping before everything is fully specified.
  • Willingness to travel to customer sites, primarily manufacturing and industrial companies, roughly once or twice a month depending on the deployment.

Nice to haves

  • Experience integrating with enterprise procurement or ERP systems such as SAP, Ariba, Coupa, Oracle, or NetSuite.
  • Background in procurement, supply chain, sourcing, or manufacturing software.
  • Deep production experience with TypeScript.
  • Experience designing agent harnesses: the scaffolding that makes a model reliable in production.
  • Experience with ClickHouse, or with other columnar analytics stores such as BigQuery, Snowflake, or Databricks.
  • Experience meeting SOC 2, GDPR, or similar compliance requirements at a startup.
  • Prior forward deployed, deployment strategist, solutions engineering, or technical consulting experience at a company like Palantir, Scale, or a comparable enterprise AI team.
  • Experience at an early-stage startup (seed through Series B).

How you will make an outsized impact

  • Customer obsession over elegance. You spend as much time understanding why a category manager does something the hard way as you do building the fix. The best architecture that nobody uses is worth nothing.
  • Ship, then learn. You get something in front of a real user quickly and let their reaction shape the next version. Progress is measured in what got deployed, not what got planned.
  • Own the outcome. Your responsibility doesn't end at the code you shipped. If a deployment is stalled on a data access request or a procurement team that hasn't been trained yet, unblocking it is part of the job.
  • Generalize deliberately. You know when to hardcode something to unblock a customer this week, and you know when to stop and build the abstraction. You leave the platform better than you found it.

Prep for this interview

5 questions likely to come up at Aron, each matched to a line in this posting.

  1. 1Integrations and APIs
    They wrote: “Strong backend and integration skills. API design, data pipelines, and working against systems whose documentation is wrong. Depth matters more to us than experience in any particular language.”

    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: “Customize the agentic workflows at the core of the product for each deployment: retrieval sources, tools, prompts, and guardrails, then harden them for reliability and observability.”

    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. 3Coding
    They wrote: “4+ years of professional software engineering experience with a track record of shipping production systems end to end.”

    How do you keep quality high when you ship fast at a customer site?

    How to answer

    Why they ask: Speed is the job, but broken code at a customer is costly. They want your guardrails.

    1. Tests for the parts that touch customer data or money
    2. Code review even when it's fast, ideally by someone on the product team
    3. Feature flags and an easy way to roll back
    4. Clean up the shortcuts in the next release, and write them down

    Tip: Name the few checks you never skip, and what you skip on purpose.

  4. 4Travel
    They wrote: “Willingness to travel to customer sites, primarily manufacturing and industrial companies, roughly once or twice a month depending on the deployment.”

    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.

  5. 5Discovery and scoping
    They wrote: “Be the technical voice in front of prospects: lead demos on sales calls, scope pilots against a prospect's own data, and handle security reviews, data handling questions, and SOC 2 questionnaires.”

    How do you decide what to build first when a customer wants ten things?

    How to answer

    Why they ask: FDEs have limited weeks per customer. This tests judgment about value, effort and risk.

    1. Score each request by business value and by effort, with the customer in the room
    2. Pick one item that proves value fast and unblocks later work
    3. Write down what's out of scope so it doesn't creep back in
    4. Revisit the list after the first release, with real usage data

    Tip: Show a simple way to rank the list and name what you'd leave out on purpose.

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

Aron

Hybrid

Apply