About
Engineer, Product Manager, Director — In That Order
I've designed the hardware, written the firmware, owned the roadmap, and built the team. My leadership is grounded in having done the work.
The Path
How I Got Here
I grew up in India — Chennai and Mumbai — and came to Minnesota for grad school at the University of Minnesota. As a kid, I was the one taking things apart to see how they worked, then building something new from whatever was lying around. That creative impulse — the high of making something exist that didn't before — is what pulled me into engineering. From taking apart toy RC cars as a kid in Chennai to leading engineering teams in Minnesota — I'm grateful for the people who made that journey possible, and for the curiosity and relentlessness that kept me going.
My career has covered a lot of ground — deliberately. I've been a hands-on embedded systems engineer, a product manager defining roadmaps and P&L, and a director building and leading multi-disciplinary teams. I've worked in aerospace, industrial automation, and professional AV. I've built hardware products, firmware, and software platforms. I believe the best engineering leaders understand the whole picture — not just the code or the circuits, but the business model, the customer problem, and the team dynamics that determine whether something actually ships.
I started my career as an electrical engineer at Joby Aviation, working on eVTOL aircraft systems in collaboration with NASA. I designed the schematics, did the board layout, wrote the firmware, and modeled the mechanical enclosure for a motor controller. It taught me what breadth actually looks like. I spent nine years at Rockwell Automation, growing from an individual contributor into a product management role, learning how to build products at scale and make engineering decisions that align with business strategy.
Today at Williams AV, I lead a team building professional audio and assistive communication products. These are the systems that make courtrooms, classrooms, and conference rooms work for people with hearing loss and language barriers. It's technology that matters — and that connection between engineering work and real human impact is what I've always been chasing.
What I've learned across these three very different environments — a venture-backed startup, a Fortune 500 multinational, and a PE-backed small business — is that the skills transfer imperfectly. What makes you effective at a 10,000-person company can actually slow you down at a 200-person one, and vice versa. Having worked across all three, I've built intuition for which playbook fits which situation.
Philosophy
How I Lead
Align the Rowing
Get everyone pointed in the same direction before optimizing for speed. Clarity of purpose beats intensity of effort.
Best Idea Wins
Meritocracy of ideas over hierarchy of titles. The best solutions come from teams where anyone can challenge the direction — including the boss.
Build the System
Processes and structures that work even when all the players have changed. Resilient teams don't run on tribal knowledge and unwritten rules.
Right-Sized Structure
Enough process to scale, not so much that it suffocates. The goal is a system that balances rigor with the speed and autonomy that good engineers need to do their best work.
Beyond Work
Community & Volunteering
Volunteer CTO
MN Tamil Sangam & Tamil School
Architected the entire software stack — community website, school LMS, a timeline history of Tamils, and AI-based applications. Built and maintain the AWS cloud infrastructure.
Parai Instructor
Board Member & Performance Lead
I teach Parai — a traditional Tamil percussion instrument — and lead the performance team for community events. Music and cultural preservation are important to me.
AI Educator
Workshop Instructor
Conducted a week-long AI and machine learning fundamentals workshop for high school students and working professionals, focused on Tamil language applications.