Staff Frontend Engineer

ComPsych Corporation•,

7d•$175,000 - $225,000

About The Position

We're modernizing how ComPsych builds technology — new customer-facing web and mobile experiences, a unified design system, and AI-powered capabilities across our products. That means raising the engineering bar for how we design, build, and operate software, with Engineering, Product, and Design working together end to end. We're looking for a Staff Frontend Engineer who already works this way and wants to define how our engineering organization builds frontend software going forward. This is a high-leverage role: you'll spend more time on frontend architecture, platform design, and technical direction across teams than on writing code line by line yourself. Frontend Engineers are software engineers first, held to the same bar for design, testing, performance, security, and production quality as everyone else — with added depth in the browser, component architecture, accessibility, and design systems. We build in Angular + TypeScript, but we're looking for deep frontend architecture experience rather than Angular tenure specifically.

Requirements

You have deep frontend architecture expertise. You've set technical direction for substantial Angular, React, or comparable applications and can reason about state and reactivity, rendering, module and package boundaries, dependency management, browser behavior, and performance — and explain where each abstraction should stop.
You have the technical depth to lead an Angular + TypeScript platform. Whether your deepest experience is in Angular, React, or a comparable ecosystem, you understand the underlying component, browser, build and bundling, package-management, testing, and performance concepts well enough to transfer that experience across frameworks and make consequential platform decisions.
You've built frontend platforms other teams successfully depend on. You understand component APIs, tokens and theming, versioning, migrations, backward compatibility, contribution models, and adoption — and you've turned recurring problems into capabilities that persist after you step away.
You can set quality, performance, security, privacy, and accessibility standards across teams. You can establish testing and quality gates, performance expectations, accessible interaction patterns, and approaches to authentication, browser storage, sensitive-data exposure, third-party scripts, and other frontend security risks.
You can reason about production systems beyond the browser. You're comfortable with API and service boundaries, authentication and authorization, asynchronous systems, observability, failure modes, deployment behavior, and the tradeoffs between frontend and backend responsibilities. You use production evidence to turn recurring problems into platform-level improvements.
You create technical leverage across teams. You turn organization-level ambiguity into durable technical direction, write and defend consequential decisions, build alignment without relying on authority, and grow Senior engineers into broader ownership.
You already work AI-first at organizational scale. You've created patterns and guardrails that let teams delegate meaningful engineering work to AI agents while keeping the output understandable, testable, secure, maintainable, and consistent with the platform.

Nice To Haves

hands-on Angular expertise
experience owning a component library or design system consumed outside your own organization
contributions to open-source frontend tooling

Responsibilities

Set frontend architecture strategy across products, as your core contribution. Define where shared patterns and platforms create leverage, where teams need flexibility, and how frontend architecture should evolve as our products and organization grow.
Lead the design system as an engineering platform, directing implementation rather than owning every line yourself. Set its technical direction, contribution and release model, and adoption strategy — delegating meaningful build work to engineers and AI agents, and dropping into the code yourself when the highest-risk work demands it.
Own frontend quality and production health as a design decision, not an afterthought. Define how accessibility, performance, reliability, security, and testing are designed into frontend systems, make platform health measurable, and turn recurring production failures into systemic improvements.
Make excellent frontend engineering easier for every engineer. Create the APIs, tooling, guardrails, documentation, and defaults that let teams move faster without requiring frontend specialists to review every routine decision.
Set AI-native engineering practices for frontend teams, and keep review and production judgment human. Define how agentic work is specified, validated, tested, and reviewed so AI increases engineering leverage without creating hidden inconsistency or technical debt — and stay accountable for what ships, and what an incident teaches you, regardless of who or what wrote the code.
Raise the bar for how the organization builds frontend software, growing Senior engineers into broader ownership, building alignment across Engineering, Product, Design, and QA, and staying hands-on in the highest-risk technical work when doing so de-risks the platform.