Cryptography Engineer

The Role

Zero-knowledge proofs for Annex identity. Triple-oracle verification for MCR. Attestation cryptography for MABOS license compliance. This is not “we use AES-256” security. This is novel cryptographic system design for systems that don’t have existing playbooks.

What You'll Do

• Design and implement zero-knowledge proof systems for Annex identity and communication
• Build cryptographic verification systems for MCR triple-oracle consensus
• Implement and maintain attestation cryptography for MABOS license compliance
• Research and develop novel cryptographic protocols for cognitive architecture security
• Audit and verify cryptographic implementations across the stack

Requirements

• PhD in cryptography, mathematics, or computer science with cryptographic focus — or equivalent demonstrated expertise
• Published work in zero-knowledge proofs, verifiable computation, or applied cryptography
• Production implementation experience — papers are necessary but not sufficient
• Rust or C required
• You understand the difference between cryptographic theory and cryptographic engineering, and you’re excellent at both

Compensation

All positions include equity in Ceridwen.ai. Salaries are TBD and will be determined based on role scope, experience, and what you bring to the table. We will not insult you with a lowball offer, and we expect you not to waste our time with inflated expectations disconnected from contribution.

The Builder Clause

We don't care where you went to school. We don't care if you went to school. Our founder is self-taught, started coding at 13, and built a 602,000-line cognitive architecture without a CS degree.

Meet the qualifications, or show us what you've built. Either path works. Both paths demand excellence.

Apply

Ready to move? Send a short note of relevant proof-of-work — past shipped projects, metrics you moved, or a draft of your first 30 days.