We're not hiring right now.
When we are, this is what it'll be like.
Diviniel is small on purpose. Every architectural decision on our products today is made by people who have to defend it under scrutiny — not a committee. That won't always be true, and when it changes, it'll happen deliberately.
What it'll be like, when there's a team to describe.
Small and direct
Fewer people, fewer layers, faster decisions. We'd rather stay small longer than dilute how decisions get made.
Built by people who ship
No separation between the people who design the architecture and the people who answer for it in production.
Depth over breadth
We care more about someone who's gone deep on client-side crypto, browser security, or applied cryptography than someone with a broad but shallow résumé.
Written down, not performed
We'd rather someone read a design doc than sit through a deck. Decisions get written, not narrated.
The kind of person, not a job req.
- Engineers who've worked seriously with browser-based cryptography, WASM, or zero-trust architectures
- People who ask “what's the worst thing that happens if this is compromised” before they ask “does it work”
- A preference for removing risk over documenting it
There are none right now.
We're a small, focused team building a specific set of products, and we're not in growth-for-its-own-sake mode. We'll post here the moment that changes — with a real role, a real scope, and no filler.
If it clicks for you, email us anyway.
Not because you saw a “we're hiring” post — because you read the About page and felt something click. We read everything, even with nothing open.