From CMS Intern to Engineering Lead

The transition from managing a Django Rest Framework and React CMS during my Deep Info Lab internship to my current role at eQ Technologic wasn't a linear progression of learning new frameworks, but rather a shift in how I view system responsibility. Back in 2021, I remember a production bug crashing a live demo during a client meeting; that specific moment of chaos taught me more about the reality of shipping code than my university coursework ever did. I spent a lot of time struggling with JWT authentication and Nginx configurations, trying to make sense of how pieces fit together under pressure. When I moved to floc, the technical stack shifted to Flutter and Firebase for a social discovery app, which is when the distinction between "frontend" and "backend" started to feel irrelevant to me. I was owning the entire lifecycle, including CI/CD pipelines with Docker and GitHub Actions, which required a much broader perspective than just writing UI components. At Smarter.Codes, the work became more about data integrity and backend refactoring for products like Hybrid.Chat, NayakAI, and TalkingDB. I was building NLP pipelines to turn multi-turn conversations into structured data, and while that kind of work isn't always glamorous, it is where you learn that the unrequested refactors and the test suites people ignore are what actually prevent a system from collapsing months later. Now, my focus at eQ Technologic is on leading refactors of legacy modules and building internal tools that my teammates actually use. I've realized that being an engineer isn't about being an expert in every tool in the shed, but about having the ownership to sit with a problem until it's solved. You gain more value by owning a feature you don't fully understand than by staying in a comfort zone with easy tasks, and you have to constantly ask why a system was built a certain way if you want to actually understand system design.