The problem you own

Compliance teams buy evidence they can hand to a regulator or a court. You own the ledger: every notice, consent, stop, export, and destruction, hash-chained, signed by a non-exportable device key, externally anchored. And you own the attestation path that makes the ledger credible: the policy engine binary and compiled policy bundle measured into a secure element at boot, so a verifier learns not just which rules were asserted, but which software actually enforced them.

What you will do

Design and build the hash-chained evidence ledger and its one-click compliance-report export.

Own key lifecycles, external anchoring, and the transient-buffer commitment semantics.

Build the measured-boot and attestation path, from software attestation now toward the secure-element and capture-interlock hardware roadmap.

Face the auditors: your artifacts are what security reviews interrogate before any pilot signs.

What great looks like

Security engineering is a design discipline for you. You can demonstrate to a CISO, not assert, that what was discarded was never written.

Stack and signals

Systems engineering, applied cryptography literacy, TPM/secure-element familiarity, compliance-facing communication.

Compensation

Cash is deliberately founder-grade; the equity is the point, and it is real. You will work directly with the founding technical leadership, in the codebase, from week one.

How we hire

One conversation about your best work, one deep-dive on a system or a deal you owned, one paid working session on a real Cull problem, one founder conversation. Usually under two weeks.