About
I build things before anyone tells me to.
AI Automation Engineer at AWS India. I design systems that turn operational processes into software - combining AI, APIs, workflow orchestration, and human judgment to solve problems at scale. Three years inside one of the world's largest cloud platforms has shown me how enterprises actually operate, where friction lives, and what automation can realistically fix.
I have worked on both sides of operational systems - first as the person following the process, and now as the person designing the automation that replaces it.
Experience ->The longer version
In 2015, I walked into a room full of students from across the country and argued Jordan's geopolitical position, its regional pressures, and its foreign policy challenges in front of a national Model UN in Delhi. I was still in school. I spent weeks preparing because I wanted to understand the problem deeply before speaking about it. That habit never left.
Three years later, while most of my college batch was settling into predictable routines, I was walking into restaurants across a tier-3 Bihar city, negotiating commission agreements on foot, and running a food delivery operation I had built from scratch because the gap existed and nobody else was solving it. When larger players entered the market with capital, scale, and incentives I could not match, I shut it down and returned to my studies.
No drama. Lesson taken.
Markets change, advantages disappear, and timing matters. What stayed with me was the instinct to spot a gap early, build quickly, and stay objective when the facts change.
When I joined Amazon in 2021, I also volunteered with Braven, a California-based nonprofit where I coached students from multiple countries on career development and professional growth. I worked alongside experienced professionals who gave their time for the same reason I did: knowledge becomes more valuable when it moves.
Looking back, the common thread across every role has been the same: understand how a system works, identify the bottleneck, and redesign it so fewer people have to think about it manually.
On AI
Most people give AI a command and wait for an answer.
I treat it as a thinking partner - something to challenge, interrogate, and build alongside.
The difference shows in the outcome. A well-directed collaboration between human judgment and AI produces results neither would reach independently. A passive interaction simply produces average answers faster.
Recently, I designed and built a production-style AWS architecture spanning Bedrock Agents, serverless infrastructure, observability, security controls, compliance documentation, testing, and deployment while working full time. AI accelerated execution, but the leverage came from architecture, trade-offs, and decision making.
The tool mattered. The thinking mattered more.
The direction
I am drawn to problems that sit between technology, operations, and people - the places where a better system changes how entire teams work.
Today that means AI automation, workflow orchestration, and customer-facing systems. Over time, I want to build products that solve meaningful operational problems at scale.
Everything I am doing now - AWS, automation, customer systems, and the projects I build independently - is part of that direction.