Veera
Annapureddy
I build backend systems that have to work - the kind where a bug at 2am means someone's order disappears or a notification never lands. Eight years in, I still find that genuinely interesting.
About
Who I am
Right now I'm at Grainger on the Customer Order team - which sounds less dramatic than it is. The system handles over 1.3M+ Kafka events a day, seven years of order history, and millions of accounts. When something breaks, people notice. That's kept me sharp.
Before that I worked in healthcare software at GuideWell Florida Blue, and insurance-domain applications at Aflac. Different industries, same underlying challenge: distributed systems with real consequences when they go wrong.
I lean toward the backend - Java/Kotlin, Python, Kafka, data pipelines - but I've shipped enough full-stack work to hold my own on the front. The part I find most satisfying isn't any specific technology. It's when a team is working well together, the architecture is clear, and everyone understands what they're building and why. I spend a lot of time trying to get teams there.
I mentor developers, do code reviews, pairing sessions, run knowledge-sharing sessions, and pull people into architecture conversations earlier than most teams do. Not because it's in a job description - because it's how the best work gets done.
I have an M.S. in Computer Science from Columbus State University. I got there via a B.Tech from KL University in India, and a move to the US that pushed me to rebuild from scratch. That path taught me more about adaptability than any course did.
Currently
Customer Order domain - Java/Kotlin, Python, Kafka, Databricks, Snowflake
Running internal sessions on architecture and engineering practices with the team.
Thinking out loud on CI/CD, Kafka event design, and distributed systems. More in progress.