Work with Voxgig

What you'll do#

You will work across code, content, community, and developer experience. Depending on your strengths and interests, you will:

• Build example applications, demos, integrations, and starter projects.
• Write tutorials, technical guides, documentation, and other developer content.
• Help developers who are using our product, and answer technical questions.
• Participate in relevant developer communities and conversations.
• Experiment with different ways of helping developers discover and understand our product.
• Turn new product features into examples and content developers can actually use.
• Identify confusing parts of the developer experience, and suggest ways to improve them.
• Gather feedback from developers, and bring useful insights back to the product and engineering teams.
• Contribute to open-source projects and developer ecosystems relevant to our work.
• Over time, explore other areas of DevRel: video, livestreams, workshops, events, community programs, and developer partnerships.

We do not expect you to arrive knowing how to do all of this. Part of the role is learning what you are good at, and developing your skills as a DevRel practitioner.

Who we're looking for#

You are technically capable enough to build software and understand how developers work. You do not need years of professional engineering experience, but you should be comfortable writing code, using APIs, working with Git and GitHub, debugging problems, and learning unfamiliar technologies.

More importantly, you genuinely enjoy sharing what you learn with other people. You might currently be:

• A junior software engineer who enjoys writing and teaching.
• An open-source contributor or maintainer.
• A technical writer who can code.
• An active member or moderator of a developer community.
• A developer who creates tutorials, videos, demos, or side projects.
• A bootcamp or computer science graduate with an unusually strong public body of work.
• Someone already doing DevRel-type work informally, who wants to make it their career.

We care much more about what you have done than what your job title has been.

The most important requirement#

We want to see evidence of DevRel-adjacent activity. That could be:

• Open-source contributions.
• Technical blog posts or tutorials.
• GitHub projects with thoughtful documentation.
• Helping people in Discord, Slack, forums, Stack Overflow, Reddit, or other technical communities.
• Organizing or participating in developer meetups or communities.
• Technical talks, workshops, livestreams, or videos.
• Developer documentation.
• Sample applications or demos you have created.
• Hackathon participation.
• Contributions to developer tooling.
• Educational content.
• Anything else that shows you like building things and helping other developers understand them.

It does not have to be polished. You do not need a large audience. And none of it needs to have been part of a paid job.

We would rather see a small GitHub project with an excellent README, or three useful technical articles, than a CV full of impressive-sounding titles.

You might be a great fit if#

• You are curious, and you learn new technologies quickly.
• You enjoy both coding and communicating.
• You can explain technical ideas clearly, without unnecessary complexity.
• You like helping people solve problems.
• You are comfortable working independently in a remote environment.
• You take initiative, rather than waiting for someone to give you a detailed specification.
• You are comfortable publishing work publicly.
• You care about the experience developers have when using software.
• You want to build a career in Developer Relations.

You do not need#

• Previous professional Developer Relations experience.
• A Developer Advocate or DevRel job title.
• A computer science degree.
• A large social media following.
• Conference speaking experience.
• Thousands of GitHub followers.
• A personal brand.

This is deliberately an entry-level opportunity. We are looking for potential, evidence of initiative, technical curiosity, and an instinct for helping developers.

Location#

This is a 100% remote role, and we are open to candidates globally.

You will be working asynchronously much of the time, so strong written communication and the ability to manage your own work are important.

Contract#

This is a contract position, part time or full time.

We are happy to work out a rate that works for both of us, depending on the particular circumstances and your level of experience. Our general contract rate policy is to match or exceed the market rate.

How to apply#

Keep it simple. Use the form on this page, and send us:

1. A short introduction, and why DevRel interests you.
2. Something you have built, ideally a GitHub repository, open-source contribution, demo, application, or other technical project.
3. Something that shows how you help or explain things to developers: a blog post, README, documentation, community contribution, video, talk, tutorial, forum answer, or anything similar.
4. Links to your GitHub, and any other places where we can see your work.
5. If you use AI for your application, and we could not tell, we will count that as a plus point.

A traditional resume or CV is welcome, but it will not be the most important part of your application. We are particularly interested in candidates who have not had the opportunity to work professionally in DevRel yet.

If you have been thinking “I would love to get into Developer Relations, but every DevRel job asks for previous DevRel experience”, this role is for you.