Thoryn

Careers

We're small. We grow when we have to.

We're not running an active hiring funnel. The team is deliberately small and grows when a specific bottleneck makes another hire obvious. If you'd be that hire — get in touch anyway.

Open roles

None we’re currently advertising

Honest version: we'd rather hire one person who fits than three who don't. Open roles get posted here when they exist; until then, this list stays empty.

No open roles right now.

Check back, or reach out below if you think we should make an exception.

What we’d hire for if forced

The shape of a Thoryn engineer

  • Cares about identity protocols. OAuth 2.0, OIDC, SD-JWT VC, mdoc, OID4VCI, OpenID4VP — these aren't footnotes for us, they're the floor.
  • Reads RFCs as primary sources. When in doubt, fetch the RFC. The spec is the source of truth, not the SDK's default behaviour.
  • Comfortable with EU-first. Hetzner Germany. Dutch jurisdiction. NIS2, DORA, GDPR. eIDAS 2.0 is not abstract.
  • Small-team energy. No committees, no managers-of-managers. Decisions are made in public on PRs and ADRs.

Locations

Where you’d work from

EU only — for the same reasons we host in Germany. Remote-first, with quarterly in-person weeks somewhere central (Amsterdam, Berlin, or similar). No US-based contracts; no third-country employment.

Think you’d be the right hire?

Reach out via contact. Tell us what you'd want to work on and why now. We respond to every message — even when the answer is 'not yet'.