Applied cryptographer_

What you'll do

Audit cryptographic implementations as they actually ship — key handling, protocol state machines, randomness, signature and encryption misuse, padding and nonce mistakes — and turn each class of bug into a registry workflow that finds it. Build the cryptography benchmarks for the bench. Publish what you find, after disclosure.

What we look for

You have broken or fixed real cryptographic code, not just read about it. You read specifications and papers for pleasure and can tell a textbook weakness from an exploitable one — and prove which is which. You are at home in at least two of Rust, Go, C and Python, and in the libraries those languages use for cryptography.

What we offer

Your work is public under your name and runs on the platform for whoever picks it up. The strongest models, the budget to run them, and a bench built to tell you honestly whether your workflow works.