Product Engineer
Build Car Check’s vehicle search and report experience across product interfaces and supporting services.
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 Product Engineer who wants to own a useful part of the product from the first question to the finished experience. At Car Check, that might mean helping someone search for a vehicle, understand an unfamiliar finding or return to a report they saved earlier.
You will work across interfaces, application logic and data flows, making decisions with designers and the people who understand vehicle records. The interesting problems often sit between those disciplines: what should a buyer see when one source is unavailable, and how should the experience recover when a request fails?
This role suits someone who enjoys talking through a problem as much as implementing it. You will help choose a sensible scope, ship the work, look for evidence that it helped and improve the parts that still feel confusing. Ownership continues after the first release.
What you’ll work on
- Own complete product journeys. Connect the interface, validation, server behaviour and stored data so that searching for a vehicle or opening a report works as one coherent experience.
- Make uncertain results understandable. Work with research and design to distinguish unavailable information, incomplete checks and findings that need a buyer’s attention, including the next useful action.
- Build for the awkward cases. Handle interrupted requests, expired sessions, duplicate actions and partial responses without losing a person’s work or presenting an outcome we cannot support.
- Ship focused improvements. Break a larger problem into useful releases, explain the tradeoffs and keep the implementation straightforward enough for another engineer to maintain.
- Follow the work into use. Add relevant instrumentation, investigate errors and combine product evidence with customer questions to decide what needs attention next.
- Raise the quality of the shared code. Review changes thoughtfully, improve reusable patterns and write tests around behaviour whose failure would affect a customer’s experience.
What you’ll bring
- You have taken web features from an unclear brief through implementation and release, and can explain both your contribution and what you learned after people used them.
- You are comfortable with TypeScript, React and server application code. You can follow a request through an API and database without treating those boundaries as someone else’s problem.
- You understand the practical details of forms, accessibility, authentication and error handling, and know when a small interaction has consequences elsewhere in the system.
- You can balance speed with care. You recognise when an established pattern is enough and when reliability, data integrity or a difficult interaction deserves deeper work.
- You communicate clearly with people outside engineering, ask questions early and use feedback to improve the result rather than defend the first implementation.
Useful, but not required
- Experience with Next.js, relational databases and products that combine information from several external services.
- Examples of improving a purchase, account or saved document workflow after investigating how people actually used it.
- An interest in making complex consumer information understandable without hiding important qualifications.
Your first few months
- Understand the registration search and report journey, including where source information enters the product and how failures reach the interface.
- Take a focused improvement through discovery, implementation and release, with clear checks for the behaviour that matters.
- Use the result and feedback to propose the next improvement, leaving the code and decision history easy for the team to follow.
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
Tell us about one feature you owned across the stack. Explain the user problem, a decision you made and what happened after release. A product link, code sample or short written walkthrough is useful.