So how *do* you find tester-developers? Certainly a job description that says "QA" seems to be an invitation for lots of resumes from script-followers. I want people who think repetetive tasks are what computers are for, not people, and that "poking at the interface" is exploration to help identify test automation to write.
Yes, yes, yes! One of my college internships evolved from CAD draftsman to CAD system programmer exactly because of this point of view: I knew the computer could do all this repetitive work for me so I pestered the sys admin all summer with questions about doing so. At the end of the summer she offered me a job. (Which led more or less directly to my employment at Microsoft, but that's a different story I'll tell some other time if any one actually cares to hear it.)
So how do I find tester-developers? I will tell you where we *think* we can find them - that is, where we are looking - but the fact that we have had a tester position open for ages now is testimony to the seeming scarcity of the breed.
Where to look comes from what you're looking for: smart people who are excellent coders and also have a passion for figuring out what makes things tick and thus what might make them break. Several sources come to mind:
Great SDE/Ts are hard to find, but they are out there. Not all of them are on my team, I swear! <g/>
[Edit 10 Mar 2005] Addendum: Yan Sun wants to know whether I consider Microsoft developers when I'm looking for SDE/Ts. Most definitely! Developers can become great testers just as easily as testers can become great developers.
*** Comments, questions, feedback? Want a fun job on a great team? I need a tester! Send two coding samples and an explanation of why you chose them, and of course your resume, to me at michhu at microsoft dot com. Great coding skills required.