8 |
9 | ## Contributors
10 |
11 | - [Hassan El Mghari](https://twitter.com/nutlope)
12 | - [Lee Robinson](https://twitter.com/leeerob)
13 | - [Cami Ramos](https://twitter.com/camiinthisthang)
14 | - [Swyx](https://twitter.com/swyx)
15 | - [Omar](https://twitter.com/OuhraOmar)
16 | - [CuddleofDeath](https://twitter.com/cuddleofdeath)
17 | - [Jakub](https://twitter.com/jacobandrewsky)
18 |
19 |
20 | ## Contributions
21 |
22 | Want to contribute resources or advice? Feel free to submit a PR!
23 |
24 | However, I reserve the right to decline contributions to keep this resource high quality.
25 |
26 | ---
27 |
28 | [](https://vercel.com/?utm_source=trpc&utm_campaign=oss)
29 |
--------------------------------------------------------------------------------
/components/Advice.js:
--------------------------------------------------------------------------------
1 | /* eslint-disable react/no-unescaped-entities */
2 |
3 | export default function Advice() {
4 | return (
5 |
6 |
7 | Advice for DevRels
8 |
9 |
10 | One of the hardest parts of DevRel is getting developer's attention.
11 | It's what every devtool company is competing for. So how do you get it?
12 | Let's look at some rules.
13 |
14 |
15 |
16 | How to engage developers
17 |
18 |
19 |
20 | Build great examples. Show developers how they can use your product through great cookbooks, example apps, and content. You want to emulate how developers would use your product/API and show them cool use cases.
21 |
22 |
23 | Show, don’t tell. Break down
24 | barriers to getting their hands on the product as quickly as
25 | possible so they can determine whether or not your product is right
26 | for them.
27 |
28 |
29 | Features not benefits. Be
30 | straightforward about specs and feature comparisons against other
31 | product lines or competitors. Don’t bury the lede.{" "}
32 |
33 |
34 | Be genuinely helpful. Invest
35 | in comprehensive, high-quality resources (e.g. great API
36 | documentation, a well-maintained help center, how-to videos, sample
37 | use cases) and make it easy to contact you directly if they need
38 | some extra help. (Chances are, they won’t)
39 |
40 |
41 | Be direct. Get to know a
42 | developer and then imagine you are writing to that individual person
43 | each time. This quickly eliminates anything sales-y and helps
44 | produce genuinely useful content.
45 |
46 |
47 | Think beyond the 9-to-5. Many
48 | developers are developers in and out of work, with side projects on
49 | a wide range of topics (from hacking their dishwasher to building a
50 | marketplace or a game).
51 |
52 |
53 | Repurpose content. This is
54 | the key to getting the maximum amount of reuse from content you
55 | spend time creating. Try following the tweet {"->"} blog {"->"}{" "}
56 | video {"->"} conference talk pipeline.{" "}
57 |
58 |
59 | Have a "breakable toy".
60 | In other words, have a real app to try around new tech and be able
61 | to show metrics on new tools/changes. It should be small but real,
62 | like a workout tracker, meal planner, or note taking app. Ideally it
63 | should also have a couple users like you & your friends.
64 |
11 | Let's talk about the 3 types of DevRel: Community, Content, and Product.
12 |
13 | Many developer advocates do{" "}
14 | a mix of these but tend to specialize in
15 | one or two.
16 |
17 |
18 |
19 |
20 | The Community Builder
21 |
22 |
23 | Community-focused DevRel centers
24 | around growing and managing a community of developers. This is usually
25 | a Slack or Discord community that's focused on a company's product or
26 | an open source technology. Managing a community consists of answering
27 | questions, designing the community in an inclusive way, and making
28 | sure members are getting value through activities like livestreams and
29 | other events.
30 |
31 |
32 |
33 | The Developer Educator
34 |
35 |
36 | Content-focused DevRel is about
37 | spreading awareness about a product through written and spoken
38 | content. This can involve writing blog posts, making videos, teaching
39 | workshops, recording podcasts, tweeting and more. Content can be an
40 | SEO play focused on the long term or be a short term promotion like
41 | new feature launches.
42 |
43 |
44 |
45 | The DX Engineer
46 |
47 |
48 |
49 | Product-focused DevRel is about
50 | owning the developer experience of the product. It's about improving
51 | how it feels for a developer to use a specific product. This can be
52 | done by talking to users to understand how they're using it, then
53 | making improvements to the documentation and creating guides based on
54 | their answers. This can also mean working on code examples, templates,
55 | and integrations.
56 |
57 |
58 |
59 | );
60 | }
61 |
--------------------------------------------------------------------------------
/components/Jobs.js:
--------------------------------------------------------------------------------
1 | /* eslint-disable react/no-unescaped-entities */
2 | import {
3 | CloudIcon,
4 | CodeIcon,
5 | LightningBoltIcon,
6 | } from "@heroicons/react/outline";
7 |
8 | export default function Jobs() {
9 | const skills = [
10 | {
11 | name: "You can code",
12 | description:
13 | "For this, you can show off some of your side projects or highlight your previous engineering experience. It's important for DevRels to be able to code to empathize with developers.",
14 | icon: CodeIcon,
15 | },
16 | {
17 | name: "You can build communities",
18 | description:
19 | "For this skill, you can show off any experience of you helping build a community or organization. It could be for college, open source, online communities or anything.",
20 | icon: CloudIcon,
21 | },
22 | {
23 | name: "You can create content",
24 | description:
25 | "For this skill, you can show off your talks, YouTube videos, tweets, and blog posts. If you don't have any of these, I'd strongly recommend you create some content.",
26 | icon: LightningBoltIcon,
27 | },
28 | ];
29 |
30 | return (
31 |
32 |
33 | Getting a job in DevRel
34 |
35 |
36 | As mentioned, the job market for devrels is very hot right now. I have
37 | startups that message me every week asking if I know any good developer
38 | advocates, so there is a big need in the market right now.
39 |
52 | When applying for developer advocate roles, it's important to show
53 | that you have some of these three skills below:
54 |
55 |
56 | {skills.map((skill) => (
57 |
58 |
59 |
60 |
61 |
62 |
{skill.name}
63 |
64 |
{skill.description}
65 |
66 | ))}
67 |
68 |
69 |
70 | While there aren't pre-requisites for the job, it's{" "}
71 | very helpful to have prior work in these
72 | areas to show off and get your career in developer advocacy started. If
73 | you don't have prior work, you should start creating content (blogs,
74 | videos, side projects) that helps demonstrate you can already do the
75 | work. Ultimately, this is a role for engineers who enjoy working with
76 | developers, creating content, and managing communities.
77 |
78 |
79 | If you already have at least two of these skills with strong evidence & can work in the US, feel free to{" "}
80 |
81 | DM me on Twitter
82 | {" "}
83 | and I can try to connect you to startups that are hiring! There are companies hiring outside the US but most of my connections are specifically hiring in SF, NYC, or remote US.
84 |
10 | If you've been hearing about DevRel and are confused what it means and
11 | how to get a job doing it, this website is for you. We're going to
12 | define what is it, explore the 3 types of devrel, discuss how to get a
13 | job doing it{" "}
14 | (and share companies that are hiring),
15 | and end with some resources and advice for aspiring and beginner
16 | DevRels.
17 |
18 |
19 | DevRel, also known as Developer Relations or Developer Advocacy, is a
20 | role that exists at developer tool companies (companies whose target
21 | market is developers). Developer Advocates{" "}
22 |
23 | help educate developers on a specific product or technology
24 | {" "}
25 | through building community, creating content, and improving the
26 | developer experience of a product.
27 |
7 |