I build backend systems that don't break.
APIs, databases and infrastructure that hold up under real load. Python and Node.js, end to end.
{
"role": "Backend Developer",
"focus": ["APIs", "Databases"],
"languages": ["Python", "JavaScript"],
"open_to_work": true
}
Who's behind the API
I work on the side of the stack most people never see, the part that has to keep working at 3am. APIs, databases, caching layers and request pipelines. If it has to stay up, it's probably my problem.
I care less about the trendiest framework and more about what holds up under real traffic: clean endpoints, predictable data models, and queries that don't fall over at a million rows.
Most of my time is spent between Python and Node.js, picking whichever fits the job instead of forcing one tool to do everything.
- Role
- Backend Developer
- Focus
- APIs, databases, systems
- Languages
- Python, JavaScript
- Status
- Open to work
Tools I reach for
Languages and runtime
Frameworks
Data and speed
How I got here
- Ongoing
Self-driven backend engineering
Learning by building real systems (APIs, database design, caching strategy) instead of stopping at tutorials.
- Foundation
Computer Science fundamentals
Core grounding in data structures, algorithms, and how systems talk to each other under the hood.