Google thinks that my skills would make me a good candidate for a Software Developer in Test. I have to say that the assessment bummed me out a little. My initial reaction was that I’ve done test; I was hoping to move on to a development job. Specifically a development job in a group with the TA who started the whole Google ball rolling for me.<\/p>\n
I tried to start feeling good about it. I read some posts from the Google Testing Blog where it was clear that development is a big part of what their testers do. The main part, really. The recruiter set up a phone chat between myself and a Google testing manager. We talked about a variety of topics: the high Dev to Tester ratio; how the job stays interesting, how it really is a development position; how the job can give me a chance to be involved in a product at many more levels than as a normal developer; and about some of the specific meaty problems that the SDTs at Google have solved. It was a good conversation, but something was still bugging me. I didn’t know what it was at the time, but now I think I’ve figured it out.<\/p>\n
Even if Google testers are different, even if they are “revered” as the recruiter put it, making sure something works right simply isn’t the same as making something that does work right. I’ll say it again, because I think it bears repeating:<\/p>\n
Making sure something works right simply isn’t the same as making something that does work right<\/p><\/blockquote>\n
The accomplishments that I am most proud of at Microvision are not the many bugs I have caught or the test procedures I have successfully run. My pride is in what I have created. It is Flic firmware version X.37. It is the Automated Testing Fixture software. I know that in my role as a tester, I have helped create a higher quality product. But I don’t feel ownership for that product in the same way that I do for projects that I actually wrote code for.<\/p>\n