And sometimes, taking a "risk" 💣 pays off! 🚀
I switched to product management lately from developer advocacy. I'll be frank— I was afraid. I couldn't stop wondering if this was the best course of action. However, I've always wanted this, so it makes sense. I've always wanted to grow, learn, and help build products. As a result, I understood that I needed to make this move even though I knew it could be a little challenging for me at first.
I initially thought I had stopped coding(which happens sometimes when you come from an engineering background). But I decided not to put the blame on my job or role. I continue to spend some of my evenings learning new languages and occasionally developing new tools, frameworks, libraries, and languages.
I was a little anxious when my role changed as an APM (Associate Product Manager). The first few days left me unsure of where to begin. But having a supportive team around me has made and continues to make me incredibly lucky. At Pragmatic Institute, I took two courses to get started, which was a great idea. However, I never feel like I've learned enough, so I continue to study product management for an hour every evening.
I won't go into detail on how to get started with product management in this article because there are many resources already available. But I would rather discuss how different it is for me to picture myself as an APM versus a Developer Advocate.
As a Dev Advocate, I would, however, primarily concentrate on producing written and video tutorials, live streaming, blog entries, community interaction, and much more. My daily tasks would be to learn about new subjects and produce content for developer and partner education. As a developer advocate, I, therefore, concentrated on increasing engagement for the product once it had been developed and released. However, things are a little bit different with being an APM. It's more like I've made progress toward the thing I was supporting!
Now, rather than evangelising the product, I spend most of my time focusing on building it. My current priorities include defining product requirements, developing user stories, conducting market research, understanding users and consumers, and contributing to product positioning. It's a lot of fun, but occasionally scary. It would be scary because I would feel imposter syndrome. Given that I am relatively new to the product, I would experience it even more. But that's what motivates us to improve, isn't it?
This concludes this short article. I won't make it any longer. I'll continue to share my opinions, insights, and thoughts in the future! If you have any questions or comments for me before then, please don't hesitate to contact me!
Sohini
Top comments (0)