Careers
Show us a bug you found and how you found it. Contest placements, bounty disclosures, a write-up of a vulnerability class, a proof of concept you built for fun — any of those tells us more than a decade of listed job titles.
Read code adversarially, build proofs of concept, write findings people can act on. You would own findings on reports from your first engagement — which means the quality of the work is attached to you, and to us.
Engagement-by-engagement collaboration on chains and techniques outside our in-house depth. You are named to the client before the engagement is signed and you sign the section you reviewed. We do not white-label anyone's work as our own.
No role listed that fits, but you have public work we can read? Send it. We are small enough that hiring is opportunistic rather than scheduled, and a strong researcher tends to create the role they wanted.
Working here
No. We care about demonstrated ability to find bugs, which can come from contest placements, public bounty disclosures, CTF results, protocol engineering, or a write-up of a vulnerability class that shows you understand the mechanism. A CV without any of those is hard for us to evaluate, whatever it says.
Yes, fully. We work IST (UTC+5:30) and overlap with European mornings and US evenings. During an incident everyone works the client's hours.
A conversation about work you have already done, then a paid trial review of a real contract with a written report, then a decision. We pay for the trial because asking for unpaid audit work is asking for free labour.
Yes. Several engagements need specialists for one chain or one technique, and we name partner researchers to clients before an engagement is signed. If you are strong in Rust, Move, Cairo or formal verification, that is the most likely first collaboration.
Write anyway if you have public work we can read. We are small, so hiring is opportunistic rather than scheduled — a strong researcher who shows up with a good finding tends to create the role.