Careers
Four disciplines, and an open application
We are not going to list roles that may already be closed. Tell us which of these you fit and what you would want to build, and you will get an honest answer about whether there is something now.
- Structure
- Distributed
- Take-home
- Paid
- Founded
- 2024
Definition
What kind of people does CirculeID hire?
People with adjacent depth rather than category experience, because the category is only a few years old. Standards implementers, regulatory analysts, supply chain practitioners and applied cryptographers. The domain is learnable in months; that underlying experience is not, and it is what the work actually rests on.
The unusual thing about this problem is how often those four have to talk to each other. A data model decision is simultaneously a standards question, a regulatory question and a question about what a tier-three supplier will plausibly do.
Disciplines
Where you would fit
Standards engineering
You have implemented a real specification and know why the edge cases matter. GS1, EPCIS, W3C credentials, or something structurally similar.
Regulatory analysis
You can read a delegated act and turn it into field-level requirements without waiting for a consultancy to summarise it.
Supply chain practice
You have run a supplier data programme and know exactly why tier three does not fill in the form.
Applied cryptography
Signing, key custody, revocation and verification — as an engineering discipline rather than a library call.
Platform engineering
Two workloads with opposite characteristics, and an identifier that must resolve for fifteen years.
Something we have not thought of
If you can make the case that we are missing a discipline, that is a strong application in itself.
Process
How hiring works here
- 01
Send something real
Which discipline, what you have built, and what you would want to work on. A short specific note beats a long general one.
- 02
A conversation
About work you have actually done, with someone who can evaluate it rather than check it against a keyword list.
- 03
A working session
On a genuine problem from our backlog. Substantial take-home work is paid, because your time has a price.
- 04
Meet the team
The people you would work with, and an honest account of what is hard here. Timezone and scope expectations are agreed before an offer.
Answers
Frequently asked questions
Why does this page not list specific vacancies?
Because a listing that is no longer open wastes the time of the person who applies to it, and we would rather carry an open application than a stale role. Tell us which discipline fits you and what you would want to work on, and we will tell you honestly whether there is something now.
Do I need to know Digital Product Passports already?
No, and almost nobody does — the category is a few years old. What transfers is adjacent depth: someone who has implemented GS1 standards in retail, worked on regulatory reporting, run supplier data programmes, or built credential systems. The domain is learnable; that experience is not, quickly.
What is the hiring process?
A conversation about what you have built, then a working session on a real problem from our actual backlog rather than an abstract exercise, then meeting the people you would work with. We pay for substantial take-home work, and we do not run whiteboard algorithm interviews for roles that never need them.
Is the company remote?
We are distributed and do not maintain public offices. In practice that means asynchronous by default, with real overlap hours rather than the pretence that a fully asynchronous engineering team never needs to talk. Timezone expectations are stated before an offer, not after.
Next step
Send an open application
Name the discipline, tell us what you have built, and say what you would want to work on here. You will get a real answer either way.