Principal Software Engineer

Role Overview

• Own the frontend architectural vision across all product teams, covering React/TypeScript patterns, state management conventions, API integration approaches, and build/deploy tooling
• Establish and maintain frontend engineering standards through Technical Design Documents, design reviews, and direct collaboration with team leads
• Drive decisions on shared libraries, tooling, and patterns—ensuring teams converge rather than diverge
• Identify and resolve technical debt in frontend systems that slows product team velocity
• Partner with the Principal UI/UX Lead to co-own the design system strategy.
• Build, maintain, and govern a shared component library that all product teams consume, ensuring consistency in look, feel, and behavior across the platform
• Define contribution models so team-level engineers can extend the design system without fragmenting it
• Ensure the component library supports multi-product scenarios cleanly, particularly as acquired products are consolidated
• Act as the go-to technical authority for frontend engineering decisions across the organization
• Provide architectural guidance and review across all teams shipping frontend code—not as a gatekeeper, but as a force multiplier
• Identify and drive resolution of systemic frontend issues: performance bottlenecks, accessibility gaps, testing strategy inconsistencies, and developer experience friction
• Build reference implementations that demonstrate how teams should adopt shared patterns and components
• Set the bar for frontend testing strategy (unit, integration, end-to-end) and ensure teams have the right frameworks and patterns to ship with confidence
• Drive improvements to frontend developer experience: build times, local development workflows, CI/CD pipelines, and debugging tooling
• Champion frontend performance, accessibility (WCAG compliance), and security best practices across the organization
• Contribute to developer experience initiatives where they intersect with frontend tooling adoption

Requirements

• 8+ years of professional frontend engineering experience, with deep expertise in React and TypeScript
• Demonstrated experience operating at a Staff or Principal level with cross-team architectural influence—not just within a single product team
• Proven track record of building and maintaining shared design systems or component libraries consumed by multiple teams
• Strong opinions on frontend architecture (state management, API layers, rendering strategies, monorepo vs. multi-repo) backed by experience shipping at scale
• Experience defining and driving frontend standards across an engineering organization
• Deep understanding of frontend testing strategies and tooling (Jest, React Testing Library, Playwright/Cypress)
• Clear technical communication—ability to write effective design documents, present to engineering leadership, and facilitate cross-team technical discussions
• Ability to influence without authority—driving alignment through technical credibility and collaboration rather than org chart power.

Tech Stack

• Cypress
• Jest
• React
• TypeScript

Benefits

• Health insurance
• 401(k) matching
• Flexible work hours
• Paid time off
• Remote work options