Salt AI
Salt AI

Forward Deployed Engineer

$160–190kRemote (US)RemoteSeniorFull-time

Posted 2 days ago

The role in short

Embed with enterprise customers in regulated industries to build, harden, and deploy production AI integrations and custom software directly into their environments.

Our Mission

Salt AI is building the intelligence layer for the enterprise. In a world where AI is fragmented across models, tools, and data silos, Salt unifies them through a compliance-first orchestration platform that helps regulated organizations deploy AI securely and at scale.

We're building the systems that power real-world AI workflows in financial services and other regulated industries. Our platform brings models, data, and existing infrastructure together so enterprises can put AI to work within their operational and compliance constraints.

The Role & How We Work

Forward Deployed Engineers build the systems that make Salt real inside our customers' environments. You'll work with enterprises in financial services and other regulated industries—using their actual data, infrastructure, and constraints—to build the custom software and deep integrations a deployment needs and get it running in production.

This is hands-on engineering, not advisory work. You write the code, build the integrations, and own the rollout into the customer’s environment. You'll exercise technical ownership: propose the approach, solve problems independently, and surface risks and trade-offs to the Deployment Strategist early. You'll build and harden the systems a defined workflow needs, support the agreed deployment and handoff period, and leave the customer able to operate independently.

We’re an AI engineering company pushing the edge of what’s possible. We build our own agent harness, and our engineers use AI agents to design, build, test, and release Salt. We’re moving from individual output to true systems-level leverage: engineers break work into pieces agents can own, set the bar, build automated checks and code reviews that catch what tests miss, and remain accountable for what ships.

What You’ll Do

  • Build & Harden Integrations: Design and implement integrations to customer infrastructure–enterprise data sources, identity systems, and internal tooling. Respect customer data and infrastructure boundaries by building permission-aware integrations that protect credentials and sensitive data, and keep telemetry useful without exposing customer content.

  • Ship to Production: Get your work running in the customer’s environment – SaaS, VPC, or on-prem – in partnership with Salt Platform engineers on the infrastructure side. Test integrations and design for failure, recovery, and observability from day one.

  • Navigate Unfamiliar Environments: Debug in unfamiliar environments where you don’t control the stack and documentation may not exist. Work with the account’s Executive Advisor to get the domain context you need.

  • Technical Ownership: Propose technical approaches and make decisions within the agreed scope. Weigh the customer’s immediate needs against maintainability, delivery effort, and potential value across other accounts; flag scope changes and material trade-offs to your Deployment Strategist early. Manage and communicate your work clearly so the delivery team can track progress and dependencies.

  • Enable Customer Independence: Contribute to the agreed workflow evaluation and handoff, working with the customer and delivery team on acceptance criteria, validation, and regression coverage. Pair with customer engineering teams to review and transfer knowledge as you go. Deliver the runbooks, architecture docs, and configuration details they’ll need to operate independently after handoff.

  • Feed the Core Product: Bring field learnings back to Product and Platform through engagement debriefs, identifying recurring customer needs and evolving suitable integrations into reusable components or extension patterns.

Must-Have Core Skills and Experience

  • Backend & Systems Engineering: 6+ years building and shipping production software, with strong Python skills and deep experience in APIs, distributed systems, and cloud infrastructure (AWS, GCP, or Azure)—reasoning about contracts, interfaces, and failure modes, not just calling SDKs.

  • AI-First Engineering Habits: Proven ability to use coding agents and AI-assisted tools effectively—defining clear constraints and verifying, challenging, and improving agent output while retaining full ownership of what ships.

  • Practical Architecture: Strong judgment to build clear, maintainable integrations and reusable patterns without over-engineering or losing important customer-specific requirements.

  • Customer-Facing Execution: Comfort sitting directly with customer engineering teams to debug in an unfamiliar environment, ask sharp questions, communicate technical trade-offs clearly, find the real constraints, and make progress with incomplete information.

  • Travel: Willingness to travel for onsite deployment work (averaging ~20%).

Nice to Have

  • Hands-on experience with LLM applications, agent frameworks, RAG pipelines, or model deployment.

  • Experience deploying into customer-controlled environments (VPC, on-prem, or air-gapped) using Kubernetes,Terraform, or other IaC tools.

  • Background in regulated industries, particularly financial services (life sciences, or government also relevant) and familiarity with compliance frameworks (SOC 2, HIPAA, GxP).

  • Prior forward-deployed, solutions engineering, or technical consulting experience.

Perks & Benefits

  • Competitive salary based on location and experience

  • Comprehensive medical, dental, and mental health coverage

  • 401(k) plan

  • Fully remote role, collaborating primarily within U.S. time zones

Join Us

At Salt AI, we're building systems that help enterprises put AI to work in financial services and other regulated industries. If you want to ship code that operates in demanding customer environments and delivers lasting value, we'd love to hear from you. We're committed to building a diverse, inclusive team and encourage applications from candidates of all backgrounds and experiences.

Prep for this interview

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

  1. 1Cloud, deployment and security
    They wrote: “Experience deploying into customer-controlled environments (VPC, on-prem, or air-gapped) using Kubernetes,Terraform, or other IaC tools.”

    A bank wants our product inside their own cloud account, with no data leaving it. How do you approach it?

    How to answer

    Why they ask: Self-hosted and private-cloud deployments are common in regulated industries.

    1. Learn their rules early: network limits, approved services, review process
    2. Package the product so it installs the same way each time (containers, Terraform)
    3. Plan how you'll get logs and updates without touching their data
    4. Run a test install with them before the real one

    Tip: Talk about the conversation with their security team as much as the setup.

  2. 2LLMs, RAG and agents
    They wrote: “Hands-on experience with LLM applications, agent frameworks, RAG pipelines, or model deployment.”

    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. 3Integrations and APIs
    They wrote: “Practical Architecture: Strong judgment to build clear, maintainable integrations and reusable patterns without over-engineering or losing important customer-specific requirements.”

    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.

  4. 4Travel
    They wrote: “Travel: Willingness to travel for onsite deployment work (averaging ~20%).”

    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.

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

Salt AI

$160–190k · Remote

Apply