Backend Engineer · Systems Architect
// Based in India. · Available for opportunities
↓ scrollI design infrastructure that scales, backends that hold, and systems that don't wake their owners up at 3am. The invisible layer — made deliberately.
// This architecture pattern underlies most of the projects below
Built for a solopreneur who needed enterprise CRM without the enterprise overhead. React frontend, Supabase backend. The architecture challenge was making complex relational data feel simple to a non-technical user without sacrificing data integrity.
An agency landing page built with the care of a product. Vite + React. The design challenge was creating a premium feel without over-engineering the build. Result: sub-1s FCP, Lighthouse 97+, zero runtime dependencies in production.
veylox.abeer.lol ↗An AI system that chains model calls into coherent multi-step workflows. The engineering challenge was managing state between inference calls without a traditional server — using event-driven architecture with a queue-backed job processor.
A fitness tracking application built not because similar apps don't exist, but because building it right was the point. PostgreSQL stores every workout as an append-only log. The schema was designed for time-series queries before the first line of application code.
The homelab is where the abstractions disappear. You can't pretend to understand networking until you've debugged your own DNS at midnight. Every production decision I make is informed by something I broke here first.
Design for failure. Everything else is a feature.
The simplest system that solves the real problem wins.
If it breaks at 3am, I should be the one who built it.
Undocumented systems are gifts to your future enemy.
Open to senior engineering roles, infrastructure consulting, and genuinely interesting problems.