Answer as many questions as you like. Keep the questions as they are and write in your own voice. Our editors will polish it before it goes out to 4M+ monthly tech readers. Q1: Let's start with you. Who are you, what do you do, and what does your company build?Q2: What does DevRel actually mean to you? Is it marketing, engineering, product, or something else entirely?Q3: DevRel works in both directions: you speak for the company to developers, and for developers inside the company. How do you balance the two, and when have you pushed back on your own team for developers' sake?Q4: Tell us about your community. Who's in it, how big is it now, and what helped it grow?Q5: What's a launch or campaign you ran that you're proud of? What happened, and what did you learn?Q6: In a product-led world, the product is the marketing. How do docs, onboarding, free tiers and sample apps fit into your DevRel work, and what's one change that measurably improved developer adoption?Q7: What's your favorite piece of content your team has shipped, and why did it work?Q8: How do you measure whether DevRel is working? What do you track, and what do you ignore?Q9: "Talk is cheap. Show me the code." Linus Torvalds wrote this on the Linux kernel mailing list in 2000. How does that idea shape the way you reach developers?Q10: There's a well-known saying that "developers are allergic to marketing." Do you agree? How do you reach developers without it feeling like marketing?Q11: Kathy Sierra argues in Badass: Making Users Awesome that the goal is to make users awesome, not to make the product look awesome. How does that idea show up in your work?Q12: How did you first come across HackerNoon, and is there a story you've read or written here that stuck with you?Q13: Whose DevRel work do you admire most, whether people, companies or programs, and what do they do that others should copy?