Backend Developer

One API serves catalogue lookups, image rendering and delivery. You would work across all of it.

• Extend the endpoints: search, catalogue traversal, resolution by VIN and by plate, delivery options
• Keep response times where they belong, which mostly means caching the right thing at the right layer
• Make failure legible. When a request cannot be served exactly, the API falls back and says so rather than erroring
• Work on the rendering pipeline: colours, shadows, grounding, cut-outs, formats and sizes on the fly
• Read the error reports customers send and fix the cause rather than the symptom

• You have built and run an HTTP API that other companies depended on
• Python or TypeScript, and willing to work in whichever the task needs
• You have opinions about caching and can defend them
• You would rather ship a small thing this week than a large thing next quarter
• English for the code and the customers

• The whole system, not a slice of it, and enough trust to change it
• Customers you can talk to directly when a design decision needs a real answer
• No sprint theatre. We decide in a conversation and then build
• Fully remote, flexible hours, hardware you actually chose