Engineer, Protocol & SDKs

Role overview

A senior individual contributor role focused on owning one or two SDKs end-to-end and hardening the verifier and signed-receipt path within an open-core protocol stack. The work treats Registry reliability as a first-class concern and approaches security as a routine engineering constraint rather than a research exercise. It is well suited to senior backend engineers comfortable with cryptographic primitives and thoughtful API design.

Responsibilities

- Own one or two SDKs end-to-end across Python, TypeScript, Go, or Rust - Harden the verifier and signed-receipt path within the protocol - Improve and maintain Registry reliability as a standing engineering priority - Apply cryptographic primitives such as signatures, DIDs, and JWT/COSE-style formats in production code - Design and evolve APIs with security treated as a baseline requirement

Requirements

- Senior-level backend engineering experience with SDK or library ownership - Comfort working with cryptographic primitives including signatures, DIDs, and JWT/COSE-style formats - Strong API design skills and a disciplined approach to security - Ability to operate effectively in a remote, async-first environment

Nice to have

- Experience working on standards-track or open-core protocol projects - Proficiency across more than one of Python, TypeScript, Go, or Rust

Benefits and work setup

- Remote-first working environment with an async-first interview loop - Human-reviewed application process with responses within five business days