I came from a Computer Science, developer role at a startup. I used to participate in lots and lots of hackathons. I discovered an interest in taking whatever APIs were available that weekend and combining them together quickly into a demo, in a sense, tinkering all the time.
At one hackathon, I was talking with the IBM team and it just so happened the team was hiring. I joined the team of advocates and began supporting hackathons from the other side of the table (among many other things).
To overly simplify it, advocates can have many different backgrounds, it depends on what you're doing day to day and the team you're on. There are experienced engineers that need to understand specifics of the tech they are advocating for and answer the hard questions, or at least be well connected to the answer. There are more broad advocates who need to be able to connect things together and understand the ecosystem as a whole. And then there's the people/business advocates who are there to have conversations and make network connections.
Some skills that are helpful:
It's such a fun and rewarding role that you wonder how you get paid to do it.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.