Explore

Kick off role

DevRel Recruitment plan exemple

The Marketing team is seeking to hire a DevRel Engineer to engage with the technical community and promote the product. Responsibilities include connecting with the startup tech community, creating technical content, fostering open source communities, and representing Company at events. The ideal candidate will have strong presentation skills, experience in SaaS or software development, and the ability to work asynchronously in a remote environment. The recruitment process entails an initial discovery call, a chat with the Head of Product, an asynchronous communication exercise, and a team meeting. Candidates are expected to apply by a specified deadline and will be evaluated on their technical and soft skills, especially their ability to network and organize events. Sourcing strategies include targeting specific job boards, communities, events, podcasts, and leveraging industry connections. The hiring process will track metrics such as time to hire, conversion rates, and candidate experience. Candidates should embody Company’s values and be prepared for a growing company with opportunities for impact.

⁠

One of the key hires within the Marketing team is a DevRel role. Their main focus will be to speak with tech audiences about our Product. They should have a strong network in the global startup tech community and be positioned as a valued contributor based on their knowledge and expertise.

⁠

Do this first:

Do a Kick off meeting with Hiring Manager asking following items:

how much experience-report, focus of the job, seniority of the role?

- team size?

-recruitment process, HM and interviewers?

- urgency? / problems or challenges with this roles?

- what´s the challenge?

- why someone might apply?

- how to pitch to the role?

- what´s the career growth?

- must have soft skills?

- who´s not a good fit (ex, consultancy)

- a good technical question for screen call

- keywords to source? companies? any slackchannel? any ideal LK profile

Create #slack-channel for updates on the role with hiring manager and team.

Create a coda.io/notion page with recruitment process

Wayfinding

Wayfinding

Page

Description

interview plan

⁠

see the Job description

⁠

key assessment criteria

⁠

how to evaluate candidate

⁠

keywords to look for

see

here

⁠

key companies to source from

see

here

⁠

key metrics to keep track of and targets for each metric

see

here

⁠

Exercise discusion

see

here

⁠

There are no rows in this table

⁠

Job Description {draft}

Our team’s single source of truth. Everything you need to know about who our team is and what we’re doing is detailed here.

Your personal space. Make yourself at home, and make your page what you need it to be.

Full time / Remote / Europe

👋 A little about us

GitBook⁠

is a modern documentation platform. Our ambition is to empower technical teams by seamlessly integrating knowledge management into their existing asynchronous workflows. GitBook is now used by over 2M users and thousands of teams such as Adobe, Netflix, Apple, Snyk, and Google and backed by top partners such as P9 Capital, Notion Capital and Fly VC.

🤔 Why we open this role?

We are growing and focused on evolving our technical product capabilities along with our core team structures, processes, and practices. After more than doubling our revenue in 2021, we are on the lookout for a DevRel Engineer to join our Support team and to be an key player of our journey of rapid growth. 🚀

With this in mind we're looking for a DevRel in Europe to help us grow our tech community thanks to initiatives as ambassador and scale our advocacy efforts, developing programs across GitBook that empowers developers through high-quality technical content and continuous community engagement.

🙌 What will you be doing?

You'll join our growing interdisciplinary team of empathic folks: name1, name2, name3 with LK profiles.

You will play a key role in advocating for GitBooks communities and their growth. This means we work pretty close with Marketing Engineering and Product. Through internal collaboration you´ll be proud of development of technical content to complement our documentation and boost the visibility and adoption of our projects. On a daily basis, you collaborate with internal teams and leaders to establish scalable Developer Relations programs focused on building a cadence of technical advocacy activities and event participation. You will spend 80% of your work in community related topics. Establish programs that nurture our open source communities and empower champions to encourage contributions and participation. You will enjoy identifying and drive potential collaboration and partnership opportunities for the community. Finding new channels to share how we can help developers.

You will also spend 20% of your time on events. For example, representing GitBook in webinars, conference or building workshops.

👩‍🏫 You will be valued for your‌

Excellent presentation skills and experience giving talks at small and large-scale events

Genuine interest in writing articles, code samples, blogs, and other content strong willingness and passion for helping others.

A passion for working with people, paired with excellent communication skills; you can explain a complex technical issue in such a way that most people could understand

You have past experience working in a SaaS company and or in software development experience.

Your experience nurturing community members and converting them into champions.

You have technical knowledge around how the web works and technologies such as JavaScript, React, Google Cloud, Firestore, and more

You can share your git repositories at GitHub/GitLab platforms

You have captured feedback and shared to internal teams.

You enjoy working at asynchronous and remote working environment.

You are a great collaborator when partnering with product, marketing and dev teams.

You are naturally positive and easy going ☀️

✨What's next?

