Queue is seeking a Frontend Engineer at the Senior/Staff level to own the operator screen and subsequent screens for our robotics-based pharmacy automation platform. The role centers on a touch-only interface used by pharmacy technicians on a large, on-machine display, with responsibilities spanning end-to-end ownership from design through production. You will ensure the screen matches design reviews, and the frontend aligns with the machine's React-based application, working in concert with our product designer.

What you’ll own - The operator screen: scope includes the prescription queue, replenishment of drugs and consumables, machine health, administration, and on-screen sign-in via a keypad. - The prototype and the application: the UI exists in two forms—a reviewed design prototype and the React application that runs on the machine. You are responsible for keeping them in sync. - The design rules: touch-first constraints (no mouse or keyboard), with targets no smaller than 48 pixels, legible text during busy tasks, and screen transitions driven by physical events rather than taps. Actions that cannot be undone are placed where technicians won’t mis-tap them. - The interruption model: a three-layer system (ambient status, attention request, blocking dialog) with clear rules for usage in each scenario, including machine fault alerts. - The interface contract: the screen renders machine state; there is no domain state on the screen; TypeScript types are generated from the machine’s Rust source, and build failures indicate contract drift. The on-machine software engineers

Queue is seeking a Frontend Engineer at the Senior/Staff level to own the operator screen and subsequent screens for our robotics-based pharmacy automation platform. The role centers on a touch-only interface used by pharmacy technicians on a large, on-machine display, with responsibilities spanning end-to-end ownership from design through production. You will ensure the screen matches design reviews, and the frontend aligns with the machine's React-based application, working in concert with our product designer.

What you’ll own - The operator screen: scope includes the prescription queue, replenishment of drugs and consumables, machine health, administration, and on-screen sign-in via a keypad. - The prototype and the application: the UI exists in two forms—a reviewed design prototype and the React application that runs on the machine. You are responsible for keeping them in sync. - The design rules: touch-first constraints (no mouse or keyboard), with targets no smaller than 48 pixels, legible text during busy tasks, and screen transitions driven by physical events rather than taps. Actions that cannot be undone are placed where technicians won’t mis-tap them. - The interruption model: a three-layer system (ambient status, attention request, blocking dialog) with clear rules for usage in each scenario, including machine fault alerts. - The interface contract: the screen renders machine state; there is no domain state on the screen; TypeScript types are generated from the machine’s Rust source, and build failures indicate contract drift. The on-machine software engineers