Sr. Fullstack Platform Engineer - (Backend Focus)

Salt AI; United States; On-site; USD 140,000 - 190,000; Full time

Job summary

Salt AI is building a governed execution platform for AI work that must be real, auditable, and trustworthy. We are hiring a Senior Fullstack Platform Engineer with a backend emphasis to turn the platform into a product customers can actually build on.

You will dive deep on Python, Django, APIs, cloud infra, Kubernetes, and data systems, while shaping the frontend surfaces and runtime behavior that deliver a reliable user experience for complex AI workflows.

Qualifications

• Proficient in Python and Django for backend services.
• Experience with cloud infrastructure and Kubernetes.
• Ability to design data contracts and platform APIs.

Responsibilities

• Develop fullstack platform features for customer workflows.
• Design and enforce data access and runtime contracts.
• Improve observability and reliability of AI workflows.

Skills

Python

Django

APIs

Cloud infrastructure

Kubernetes

Workflow execution

Observability

Reliability engineering

Tools

React

Job description

Sr. Fullstack Platform Engineer - (Backend Focus)

Salt AI is building the governed execution platform for AI work that has to be real: deployable, auditable, permission-aware, and reliable enough for regulated industries.

Our customers are doing work where “the demo looked cool” is not enough. In life sciences, that can mean RNA-targeted drug discovery, combinatorial chemistry, clinical-trial-adjacent research, and scientific workflows that need traceability, reproducibility, and trust. In financial services, healthcare, legal, and government, it means sensitive data, private infrastructure, and AI systems that have to be controlled rather than merely impressive.

We are looking for a Senior Fullstack Platform Engineer who can help turn that platform into something customers can actually build on: software that feels considered, powerful, fast, trustworthy, and unusually good for the complexity underneath.

This role leans backend and platform. You should go deep on Python, Django, APIs, cloud infrastructure, Kubernetes, workflow execution, data systems, reliability, and platform contracts. But the scope is still fullstack. You are not just building backend services in isolation. You are responsible for the Fullstack of the customer experience: infrastructure, data contracts, APIs, runtime behavior, UI surfaces, failure states, and the quality bar of the thing a customer actually uses.

The Role

This is a Fullstack Platform Role for someone who likes deep systems, clean abstractions, and product surfaces that make hard infrastructure feel usable.

You will work across workflow execution, agent orchestration, pipeline-as-tool contracts, customer data access, retrieval, permissions, observability, and the product surfaces that expose those capabilities to real users. Some weeks the important work will be backend architecture. Some weeks it will be the API and event contract that makes the frontend possible. Some weeks it will be a React surface that helps a customer understand what happened inside a distributed AI workflow.

The through-line is platform leverage plus customer experience: building primitives that make Salt more trustworthy, more composable, easier for internal teams to extend, and dramatically better for customers to use.

We are an AI-first engineering team building AI tools for modern, forward-thinking companies. That does not mean accepting AI-generated slop at higher velocity. It means using AI to increase your leverage while keeping your standards intact. The right person can use agents, code generation, and modern tooling aggressively without surrendering authorship, judgment, or accountability.

AI should make you faster, not less discerning. We are hiring engineers whose taste survives contact with AI-generated code.

What Good Looks Like Here

We are closer to Linear than to a traditional enterprise software team in how we think about quality. Craft is not a decorative layer, and it is not limited to the frontend. Quality is the whole customer experience.

That Means

• You know what good looks like. You can tell when a workflow is technically correct but still wrong: too vague, too slow, too brittle, too noisy