> Markdown version of [/jobs/ext/4659173-staff-software-engineer-frontend](https://www.wearedevelopers.com/jobs/ext/4659173-staff-software-engineer-frontend). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Staff Software Engineer, Frontend - **Company:** ROMAN - **Location:** New York, NY, United States - **Salary:** $211,700 - $292,000 - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Design of User Interfaces, Human-Computer Interaction, Software Construction, Software Engineering, TypeScript, ReactJS, Concurrency, Backend, Playwright, Production Code, Front End Software Development, Api Design, Api Management - **Published:** November 10, 2026 - **Apply:** https://www.careerbuilder.com/job-details/staff-software-engineer-frontend-new-york-ny--688fc775-c5e4-4c85-9f33-fede1cf4731b ## About the Role Software Engineering, User Interface/Experience (UI/UX), Healthcare, Medical Billing, Telehealth, Pharmacy, Logistics, Concurrency, User Interface/Experience (UI/UX), Organizational Skills, * Significant recent experience building and owning production applications with React and TypeScript, with deep expertise in frontend architecture. * A track record of setting technical direction for frontend work that spanned multiple teams or systems, and seeing it through to adoption. * Experience architecting complex, stateful product workflows, such as multi-step forms, scheduling, messaging, queues, or data-dense applications. * Deep fundamentals in component architecture, state management, API design and integration, server-side rendering, accessibility, performance, testing, and failure-state design. * Experience making architecture decisions with long-term consequences. You should be able to explain what you considered, what you traded off, and what you'd do differently. * Experience owning the reliability and production health of what you and your teams ship, including observability, incident response, and follow-through after launch. * A track record of shaping product direction with Product and Design, including disagreeing constructively when the stakes were high. * Evidence of influencing engineers and stakeholders outside your own team without relying on authority. * Experience improving how other engineers work, through shared patterns, design systems, standards, tooling, or mentorship. * The ability to explain technical decisions and tradeoffs clearly to engineers, non-engineering partners, and leadership. * Evidence of connecting technical work to measurable outcomes for users or the business. Bonus Skills * Experience in healthcare, telehealth, clinical workflows, or another highly regulated industry. * Experience building software for specialized internal or operational users, such as clinicians, support teams, financial operators, or other domain experts. * Experience leading a design-system modernization or a large-scale frontend migration. * Familiarity with tools such as Turborepo, TanStack Query, React Aria, Playwright, Storybook, or Chromatic. * Experience using AI or automation to improve product workflows or engineering workflows. ## Description We're looking for a Staff Frontend Engineer to help set the technical direction for frontend engineering at Ro. Our frontend covers two kinds of products. Millions of patients use it to start and manage their care. Providers and care teams use it to deliver that care, through clinical workflows, patient-provider messaging, scheduling, task queues, and operational tools for pharmacists, care coordinators, and patient advocates. Many of these are complex, stateful, data-dense workflows. Frontend architecture directly affects how efficiently and safely care gets delivered. You'll stay hands-on in the code and also shape how we build across teams. That includes frontend architecture, shared patterns, the design system, and the standards other engineers rely on. You'll work with Product, Design, backend engineering, Data, and Clinical to turn ambiguous problems into clear technical direction. You'll be accountable for whether what we ship works for the people using it. This role is for someone who already works beyond a single project or team. We'll judge your impact by what you build and by how much better other engineers and teams build because of you. What You'll Do * Set technical direction for complex frontend product areas that span multiple teams, from problem definition through architecture, rollout, and iteration. * Find the most important frontend problems across teams, including ones that aren't on anyone's roadmap. Build the case for solving them and get teams aligned. * Make architecture decisions with long-term consequences. These cover component design, application state, data fetching, API contracts, error handling, and performance. Document the tradeoffs so others can build on them. * Lead the evolution of our shared frontend architecture and design system, including our ongoing design-system modernization, and drive adoption across teams. * Work with backend engineers and other technical leads to define clear boundaries and contracts between frontend and backend systems. * Work with Product and Design leaders on scope, sequencing, and product direction. Help them understand the technical options and what each one means for users. * Translate complex clinical, operational, and patient workflows into interfaces that are intuitive, reliable, and safe. * Balance near-term delivery against long-term engineering health, and make those tradeoffs visible to the people affected. * Raise the quality bar across frontend in testing, accessibility, observability, reliability, and performance. Own production outcomes for the systems you lead. * Use user feedback, product data, and operational metrics to judge whether what we shipped worked, and decide where to go next. * Help other engineers, including senior engineers, make better technical decisions through mentorship, design reviews, and day-to-day collaboration. * Write production code, especially on the most consequential and highest-risk parts of the work. * Participate in on-call rotations and take ownership of the health of the systems your teams operate.