Description review
Cardog | Toronto, Canada or REMOTE | Full-time
Cardog · Full-time · back to the listing
HR standards
29/100
poor
Title ↔ description
34/100
poor
Reads as
Data Engineer
96% confident
How others title the same work
Large employers
- Data Engineer, Product Analytics Meta
- Senior Staff Data Engineer Mozilla
- Staff, Analytics Engineer, GTM Data Science & Analytics Twilio
- Senior Software Engineer - Data Platform Coinbase
- Senior Security Data Engineer Doordash
Startups
- Business Intelligence Engineer GoSats
- IPinfo.io | Data Engineer | REMOTE (Anywhere) | Full-time IPinfo.io
- Senior Data Engineer Camber
- Senior Data Engineer Instrumentl
- Cardog | Toronto, Canada or REMOTE | Full-time Cardog
What the listing never says
- No section describes what the person would actually do. Scope clarity
- No pay range published. Candidates cannot tell whether applying is worth their time. Pay transparency
- No location or timezone policy stated, so a candidate cannot tell where they may work from. Scope clarity
The listing, marked up
Nothing in the wording of this listing tripped a check. The scores above still judge how complete and coherent it is.
https://cardog.app/careers
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
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