The honest story of how I became an engineer, what I care about, and the convictions that shape the software I build.
I didn't start my software career through a conventional computer science pipeline or a neat whiteboard algorithm round. I started working close to real operational pain—spreadsheets, MIS systems, internal logistics, and manual data pipelines.
And in hindsight, that was the most valuable foundation I could have had.
When you sit next to the coordinators and support personnel who have to use internal software for eight hours every day, you develop an instinctive empathy for the user. You see firsthand that nobody cares what trendy framework was used; they care whether the report downloaded, whether the data got corrupted, or whether the system timed out during month-end.
“When something broke, I didn't just restart the server or apologize. I stayed late and dug into the logs until I understood exactly why it broke.”
That habit of relentless forensic curiosity is what drove the progression from basic automation scripts to writing full-stack web applications, designing database schemas, architecting background job queues with BullMQ and Redis, and eventually stepping into technical ownership as an Associate Manager at College Vidya.
Today, as a Software Developer at ProSync Infotech, I focus on the parts of systems that have to actually work: data integrity, idempotent API boundaries, predictable database migrations, and clean developer abstractions.
// INTELLECTUAL CHARACTER
“Ledgers where every cent must balance, background queue workers that never drop messages, idempotent API contracts, and zero-downtime database migrations.”
“I have an unreasonable amount of respect for a well-designed relational schema with proper foreign keys, check constraints, and indexed access paths.”
“If the employee has to keep a browser tab open for 20 minutes for a background job to finish, something has gone architecturally wrong.”
“Most software does not need 15 microservices. It needs a well-structured monolith, strict module boundaries, an indexed PostgreSQL database, and good typography.”
“Currently training myself to spend more time sketching architecture, failure modes, and state transitions on paper before typing the first line of code.”