Frontend Engineer
Build accessible, responsive vehicle search, report and account interfaces with the shared Car Check design system.
Car Check helps people understand a used car’s history. We bring vehicle records together with clear explanations, keeping the source, timing and limits of the information close to each finding.
We care about the whole experience, from the reliability of a lookup to the words that help someone decide what to ask next.
The opportunity
We are looking for a Frontend Engineer who cares about what a product feels like when someone is using it for a real decision. A vehicle report contains unfamiliar language, multiple sources and different levels of certainty. The interface needs to make those differences easy to understand on a small screen as well as a large one.
You will work closely with design and product engineering on the journey from the first search to the detailed report. That includes forms, navigation, charts, account screens and the shared components that keep the experience consistent. Accessibility and responsiveness are part of the work from the beginning.
There is room here for someone who notices the details: a focus state that gets lost, a layout that shifts while loading or an error message that offers no way forward. We want those observations to become dependable improvements across the product.
What you’ll work on
- Build clear, accessible interfaces. Use semantic HTML and shared React components to make search, report and account flows understandable with a keyboard, a screen reader or touch input.
- Make every state deliberate. Design loading, empty, error and success behaviour with the team, keeping people informed without unnecessary movement or interruptions.
- Protect consistency across the product. Work within the existing typography, themes and control patterns, and improve the shared implementation when several screens need the same behaviour.
- Keep information usable on smaller screens. Refine dense report sections, data displays and navigation so that important context survives changes in viewport and text size.
- Investigate performance at the source. Track down avoidable rendering, layout shifts and expensive assets, and evaluate whether an optimisation improves the experience people receive.
- Verify meaningful interactions. Cover critical behaviour with focused tests and review the details that are easy to miss, from focus restoration to preserving form input after a failure.
What you’ll bring
- You have built and maintained React and TypeScript interfaces used beyond a prototype, with a solid understanding of browser behaviour and CSS layout.
- You can explain how you approach accessible forms, focus management and interactive components, including situations where native browser behaviour is the right choice.
- You are comfortable translating a design into a responsive implementation and discussing details that need to change when real content or unusual states appear.
- You can diagnose a rendering or interaction problem systematically, using evidence to separate the underlying cause from the symptom someone reported.
- You care about maintainability and can contribute to a shared component without solving one screen’s problem at the expense of every other screen.
Useful, but not required
- Experience with Next.js rendering patterns, design systems and interfaces that support more than one colour theme.
- Work on accessible charts, long documents or other interfaces with a high density of information.
- Examples of measurable performance improvements or accessibility fixes that changed how people could use a product.
Your first few months
- Learn the shared components and review a complete search and report journey across its main states and screen sizes.
- Ship a focused interface improvement that resolves a real usability, accessibility or reliability problem.
- Identify a repeated source of friction and improve the shared pattern so the benefit reaches more than one page.
How we work
Start with the buyer, follow the evidence and make the complex clear. We value thoughtful questions, shared learning and care in the details of what we build.
We work in focused pieces, make important decisions easy to follow and bring questions into the open while there is still time to act on them. You will have room to shape the work, with the responsibility to explain your choices, ask for help and follow through on the result.
Apply for this role
Share an interface you built and explain a difficult interaction, accessibility decision or performance problem you worked through. Include your specific contribution and a link or short walkthrough where possible.