The mandate: Own the user experiences that make Retell's platform usable — prompt management, dashboards, analytics, and customer-facing tools — built in React and TypeScript. You lead frontend projects end to end from architecture through launch, and you work directly with customers to onboard, debug, and turn what you learn into UX improvements. The framing that pulls the right candidate: this is a product-surface-owner role at a company where the frontend genuinely is the product. Small team, no frontend org above you, and a design problem nobody has solved — making a probabilistic system legible to an operator who isn't technical. Note the customer collaboration, and screen for it. Working directly with customers to onboard and debug is a named responsibility, same as the backend req. Frontend engineers who want to live entirely in the codebase will find that unwelcome. What You'll Own
-
Core UI features: prompt management, dashboards, analytics tools
-
Responsive, intuitive interfaces in React, TypeScript, HTML, CSS, JavaScript
-
Frontend projects end to end — architecture, coding, iteration, launch
-
Collaboration on backend APIs and DevOps to keep the whole path fast and scalable
-
Direct customer onboarding, debugging, and translating feedback into UX improvements Requirements Hard gates:
-
2+ years building production-grade apps with React and TypeScript. Both, not React alone.
-
Degree in CS, CE, or equivalent practical experience
-
On-site in Redwood City
-
Can code live. Two 45-minute technical rounds — the first is React-specific — plus a three-round onsite. Profile:
-
4–8 years total for the senior bar (the JD's 2+ is the floor, not the target — the band signals senior)
-
Founder-style ownership. The JD says "take ownership like a founder" and pairs it with "clean design thinking."
-
Learns new tools and frameworks fast
-
Collaborates well in a small team, balancing clarity and momentum Strong bonuses:
-
Complex data-dense UI work — dashboards, analytics, observability tooling, admin consoles, log viewers. Closest match to what this person will actually build.
-
Real design taste. "Clean design thinking" is in the JD, there's no dedicated design org at 50 people, and the product is developer- and operator-facing. Candidates with a portfolio, a personal site with taste, or visible design sensibility get a real bonus.
-
Developer tool or platform UI experience — the audience is technical
-
Real-time UI: WebSockets, streaming updates, live call monitoring
-
Graph, node-based, or flow-builder interfaces (React Flow, canvas work) — directly relevant given Conductor
-
Audio UI: waveform rendering, transcript playback, call review interfaces
-
Frontend performance work at scale
-
Startup experience, especially early-stage Location and visa:
-
On-site, Redwood City
-
Sponsorship: Yes — H-1B, TN, L-1, E-3, F-1 (OPT/CPT), and O-1 Anti-patterns
-
Marketing-site and landing-page specialists. Different job entirely.
-
Engineers who ship pixel-perfect components but can't reason about state architecture or data flow
-
Designers who code a little
-
Big-company frontend engineers who worked inside a mature design system with a dedicated design partner and never made a product decision
-
Anyone who wants zero customer contact
-
React-only candidates with no real TypeScript depth — the first technical round is React-specific and TypeScript is a stated requirement
-
Remote requirements Who Will Thrive Here
Someone who's owned a complex product surface and cared about both the architecture and how it feels. They've built a dashboard that engineers actually liked using, they have opinions about state management they can defend, and they notice bad spacing. At 50 people with no frontend org and no design team above them, they get to decide what this product looks like — which is the whole reason to take this over a bigger company paying similar money.