I've been interviewing a ton of people for DevRel. Here are some tips:
- Take time to understand questions, especially complex ones. Even if you think you understand, take time to reiterate/paraphrase back to ensure you do. Understanding complex questions & helping *is* the job

- Be ok with saying you don't know. Googling answers & asking someone who does know are ok & standard for the job. Making up answers is not ok.

- Research company, how they view their product & the market. You're literally asking them to let you embody this. Are you ok with it?

- REALLY research the company! If you don't understand it & agree with it, why would you want to spend your life representing it?

- USE THE PRODUCT! Give it a try. Again, how can you rep this company if you don't have a solid grasp of what they do & how?

- Once you grok the company, their perspective & their product, ask where it's headed. Are you ok with this? Does it fit with your goals/direction? Again, you're literally lending your face & reputation to the company. You need to be ok with where they are going.

Those are the big points that a majority of folks sadly miss. DevRel can be a really fun, engaging job (for me it is!), but don't be blinded by the travel & conference spotlight. Those are the medium in the same way a sw dev job isn't about the language, but what you're building

At the end of the day, if you take away the "fun" & "flashy" parts of it, you need to still be engaged with the job. In the same way, if as an engineer, someone told you your org was switching languages/tools, you should be ok with it, because what you're building matters more.

p.s. One of my tasks at @GremlinInc will be to grow the DevRel team. Hit me up in January if you're interested in joining.