Navigating your first 90 days in Developer Relations
Hit the ground running in your new DevRel position :)
Starting a new role in developer relations can be quite challenging. You need to learn new stack, understand company dynamics, get used to processes, and make a positive impact quickly. For DevRel roles, expectations are high from day one.
According to research from Index Ventures, the pace of scaling for successful venture-backed tech companies has accelerated significantly. Between 2000 and 2020, the time taken to scale to 500 employees has shrunk from over eight years to just five years. This faster scaling reflects a more dynamic startup environment, with greater availability of capital and a deeper pool of experienced employees. While there's no universal timeline, the pressure to reach a "break-even point" - where you're contributing more value than you're consuming - is massive.
This makes your first 90 days crucial for setting the tone of your time in that company and demonstrating your skills to push the developer relations program forward.
🛠️ Cracking the DevRel code
The book "The First 90 days" by Michael D. Watkins provides a framework for successfully transitioning into a new role.
While the book has founders and leaders as a target audience, its principles apply broadly to us, developer relations professionals at all levels. Key strategies include preparing yourself, accelerating your learning, and aligning with the organization's expectations.
The book is a great read and it emphasizes the importance of understanding a company’s culture, building relationships, and creating early wins to establish credibility. Which… is very much needed in DevRel.
Mastering the landscape
In the first month, focus on learning and relationship-building.
Meet with different teams to understand their perspectives on developer relations. Ask about their expectations and potential areas for collaboration. This helps you align your goals with broader company objectives.
Avoid the temptation to start trying to implement random strategies from previous roles. YES, I said it. Let’s all agree that… what worked well at one company might not be effective in a new context. Instead, take time to absorb information and understand the unique challenges and opportunities in your new environment.
Dialing your DevRel blueprint
By the second month, you should have a solid understanding of the company's dynamics.
Start developing your strategic plan, but you got to stay flexible. Continue to gather feedback and refine your approach based on new insights, feedback, and data.
What can be areas where you can create value quickly? Look for opportunities to align developer relations KPIs with other teams' objectives. This helps demonstrate the value of DevRel across the organization and builds internal buy-in for your initiatives.
Booooooosting your DevRel rocket
In the third month, you should be ready to execute and optimize your plans.
By this point, you should have internal alignment on your strategy. Launch initiatives and start building out your developer relations program.
Focus on improving efficiency within your team and in cross-team collaborations. If you're in a leadership role, a Head of DevRel, for example, consider how to optimize your team structure before making new hires. Address any gaps or blockers you've identified in your first two months.
😉 DevRel 90 day plan… a starter kit!
Days 1-30
Develop a 90-day strategic plan with measurable KPIs and goals
Conduct stakeholder interviews across product, marketing, and sales teams
Create a data dashboard tracking key metrics (API usage, documentation views, community activity)
Strategize potential co-marketing campaigns with key ecosystem partners
Publish primer guides, get started guides, and technical blog posts on high-traffic developer platforms
Attend local tech meetups and start attempting to secure speaking opportunities
Set up weekly developer office hours
Audit existing documentation and create a prioritized improvement plan
Days 31-60
Launch a weekly developer newsletter (aim for 1000+ subscribers)
Create and publish in-depth technical tutorials
Organize a virtual hackathon with 100+ participants and get feedback from them!
Implement a path to collect feedback from developers using your product
Start a "developer of the month" program to recognize community contributions
Collaborate with product team to provide dev pain points as a feedback loop
Create and publish a features request board and roadmap for implementation to increase transparency
Host a workshop with an ecosystem partner to cross-pollinate dev communities
Develop a technical SEO strategy to improve website and documentation discoverability
Days 61-90
Present DevRel metrics to company leadership
Participate and have an impact-focused plan to attend a major developer conference (preferably in-person for bigger outcomes and relationship building)
Plan a developer certification program to your stack
Implement an automated onboarding email sequence for new developers
Publish a comprehensive API cookbook with real-world examples make it easier for devs to understand your product’s value and application!
Establish a developer community moderation board with 5-10 key community members
Launch a developer ambassador program with 20+ initial members
Collaborate with product team to plan the potential implementation of features based on developer feedback
Throughout these 90 days…
Track and report on key metrics weekly (API calls, sign-ups, active users, projects built in a hackathon, decrease of support tix)
Host quick and short daily standups (15 to 20 minutes) with your team to ensure alignment, delegation, and quick problem-solving
Continuously collect and act on developer feedback through feedback, interviews, and community engagement
Optimize and iterate on your strategy based on data and feedback, adjusting priorities as needed
Remember… the goal is to demonstrate actual value quickly while building a foundation for long-term success. You need to be prepared to adapt this plan based on your company's specific needs and priorities.
🎥 Write your own success story…
If you’re a manager… Onboarding new team members a structured approach helps new teammates to understand expectations and company culture faster. Quicker productivity and better integration with existing teams is now on the table ;)
Launching new initiatives a 90-day plan provides a framework for introducing new projects or programs. It allows for proper research, stakeholder buy-in, and a definitely a phased rollout, increasing chances of success and opportunities for optimization!
Improving cross-team collaboration by efficiently meeting with different teams and aligning goals, you can break down silos, and create more effective partnerships (and get supporters 🤝🏻) across the organization.
Time to get started…
The first 90 days in a new Developer Relations role are mega important for setting the tone of your time in a company and being successful, while being well perceived by your teammates.
By approaching a starting period with a structured plan, you can speed up your onboarding, your learning, build strong relationships, and lock some early wins. Remember, the goal is not just to survive but to thrive in your new role.
Effective leadership in developer relations requires a balance of technical knowledge, strategic thinking, and strong interpersonal skills. By continually refining these abilities and adapting to your specific context, you can drive significant value for your team and organization.
To learn more, get support, and meet other developer relations professionals, join our community HERE! 👋🏻