Frontend Software Engineer, Auth

Nominal is building the connected test and operations platform powering the world's most advanced hardware systems, from spacecraft and autonomous vehicles to next-generation defense programs. Our platform gives hardware engineering teams a single place to ingest data, analyze performance, automate test execution, and collaborate across every phase of development, so they can move faster without sacrificing safety or precision. We're a fast-moving team that owns problems end-to-end, works across disciplines, and thrives at the intersection of hardware and software.

We serve top-tier commercial and defense customers, from autonomy leaders like Anduril and Shield AI to next-generation aerospace teams like Hermeus and REGENT, and performance engineering teams like Pratt Miller Motorsports, alongside mission partners within the U.S. Navy and U.S. Air Force on programs where failure isn't an option. We're backed by Sequoia, General Catalyst, Founders Fund, Lux Capital, and Lightspeed. Our team draws from SpaceX, Palantir, Anduril, Applied Intuition, and other leading companies, united by a common mission: giving hardware engineers the tools to build the future with speed, safety, and confidence.

At Nominal, the frontend goes far beyond a visual layer on top of APIs. For the Auth team, it's where administrators decide who can see and change sensitive test data, and where every user learns what they're allowed to do and why. Our customers run programs where the wrong person seeing the wrong data is a serious problem, so access control has to be precise, and the interface has to make that precision clear.

We're looking for engineers who love reasoning about permission models as much as building intuitive interfaces. You'll work at the intersection of product, design, and engineering to turn a relationship-based authorization system into tools that let admins control access with confidence and let users understand exactly why they can or can't see something. Success in this role is measured by building products that make a precise, deny-by-default permission model legible without hiding its power.

You'll partner closely with backend engineers, designers, and product teams to define workflows, shape product direction, and make thoughtful technical tradeoffs in an environment where requirements are often ambiguous and the best solutions aren't immediately obvious. You'll own the auth frontend largely end to end, so your judgment will shape how access control feels across the whole product.

Build the interfaces administrators use to assign roles, manage users and groups, create workspaces, issue and revoke API keys, and control which data sources each person can see. You'll help define the workflows and interaction patterns that make a relationship-based permission model understandable and hard to misconfigure.

Bring the permission model into every part of the app so that what users see matches what they're allowed to do, from hiding actions they can't take to explaining why. You'll also build the sign-in experiences that connect Nominal to customers' enterprise identity providers.

Partner closely with product, design, and engineering to turn loosely defined ideas into intuitive user experiences. You'll challenge assumptions, validate workflows directly with users, and make confident product decisions when requirements are incomplete.

Develop scalable frontend architecture using React, TypeScript, and modern web technologies. You'll work across application state, data fetching, rendering, and performance to support complex workflows and large datasets.

Design experiences that expose powerful capabilities without overwhelming users. You'll think deeply about information architecture, interaction design, and how technical users reason about their work.

Experience with role-based or relationship-based access control, and familiarity with SpiceDB or other Zanzibar-style authorization engines.

Comfort with sign-in flows, session management, and enterprise identity standards such as OIDC and SAML.

Experience making permission models understandable to end users, or designing interfaces where correctness has real consequences.

Experience designing products around complex object models, relationships, and workflows rather than simple CRUD interfaces.

Ability to understand user goals, simplify complicated workflows, and make thoughtful product decisions under ambiguity.

Comfort reasoning about APIs, data loading strategies, backend constraints, and making architectural tradeoffs across the full stack.

Experience optimizing rendering, managing large datasets, virtualized interfaces, streaming updates, caching strategies, and browser performance.