samsullivan

Cardog turns raw vehicle data into facts you can check: VIN decode, market price, recalls, and what the car's own modules report. Insurers, dealers, manufacturers and the public bodies that register vehicles all use it. We're a small team and every engineer owns a whole area.

Data - Data Platform Engineer (Remote). Own the datasets: government files, manufacturer filings, dealer listings, signals from the vehicle. Decide which source wins when two disagree, and be able to prove it. SQL first, entity resolution, tens of millions of rows. Postgres, TypeScript, Workers, R2. - VIN Decode Engineer (Remote). Own decode accuracy. Read manufacturer filings line by line, write the patterns, and test them against millions of real VINs. For people who are obsessive about correctness. TypeScript, Postgres.

Design - Design Engineer (Remote). Own the component library and the screens built on it. Dense data, and making uncertain or missing values look uncertain. You design in the browser and you merge it yourself. React, Next.js, Tailwind. - Founding Engineer, Dealer Platform (Toronto / Remote). First engineer on software for dealer groups. Time in stores, then ship it the same week. Strong Postgres, multi-tenant.

Business - Account Executive (Toronto / Remote). Enterprise and public-sector sales cycles measured in quarters. Run technical first calls alone and pull your own numbers in SQL. - Policy & Standards Lead (Ontario). Represent us in the consultations and standards bodies writing the rules for vehicle data. Closer to counsel than comms.

Field - Hardware Engineer, Vehicle Interface (Toronto). Own the diagnostic-port device: board, firmware, enclosure, from bench to a unit on a dealer lot. C or Rust, CAN at the frame level, UDS/ISO-TP against real cars. - Forward Deployed Engineer (Ontario). Take named accounts from the first meeting to a running system. TypeScript, SQL, and some time under dashboards.

Apply on the page (each role takes applications in place) or write to [email protected].

We're the system of record for the Canadian vehicle: raw automotive data turned into facts that can be checked. Our open-source VIN decoder sits underneath a government vehicle registry.

Some of what's interesting:

- A government registry, a manufacturer's own filing, a listing site and an insurance record will describe the same truck four different ways, and nothing in any of those files says they're the same truck. Reconciling that, for every vehicle in the country, in a way that holds up when a regulator asks how you know, is most of the data work.

- Seventeen characters on a door frame encode manufacturer, plant, model year and build attributes — badly, inconsistently, and differently per manufacturer. Public reference data covers some of it. The rest gets worked out from filings, recall documents, and patterns inferred across millions of vehicles.

- We read vehicles directly over OBD-II now. Forty modules answered on a recent Hyundai, each reporting its own part number and installed software version. Nothing downstream of the VIN moves when a module is reflashed, so no registration, history report or dealer system knows what software is actually in a car.

Hiring: VIN Decode Engineer, Data Platform Engineer, Infrastructure Engineer, Founding Engineer (dealer platform). TypeScript, Postgres, Cloudflare Workers.

Full descriptions and apply: https://cardog.app/careers

https://cardog.app/careers

https://cardog.app/careers

https://cardog.app/careers