Netic
Netic

Forward Deployed Engineer

San Francisco, CAOn-siteMidFull-time

Posted Sep 9, 2026

The role in short

Build and deploy multi-modal AI agents and production software systems directly with enterprise customers to automate business workflows.

Netic is the AI revenue engine for essential services who are the backbone of the American economy. With $43M in funding from Founders Fund, Greylock, Hanabi, and Dylan Field who led our Series B, we helped our customers book hundreds of thousands of jobs across services industries in North America. There are now companies operating entirely AI-first on Netic.

You’ll join our team with relentless builders from Scale, Databricks, HRT, Meta, MIT, Stanford, and Harvard in bringing frontier AI to the physical economy, where the problems are hard, the data is complex, and the impact is immediate and tangible.

Our Forward Deployed Agent Engineers are at the heart of building AI that transforms how essential services businesses operate. This role combines cutting-edge AI development with real-world impact, creating systems that handle complex business operations autonomously.

What You’ll Do:

  • Architect agents: Build and ship multi-modal AI agents that drive business impact for essential service companies.
  • Co‑build with customers: Work directly with enterprise stakeholders to map workflows and deploy our product to unlock immediate revenue lift.
  • Own end‑to‑end lifecycle: Manage everything from design to implementation to rollout, including deployment, measuring success, and iterating with customers.
  • Ensure scalability: Build reliable systems that support thousands of concurrent interactions with strong performance.
  • Run rapid experiments: Evaluate cutting‑edge text/voice models, fine‑tune, A/B test live, and iterate in tight feedback loops.
  • Elevate the platform: Surface patterns and opportunities across customers to inform product and engineering roadmaps.

What You’ll Bring:

  • Production experience: A track record of building and maintaining production systems using Python (asyncio, FastAPI) and TypeScript (Node, React).
  • AI systems expertise: Hands-on experience with LLM, TTS and speech APIs, fine-tuning models, vector databases, RAG, and evaluation frameworks.
  • Performance focus: Ability to meet SLAs, resolve issues, and optimize systems for speed and reliability at scale.
  • Scale mindset: Experience building production monitoring and debugging systems across cloud infrastructure and databases.
  • Customer obsession: Comfortable engaging directly with customers to troubleshoot issues, understand edge cases, and deliver fast solutions.

Our values

  1. Obsess over the customer
  2. Every second counts
  3. Sweat the details
  4. There are no blockers
  5. Be self-directed
  6. Seek and speak the truth
  7. Enjoy the ride

We are an equal opportunity employer and do not discriminate on the basis of race, religion, national origin, gender, sexual orientation, age, veteran status, disability or any other legally protected status.

Prep for this interview

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

  1. 1Coding
    They wrote: “Production experience: A track record of building and maintaining production systems using Python (asyncio, FastAPI) and TypeScript (Node, React).”

    Here's a CSV export from a customer. Write a script that cleans it and loads it into our API.

    How to answer

    Why they ask: Very close to real FDE work. They watch how you handle bad rows and failures.

    1. Read with a proper CSV parser; check the header first
    2. Validate each row and collect errors, not crash on the first one
    3. Send in batches with retries and a clear report at the end
    4. Write one or two quick tests for the parsing

    Tip: Talk through edge cases out loud: encodings, missing fields, duplicates, rate limits.

  2. 2Discovery and scoping
    They wrote: “Co‑build with customers: Work directly with enterprise stakeholders to map workflows and deploy our product to unlock immediate revenue lift.”

    A customer says “we want AI in our claims process.” What do you ask in the first meeting?

    How to answer

    Why they ask: Most FDE work starts this vague. They want to hear you find the real problem before you pick a tool.

    1. Map the current process: who touches a claim, in what order, with which systems
    2. Find the slowest or most error-prone step and ask what it costs them
    3. Agree on one measurable goal (for example time per claim, or error rate)
    4. Ask what data you can access, and who signs off on security

    Tip: Ask about the work, not the technology. Who does it today, how long it takes, what a mistake costs, and how they'd know it got better.

  3. 3Integrations and APIs
    They wrote: “AI systems expertise: Hands-on experience with LLM, TTS and speech APIs, fine-tuning models, vector databases, RAG, and evaluation frameworks.”

    A customer's API starts returning errors in production at 2am. What do you do?

    How to answer

    Why they ask: FDEs often own production for their customers. This tests incident handling and communication.

    1. Check your side first: logs, recent deploys, retries piling up
    2. Stop the damage (pause jobs, queue requests, turn off the feature)
    3. Tell the customer what you see and what you've done, in plain words
    4. Afterwards: add a check that would have caught it, and write a short report

    Tip: Split the answer into the first hour and the week after.

  4. 4LLMs, RAG and agents
    They wrote: “Architect agents: Build and ship multi-modal AI agents that drive business impact for essential service companies.”

    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.

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

Netic

On-site

Apply