About Me

They say time flies when you’re having fun, but when you spend two decades doing something that you love, it doesn’t just fly, it blurs. This is a short exploration of my life in tech in the hope of connecting with fellow builders and minds who share this obsession.

The Origin Story: From a Nintendo Magazine to Enterprise Identity #

Every engineer has a spark that started it all. Mine didn’t come from a computer science textbook or a high-tech lab, it started with a Nintendo magazine.

As a teenager, I stumbled upon a small guide explaining how to write basic HTML in its pages.

Intrigued, I built my very first website. That tiny project cracked open a door to an entirely new world, and I quickly found myself diving headfirst into C#, SQL, JavaScript, and anything else I could get my hands on. I didn’t have to look far for inspiration; fueled by my uncle and mentor, who guided my early steps, I knew early on that this was the path I wanted to pursue. I devoured every technical book, tutorial, and problem I could find.

Building from the Ground Up: The Entrepreneurial Leap #

That early curiosity eventually scaled up, leading me to co-found a company alongside a team of talented engineers to deliver tailored software solutions for small and medium businesses.

Running that business gave me an invaluable perspective that you can’t get anywhere else: a direct, unfiltered taste of working side-by-side with end-users. Solving their real-world problems forced me to develop a true product-oriented mindset and a deep service attitude. It wasn’t just about writing clever code anymore; it was about listening closely, understanding business pain points, and building technology that genuinely made people’s lives easier.

Choosing the Red Pill #

A major turning point in my career came when I joined Microsoft. I faced a rare luxury: choosing between three distinct teams: MSN Hotmail (now outlook.com), MSN Messenger (now extinct), and Windows Live ID (now Microsoft account).

For me, it was an absolute no-brainer. What could possibly be cooler than security? Ever since I watched The Matrix for the first time, I had wanted to be a hacker (the good kind, of course). Securing complex systems felt like playing in the ultimate digital sandbox.

Fast forward 15 years, and that fascination hasn’t faded an ounce. The threat landscape has evolved, the perimeters have dissolved into the cloud, and the protocols have grown infinitely more sophisticated, but the core thrill remains. Computers and security are, and always will be, one of the most exciting spaces to work in.

The Microsoft Era: Finding My Footing at the “Olympus of Computer Science” #

When I joined Microsoft, I always looked up to the people working there. To me, it felt like the Olympus of computer science. A place where only the best and brightest could belong.

Early on, I had the chance to do some penetration testing on pre-release versions of the service. I managed to find a security vulnerability, something that, to this day, still makes me genuinely proud. Discovering a flaw in code that was already considered rock-solid was a humongous achievement for me. It was the moment it truly clicked: I am here, and I have what it takes to stand shoulder-to-shoulder with this team.

That validation set the stage for what came next. I was blessed to be part of shaping identity as the world knows it today. We were pioneering features that didn’t exist yet:

• Adding authentication via push notifications
• Shipping Two-Factor Authentication (TFA) for the first time
• Building session authentication for “dumb” devices
• Delivering quite literally the very first WebAuthn implementation in the entire industry, building it while the W3C specification was still a draft.

It genuinely felt like we were writing history. Back then, we had to explain to users why security mattered and what TFA even was. Today, those concepts are universal, every website uses them, and everyday users understand why they’re essential.

Of course, working at Microsoft back then had another massive perk: exposure to the latest and greatest before the rest of the world ever laid eyes on it. Surrounded by heavily guarded IP and early prototypes, I got a sneak peek at an Xbox One (back when it was Project Scorpio), the HoloLens (a mind-blowing augmented reality headset at the time), early Surface tablets, and Windows Phones. It was an unforgettable time to be building the future.

Forging Engineering Rigor #

At Microsoft, I met some of the most talented engineers I’ve ever had the pleasure of working with. It was an era of old-school, high-quality software and services, a time when building the best, most polished product was the absolute top priority. That’s not to say today’s software isn’t good, but priorities have shifted; in the modern spirit of rapid, continuous delivery, inevitable trade-offs are made.

That experience forged the way I view software engineering. I learned how to thrive in ambiguity and developed a high tolerance for frustration. Up until that point, my career had been spent in companies where software was an internal tool applied to business operations. Microsoft was different: it was my first time working at a place where software was the main product.

Working at that scale makes you a trailblazer. When you can’t rely on off-the-shelf package solutions, you have to build from scratch. That constraint changes how you approach architecture entirely, it forces a level of creativity and problem-solving that only grows when you work at the bleeding edge of a product-first technology company.

The Evolution of Identity: From Consumer Scale to Bare-Metal Infrastructure #

My career in identity has taken me across the entire spectrum of the ecosystem. I started on the consumer side with Microsoft Account, moved into enterprise territory with Entra ID when those teams merged, and eventually journeyed all the way to a completely different domain: infrastructure identity.

As a technical leader owning a core foundational component of Azure, I took on the biggest responsibility of my career. This identity provider ran at the bare-metal level, meaning it couldn’t rely on any other service to handle the complexity of scaling. In modern cloud architecture, it’s rare to build something that stands entirely on its own, you can almost always lean on another layer to abstract away complexity. Not here. At the bare-metal tier, you are the bedrock, the ultimate problem solver everyone else relies on.

To put its criticality into perspective: when a new Azure datacenter spun up, the absolute first thing deployed was DNS, because you need network access before anything else. Right after that came our authentication service, so that every other service could securely talk to one another. Operating at that foundational tier of cloud infrastructure profoundly shaped my leadership. It taught me how to thrive under intense pressure, navigate unprecedented complexity and juggle multiple concurrent projects.

Taking the Next Leap: DocuSign #

That incredible journey left me hungry for the next big challenge. I took a leap of faith and joined DocuSign as an architect, stepping into a role where I had a blank check to improve and secure our identity organization.

This is where I am having the most fun right now, doing my best work alongside an amazing team of brilliant people. Beyond the technical challenges, this great company has shown me that technology truly has a very human face. The team culture here is fantastic, balancing a rigorous engineering discipline with a genuine human touch that keeps everyone engaged, supported, and inspired every single day.

Fast-forward 15… 20 years, and it feels like it all happened in a flash. Yet, every morning I sit down to tackle a new challenge, I still have the same curiosity I felt as a kid building my first website. The tech changes, but the thrill of the craft never gets old.