Building bridges between bits and narratives
I'm a full-stack engineer who thinks like a product builder and approaches problems like an urbanist—focused on systems, patterns, and how people actually experience the things we create.
How I think about building
Systems over features
Good products aren't collections of features—they're systems that solve real problems. I focus on understanding the full context: user needs, technical constraints, and organizational goals.
Impact over activity
Engineering is about outcomes, not output. I measure success by what changed for users and the business—whether that's 2x engagement, 733% growth, or enabling new editorial possibilities.
Craft over perfection
Great products ship. I believe in building with care, iterating based on reality, and knowing when good enough beats perfect. Speed and quality aren't opposites—they're both essential.
Cross-functional fluency
I invest in understanding how different functions work—engineering, design, editorial, product—so I can communicate more effectively and collaborate more smoothly. Better understanding leads to better work.
The path from cities to code
Urbanism & Systems Thinking
Caribbean Queens. A childhood spent noticing how neighborhoods breathe—who stays, who goes, what changes when a new building goes up. Urban planning gave me the vocabulary. My thesis mapped change in Bushwick and South Queens. What I was really after: how systems work.
Journalism & Storytelling
At The Amherst Student, I discovered something: good storytelling needs good infrastructure. So I built it. Rebuilt the digital platform, grew readership from 1,200 to 10,000. The lesson that shaped everything after—tools matter as much as craft.
Engineering & Product
Now at The Atlantic, building platforms that serve millions of readers. The urbanism training stuck—I think about software the same way I think about cities: user flows, sustainable systems, how the pieces connect.
What I'm focused on now
Currently building audio infrastructure at The Atlantic, working on problems of scale, reliability, and editorial velocity. I'm drawn to the intersection of deep technical work and product thinking—understanding not just how to build, but what to build and why.
Areas I'm actively exploring:
- AI/ML integration in content platforms and how it changes editorial workflows
- Search and discovery at scale—making large datasets useful and explorable
- Building sustainable systems that outlast their creators
- The role of technology in civic infrastructure and journalism
How I build
Product Engineering
Next.js, React, TypeScript, GraphQL, Node.js, Django, Python
Infrastructure & Scale
AWS, GCP, PostgreSQL, Redis, monitoring, performance optimization
Product & Leadership
Cross-functional collaboration, technical architecture, team leadership
Tools & Process
Linear, Figma, Git, CI/CD, agile workflows
Let's work together
I'm looking for engineering roles where I can tackle complex technical challenges while staying close to the product—particularly in journalism, civic tech, or products that help people understand complex systems.