Senior Frontend Developer

I'm hiring a senior frontend developer to own the frontend of Sauna, AI product for knowledge workers. This role is for someone who wants real ownership of the product experience, not someone who only wants to pick up predefined UI tickets.

You’ll work on the part of the product users see and feel every day: the interface, interaction logic, responsiveness, feedback states, and overall clarity of the experience. The product itself is complex. Your job is to make it usable without hiding the complexity in a misleading way.

This is a strong fit for someone who can take rough direction, make sound product decisions, and ship clean, thoughtful frontend work without needing constant step‑by‑step guidance.

• Own the frontend of the core product.

• Build and improve product interfaces in React and Type Script.

• Design and implement interaction patterns for complex workflows.

• Handle edge cases properly, including loading, empty, error, and transition states.

• Improve speed, clarity, and usability across the product.

• Contribute to end‑to‑end feature delivery when needed.

• 4+ years of frontend engineering experience.

• Strong React and Type Script skills.

• Experience shipping complex production web applications.

• Good product sense and design judgment.

• Ability to work independently and make decisions.

• US work authorization or O‑1 eligibility.

• Based in San Francisco or willing to relocate before starting.

• Type Script

• React

• Zustand

• Tailwind CSS

• IndexedDB

• Tan Stack

• Cloudflare Workers

This is an on‑site role in San Francisco. The interview process includes an application, short intro steps, a system design interview, and a paid work trial on a real project. The stated compensation is $180,000 to $240,000, plus meaningful early‑stage equity, health and dental coverage, 401(k), PTO, gym budget, and lunch.

• Not a role where you wait for complete specs before starting.

• Not a role where “senior” means just mentoring juniors while someone else owns the product.

• Not a role where buzzwords matter more than shipped work.

• Not a role for someone who wants to stay only inside a narrow frontend.

That requires more than React knowledge. It requires judgment: when to cache, when to refetch, what to show while work is in progress, how to handle uncertainty, and how to avoid turning a powerful product into a confusing one.