Autoscience
Autoscience

Forward Deployed Engineer

Menlo Park, CAOn-siteMidFull-time

Posted Oct 12, 2026

The role in short

Embed with customers to deploy AutoScience AI agents into their ML infrastructure, writing production code to integrate and optimize automated research systems.

Company Description

At Autoscience Institute, we create AI systems that autonomously conduct AI research. Recently, we announced the first AI agent to autonomously create peer-reviewed literature (ICLR 2025 Workshops). We are passionate about pushing the boundaries of artificial intelligence and contributing to groundbreaking advancements

Role Description

We’re looking for a full-time on site role for a Forward Deployed Engineer to bring AutoScience into the most important machine learning environments in the world.

You’ll work directly with customers to understand their ML systems, deploy AutoScience into their infrastructure, and turn ambiguous modeling problems into environments where our automated researchers can run thousands of useful experiments.

This is not a traditional solutions engineering role. You’ll write production code, work inside real ML pipelines, debug distributed systems, reason about machine learning challenges, and collaborate directly with our research and engineering teams to make the core product better.

You’ll own deployments end-to-end from the first technical conversation to the first model improvement shipped into production.

Qualifications

  • You’re an unusually strong engineer who likes operating where the problem is poorly specified. You bring strong interpersonal judgment and communication skills, build trust with teammates and stakeholders, and collaborate effectively across different working styles and areas of expertise.
  • You get enjoyment from socializing with technical and non-technical customers
  • You should be comfortable opening an unfamiliar ML repository, understanding how the system works, getting it running, identifying what matters, and shipping something useful quickly.

You likely have:

  • Strong software engineering fundamentals and excellent Python skills.
  • Experience building, training, evaluating, or deploying machine learning systems.
  • Experience working with production cloud infrastructure and containerized workloads.
  • Strong debugging skills across software, infrastructure, data, and ML systems.
  • Experience owning technically complex projects from an ambiguous starting point through production.
  • Good judgment about when to build something robust and when to move quickly.
  • The ability to communicate deeply technical ideas with researchers, engineers, and technical leaders.
  • An eagerness to spend significant time working directly with customers.
  • A high degree of autonomy and comfort working in a fast-moving environment.

Benefits & Perks

  • Our comp is competitive against major LLM frontier lab packages
  • Unlimited PTO and flexible working arrangements
  • Conference attendance and publication support

Our Culture

We're a team of passionate researchers and engineers working to automate scientific discovery. We believe in the power of AI to accelerate scientific discovery and are committed to responsible AI development.

We are an e-verify employer.

Prep for this interview

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

  1. 1Coding
    They wrote: “Strong software engineering fundamentals and excellent Python skills.”

    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: “We're a team of passionate researchers and engineers working to automate scientific discovery. We believe in the power of AI to accelerate scientific discovery and are committed to responsible AI development.”

    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. 3LLMs, RAG and agents
    They wrote: “Our comp is competitive against major LLM frontier lab packages”

    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.

  4. 4Ownership and working with customers
    They wrote: “Experience owning technically complex projects from an ambiguous starting point through production.”

    Tell me about a project where the requirements kept changing. What did you do?

    How to answer

    Why they ask: Ambiguity is the norm. They want proof you can keep moving without a clear spec.

    1. The project and why requirements kept moving
    2. What you did to pin them down (short demos, written decisions)
    3. The trade-offs you made to keep shipping
    4. The result, with a number if you have one

    Tip: Show how you reduced the change, beyond how you coped with it.

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

Autoscience

On-site

Apply