From Operations to Software Engineering: The Honest Path

Starting Close to the Real Work

I didn't start my software career with a neat computer science whiteboard interview. I started working around operations, MIS, spreadsheets, and internal data.

And that turned out to be the best possible foundation.

When you work where software meets real people:

• You see how painful bad software is for the people forced to use it daily.
• You realize that people don't care what JavaScript framework you used; they care whether the report downloaded or whether the student got their login credentials.
• You build an instinctive hatred for software that silently fails.

Earning Technical Responsibility

Moving from writing scripts and automation into owning production APIs and services was driven by one simple habit: When something broke, I didn't just restart it. I investigated until I understood why it broke.

That curiosity is what led from basic scripts to writing full-stack systems, managing database migrations, designing background job architectures, and eventually stepping into technical leadership as an Associate Manager.