SOMEONE must want this job!
This isn't the sort of semi-permanent topic I'd like to be doing more of, but we've had an opening for an SDET or two for months now- I've been trying to do the work of more than one to cover this, things are going undone, customers are being under-served, and I sure could use the help!
You'll need to know kernel driver basics [there will most certainly be a quiz], and understand the basics of testing software. You'll need to be passionate about software quality in general and driver quality in particular, providing good customer service [we want developers to LIKE using the frameworks], and I can tell you from my own experience that while the work isn't easy, expectations are realistically achievable and good results will definitely be noticed. You'll be coming to Redmond, but I've been here for nearly 20 years, and I think there's a lot to like about that.
In return, you get an insider's chance to influence the current and future direction of driver development for Windows and help us help the development team to drive the quality of KMDF and UMDF to ever-higher levels. You may put paid to the last BSOD in creation [OK- that one might be a stretch, but it's good to have dreams as well as goals]. You may create new WDK samples, as several of our team have done. You may create new WDK tools as I and others in our team have. You'll probably meet Doron and Peter! Ilias, Patrick, and I you won't have much choice about meeting, since we will be your co-workers, but we're pretty decent folk...
I myself find the pay and benefits to be excellent- you can see summaries on the main Microsoft site. Once you've solved all the driver problems that ever existed [or you decide its time to try something else- these openings came from people moving on to other jobs at Microsoft], you can see what other challenges and opportunities await you at the best software company on the planet [my opinion, but it is my blog, so I can do that here].
If you think you've got the right stuff, we'd love to talk to you. The first two links should get you started- if they stop working ping my email, and I'll follow up. When [I really hope that doesn't need to be "if"]they're filled, I promise I'll update this post appropriately so nobody gets their hopes up unjustifiably...
PS- If you're an experienced developer and think there's some sort of downgrade to becoming an SDET, please don't. My motto- The 'T' doesn't stand for 'trainee'. People can and do move back and forth between these roles- it's often a good way to add skills and experiences useful in your career.
