I'm also talking to other companies in San Francisco, Mountain View, and Santa Clara. I had a lot of fun talking to the SF company, first because I know the team lead from around my communities, and second because they had a homework problem that was a lot of fun to work on: parsing a data format the company uses. I actually saw the team lead at the cocktail party last night, and he said one of the warnings my code printed out--I wrote it like I would write production code, which means it was really good--reminded them that they have to update the problem description, because strictly according to the description, all of the sample data was invalid in one aspect. (I decided to make those be non-fatal errors, because otherwise the exercise was useless.)
The Mountain View company is moving very. Very. Very. Slowly. It'd be nice to give them a chance, but I need to get to work.
I've been struck pretty hard in the face not only how rusty I am at coding, but how a normal interview process doesn't really capture what's useful about me. I'm an unusual package as a software engineer, and I've struggled for years to describe it. I'm a good programmer, but not the absolute best. I'm very good at complex systems, understanding and affecting what happens in networks of many moving parts. I'm good at translating and facilitating communication between human beings who can't seem to communicate. I'm pretty dogged about tracking down bugs. And then a lot of the time, information and questions come past me, and I have something useful to contribute.
I need a more compelling pitch than "I'm generally really handy to have around."
UPDATE: My friend at the Palo Alto company says that when they asked why I was useful, he said, "He fixes shit." Which is true! But begs for elaboration. I'll have to work on it.
UPDATE 2: Anna reminds me that J said I'm "like a Google, but one you can Skype." Good brainstorming so far.