About the role
Senior / Staff Frontend Engineer - Robot Control Interfaces
Location: Bay Area, CA (Hybrid, 3 days/week on-site)
Role Type: Full-Time
Reports To: Head of Software Engineering
Compensation: $163K-$213K
READ THIS FIRST
This is not a typical web frontend role. We need someone who has already built the control panel or operator screen for a physical machine, and who has handled a constant, millisecond-by-millisecond stream of live data coming directly from moving hardware.
You are a strong fit if you have:
• Built an operator interface for a machine that people used while it was running (a robot, industrial equipment, medical device, kiosk, point-of-sale terminal, vehicle system, or similar)
• Kept a UI fast and accurate while live data poured in from a moving machine, and can explain exactly how you did it (throttling, batching, dropping stale updates, handling reconnects)
This is probably not the right role if your experience is limited to dashboards over REST APIs, marketing or e-commerce sites, internal enterprise tools, or chat, video, or financial data feeds with no physical hardware behind them.
ABOUT OUR CLIENT
Our client builds intelligent robotics engineered to automate prescription dispensing. Their flagship machine takes stock bottles of medication and autonomously produces accurately counted, labeled vials, freeing pharmacists and technicians from repetitive manual tasks so they can focus on patient care. The system sits right behind the pharmacy counter and blends physical robotics with intuitive software.
ABOUT THE ROLE
You will take full ownership of the primary interface used to operate the machine: a large, touch-only screen built for busy pharmacy technicians in high-throughput environments. The screen shows what the robot is doing as it happens, with state streaming in from the machine over WebSockets. Over time you will also define the frontend standards for every other product interface, including cloud management dashboards, mobile controls, and future systems.
The role is open at two levels:
• Senior: you own the operator screen end to end.
• Staff: you also set the frontend standards, design system practices, and engineering workflows that other engineers build against.
WHAT YOU'LL OWN
• The operator interface: prescription queues, medication and consumable replenishment, machine diagnostics, system administration, and secure technician sign-in
• Live machine state: a screen that renders what the robot sends, stays responsive under a constant firehose of updates, and always lands on the truth after a reload or dropped connection
• Touch-first rules: touch targets of 48px or larger, high-contrast text readable at a glance, screens that advance on physical events, and safeguards against accidental taps on high-stakes actions
• A three-tier alert model (ambient status, call for attention, blocking dialog) that keeps technicians informed without overwhelming them
• A strict TypeScript contract generated from the machine's Rust source models over WebSockets
• Design-to-production fidelity: turning interactive prototypes from our product designer into React applications without losing the intent
• Quality: unit tests, end-to-end browser tests, design token enforcement, and linting
MUST-HAVES (all required)
1. Machine control interface experience: you have built the control panel, operator screen, or HMI for a real physical machine that operators used on the job.
2. Live data from moving hardware: you have built UIs that handle a constant, millisecond-by-millisecond stream of data from a moving machine without lag, dropped state, or a frozen screen.
3. End-to-end ownership of a high-availability product surface in production.
4. Advanced TypeScript with strict compiler settings, writing types that make invalid states impossible to express.
5. React 19 and state architecture where the backend or hardware owns the truth and the screen renders it.
6. Hands-on with Tailwind CSS (v4), Vite, Vitest, and Playwright.
7. A track record of turning living design prototypes into production software while staying aligned with designers.
NICE-TO-HAVE
• Fixed touch panels, point-of-sale terminals, embedded browsers, or industrial controls
• State machines and explicit states and transitions
• Design systems or standards adopted by multiple engineering teams
• WCAG 2.1 AA accessibility, or work in healthcare, industrial automation, or robotics
FIRST 90 DAYS
• Day 30: merge your first UI changes and learn the queue, replenishment, and alert flows alongside the design team
• Day 60: own design updates, refine end-to-end tests for real technician workflows, and finalize the three-layer alert framework
• Day 90: operator interface ready for production and security review, frontend guidelines written, and a roadmap for the cloud operations dashboard
WHY JOIN
Your software directly controls physical robotics working in real pharmacies. It is a small, high-trust team with no bureaucracy, and you will work in person three days a week next to the hardware and robotics engineers. Values: Servant Leadership, Do the Hard Things, Own Your Work, Default is Now.