Eighteen people
and 1,340 feeds
that never stop.
Reference data is unglamorous, permanent infrastructure. If the idea of owning a country’s company register — the parser, the latency, the number we publish — sounds like a good year, read on.
Six roles, all with a named owner
Each one is written by the person you would work with. Apply by writing to the address below — it goes to them, not to an applicant tracking system.
- Have built something that parses hostile real-world formats and stayed correct for years
- Read Spanish or Portuguese well enough to tell a filing type from a gazette notice
- Think a coverage percentage is a promise rather than a metric
Full-time
- Have shipped a retrieval or entity-resolution system that real money depended on
- Can explain a calibration curve to someone in procurement
- Would rather publish the cases you lose than round them off
Full-time
- Have run a latency-sensitive service at four nines and written the postmortems
- Believe an error message is part of the product
- Have opinions about idempotency keys and can defend them
Full-time
- Write documentation that assumes the reader is competent and busy
- Have maintained a client library across a breaking API version
- Notice when a quickstart takes nine minutes rather than three
Full-time
- Have run an Article 28 programme at a company that actually processes personal data
- Can write a policy a customer reads to the end
- Would push back on a launch, in writing, with reasons
Full-time
- Have sold a developer-facing product to a technical buyer without a demo script
- Speak German at a business level
- Are comfortable telling a prospect the product is a bad fit
Full-time
Nothing here fits but you think we are wrong about that? Write to jobs@spotit.ai anyway. Two of the eighteen arrived that way.
Four things that are true here
Stated so you can decide against us early. Every one of them costs us something, which is how you know they are real.
Publish the number you lose on
SPOT-Bench includes the cases we get wrong, the coverage table shows Tier 2 markets at 9% financials, and the status page keeps every postmortem. It is easier to hold a standard than to remember which figure was for whom.
Small team, whole problems
Eighteen people. Nobody owns a slice of a pipeline — you own the jurisdiction, from the polling strategy to the number on the coverage page. That is a lot of rope and it is the point.
Writing over meetings
Decisions are written down before they are discussed. Two fixed meetings a week; the rest of the calendar is yours to defend.
Registers do not care about your sprint
A court publishes when it publishes. We build for the median filing, alert on the tail, and treat a holiday schedule as a monitoring input rather than an excuse.
Hiring, start to finish
Four steps, two to three weeks end to end, and a stated salary band before the second conversation. We do not run competitive processes against a deadline and we do not ask for unpaid work.
- 01Written intro
Send whatever tells the story — a repository, a document, a note. No cover letter template, no “tell us about yourself”. We reply either way, inside a week.
- 02Conversation, 45 min
With whoever runs the team. What the work is, what it pays, and whether you want it. Salary band stated in this call, before you invest more time.
- 03Paid work sample, 4 h
A real problem from a real backlog, scoped to half a day and paid at €600. Take it whenever suits you. No take-home marathons, no algorithm trivia.
- 04Two conversations
One on the work sample with the team, one with a founder about the next two years. Then a decision within 48 hours, with reasons either way.
What the job comes with
Stated in full, because a benefits page that says “competitive” is telling you something.
Spotit Ltd is an equal opportunity employer. Candidate data is processed under the privacy policy and deleted 12 months after a decision unless you ask us to keep it.