A day in the life, not a job title
Developer relations, usually shortened to DevRel, is easiest to understand through what the job actually involves rather than the title itself. On a given week, a Web3 DevRel person might write or update documentation for a protocol, build a sample project or starter template that shows a new developer how to get something working quickly, answer technical questions from builders in a Discord or Telegram community, and sit in on an internal engineering meeting to relay what those builders are struggling with. None of that is marketing in the traditional sense, and none of it is pure software engineering either. It sits deliberately between the two.
This is why DevRel is often described as a bridge role. On one side is the protocol's engineering team, which understands the system deeply but is focused on building it, not explaining it. On the other side is a wide range of external developers, from complete newcomers to experienced teams integrating the protocol into a production product, who need accurate, current, and honestly written information to succeed. DevRel exists to keep that connection healthy in both directions.