I'll summarize some experiences from
- My work at a product MNC
- My research + prep work for product startup/s interviews
Read below 👇🏻
#DeveloperRelations #Thread
- Engage with a unique audience : Developers
- Reach devs@scale (1:few:many)
- Help devs make *meaningful* solutions
- Receive critical product feedback
- LOVE (Trust) your product
- Become successful
- Solve meaningful problems
- Navigate through challenges
- Inspire others to build
“To the Community, You represent Company,
To the Company, You represent Community” ❤️
- Why should one learn it?
- How can one take the start?
- What are some use cases?
- When would you recommend using it?
- What are the limitations?
#KnowYourProduct
Quantitative: #reach, #impressions, #attendees, #trainings, #communities
Qualitative: success stories, use cases, product feedback, open source contributions
Some must dos:
- Put your ‘Community’ first
- Be open, inclusive & accessible
- Understand your ‘local’ developer
- Scale 'meaningfully'
- Market readiness
- Community retention
- Balancing quality with scale
- Alignment with product teams
- You get an opportunity to change lives, make an impact, help people find jobs.
- You get to meet some amazing & brightest minds from all across the globe.
- You add value to business, but you don’t have to pursue crazy sales goals.
unroll