Casual self

About

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.

Snapshot

Location

Bethesda, MD

Open to relocation?

Yes, to the following:

  • San Francisco, CA
  • San Diego, CA
  • Seattle, WA
  • Denver, CO
  • New York, NY
  • Boston, MA
  • Miami, FL

Core Stack

  • Rust
  • Python
  • TypeScript

Domains

  • Crypto infra
  • Data pipelines
  • Distributed systems

History

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.

What I Do Well

  • Backend development in Rust, Python, and TypeScript
  • Understanding distributed and crypto-influenced systems
  • Communicating clearly with technical and non-technical teams
  • Reasoning about product decisions and system behavior
  • Breaking down complex problems into simple steps
  • Building and debugging data pipelines

Where I Create Value

  • Improving performance, reliability, and data flow
  • Evaluating technical risk and system design
  • Translating product goals into clear engineering work
  • Supporting teams during discovery, architecture, and delivery
  • Bringing curiosity, structure, and steady problem-solving
  • Helping teams make practical decisions instead of theoretical ones

What I am Looking For

  • Backend or platform engineering roles
  • Technical product roles focused on developer experience or infra
  • Solutions or protocol support roles that blend engineering with communication
  • Technical diligence, research, or platform work in crypto or infra
  • Teams building in crypto infrastructure, DePIN or compute networks, or dev-tools

How I Work

  1. Understand the problem
  2. Workshop a solution
  3. Evaluate and iterate
  4. Build and deliver
  5. Measure and optimize
I try to understand the problem space first, then map out the simplest path that will actually move things forward. Good solutions usually show up after a few careful iterations, not on the first attempt. I like to test ideas in small steps, learn from what the system tells me, and adjust until the result feels solid and reliable.

Connect with me: