Open to senior backend roles
Senior Technical Lead & Backend Architect
Backend systems thatdon't break at scale.
I focus on the boring stuff — systems that stay up, scale predictably, and don't page you at 3am.
I've spent most of my career on backend systems — the parts that handle load, manage state, and fail gracefully when things go wrong. Java, Spring Boot, AWS. Mostly fintech and e-commerce, where downtime costs money.
Background
7 Years in Backend Engineering
Most of my work has been on systems where reliability matters — fintech platforms, e-commerce infrastructure, payment processing. The kind of code where bugs cost money and outages wake people up.
I've built systems handling 10M+ requests per day, led teams through scaling events that required rethinking entire architectures, and made the boring call to simplify instead of adding another layer of abstraction. The technical problems are interesting, but the judgment calls compound over time.
I care about error handling, reasonable abstractions, and systems that fail gracefully. Code that's clear enough for the next person to understand. Documentation that explains why, not just what.
As a Tech Lead, I've learned that the hard part isn't writing code — it's making decisions that won't bite the team six months later. Choosing when to refactor, when to ship with known tech debt, when to say no to a feature that doesn't fit the architecture.
Java and Spring Boot are my primary tools, but I've shipped production code in Node.js and Python when the situation called for it. AWS for infrastructure. PostgreSQL for data I care about. The stack matters less than knowing when to use what.
Full BackgroundWhat I Do
Areas of Focus
The problems I spend most of my time on.
Distributed Systems
Designing systems that handle failure, partition data correctly, and scale without rewriting everything. Choosing the right trade-offs for the problem.
Backend Infrastructure
Java, Spring Boot, PostgreSQL, Redis, AWS. The stack I've shipped production systems on for 7 years. Practical experience, not just tutorials.
Technical Decision-Making
Architecture reviews, tech debt prioritization, build vs buy. The judgment calls that compound over time.
Connect
Let's Talk
Open to discussing interesting technical challenges, architecture problems, or opportunities at companies building at scale.