Senior Staff Frontend Engineer

About the Role

OpenLoop is the clinical and operational infrastructure that digital-health brands, clinics and employers use to run virtual care across all 50 states. Our clients put their brand on the front end; everything behind it runs on us: clinicians, intake, scheduling, charting, pharmacy and fulfillment, payments and licensing. Clients reach that infrastructure through one client platform, from a no-code storefront to a full Partner API, and our job is to make it effortless for them to adopt.

As a Staff Frontend Engineer you are the technical architect of our unified web platform: one front end, composed from many services and built by many teams. You decide how the front end is structured, packaged and distributed, you own how fast it loads and how we know, and you lead the consolidation of existing apps onto it without breaking the clients who depend on them. You write production code every week, you set the patterns the rest of engineering builds on, and you keep the end user’s experience at the center of decisions that are too often made from the backend out.

This is an architecture role, not a pixel-pushing one.

What You'll Do

• Architect one front end over many services. Design the structure of a unified web platform that sits on top of many backend services and is built by multiple teams: module boundaries, routing, shared state, and how teams ship independently without stepping on each other.
• Decide how front-end code is packaged and distributed. Own the strategy for shared libraries, component systems and package distribution, so a change made in one place is safe everywhere it lands.
• Own performance end to end. Set load-time and bundle budgets, find and fix what slows the platform down, and put real-user monitoring behind every page so performance is measured, not assumed.
• Consolidate without disruption. Lead the migration of existing web apps into the unified platform in a deliberate sequence, with clear compatibility windows, so clients and users never feel the seams.
• Build for the person on the other side of the screen. Work closely with UX designers and product to turn designs into accessible, responsive experiences that hold up on desktop and mobile browsers, for patients, clinicians and clients alike.
• Raise the bar. Set front-end coding standards, review code, and mentor the full-stack engineers who work in the front end today. Help design our front-end interview loop and serve as a technical interviewer.

Who You Are

Required Qualifications:

• 10+ years of software engineering experience, primarily in front-end/UI. Your career has been built in the front end, not as a backend engineer who also does UI.
• Deep expertise in React and Next.js, along with modern TypeScript and build tooling.
• Experience building or scaling a large enterprise front end: one UI composed of many services and built by many teams.
• A track record of making UIs highly performant: you can name the performance problems you diagnosed, how you measured them, and what changed after you fixed them.
• Strong problem-solving and system-level thinking: you reason about the whole platform, not just the component in front of you.
• Real care for the end-user experience, and a habit of thinking from the customer's or patient's point of view.
• Clear communication with engineers, designers and product partners, including explaining architectural tradeoffs to people who are not front-end specialists.

Preferred Qualifications:

• Experience with micro-frontend architectures or module federation.
• Familiarity with user personas, UX research and accessibility standards.
• Comfort with design tools such as Figma; we have dedicated UX design support, so this is a plus, not a requirement.
• Experience in healthcare or another regulated domain where a mistake has consequences beyond a rollback.
• Bachelor's degree in Computer Science, Engineering or a related technical field, or equivalent practical experience.

How You Work

OpenLoop's values are prescriptive, and this role tests all of them:

• Disciplined Intensity: effective under real deadline pressure, and you build systems and standards instead of becoming the only person who can fix the frontend.
• Do No Harm: patient safety, accessibility and data privacy come first, and you know when to slow down to do it right.
• Step In, Stay In: your ownership travels through the migration to the outcome, not to the handoff.
• Purposeful Speed: you ship fast without leaving behind something only you can maintain.
• Clarity Over Comfort: you say the thing, explain the why, and invite disagreement.