Found AI
Found AI

Forward Deployed Engineer

$155–185kChicago, ILHybridMidFull-time

Posted 2 days ago

The role in short

Lead customer deployments by building production AI agents and data ontologies for industrial operations workflows.

About Found

Found AI is decision intelligence for industrial operations. We deploy Refinery to build a unified business ontology of a company’s enterprise data and decision logic, including the fragmented legacy data and undocumented decisions their operation runs on. That lets people and agents continuously execute the high-value workflows that depend on many disparate inputs, driving speed, accuracy and measurable operational outcomes. On that foundation, our Forward Deployed Team, working side by side with our customers’ subject matter experts, deploys agents for the revenue, operational and capital decisions every manufacturer, materials company and logistics operator faces: quoting, scheduling, capacity planning, routing and dispatch, and capex. Everything runs in a secured environment and every decision is auditable.

Why this role exists

Every Found deployment pairs engineers with the customer’s experts until a production workflow runs on their data. As deployments multiply, we need engineers who lead them. You’ll lead the deployment for one customer at a time, inside a delivery pod: you capture how the operation works, build the ontology and agents on our platform, and are the customer’s go-to technical lead. A Deployment Strategist runs the account and an Operational Partner advises on the operation.

What You’ll Deliver

First 90 days

  • Lead workflow capture on a live deployment: SME interviews, process maps, and the data behind each decision.
  • Ship the first production agent, built with the customer’s experts and tuned to their tolerance for error.
  • Make one recurring piece of deployment work reusable.

First 12 months

  • Lead a deployment end to end, with operators deciding daily on what you built and the next use case scoped.
  • Earn the customer’s trust as their technical lead, from the plant floor to the executive readout.
  • Ship components the product team adopts, so the next deployment starts further ahead.

What You’ll Own

  • Customer outcomes on your deployment: the metric moves, and the ontology, models, and agents behind it hold up.
  • Tested, documented code the next engineer can pick up.
  • Evaluations that show whether an agent’s output is right, and the fix when it isn’t.
  • Fast turnaround on customer feedback during a deployment.
  • Field signal back to product: what customers needed that the platform didn’t have.
  • The technical relationship with the customer’s SMEs, IT, and executives, with no surprises.

What We're Looking For

Must-haves

  • You’ve shipped production code in Python or TypeScript that other people depend on.
  • You write SQL and can model data from systems you didn’t design.
  • You’ve built something real with LLMs: an application, agent, or pipeline, at work or on your own.
  • You’re at home in a consultative, customer-facing setting: you can interview an operator, map how the work really gets done, and explain a tradeoff to an executive in plain language.
  • You say what you don’t know, then go find out. You act without waiting to be asked, and ship a good-enough version you improve in the field.

Nice-to-haves

  • Forward deployed, solutions, or consulting work. Prior FDE experience is a plus, not a requirement.
  • Familiarity with industrial systems (ERP, MES, TMS, GIS).
  • A feel for the UX operators will actually use.

Our Values

We hire against our values that are rooted in Trust. In your work and in conversation, this looks like:

  • Trust: is earned and acts as the Foundation of every interaction.
  • Childlike Curiosity: you learn perpetually, ask why, and meet the world with wonder.
  • Abundance Mentality: you expand through collaboration and optimism. The only limits are the ones you accept.
  • Proactive Autonomy: you think independently and take initiative without waiting for permission.
  • Execute Relentlessly: you move with urgency and discipline, turning ideas into outcomes through obstacles.
  • Intellectual Honesty: you pursue truth over ego, challenge ideas rigorously, and adapt to new evidence.
  • Collective Accountability: you share responsibility for the quality and impact of what we build together.

Logistics

  • Location: Chicago hybrid. 25% to 50% travel to customer sites, heaviest during the workshop and workflow capture.
  • Reports to: Co-founder & CTO
  • Experience: 3+ years of consulting, software or data engineering
  • Compensation: $155K–$185K base
  • Equity: Yes.
  • Benefits: Medical (BCBSIL Blue PPO, 90% company-paid), dental (75% company-paid), and voluntary vision coverage.
  • Type: Full-time

How To Apply

  • What we want to see: a short note on why this work, plus something you built (repo, demo, or write-up). No formal cover letter.
  • What the process looks like: intro call with the CTO, a working session (build a small piece of a deployment from a sample dataset, then walk us through it), a values and role loop with the team, references, then an offer. Typically two to three weeks.
  • AI in your application: use whatever tools you’d use on the job, including AI. We care that you can direct it well and stand behind every word as your own.

Equal opportunity

Found AI is an equal opportunity employer. We hire on evidence of the work and the values above, not pedigree. If you read the must-haves and you’re close but not a perfect match, apply anyway and tell us why you’d be good at this. The calibration above means we’d rather assess than screen you out. We’ll provide reasonable accommodation in the hiring process on request.

Prep for this interview

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

  1. 1Coding
    They wrote: “You’ve shipped production code in Python or TypeScript that other people depend on.”

    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. 2Travel
    They wrote: “Location: Chicago hybrid. 25% to 50% travel to customer sites, heaviest during the workshop and workflow capture.”

    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.

  3. 3Data and SQL
    They wrote: “You write SQL and can model data from systems you didn’t design.”

    Write a query that finds each customer's first and most recent order.

    How to answer

    Why they ask: A quick check that you're comfortable with grouping, joins and window functions.

    1. Clarify the tables and what counts as an order (cancelled ones?)
    2. Use MIN/MAX with GROUP BY, or ROW_NUMBER() if you need the whole row
    3. Handle ties on the same timestamp, and customers with no orders
    4. Explain how you'd test it on a few known customers

    Tip: Say what you'd check in the data before writing the query: duplicates, time zones, nulls.

  4. 4LLMs, RAG and agents
    They wrote: “You’ve built something real with LLMs: an application, agent, or pipeline, at work or on your own.”

    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.

  5. 5Ownership and working with customers
    They wrote: “Proactive Autonomy: you think independently and take initiative without waiting for permission.”

    Describe a time you had to tell a customer bad news.

    How to answer

    Why they ask: FDEs are the face of the company on site. Trust is part of the job.

    1. The situation and what went wrong
    2. When and how you told them
    3. The plan you offered
    4. How the relationship looked afterwards

    Tip: Pick a story where you told them early and came with a plan.

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

Found AI

$155–185k · Hybrid

Apply