Paradigm (AI research spreadsheets)
Paradigm (AI research spreadsheets)

Deployed Engineer

$180–280kNew York, NY; San Francisco, CAOn-siteMidFull-time

Posted Aug 24, 2026

The role in short

Embed with customers to identify workflows, build integrations, and deploy production AI agents on the Paradigm platform.

About Paradigm

Paradigm is a new type of spreadsheet for automating manual research with agents. We are based in San Francisco and are backed by ~$10M from General Catalyst, Y Combinator, and some of the best builders and operators in technology, including the founders of Ramp, Dropbox, and more.

Our team is small and talent-dense. We are serial builders who have worked and studied at Google, Databricks, Penn, Bridgewater, and more.

The spreadsheet interface is just the beginning. Our mission is to build a new type of agent-centric workspace that massively increases the productivity of knowledge workers. If you want to work on frontier AI systems that tackle meaningful real-world challenges and push the boundaries of what intelligent software can do, apply to join us.

About the Role

At Paradigm, some of our hardest and most important engineering problems begin with a customer.

Deployed Engineers work directly with our customers to identify high-value workflows, understand their data and systems, and turn those workflows into production AI agents on Paradigm.

You might spend one week working with an investment firm to automate diligence across thousands of companies and the next building a workflow that connects a customer’s CRM, internal documents, and external data sources to continuously surface new opportunities.

You’ll operate at the intersection of engineering, product, and our customers. You’ll prototype solutions, build integrations, configure and deploy agents, debug failures, and help customers move from an initial use case to organization-wide adoption.

This is not a traditional solutions engineering role. We expect Deployed Engineers to build. You’ll have the autonomy to solve customer problems directly and the responsibility to bring what you learn back into the core product.

In this role, you will:

  • Own the technical customer lifecycle, from deployment through production adoption and expansion, making sure our customers are successful with Paradigm
  • Work directly with customers to understand how their teams operate and identify the highest-leverage workflows for Paradigm
  • Design and deploy AI agents that combine reasoning, web research, premium external data, and customers’ internal systems
  • Build integrations into systems like CRMs, document stores, data warehouses, and internal APIs
  • Debug agent behavior, data quality issues, integrations, and other problems that emerge in real-world deployments
  • Build deep relationships with users and technical stakeholders, from analysts and operators to engineering leaders and executives
  • Turn patterns you see across customers into product improvements and help shape Paradigm’s roadmap
  • Drive customers from a successful first workflow to broad, repeatable adoption across their organization

Requirements for the role:

  • Strong engineering foundation from a rigorous technical environment
  • Demonstrated track record of exceptional performance in whatever you’ve pursued, whether academic, professional, athletic, or entrepreneurial
  • Experience writing and debugging production software
  • Proficiency in at least one modern programming language
  • Ability to quickly understand unfamiliar APIs, data models, and technical systems
  • High tolerance for ambiguity, intensity, and sustained effort when the problem demands it
  • Willingness to travel

You might excel if you…

  • Love taking an ambiguous business problem and turning it into a working technical system
  • Want to spend significant time with real users rather than building in isolation
  • Are excited by LLMs, agents, data infrastructure, and the challenge of making them reliable in production
  • Enjoy moving between writing code, debugging data, talking to customers, and thinking about product
  • Get unusually excited when someone says, “We spend 20 hours a week doing this manually”

Prep for this interview

5 questions likely to come up at Paradigm (AI research spreadsheets), each matched to a line in this posting.

  1. 1Integrations and APIs
    They wrote: “Build integrations into systems like CRMs, document stores, data warehouses, and internal APIs”

    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. 2Discovery and scoping
    They wrote: “Build deep relationships with users and technical stakeholders, from analysts and operators to engineering leaders and executives”

    A delivery company is losing money and hands you six months of order data. Where do you look first?

    How to answer

    Why they ask: This is the classic case round: a vague business problem and a pile of data. They watch how you narrow it down.

    1. Ask how they measure “losing money” today and since when
    2. Split cost per delivery by region, time, driver and order size to find where the loss sits
    3. Check the data for gaps that could fake a pattern (refunds, cancelled orders)
    4. Propose one fix to test in a single region, with the number that proves it worked

    Tip: Say what the data can and can't tell you before you pick an angle. Missing columns are part of the answer.

  3. 3Data and SQL
    They wrote: “Ability to quickly understand unfamiliar APIs, data models, and technical systems”

    The customer's data is spread across five systems that disagree. How do you get one clean view?

    How to answer

    Why they ask: Real deployments rarely have one source of truth. They want a practical approach, not a perfect one.

    1. List each system and what it's the best source for
    2. Pick matching keys and decide how to handle records that don't match
    3. Load into one place with clear rules, and keep the raw copies
    4. Show the customer the mismatches; they often fix the source

    Tip: Name the system the business trusts most for each field, and get the customer to agree.

  4. 4LLMs, RAG and agents
    They wrote: “Deployed Engineers work directly with our customers to identify high-value workflows, understand their data and systems, and turn those workflows into production AI agents on Paradigm.”

    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: “High tolerance for ambiguity, intensity, and sustained effort when the problem demands it”

    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

Paradigm (AI research spreadsheets)

$180–280k · On-site

Apply