
I’m a technical operator with experience across backend engineering, data pipelines, and emerging Web3 infrastructure. I like building things, understanding how systems behave under real-world constraints, and explaining that thinking to others.
I’ve worked on distributed systems, real-time APIs, DAO tooling, and data engineering projects using Rust, Python, and TypeScript. I enjoy the engineering side, but I’m also drawn to the product and analytical parts of shipping — the “why are we building this and how does it actually help?” layer.
Right now I’m exploring roles that sit between backend development, product, and technical diligence. I’m curious about how systems scale, how teams make decisions, and how to evaluate the technical foundations of a project.
If you’re working on something in crypto infrastructure, compute networks, DePIN, or developer-facing tools, I’d love to talk.
Bethesda, MD
Yes, to the following:
I started in marketing during my undergrad, but I eventually realized I cared more about how systems worked than how they were presented. That curiosity pushed me toward software, and I taught myself development and data engineering through side projects, tutorials, and a lot of trial and error. My first real technical experience came at Truth Initiative where I supported analytics pipelines and learned how organizations use data to guide decisions. During that time I became fascinated with crypto and programmable money, which motivated me to pursue a Master’s in Software Engineering so I could build a deeper understanding of distributed and data-driven systems. That interest carried into my roles at Accenture and Agora where I worked on crypto-related projects and learned how production systems behave under real constraints. Those experiences shaped how I think about engineering today. I try to stay practical, curious, and focused on understanding the entire system rather than only the code in front of me.