Frequently Asked Questions
I'd consider a remote position that required at most 5% time away from my family and at least 50% pair programming. Otherwise, the answer is no.
Now, if you have a job that I could do from Portland, click here for my contact information. (You might want to keep reading this page first, though.)
The address is: sam (at) [my last name] (dot) com. (Don't forget the hyphen.)
I'd prefer to avoid phone calls for a number of reasons:
- I'm on a maker's schedule, which means interruptions are surprisingly disruptive to my flow.
- I've already tried to answer some of the most basic questions on this site, and I've probably phrased them more clearly here than I will on the phone.
- This question is asked frequently enough that my default answer has to be, if not "no," at least "read this first."
- If and when a chat does seem warranted, I'd prefer to conduct it in person or on video.
I'm always happy to hear about new opportunities, but I'm satisfied with my current situation, and I'm highly selective in general. Over the years, I've developed a good idea of the kind of environment where I thrive: small companies doing work I value, with considerate, capable teammates who pair program regularly and who consider "production code with no test coverage" to be an oxymoron.
If you really want to grab my attention, tell me how you collaborate, how you keep quality high, how you contribute back to the community, and how you help your team continue to learn and grow. (I'm especially interested in mentoring developers who are earlier in their careers.) Last but definitely not least, tell me what you do to keep your team diverse and inclusive.
No, but there's a chance I might know someone who is.
Possibly. It depends on what you're looking for, and on who I've talked to recently. Sometimes I know people who are looking for something new... but the more senior folks I know tend not to be on the market for very long (or, in some cases, ever).