About thisrole

Axiom is a focused initiative within Prescryptive, with a dedicated team building a new set of applications for our internal teams, customers, and external partners. As the first Software Engineer dedicated to Axiom, you willestablishthe frontend architecture and engineering patterns for these applications and build the foundation that supports them as the initiative grows.

You will work closely with the Axiom team and engineers and technical leaders across Prescryptive to build fast, accessible, well-architected interfaces on top of a governed backend architecture, with visibility into how your work connects to the company’s broader direction. The backend handles authorization and business logic, while you focus on interfaces that capture what a user is trying to do and clearly present the result.

This is a hands-on rolerequiring deep frontendexpertise, sound technical judgment, and proven ability to work through open design questions. You will build production software, make durable technical decisions, collaborate closely with others, and helpestablishthe standards these applications will build on.

What you will do

• Own the frontend architecture for applications serving internal, customer, and partner audiences, each withdifferent needs.

• Establish how these applications integrate with our backend, including interactions that complete quickly and processes that involve a longer review or approval step.

• Build a multi-tenant theming and branding architecture that allows different organizations to have a distinct, professional look and feel within a single codebase.

• Set accessibility, code quality, and documentation standards for the application suite and helpestablishthe engineering patterns that support it as the team grows.

• Work closely with the Axiom team and engineers and technical leaders across Prescryptive to resolve open design questions as they arise.What you will bring (requiredskills and experience).

What you will bring (minimumrequiredskills and experience)

• 8+ years of professional software engineering experience, with provensuccessdesigning, building, and shipping complex production applications.

• Deepexpertisein React and strongproficiencyin TypeScript, withdemonstratedownership of frontend architecture and significant technical decisions.

• Hands-on experience with MUI (Material UI) or a comparable design system, such as Ant Design or Chakra,including building and maintaining a shared component libraryand theming system, not only using pre-built components.

• Demonstrated experienceestablishinga design system orcomponentlibrary from an early, near-zero starting point.

• Demonstrated experience building multi-tenant or white-label frontend architecture, specifically theming and branding that varies by customer or organization within a single codebase.

• Demonstrated, hands-on accessibility experience, including ARIA patterns, keyboard navigation, and screen reader testing.

• Demonstrated, hands-on use of AI-assisted development tools, such as Claude Code or similar tools, as part of a responsible professional engineering workflow.

• Experience building against well-governed, strongly typed APIs where the frontend calls clearly declared interactions rather than ad hoc endpoints. Candidates from healthcare, fintech, insurance, or other regulated industries often have experience with this pattern.

• Proven ability to build interfaces around both interactions that complete quickly and processes involving longer review or approval steps, sometimes spanning hours or days. Prior experience with a workflow orchestration or business process engine is a strong plus.

• A demonstratedtrack recordworking with regulated or sensitive data, such as healthcare or financial data, and sound judgment about what should and should not be handled client-side.

• Strong written communication, withdemonstratedability to clearly document architecture, technical decisions, and the reasoning behind them.

• Proven ability to independently work through evolving architecture and open design questions, surface ambiguity, help drive decisions, incorporate input from others, and move work forward without waiting for every question to be resolved.

Ideallyyou will also have

• Conceptual familiarity with policy or authorization engines, even without direct hands-on experience with a specific product.
• Experience building both an internal tool and an external, customer-facing product.