Senior Frontend Engineer

ComPsych Corporation•,

1d•$150,000 - $200,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 Senior Frontend Engineer who already works this way and wants to own significant parts of our frontend foundation. This is a high-leverage role: you'll spend more time on domain-level architecture, technical direction, and production ownership than on writing every line of code 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 strong React or comparable frontend experience is directly relevant.

Requirements

Deep TypeScript and modern frontend engineering experience.
Built substantial applications with Angular, React, or a comparable framework and understand component architecture, state and reactive data flows, routing, rendering, APIs, asynchronous behavior, and the tradeoffs behind the patterns you choose.
Strong browser and web-platform fundamentals. Understand semantic HTML, CSS, the DOM and event model, rendering behavior, browser APIs, progressive enhancement, and cross-browser behavior, and can diagnose difficult issues using profiling and developer tooling.
Designed reusable frontend systems other engineers depend on. Understand component API design, composition, tokens, theming, package and version management, migrations, and backward compatibility — and know where abstractions should stop.
Can design and own a frontend testing strategy. Know what belongs at the unit, component, interaction, visual-regression, and end-to-end levels.
Can set the bar for frontend accessibility and performance. Can define accessible interaction patterns, validate them with assistive technology, and diagnose rendering, network, and browser performance using instrumentation and evidence.
Understand frontend security and privacy deeply enough to design for them. Can reason about XSS, authentication and session handling, browser storage, sensitive data in logs, analytics and URLs, third-party scripts, and other browser-specific risks.
Operate as a technical leader. Turn ambiguous problems into sound technical decisions, explain the tradeoffs, mentor other engineers, and have carried meaningful production and incident responsibility.
Already work AI-first. Agentic tools are a primary development surface for planning, implementation, testing, and review. Delegate well-scoped work, catch plausible-but-wrong APIs and browser behavior, and remain accountable for what ships.

Nice To Haves

Experience with Jest, Testing Library, Playwright, Storybook, or similar tooling is preferred.
Hands-on Angular expertise.
Experience with Storybook or visual-regression tooling.
Contributions to a shared component library.

Responsibilities

Own a frontend domain end to end, as your core contribution. Take responsibility for its architecture, quality, evolution, and production behavior, including the shared capabilities other engineers and teams depend on.
Set technical direction within the frontend platform, directing implementation rather than owning every line yourself. Design patterns that solve real product needs, establish clear boundaries, and delegate meaningful build work to AI agents — dropping into the code yourself when debugging or complexity demands it.
Solve difficult frontend problems in production, and keep review and judgment human. Lead diagnosis when behavior, performance, or reliability breaks down, make deliberate browser-support tradeoffs, and stay accountable for what ships and what an incident teaches you, regardless of who or what wrote the code.
Partner with Product, Design, QA, and full-stack engineers to shape solutions. Bring frontend architecture, browser behavior, accessibility, and platform constraints into decisions early enough to change the solution.
Set the quality bar for your domain. Define how accessibility and testing should work, make changes verifiable before release, and ensure consuming teams can evolve safely as the platform changes.
Raise the engineering bar around you, mentoring other engineers, reviewing consequential changes, and making strong engineering decisions repeatable without depending on your review.