About Me

I’m a systems engineer focused on infrastructure, security, distributed systems, robotics, and low-latency software.

I build tools which operate close to failure boundaries: policy engines, robotics platofrms and infrastructure.

Previously, I worked at SpaceX and American Express, where I learned how difficult it is to operate complex systems at scale, and how important it is to focus relentlessly on the critical path.

Most of my work starts from asking the same questions:

What actually breaks in the real world?
What assumption was made yesterday, but no longer applies today?

That usually leads me toward reliability, security, operational simplicity, and removing unnecessary abstraction.

• Cybersecurity and red teaming
• System hardening through KISS
• Reverse engineering and exploit development
• Low-latency systems
• Hardware acceleration, through CUDA, OpenCL, OpenACC, FPGAs
• Artificial Intelligence (traditional, not LLM-based)
• Large scale data analysis
• Search and large scale data structures
• Embedded systems (Microcontrollers, SoCs, FreeRTOS, Linux)
• Learning new things and trying the impossible

At SpaceX, I worked on the design software team, building internal systems operating under real operational pressure.

The environment forced me to think differently about engineering. Reliability, simplicity, and time-to-market often mattered more than ideal architecture. Requirements changed constantly, timelines were aggressive, and systems frequently had to work long before they were elegant.

A large part of my work focused on internal tooling around PCB/PCBA design workflows, including CAD kernels, rendering systems, and integrations with electronic design tooling such as Altium.

More importantly, the experience changed how I think about complexity. I learned that systems usually fail at the boundaries: between teams, between assumptions, and between what is necessary versus what is merely nice to have.

At American Express, I worked primarily as a Java/full-stack engineer on customer-facing enterprise systems.

A large part of the work involved maintaining and improving legacy applications operating at significant scale, alongside building automation and tooling to reduce operational friction for developers and deployments.

Working at AmEx gave me a firsthand look at how large organizations accumulate complexity, and how much engineering effort ultimately goes into keeping critical systems stable and operable over long periods of time.

During my tenure at AmEx, I also became increasingly interested in application security and systems behavior under failure conditions. Part of this involved researching vulnerabilities in internal systems, including exploit development and identifying sandbox isolation weaknesses to validate security assumptions.

• LinkedIn
• GitHub
• Email me