The last month has given me a great opportunity to speak with a range of companies about the work they're doing, and the things they see as important to the future of the Internet in the next few years. I talked with big and small companies, from startups to the Fortune 500, and was honored to be offered the chance to work with many of the people with whom I most enjoyed talking.

I am very happy, then, to say that I'm moving to Silicon Valley to pursue what Six Apart taught me was my dream job: technology evangelism. I'll be joining a good young company that I've heard has some potential. I'll be working as a Developer Programs Engineer for Google's social properties-- everything from the big products to a lot of the exciting underpinning technologies, like Brad Fitzpatrick's Social Graph API that infinitely decreased the time necessary to build Mnikr.

So while I'm sad to leave my friends behind in Boulder, I'm excited by the possibilities that come next, and the things and people that I'll be able to work with at Google. In two weeks, I'll be starting there, though I don't think I'll refer to myself as a noogler (despite the offer letter encouraging it). In the meantime, I'll be packing and moving myself, my computer, and my cats; the rest, apparently, Google "has people for," which is certainly pleasant; in general, all their perks (not just the famous ones, like food, but the ones that blogs don't cover, like how they handle relocations) give the impression of actual human beings running HR, which is certainly a nice change.

Oh, and for those of you who wonder: If you type Google into Google at Google, you do dereference unto the void; however, the void also dereferences unto you. :-) (Yes, I tried it. Also: guest WiFi that can do 10MBps upstream is pretty awesome for interviewees.)

I mean, it's a legitimate question. There are plenty of engineers on the market these days; while we don't have any trouble finding work, there are plenty of good engineers around if you know how to look. So why should someone hire me in particular?

Well, dear reader, let's look at what I can do-- I mean, I graduated from a relatively prestigious university, so surely I can do something. Much of what I bring to a company, though, doesn't come from coursework-- it comes from messing around with friends (student, faculty, or otherwise) late at night, trying to come up with cool stuff that works. At my last company, we supported SDKs in six languages. I was the only person who had shipped code (not just there-- indeed, mostly not there) in all six-- Python, PHP, Ruby, Perl, Java, and Objective-C. I wrote the Perl SDK from scratch in just a couple of days, while helping a customer debug their OAuth stanzas (that they were using in lieu), and made sure it not only passed its own extensive unit test suite, but all the Perl "Kwalitee" measures as well. Having never done Android development, I got a basic AR system working in a day. The prettiest, however, of the random tasks I undertook, was a data visualization I did in just a few hours (of my own time, late one night) that got us a lot of good press.

SXSW Interactive Checkin Visualization on Vimeo.

It's in Processing, if you're curious. Another language I picked up on the side (also how I learned Ruby, PHP, and Objective-C).

That leads me to the corollary, then. I love technology, and I love hacking, but it's not all I do; in the last twelve months I've served as communications head for a political campaign, replaced bits of my house, played in a pretty good little orchestra (I've played violin for nearly 19 years), spoken at conferences, and generally led a fairly interesting life through circumstances best labeled "odd." All of these things make me a better hacker, in the most traditional sense; I get things done using whatever means necessary for the job at hand, and I'm not afraid of picking up a new skill or two if they're what would work the best.

And things do indeed get done well. When I commit to a deadline, it gets done, no matter what-- as a young intern at VeriSign, I once stayed overnight to finish integrating VeriSign's one-time password technology with the research project that would become http://pip.verisignlabs.com, rather than disappointing their head of research. (I was later given the favor of researching and submitting a security patch to the open source version, Apache Heraldry.) I've worked on old codebases and new, for huge, established corporations, the government, and tiny startups just trying to make their way in the world.

So, as Arlo Guthrie said: "the only reason I'm singing you this song now is that you may know someone in a similar situation-- or you may be in a similar situation-- and if you're in a situation like that, there's only one thing you can do:" ping me. (You could sing Alice's Restaurant, but as a hiring strategy, that might have a somewhat limited scope.) I want to work for groups who want to be the best, and who need someone to fill in their cracks with a breadth of experience, and an attention to detail that can bring companies to the top. If that sounds like you, my email address is bfo -at- ussjoin -dot- com, and my resume is-- as always-- at http://ussjoin.com/resume.html. Good hunting!