We build the image API behind tens of thousands of vehicle listings. What you build reaches production the same week, and you talk to the people using it rather than to a ticket about them.
Build the studio our cars are shot in. Lighting, materials and paint that hold up across two thousand models without a photographer.
Read the role Design3D Render Artist, part-timeThe same studio work at half the week. For someone with a practice of their own who wants a steady piece of it.
Read the role Design3D Render Artist, freelanceProject work on the render pipeline. Take a batch of vehicles, deliver finished studio renders, invoice per batch or per day.
Read the role EngineeringBackend DeveloperBuild the API behind every image here. Catalogue, rendering, delivery, and the caching that keeps it fast.
Read the role EngineeringBackend Developer, part-timeHalf a week on the API. A defined area rather than the whole system, so twenty hours is genuinely enough.
Read the role OperationsCatalogue Data SpecialistOwn the vehicle catalogue: which cars exist, what they are called, and why a customer thinks one is missing when it is not.
Read the role SalesSales and PartnershipsTurn inbound interest into customers. Dealer groups, marketplaces, leasing and rental platforms, mostly across Europe.
Read the roleFive steps, and you always know which one you are on.
The form on each role, or an email. A CV is enough to start. No cover letter, no motivation essay, no account to create.
Within two working days, either way. A no comes with a reason, not with silence.
Half an hour with the people you would work with, not with a recruiter reading from a sheet. You ask as much as we do.
A small piece of actual work, paid if it takes longer than an afternoon. No unpaid take-home projects, no whiteboard riddles.
Within a week of the last conversation, with an offer you can take away and think about.
There is no career ladder with nine rungs and no separate department for every concern. Some weeks the work is unglamorous catalogue maintenance. If you want a defined lane with someone else owning the edges of it, this is the wrong place.
You see the whole thing. The API, the customers using it, and what your change did to both. Decisions are made in a conversation rather than in a quarterly planning cycle, and you will be trusted with more than your title suggests.
