What is the job of a Developer Relations Engineer (DevRel)?
The job of a developer relations engineer, known as DevRel, consists of being the link between a company that offers software tools and the people who write programs using those tools. The tool might be an application programming interface, a code library, a cloud platform or an open-source product. The aim is for developers to understand the product, to be able to use it without getting stuck and to have a channel for giving their opinions about it.
A typical day mixes technical work and work with people. It can include writing a sample program that shows how to use a new feature, answering questions in forums and messaging groups, preparing a talk or a workshop, and meeting the product team to tell them which problems come up again and again for the people who use the product. Some days involve travel to events; on others, almost all the time is spent at the computer writing and testing code.
Typical tasks
- Writing sample programs and step-by-step guides that show how to use a product.
- Preparing and giving talks, workshops and demonstrations, in person or online.
- Answering technical questions from the community in forums, code repositories and social networks.
- Testing new products from the point of view of someone who writes code and reporting bugs or confusing parts.
- Gathering feedback from the community and bringing it to the product and engineering teams.
- Working with technical writers to improve the documentation.
- Organizing or supporting meetups, programming contests and user groups.
Subjects and content usually covered
- Programming in one or more languages and application development.
- Data structures, algorithms and databases.
- Networks, application programming interfaces and cloud services.
- Version control and work with open-source code.
- Software engineering and testing.
- Spoken and written communication, and technical writing.
- The basics of product work and digital communication.
Usual duration and type of training
There is no single training path for this job. The most common route is a university degree in engineering or computer science, which usually takes 4 to 5 years, depending on the country. There are also technical programs in programming, lasting 2 to 3 years, and intensive courses of 3 to 12 months.
In addition, a period of experience as a programmer is often needed before moving into this position. The total length varies a lot depending on the country and on each person's path.
How you get there and what is usually required to practice
People generally get here from a related engineering degree, such as systems, computing, software or computer science, or from a programming career without a university degree but with experience they can show. It is common to start as a developer, in technical support or as a technical writer, and later move into DevRel.
No professional license is required. Things that are usually valued include a portfolio of projects and code samples, contributions to open-source projects, published explanatory texts or videos, and experience speaking in public. Reading and writing English is often needed because the documentation and a good part of the communities work in that language.
Skills that help
- Writing code fluently and reading code written by other people.
- Explaining technical topics in simple words, in writing and out loud.
- Listening to the people who use the product and noticing where they get confused or frustrated.
- Speaking in front of an audience, from a small room to a large conference.
- Learning new technologies quickly and trying them out before explaining them.
- Working with engineering, product and communication teams, and translating between them.
Career paths and job opportunities
- Software companies and cloud service companies.
- Companies that offer programming interfaces, such as those for payments, messaging or maps.
- Organizations that maintain open-source projects.
- Technology startups that need other people to build on top of their product.
- Agencies and consultancies that help companies with their relationship with technical communities.
What you are not always told
- It is a position that does not exist in every company and its name varies a lot; sometimes it appears as technical evangelist, developer advocate or community engineer.
- The effect of the work is hard to measure, and that can create pressure to justify the value of what is done.
- Travel, events and replies to the community can take up weekends and hours outside the usual schedule.
- The person has to stay technically up to date while dealing with people, and dividing time between coding, writing and speaking is not simple.
- It is usually a position reached with previous experience, so a first job in technology is rarely this one.
How the field is changing
Artificial intelligence tools already help to generate code examples, drafts of documentation and answers to frequently asked questions, which changes the time spent on each task and makes it more important to check what they produce. Communities increasingly meet in online spaces and through videos, as well as at in-person events. There is also more attention to the quality of documentation, to accessibility and to transparency in open-source projects.
Want to know if this is the right career for you?
Take the free vocational test with 5 scientific methods — CHASIDE, Holland, Big Five, MMMG and VAK — to get your personalized profile. You can also explore all university careers or learn about the scientific methodology.