Urgent.News

What's breaking now, across thousands of outlets.

Tech

Meet the Developer Advocate [HackerNoon Interview]

Meet the Developer Advocate: a HackerNoon interview series on DevRel philosophy, community growth, product-led marketing and the launches that worked.

Meet the Developer Advocate [HackerNoon Interview]

Q1: I am Maya Patel, a Developer Advocate at TechSmith, a company that builds products to help teams create and share video content more efficiently.

Q2: DevRel is about bridging the gap between a company's technical offerings and the developers who use them. It combines aspects of marketing, engineering, and product, aiming to foster strong relationships and enable successful developer experiences.

Q3: Balancing the two directions requires clear communication and alignment with the company's goals. I push back on my team when I believe a decision may disadvantage developers or hinder their success, always advocating for their needs and well-being.

Q4: Our community primarily consists of developers who actively use and support our products. It has grown steadily due to the value we provide through our resources, events, and engaging conversations, now boasting over 5,000 active members.

Q5: One launch I'm particularly proud of was our API release. We introduced comprehensive documentation, sample apps, and a robust onboarding process, which resulted in a 40% increase in developer adoption within the first month.

Q6: In a product-led world, docs, onboarding, free tiers, and sample apps are crucial for developer adoption. We focus on creating user-friendly, comprehensive guides and ensuring our free tiers and sample apps showcase the product's capabilities effectively. One change that measurably improved adoption was simplifying our onboarding process, reducing the time it takes for developers to start using our product.

Q7: I particularly enjoy our "Developer Spotlight" series, which highlights exceptional developers who have achieved great success using our products. This series showcases real-world success stories and serves as a testament to the effectiveness of our tools.

Q8: We measure DevRel's success by tracking metrics such as developer engagement, adoption rates, and the quality of feedback we receive. We prioritize user satisfaction and the impact of our efforts on the product's growth and the developer experience.

Q9: Linus Torvalds' quote, "Talk is cheap. Show me the code," underscores the importance of demonstrating tangible value to developers. Our approach involves providing hands-on resources, code samples, and robust APIs that allow developers to explore and integrate our products seamlessly.

Q10: I disagree with the notion that developers are allergic to marketing. While marketing can sometimes feel insincere, we focus on delivering genuine value and building authentic relationships with developers. Our approach is centered around solving their problems and empowering them, rather than pushing a product agenda.

Q11: Kathy Sierra's idea of making users awesome, not just the product, aligns perfectly with our DevRel work. We aim to empower developers, providing them with the tools, resources, and support they need to excel and overcome challenges, ultimately making them better developers.

Q12: I first discovered HackerNoon through a compelling article on developer community building. The thought-provoking content and insightful discussions resonated with me, and I continue to learn from and contribute to the vibrant HackerNoon community.

Q13: I admire the work of Sarah Mei, a developer advocate at Shopify. Her emphasis on clear communication, empathy, and fostering a supportive community sets a high standard for DevRel. Her approach to building strong relationships and empowering developers is something others in the field should definitely emulate.

Written by urgent.news from HackerNoon's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at hackernoon.com →

More in Tech

The Validation Rule That Was Itself Invalid

I lost a save cycle last week to a bug that I now think is one of the most under-discussed failure modes in configurable systems: a validation rule that was itself incompletely configured.

  • Validation rule incomplete, causing bug during save cycle
  • Ambiguity arises as system can't determine rule status
  • Address configuration issues to prevent errors

More from Wednesday 23 September →