Engineer. Builder. Relentless learner. Here's who I am beyond the code.

Ajay
Full-Stack Software Engineer
Quick Facts
Origin
Andhra Pradesh, India → USA
Education
MS in Computer Science
Current Role
Software Engineer @ SLK Holdings
Focus Areas
I grew up in Andhra Pradesh, India, where my curiosity for how things work led me straight into computer science. What started as tinkering with code in college quickly became an obsession — not just with writing software, but with understanding whycertain systems endure while others crumble. I earned my Bachelor's in Computer Science from Jawaharlal Nehru Institute of Technology, then moved to the United States to pursue my Master's at the University of Central Missouri (GPA 3.5), where I dove deep into full-stack architecture, real-time systems, and machine learning.
Today, I work as a Software Engineer at SLK Holdings, where I design and ship production systems on Azure — from event-driven pipelines with Service Bus and BullMQ to containerized microservices on AKS. I've cut API response times by 60%, reduced manual operational overhead by 90%, and integrated payment and shipping systems that handle real money and real logistics. But what drives me isn't just the engineering — it's the thinking behind it. I obsess over why one tech stack fits a problem better than another, how system design decisions ripple through performance and maintainability, and what it takes to build products that people actually rely on.
My biggest dream is to become an entrepreneur who builds software that isn't just useful today, but sustains for decades. I believe in the discipline of relentless building — the kind where you show up every single day, ask hard questions about every product and system you encounter, and let progress silence the doubters. For the past year, building has been my obsession: from GitScripe (a multi-agent LLM platform) to DayVault (an offline journaling app) to contributing to open-source projects like OpenClaw. I'm not here to ship once and walk away. I'm here to build things that last, and I'm just getting started.
I don't just learn frameworks — I study the principles underneath them. When I pick a technology, it's not because it's trendy; it's because I've analyzed the business domain, the network constraints, the performance characteristics, and the long-term optimization trade-offs. Generalized system design knowledge is what lets me move fluidly between React and Flutter, between Node.js and .NET, between cloud-native and fully offline architectures.
I think of discipline not as routine, but as a kind of possession — the relentless drive to keep going when everyone around you says it's pointless. You prove them wrong not with words, but with progress. That's the mindset I bring to every project, every pull request, and every product decision.