A few weeks ago, we shared with you our ambitious plan to build out the Asana platform. Our goals are lofty, and we knew that we wouldn’t be able to drive this effort without some expertise. We recently welcomed Andrew Noonan to lead developer relations and we couldn’t be more excited to have him start working with our developer community to introduce even more integrations and workflows into Asana. We sat down with Andrew to chat about his goals, which integrations he’d build, and what brought him to Asana in the first place.
Welcome to San Francisco! You recently moved here from Denver, CO — tell us a little about what you’ve been doing these past few years.
Thank you! It’s great to be here. I started my career as a software engineer and got into the startup world working for Gnip in Boulder. Early on, I saw a need for developer relations so I wrote a business plan for the function and pitched it to the company. They liked it and created a new team.
Gnip got acquired by Twitter, so I joined the dev relations team there. It was definitely a transition: my team at Twitter included 10-12 developer advocates and then another 50 or so individuals around the organization that touched our work in some way. I met a lot of new people, went to bigger events in the developer community, had a bigger budget, and learned a ton. But joining Asana allows me the unique opportunity to jump back to when I first got into the developer relations world: to take something super nascent and really grow it out.
What is it about developer relations that got you excited about it in the first place?
I have always loved engineering, but I found myself wanting to explore more areas of the business. I really enjoy people and I saw the transition to developer relations as an opportunity to continue coding but to also wear product, marketing, and business development hats; it’s the best of both worlds. In addition to exploring more areas of the business, as a dev relations advocate, I get to interface with all the developers that are using the product. On many occasions, I’ve found myself learning about a new technology and then staying up to write an example app: this process allows me to get to the same problem the other developer landed on, ultimately helping him or her succeed.