top of page
  • Harpreet Sahota

DevRel Rookie? No Problem! A Step-by-Step Guide to Thriving in Your New Role

#devrel #developerrelations #community


Are you ready to rock your DevRel role? 🤘 Then you and I are about to put together a 30-60-90 day plan to make the most of your first few months on the job.


You only have one responsibility during the first 30 days: learn as much as possible about the company, its products, its users, and its messaging.
  1. Learn how to contribute to the team by talking to stakeholders.

  2. Ask the founders about their "founder story."

  3. Study company messaging and tone.

  4. Lurk around the community.

  5. Find out why developers should use your product.

  6. See how the community uses the product, interacts with the team, and helps each other.

You’re looking for answers to the following questions:

  • What's the monetization strategy?

  • Is there a product-market fit?

  • How are you different from your competitors?

  • Who are the relevant personas?

  • What's the value proposition to developers?

You're trying to figure out how to best contribute to the team.


That means you need to:

  • Talk to stakeholders and learn about their goals

  • Study company messaging and tone

  • Discover why developers should use your product.

  • Lurk around the community to see how people interact with the product and each other.

  • Research your competitors to see how they compare to your company.

  • Look at their products, pricing, messaging, and target audience.

How do they differ from your company?

How differentiated are your company and its products from the competition?


The next 30 days are about building relationships.

It would help if you had allies across different teams within the company - community, sales, marketing, customer success, product, and engineering.


Figure out their priorities and goals and how you can work together. Make sure you understand how each team contributes to the company's overall success and how you can support them in your role.


Set up regular check-ins and communication channels and make sure everyone is on the same page and working towards a common goal.

Start adding value to the community.


Create useful content like writing technical articles, hosting virtual events, creating tutorials and demos, or starting a developer podcast. Good content establishes you as a helpful, knowledgeable resource and creates a positive reputation for your company with the developer community.

Final 30 days: It's all about the developers!

Perform a developer experience audit of your product and your competitors. Go through quick start guides, documentation, code samples, and use cases of your products and competitors. Gather feedback from developers about their experiences and identify areas for improvement.

You best be able to answer:

  • What skill level is required to build something with your products?

  • How long will it take to implement something with your products,

  • What is missing from the documentation to implement these products?

  • What's the time to say "hello world"?

  • What's the time to value?

By answering these questions, you can help developers determine the pros and cons of your product and help them make informed decisions about the right tool for them.


Try to gather feedback from developers about their experiences with your company's product and those of your competitors. This can help you identify areas for improvement and give you ideas for new content or resources to create.

I hope you’re ready to crush your new role!

A 30-60-90 day plan will skyrocket your learning and development and help you make a real positive impact on your developer community.

Think of it as a roadmap to DevRel domination!

Summary

In the first 30 days, you'll dive deep into understanding your company, its products, its users, and its messaging.

You'll talk to stakeholders, study company messaging and tone and discover why developers should use your product. And don't forget to lurk around the community to see how people interact with the product and each other.

The following 30 days, it's all about building relationships with different teams within the company and adding value to the community through blogs, events, tutorials, or podcasts.

Finally, in the last 30 days, you'll focus on the developer experience, perform a developer experience audit of your product and your competitors, gather feedback and create resources to help developers be successful.

Remember, Rome wasn't built in a day, and your DevRel career is no exception. Stay patient, focus on your goals, and trust that your hard work will pay off.

And don't be afraid to seek help and advice when needed, having a support system will help you navigate the ups and downs.

With this plan, your determination, and your hard work, you'll excel in your role and make a meaningful contribution to the field of DevRel.

-------------

Meet Harpreet Sahota, a seasoned DevRel manager at Deci AI. With four years of experience in the field, Harpreet brings a wealth of knowledge in the machine learning space, having previously worked at companies like Comet and Pachyderm. He brings a unique perspective, having also worked as an actuary and biostatistician, and having built successful data science teams in the past. He is also experienced in building and scaling DevRel teams, as well as being a founding member of teams or lone ranger on others. Follow Harpreet for in-depth tweets on all things DevRel and Deep Learning.



bottom of page