Given we are so transparent, it seems that most folks who conduct interviews at GitLab expect candidates to have done a fair bit of research in advance of the interviews. So if you're looking to join the Developer Evangelism team, brushing up on our handbook and familiarizing yourself with what we do would be a good idea. That will allow you to come to the interview prepared to frame your experience and abilities through the lens of how we work and the results we aim to deliver to GitLab and our community.
Sharing my personal experience, not speaking for GitLab here:
One thing I did when I was excited about the Developer Evangelist role: I started writing a document in the open, collecting thoughts what I learned, what I want to do, and which ideas could help this drive forward. Markdown, Web IDE, Git commits. Don't check the commit times, they might be at 3am in the morning from an iPad :-)
It was too ambitious, and strategies changed. Still, it allowed me create a single source of truth and define a path forward, preparing for coffee chats and later interviews. I like to come back occasionally for ideas on new content :)
Given we are so transparent, it seems that most folks who conduct interviews at GitLab expect candidates to have done a fair bit of research in advance of the interviews. So if you're looking to join the Developer Evangelism team, brushing up on our handbook and familiarizing yourself with what we do would be a good idea. That will allow you to come to the interview prepared to frame your experience and abilities through the lens of how we work and the results we aim to deliver to GitLab and our community.
We share details on the process in our handbook: https://about.gitlab.com/handbook/hiring/interviewing