Jeffrey McManus, who recently left eBay for Yahoo, is looking to hire few good Yahoo!s to help with our growing developer network.
He says:
I've got two openings on my team at Yahoo, one is for a manager of marketing and community for the Y! Developer Network, and the other is for a Technical Evangelist/Developer Support specialist.
For the marketing/community position, a strong technology marketing background (preferably targeting a developer audience) and hands-on experience supporting an online community is crucial.
For the evangelist/support role, we're more flexible with respect to what you've done in the past (a coder looking for a new set of challenges would work, a sales engineering type might work, I'd even consider a technical documentation specialist if you're on the more technical side). What's most important is that elusive combination of technical experience, great communication skills, and a passion for helping developers.
Yahoo is a nice place to work and we're going to be building out our third-party developer initiatives significantly in the coming year, so if you've ever wanted to get in on the ground floor of something big, now's your chance.
Emphasis mine. If you'd to help shape the future of Yahoo's Developer Network, now is the time to get on board. Get in touch with Jeffrey, or send me your resume.
Posted by jzawodn at May 03, 2005 03:15 PM
you could use and evangelist since i never even heard of ydn before this post.
YDN has been around fr a few months now [blank]...
Jeremy, I sent in my resume yesterday. Hope you find someone well qualified for those positions. I read an article in Fortune this morning about the Microsoft vs Google war that was very enlightening and if Yahoo is going to continue to stay ahead of the big M then the innovations are going to continue to have to flow. Good luck.
I have used the google API for a while. Haven't had the chance to develop with the Yahoo API. I was going through the dcumentation and I really like the idea of context in the request paramaters. I can't do that in google API. You should add more features like that, where developers can disect more of your database to fit their needs. You might see a growth in sudden developer interest.
My best advice is open it up. The more we can do with it, the more of us you will see.