Hire Me

Systems Engineer and Architect (Rust · Applied Cryptography · Confidential Computing · Embedded Systems)

NYC (EST) · Remote, async-first · Available now

I build production cryptographic systems in Rust. Transparency logs, attestation pipelines, sealed execution environments, high-throughput verification services. The kind of infrastructure where “trust me, it works” isn’t an answer — because the code has to prove it.

What I do best

• Rust systems engineering — 5K+ RPS production services, protocol to deployment
• Applied cryptography — RFC 3161, RFC 9162, Ed25519 / SHA-256, Merkle trees, JCS
• Confidential computing — Intel TDX sealed execution, remote attestation
• Audit & integrity infrastructure — tamper-evident logs, chain-of-custody, compliance receipts
• Embedded systems — analog front-end, KiCad, board bring-up against calculated values

Engagement

• Rate: on request — quoted against scope and duration
• Commitment: part-time or full-time, contract or permanent — 1099 preferred, W-2 available. Remote is the one part that isn’t negotiable.
• Model: defined weekly scope, written acceptance criteria, one decision-maker on your side
• Start: within one week

Best fit

You need a senior engineer who:

• Ships security-critical Rust code without hand-holding
• Can own a cryptographic subsystem end-to-end — spec, implementation, tests, deployment
• Reads RFCs and implements them correctly the first time
• Writes the kind of documentation your next engineer will thank you for

Common contexts: compliance and audit tooling, attested computation, evidence systems for legal/forensic use, crypto/web3 infrastructure, any project where “the DBA could silently rewrite this” is not an acceptable threat model.

Let’s talk

Fully async by default. Email first.

I don’t do interview loops. I’m happy to have a technical call about a concrete scoped engagement — and if you want to evaluate me first, send a scoped paid trial task on work you choose, and I’ll return a written result.

If you have a project in mind: include your stack, your timeline, and what outcome would make this a success. That gets us to a useful first response faster.