3 Reasons Why I quit my job as Google’s Chief Developer Advocate

After seven incredible years at Google, I've decided to embark on a new adventure. In this post, I'll share the three main reasons behind my decision to leave one of the most coveted jobs in tech. This isn't just about my journey – it's a reflection on career growth that might inspire you to reassess your own professional path.

Introduction

When I first joined Google, I was a wide-eyed developer living out my dream. Google lived up to its reputation – free food, brilliant colleagues, cutting-edge tech, you name it. But as the saying goes, all good things must come to an end. Or in this case, evolve into something new.

Let's dive into the three big reasons why I decided to leave Google, and explore how these principles can apply to anyone's career, regardless of where you are in your professional journey.

Reason #1: I Wanted to Get Uncomfortable Again

After seven years at Google, I found myself in a comfort zone. I could debug our systems in my sleep and probably dreamed in Google's internal programming languages! While this level of expertise is great for productivity, it's not ideal for personal growth.

Comfort, when it comes to career growth, can be a sneaky dream-killer. I realized my growth was slowing down because I wasn't being challenged like I used to be. So, I made a decision that might sound crazy – I chose to make myself uncomfortable again.

By leaving Google, I'm throwing myself into a new world of tech stacks, unfamiliar codebases, and yes, probably a few moments of impostor syndrome. But that's where the magic happens. That's where we grow, innovate, and become the best versions of ourselves as developers and tech leaders.

It's like learning a new programming language. At first, it's frustrating, but as you push through the discomfort, you start to see the world in a new way. You bring fresh perspectives to old problems and innovate in ways you never thought possible before.

Reason #2: Changing the Outcome Requires Changing the Input

In coding, if you keep using the same input, you'll always get the same output. This principle applies to our careers too. I realized that if I wanted different results in my career – new skills, different types of projects, a fresh perspective – I needed to change my input.

Google was an incredible input. It taught me so much and shaped me as a developer and a person. But I started to wonder: what else is out there? What could I learn in a different environment? What problems could I solve that I haven't even encountered yet?

Leaving Google isn't about running away from anything. It's about running towards new experiences, new challenges, and new inputs that will hopefully lead to exciting new outputs in my career.

Reason #3: Every Role Has a Shelf Life

Roles in our career are like favorite childhood toys. They serve a purpose, bring us joy, and help us grow. But eventually, we outgrow them. And that's okay! It's natural, it's healthy, and it's how we progress in our careers.

I realized that my role at Google, as amazing as it was, had served its purpose in my career journey. I had achieved many of the goals I set for myself when I joined, and even surpassed some I hadn't even considered. I had grown, learned, and contributed in ways I never imagined possible.

But I also realized that my future goals, my vision for where I want to be in 5 or 10 years, required something different. It required me to write a new chapter in my career story.

Conclusion

Leaving Google wasn't an easy decision. There were sleepless nights, lengthy pros-and-cons lists, and yes, a few tears. But ultimately, I knew it was the right move for me.

The real lesson here is that your career isn't about following a preset path or sticking with something just because it's comfortable or prestigious. It's about continually assessing where you are, where you want to go, and making the moves necessary to get there.

As I embark on this new chapter, I'm filled with a mix of excitement, nervousness, and gratitude. I encourage all of you to take a moment to reflect on your own career. Are you still growing? Are you challenged? Are you on the path to where you want to be?

Remember, your career is a marathon, not a sprint. Keep pushing your boundaries, be open to change, and never, ever stop learning.

Thank you for letting me share this personal journey with you. I can't wait to tell you all about my new adventures soon. Until next time, keep coding, keep growing, and most importantly, keep being your awesome selves!

Bye Bye Google, Thanks for everything!

Previous
Previous

What is Platform Engineering? How is it different from DevOps?

Next
Next

What are AI Agents?