I'm a software engineer with a strong focus on systems programming, security, and infrastructure tooling.
I actively contribute to open-source projects in the container, fuzzing, and reliability ecosystem.

• Systems & Infrastructure

  • Containers, runtimes, and orchestration internals
  • Linux, namespaces, cgroups, syscall boundaries
  • Reliability, correctness, and hard-to-debug failure modes

• Security & Testing

  • Fuzzing, sanitizers (ASan/UBSan), crash triage
  • Memory safety, undefined behaviour, edge-case discovery
  • Large-scale automated testing infrastructure

• Languages

  • C / C++ (primary)
  • Go (infrastructure & tooling)
  • Shell, Python (glue & automation)

I’m particularly interested in projects that sit close to the OS and require careful engineering trade-offs.

• containerd
  • Runtime internals, container lifecycle, low-level integration
• Related tooling in the cloud-native ecosystem

• ClusterFuzz / ClusterFuzzLite
  • Fuzz infrastructure, crash reporting, triage workflows
• google/fuzztest
  • Modern fuzzing for C++ with strong ergonomics

I enjoy working on problems where correctness, performance, and observability intersect.

• Prefer simple, explicit designs over clever abstractions
• Strong believer in tooling-assisted correctness
• Care deeply about:
  • Code review quality
  • Long-term maintainability
  • Developer experience for contributors

• Collaborating on serious open-source infrastructure
• Mentorship and deep technical discussions
• Projects where:
  • Performance matters
  • Bugs are expensive
  • Tests actually mean something

• GitHub: you’re already here 🙂
• Open to discussions via issues, PRs, or design docs

“Make it correct, then make it fast — and never the other way around.”