Please apply by Monday, October 10 at 5:00PM Central European Time (CET). Introduce yourself to us as a colleague. Tell us why you want this job and why you’d like to work at GitBook. As a fully remote company we rely on written asynchronous communication a lot. We value great writers, so be yourself, be creative, and take your time.

First, we will take the time to review your application and we will get back to you, regardless of our decision. We can't promise detailed feedback due to the volume, but we will send out a response.

We'll continue with interviews and the asynchronous communication.

Here's what our process will look like from beginning to end:

Discovery call (25 minutes) with our Talent Acquisition Manager to look for healthy alignment.

Chat with {Name} (25 minutes) with X, our Head of Product, to learn more about you.

Asynchronous communication (condensed, no more than 3 hours of your time), we invite you to a private space where we collaborate using written asynchronous communication. You will learn how to use GitBook and propose a couple of hypothetical activities for our community (based on real cases) as an exercise.

Meet the team (50 minutes) with two peers across GitBook, to confirm that you will thrive in our culture and answer any questions about what it's like working here.

👥 Join GitBook

You will be joining during a pivotal moment for GitBook. We've enjoyed great success since we were founded, and now we're taking conscious steps to take our company to the next level.

That means you will have the opportunity to build, positively impact the trajectory of the company and enjoy the benefits of helping grow our company 20x.

Every single team member is a valuable addition to our culture, so it's important for us to state our company values:

🚀 Ambition (Aim higher)

✊ Ownership (Take control and Own it)

📈 Accountability (Be accountable to results)

🙋‍♀️ Care (Give a sh*t)

🏃‍♂️ Train (Grow yourself)

🤝 Genuine (Say it and accept it)

👯‍♂️ Team player (Leverage the team)

🏗 Architect (Plan & Build)

🖱How to apply? Send us your application

here⁠

Sourcing Strategy

Since I have no context on this role (is it new? is it senior? are there X expectations within 3 months?) sourcing strategy should be shared with Hiring Manager to contrast.

Channels

Finding specific

jobboards⁠

for this roles, and test, as they are not quite popular.

Finding

slack channels or communities⁠

for this role.

Finding events (evenbrite, meetup, webinnars) around this topic.

Finding

Podcast⁠

where we can find candidates.

Join

Dev Advocate communities⁠

at twitter

Public figures on the field, such

her⁠

, might have connections or could refer someone.

Boolean string search with keywords “developer communities”, “developer advocate” other roles as “Principal Sw” sometimes are accountable for this communities.

Here the one i used⁠

⁠

Create a compelling email for sourced candidates (previously reviewed by Hiring Manager to make sure it is attractive). Doing a-b testing if needed.

Our Candidate Experience

Keys for the role

🛠️ Key assessment criteria:

Technical skills: level of expertise in development (not sure which would be the minimal), Key Stack that is a must JS/React.

Soft skills: Must be a great communicator, natural networker. Has shared experiences on building events or communities and role on it. Organisation skills for events a nice to have.

Slack has defined the level of seniority for this role

here⁠

⁠

💼 Companies to Source from

Find companies with great reputation such GitLab Github Slack DataDog Kubernates Koda Pronovix DXHeroes

SaaS companies providing product support.

⁠

Here´s⁠

a list of nominated companies for DevAwards with a list of

winners⁠

⁠

🧜‍♀️ Possible candidates

⁠

IBM candidate⁠

https://huangjunye.github.io/⁠

⁠

CubeDev candidat⁠

⁠

AuthO candidate⁠

⁠

Google Android candidate⁠

⁠

Slack⁠

candidate ,

intern⁠

⁠

Snowflake⁠

candidate

📈Metrics

TTH (time to hire) [target 30 working days]

#candidates sourced vs. #candidates hired /#replies candidates [100 vs 2% conversion rate]

drop off rates [10%]

source of candidate (referral, inbound, outbound, website, events, agencies) [no target]

Candidate Experience rate [8.5 NPS]

Hiring manager experience rate [9 NPS]

Add your sentiment below. When your team is ready to discuss, expand all the sentiments and review as a group.

Clear template

⁠

Pulse: How do you feel about this exercise?

⁠

Add your sentiment

⁠

Sentiment

Author

Reflection

No results from filter

⁠

All sentiments (
`4`
⁠
)

⁠

4

⁠

submitted with average sentiment of

3.5

⁠

Sentiment

Author

Reflection

Discussion notes

Open

Tools to use?

Open

There are no rows in this table

⁠

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.

Kick off role

Do this first:

Job Description {draft}

👋 A little about us

✨What's next?

👥 Join GitBook

Sourcing Strategy

Keys for the role

🛠️ Key assessment criteria:

💼 Companies to Source from

🧜‍♀️ Possible candidates

📈Metrics

Pulse: How do you feel about this exercise?

All sentiments (4⁠)

All sentiments (
`4`
⁠
)