Sr. Fullstack Product Engineer - (Frontend 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 Full Stack Product 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 frontend and customer experience. You should go deep on React, TypeScript, design systems, motion, interaction design, dense information interfaces, and the craft of making complex software feel powerful, calm, and beautiful. But the scope is still fullstack. You are not just implementing screens. You are responsible for the full stack of the customer experience: the interface, the interaction details, the runtime behavior, the APIs, the data contracts, the failure states, and the quality bar of the thing a customer actually uses.

The Role

This is a fullstack product engineering role for someone who likes deep systems, clean abstractions, and product surfaces that make hard infrastructure feel usable.

You will work across the platform layer and the application layer: workflow execution, agent orchestration, pipeline-as-tool contracts, customer data access, retrieval, permissions, observability, and the UI surfaces that expose those capabilities to real users. Some weeks the important work will be a React interface that makes a complex decision legible. Some weeks it will be shaping the API and event contract behind that interface. Some weeks it will be digging through backend behavior to understand why the customer experience does not feel right yet.

The through-line is platform leverage plus customer experience: building product surfaces that make Salt more trustworthy, more composable, easier for customers to understand, and dramatically better 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 visual polish. 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, too ugly, too hard to trust, or too poorly fit to the customer’s real problem.
• You care about the feeling of rightness. You notice naming, hierarchy, density, empty states, logs, permissions, latency, copy, transitions, API shape, loading behavior, failure modes, and the small frictions that make complex software feel either elegant or exhausting.
• You use AI without outsourcing judgment. You can delegate work to agents, but you still define the problem, set review criteria, constrain the implementation, verify the behavior, and decide whether the result is good enough to ship.
• You build with customers close by. You are comfortable using real customer workflows, support threads, calls, prototypes, and internal dogfooding to understand what the product needs to become.
• You keep the team small by raising the bar. We would rather have a few engineers with strong taste, high agency, and deep ownership than a larger team producing more undifferentiated software.
• You do not ship half-baked experiences to customers. Early prototypes are useful. Internal dogfooding is useful. Customer co-creation is useful. But the public product should feel cared for.

**What You’ll…