Kastle
Kastle2 open roles

Head of Deployments

San Francisco, CAOn-siteSeniorFull-time

Posted 22 days ago

The role in short

Build and lead Kastle's deployments org (FDEs, deployment PMs, process specialists) that takes AI agents live inside banks and lenders.

Who We Are:

Kastle is building the AI employee for financial services. We work with some of America's largest banks, helping them scale their operations using autonomous AI Agents that process payments, originate loans, and help customers get a world class experience during some of the biggest financial decisions of their lives.

We've processed over $2 billion in transactions and are backed by Insight Partners and Y Combinator. If you are interested in building AI that is applied in the real world where precision, reliability, and performance matter and redefine access to credit across the world, apply below.

We just raised a $24M Series A and are growing fast!

About the role

Kastle is hiring its first Head of Deployments to build the team that takes our AI agents from signed contract to live production inside banks, lenders and mortgage servicers.

Kastle is the AI workforce platform for financial services, starting with consumer lending. Our voice, SMS and workflow agents collect payments, answer borrower questions and qualify loan inquiries, working on top of the systems lenders already run, such as ICE MSP, rather than replacing them. We're a San Francisco team backed by Insight Partners, Y Combinator, Commerce Ventures and Fifth Wall, and we closed a $24M Series A in September 2026.

You'll report to the CEO and own every customer deployment end to end. You'll lead forward deployed engineers, deployment PMs and process specialists who embed with lending operations teams, scope workflows, integrate with core systems and get agents into production safely. As we scale across banks and financial institutions globally, you'll turn bespoke rollouts into a repeatable deployment engine.

What you'll do

  • Build and scale the deployments org. Hire, develop and retain forward deployed engineers, deployment PMs and lending process specialists. Set the hiring bar and team structure as we grow from a handful of deployments to dozens running at once.
  • Own delivery for every customer. Be accountable for time-to-live, quality and adoption at each bank, credit union, lender and servicer. Run kickoffs, scoping, integration, UAT and go-live, and step in personally on the hardest accounts.
  • Make deployments repeatable. Turn one-off rollouts into playbooks, reusable integration patterns (servicing cores, LOS, dialers, CRMs) and tooling that cut deployment time with each customer.
  • Get compliance right from day one. Partner with customers' risk, compliance and InfoSec teams on vendor reviews, model risk management and consumer protection rules (TCPA, FDCPA/Reg F, UDAAP) so agents launch safely and audit-ready.
  • Feed the product roadmap. Turn what you learn in the field into clear product requirements. Work closely with Engineering and Product on what becomes platform versus what stays custom.
  • Partner with Sales and Customer Success. Join late-stage deals to scope solutions credibly, define clean handoffs from sale to deployment to ongoing success, and help expand accounts after launch.
  • Bring operational rigor. Define engagement models and deployment pricing, plan capacity for a scarce team, track deployment metrics, and report customer outcomes to leadership and in customer QBRs.

What we're looking for

  • 8+ years in technical, customer-facing roles, with 4+ years leading deployment, solutions engineering, professional services or implementation teams
  • A track record of building a team or service line from early stage and scaling it through rapid growth
  • Hands-on experience deploying enterprise software into regulated environments, ideally banks, lenders, mortgage servicers or other financial institutions
  • Strong technical depth: APIs, system integrations, data pipelines and the SDLC, enough to unblock engineers and earn trust from customer IT teams
  • Working knowledge of LLMs, AI agents or conversational AI, and sound judgment on where they work in production and where they don't
  • Commercial instincts: you've scoped and priced services work and supported complex enterprise sales cycles
  • Clear communicator who can run a room with a bank COO one day and debug an integration with an engineer the next

Nice to have

  • Domain knowledge of consumer lending operations: servicing, collections, loss mitigation or originations
  • Experience with servicing and lending systems such as ICE MSP, Black Knight, Encompass or similar cores
  • Background with voice or contact-center technology
  • Prior early-stage startup experience

We encourage you to apply even if you don't meet every qualification.

Prep for this interview

3 questions likely to come up at Kastle, each matched to a line in this posting.

  1. 1Integrations and APIs
    They wrote: “Strong technical depth: APIs, system integrations, data pipelines and the SDLC, enough to unblock engineers and earn trust from customer IT teams”

    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. 2LLMs, RAG and agents
    They wrote: “Working knowledge of LLMs, AI agents or conversational AI, and sound judgment on where they work in production and where they don't”

    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.

  3. 3Discovery and scoping
    They wrote: “Feed the product roadmap. Turn what you learn in the field into clear product requirements. Work closely with Engineering and Product on what becomes platform versus what stays custom.”

    How do you decide what to build first when a customer wants ten things?

    How to answer

    Why they ask: FDEs have limited weeks per customer. This tests judgment about value, effort and risk.

    1. Score each request by business value and by effort, with the customer in the room
    2. Pick one item that proves value fast and unblocks later work
    3. Write down what's out of scope so it doesn't creep back in
    4. Revisit the list after the first release, with real usage data

    Tip: Show a simple way to rank the list and name what you'd leave out on purpose.

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.

More at Kastle

Similar roles at other companies

Kastle

On-site

Apply