This strikes me as unusual, usually the support and testing guys want to get into development not the other way around.

Quite. I'm thinking my path would be more in terms of operations (speccing new equipment reqirements, network design, bandwidth needed, monitoring, maintenance) and in terms of QA and release control (automated testing, random testing, continuity, focus groups).

For example, when Scott Cook of Intuit was building Quicken, he (or one of his guys) would plonk themselves down beside amateur testers and watch how they used the software. Every time the tester ran into a problem, the programmers would be told where the problem was, and to simplify or clarify the interface.

I guess I'm getting to the point where I can say, "Development? Yeah, done that.", and be able to move on to the next thing. The most obvious step to me right now is Operations and Support.