top of page
ankit_avatar_square.jpg

Hi, I'm Ankit.

Why "The Builder."

 

I didn't pick The Builder. because it sounded catchy. I picked it because it is the simplest description of what I actually love doing, and what I believe great engineering leadership is about.

 

It started early, staying up late watching MacGyver with my dad and obsessing over how things worked under the hood—from taking apart hardware, to designing 64- and 128-core processors at Intel, to still slipping into a half-day coding hack session or building an AI agent from scratch over Christmas break just to keep calluses on my hands.

 

Along the way, colleagues and mentors remarked that even as the organizations I led grew to hundreds of people, I never stopped thinking like a builder: pairing a high technical bar with real empathy, holding strong opinions while staying open to being convinced, and refusing to let teams hide behind slideware.

 

That is what I believe in: being the surgeon, not the architect. Cutting away accidental complexity, pushing ownership down to small teams, and building systems that actually hold up when they meet the real world.

 

My Journey

 

I started out designing 64- and 128-core processor architectures at Intel, spent nearly 15 years at Amazon and AWS learning what happens at the 1% tail, rebuilt Foursquare's data platform, led Engineering, Product, and AI at Cruise, and today serve as SVP of Engineering at Hims & Hers.

 

​Across every stop, the job has always come down to the same thing: cutting away accidental complexity so small, high-trust teams can build things that matter.

What Each Chapter Taught Me

Scale (Amazon FBA, Prime & AWS IoT): What happens at the 1% tail when billions of requests or devices hit a race condition?

 

Safety (Cruise): When a probabilistic system meets the physical world and gets it wrong, who catches it and how fast?

 

Care (Consumer Healthcare): Would a clinician and a patient actually trust this?

 

​

 

How I Lead — Operator README

 

• Read COE traces from first principles instead of settling for surface-level root causes.

 

• Run small, working architecture reviews focused on state boundaries and failure modes, not slideware.

 

• Favor 5 teams of 10 over 2 functional orgs of 25—clear ownership beats coordination overhead.

 

• Keep coding on weekends so technical intuition stays sharp.

 

​

 

Outside Work & Personal Interests

 

• Teaching Kids to Build: Tinkering at the kitchen table—electronics, robotics, and learning how to break problems down instead of blindly trusting the first answer.

 

• Education & Community: 12+ years serving as an Education Advisor with the American Red Cross, alongside causes in children's education, economic empowerment, and STEM.

 

• Hands-On Weekend Coding: Never letting technical intuition turn into slideware—building small AI tools, benchmarks, and weekend prototypes to stay close to the metal.

 

​

 

What Colleagues Say

 

​"High bar paired with real empathy." · "Strong opinions, open to being convinced." · "Excellent writer and storyteller."

Let's Connect

I enjoy trading notes with fellow engineering leaders, founders building high-trust AI products, and builders navigating hard scale or org-design problems.

Connect on LinkedIn · Advisory & Speaking → /contact

Views and opinions expressed on thebuilder.info are strictly my own and do not represent my employer.

bottom of page