Frontend Engineer — Consoles

The role You are the only frontend engineer on the programme and you own three consoles outright — Station, Park and Hub — plus the public website. The Station console becomes the daily working surface of every franchisee the network signs. Key responsibilities Build the Station console: day board, custody countersign, cash position, roster, stock draw and the station performance strip Build the Park console: dispatch oversight, approval queue, fleet and maintenance, station variance and cash views Build the Hub console: network view, realised-rate dashboard, reconciliation and variance board, compliance registers Build in that order — Station, then Park, then Hub. It is fixed Work against frozen contracts and mock servers from the contract freeze; engineering does not wait for design Hold first meaningful paint under two and a half seconds on the actual station tablet over a typical mobile connection Ship role-scoped negative tests for every screen, so a station token attempting a network endpoint is refused by the server rather than hidden by the interface Eligibility Three or more years of React in production, with at least three data-heavy dashboards or consoles shipped — not marketing sites State management and API integration, including live-updating views Real performance profiling: developer tools, an audit tool, and bundle budgets you actually held Role-based access patterns, and responsive work from desktop down to tablet You write component tests rather than clicking through manually What you get Three consoles and the public site, owned end to end Told honestly before you join where console polish sits if the date comes under pressure How the process runs Fill in the short form on this page. We read it ourselves. Every application is read. If we want to meet you, we call you.