Cadre AI
Cadre AI

Forward Deployed AI Engineer

$100–140kSan Diego, CAOn-siteMidFull-time

Posted 2 days ago

The role in short

Embed with clients to architect, build, and ship production AI systems including LLM pipelines and agents, owning the technical delivery end-to-end.

About Cadre AI

Cadre AI is an AI strategy and integration firm that builds production AI systems for B2B companies in private equity, wholesale lending, real estate, and SaaS. We don’t build decks about what AI could do. We ship systems that move revenue, compress costs, and automate the work that used to take entire teams.

The Role

The Forward Deployed AI Engineer is a critical role at Cadre AI. You are the person in the room with the client, the person writing the code, and the person architecting the system. There is no handoff between “strategy” and “execution.” You own both.

You will embed directly with our clients to understand their operations, identify the highest-leverage AI opportunities, and then build and ship production systems that deliver measurable results. One week you might be designing an LLM pipeline that processes financial documents. The next, you’re standing up a voice agent for a construction company or building a revenue operations engine for a hardware manufacturer scaling globally.

This role is AI-first in how you work, not just what you build. You use Claude Code, Cursor, Codex, and whatever tools let you ship quality code at a pace that would be impossible without them. Speed and quality are not tradeoffs here. They’re both the expectation.

What You’ll Do

Own Client Delivery End-to-End

  • Embed with clients across private equity, lending, real estate, and SaaS to map their operations and identify the AI use cases that will move the business
  • Run discovery sessions, translate business pain into technical architecture, scope the work, and then build it yourself
  • Present to C-suite stakeholders, translating complex trade-offs into clear decisions with measurable expected outcomes
  • Manage client relationships as a trusted technical partner, not a vendor. Clients should feel like you’re part of their team

Build and Ship Production AI Systems

  • Architect and deploy LLM/RAG pipelines, agent orchestration systems, conversational AI, document intelligence, and predictive analytics
  • Use AI-native development tools (Claude Code, Cursor, Codex) to write, review, and iterate on production code at startup speed
  • Build evaluation frameworks, regression suites, and observability layers that prove your systems work and catch when they don’t
  • Convert proofs-of-concept into stable, monitored production services. The demo is not the deliverable. The running system is
  • Design and enforce data quality rules, ETL pipelines, and secure cloud deployments across AWS, GCP, and Azure

Drive Strategy and Scale the Practice

  • Contribute to Cadre’s 8-pillar AI transformation framework, turning field learnings into repeatable playbooks
  • Identify patterns across engagements and build reusable components, prompt libraries, and architecture templates that accelerate future pods
  • Scout emerging models, tools, and research (Claude, GPT, Gemini, Llama, open-source). Run experiments and share what works with the team
  • Mentor junior engineers through pair programming, design reviews, and hands-on coaching

Who You Are

  • 3+ years building software, with 2+ years focused on AI/ML systems in production (not notebooks, not proofs-of-concept)
  • You have shipped LLM-powered products to real users and understand the gap between a working demo and a reliable system
  • Hands-on with modern LLMs, RAG architectures, agent frameworks, and prompt engineering. You have opinions about when to use each and you can defend them
  • Fluent in Typescript & Python and comfortable across the stack (React/Next.js, PostgreSQL, cloud infrastructure). You can build a full application, not just a model
  • Exceptional communicator who can whiteboard architecture with engineers in the morning and present ROI to a CFO in the afternoon
  • AI-native in how you work. You actively use AI coding tools to multiply your output and you’re always testing new ones
  • Comfortable with ambiguity. You can walk into a client engagement with a vague problem statement and leave with a concrete plan
  • Strong judgment about when to use prompt engineering vs. RAG vs. fine-tuning vs. classical ML based on the actual constraints (data, latency, budget, timeline)

What Sets You Apart

  • Former founder, early startup engineer, or someone who has operated like one inside a larger org. You know what it means to own the entire problem
  • Track record of deploying AI systems that moved a business KPI, not just a model metric. You can point to the revenue gained, cost saved, or time eliminated
  • Experience in consulting, professional services, or client-facing engineering where you had to earn trust and deliver under pressure
  • You’ve led end-to-end launches of agent-based or LLM systems at production scale, including the unglamorous work of error analysis, edge case handling, and monitoring
  • Active in the AI community. You write, speak, contribute to open source, or build in public. You’re a practitioner, not a spectator
  • Domain experience in financial services, real estate, lending, or B2B SaaS

Our Tech Stack

AI & LLM

LiteLLM, DSPy, Langfuse, Claude, GPT, custom agent frameworks

Backend

Typescript, Python, FastAPI

Frontend

React, Next.js, Vercel

Data

PostgreSQL with pgvector, Supabase

Infrastructure

AWS, Render (PaaS), Docker

Dev Tools

Claude Code, Cursor, GitHub

Why Cadre AI

  • Real ownership. You will not be writing tickets for someone else to build. You scope it, build it, ship it, and see the impact with your own eyes
  • Variety and velocity. Every engagement is a different industry, a different problem, and a new chance to build something that matters. You won’t get bored
  • AI-native culture. We don’t just build AI for clients. We use it to run our own operations. You’ll work with people who are as obsessed with the tools as you are
  • Access to the frontier. Through our partnerships with Anthropic, OpenAI, and YC, you’ll be among the first to experiment with new models and capabilities
  • Upside. We’re a bootstrapped, profitable, fast-growing company. Early team members share in the success they help create
  • No bureaucracy. Small pods. Clear accountability. The best idea wins, regardless of who says it

Cadre AI is building the future of how companies adopt and operate AI. We believe the best AI systems come from engineers who understand both the technology and the business it serves. If that’s how you think, we want to talk.

Compensation

The base pay range for this role is $100,000 – $140,000 per year.

Prep for this interview

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

  1. 1LLMs, RAG and agents
    They wrote: “Hands-on with modern LLMs, RAG architectures, agent frameworks, and prompt engineering. You have opinions about when to use each and you can defend them”

    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.

  2. 2Discovery and scoping
    They wrote: “Run discovery sessions, translate business pain into technical architecture, scope the work, and then build it yourself”

    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. 3Coding
    They wrote: “Fluent in Typescript & Python and comfortable across the stack (React/Next.js, PostgreSQL, cloud infrastructure). You can build a full application, not just a model”

    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.

  4. 4Integrations and APIs
    They wrote: “Design and enforce data quality rules, ETL pipelines, and secure cloud deployments across AWS, GCP, and Azure”

    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.

  5. 5Ownership and working with customers
    They wrote: “Comfortable with ambiguity. You can walk into a client engagement with a vague problem statement and leave with a concrete plan”

    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

Cadre AI

$100–140k · On-site

Apply