If you've been active on Twitter Development Talk in the last few
months, you've probably had a question or two answered by one Doug
Williams (@dougw). Before we could even find the time to post a job
listing for the position, Doug sought us out to help take on the
support load generated by the rapidly growing Twitter API developer
community. His first official day as a Twitter employee was last week,
and Matt (@mzsanford) and I are busy showing him the ropes and
spider-filled corners of the system this week.

Matt will be helping out across the board, but here's a few changes
and improvements he's going to help us make over the coming months:

1. Faster official responses to questions about the Twitter API.
2. Faster approval of requests for application attribution,
whitelisting, access to the data mining feed, etc.
3. Better documentation and community resources.
4. A better way to developers to showcase their applications to
prospective users.
5. Making full use of the @twitterapi account to keep up with Twitter
developers via Twitter (what a concept).

...and much, much more. Basically, having Doug on board means that we
have the extra pair of hands we need to make the Twitter development
community the best it can be in 2009.

Doug will be joining me at Twitter HQ in San Francisco later this
month. Matt will remain at a safe distance in Seattle for the time
being. Matt and I will remain just as involved in the community as we
have been (which is to say, a bit harried from churning out code, but
eager to help out when we can).

Please note that if you're envious of Doug's newfound employment with
Twitter, Inc., we're hiring, and we consider prior work with the
Twitter API a big plus. See http://twitter.com/jobs to apply, and do
apply even if you don't see a position that exactly matches your
skills. We know a good hire when we see one, like Doug.

Give Doug a warm welcome!

-- 
Alex Payne - API Lead, Twitter, Inc.
http://twitter.com/al3x

Reply via email to