I alluded to this a few days ago, but I have a new role. Starting today, I am back at Microsoft. I’ve joined the Microsoft Identity division as a Principal PM and will be helping drive the efforts to build the best identity Software Development Kits (SDKs) and tools for developers that use services such as Microsoft Azure Active Directory and the Microsoft Account.
If you asked me 20 years back as to what I want to do with my life, I'd probably answer with something like "build stuff with computers." From the early days of my career, to some of the more recent adventures, I tried to find teams where I can be very hands-on with the tech stack and build, build, build.
Talk about making some life changes in a short period of time! I am genuinely pumped to be coming back to something that is near and dear to my heart - developer relations.
Last week I mentioned that after six year at Microsoft I was leaving the company to pursue a new adventure that would push my growth and skills to new levels. To me, learning can only be done if I constantly push myself outside my comfort zone - I think today’s decision does this. I am happy to announce that starting today I will be joining Amazon Web Services as a Senior Product Manager, Technical on the Amazon EventBridge team, making serverless and event-driven infrastructure more accessible and developer-friendly.
Jeff Sandquist, CVP of Developer Relations at Microsoft, once said that “change invigorates the soul”. Working with Jeff’s organization was one of the highlights of my career - collaborating with some of the smartest folks in the industry, shipping things that have an impact (also known as docs.microsoft.com) and being very closely aligned with developer needs. I’ve been at Microsoft for close to six years, and I always felt like I am never the smartest person in the room - the sheer caliber of individuals that I had the honor of working with speaks volumes for the kinds of organizations that exist within the company.
Daniel Kahneman, a psychologist and economist notable for his work in the psychology of decision making, noted that “true intuitive expertise is learned from prolonged experience with good feedback on mistakes”. And let’s be realistic - any human makes mistakes, in both professional and personal matters. It’s a part of everyone’s life, regardless of your socio-economic background or the range of skills and abilities you possess. And just like with any skill or ability, one can make less mistakes over time.
The other day I had a conversation with my skip-level manager about what it means to be a leader in an independent contributor role, that prompted me to sit down and write this out. I’ve always been fascinated about ways in which I can multiply my impact, so this seemed like an important conversation to have. A lot of times product managers assume that just because they are in an Individual Contributor (IC) role, that means they need to focus only on their immediate areas - things that yield positive outcomes in projects and initiatives that are directly related to one’s line of work.
What is the purpose of a 1:1 with your manager? I wanted to do a write-up to dispel a common misconception around what that meeting with your manager is, and how you can channel it into a much more productive use of time. Status Whenever I talk to new hires, and they set up 1:1s with me or their new manager, one thing becomes very obvious - a lot of people consider 1:1 meetings to be a forum to discuss everything they’ve done in the past week/month/quarter.
August already flew by and it’s a good time to finally post the presentation I delivered here in Vancouver, BC, at the Open Source Summit North America 2018. This year, it so happened that I had the pleasure of doing two rounds on the same topic - Docs as part of the product: open-source documentation at scale. The two rounds were: A lighting talk, giving a high-level overview of where we’re going with open docs.