wasdev_Neil

Interesting question! The obvious answer would be the analytical and problem solving skills that are part and parcel of studying a degree in any scientific or technical field - I've found those map very well into the sort of skills you need as a software engineer.

More specifically, I spent a large proportion of my final-year timetable as part of a research group with postgrad/postdoc researchers. The ability to be comfortable working on something completely new, and getting up to speed very quickly, is probably the most important thing I learned!

One thing I always like to mention is a guy in a previous team I worked in - he was incredibly technical, held a position at 'architect' level, and was a Zoology graduate!

(Apologies to those of you who were hoping my reply would outline how IBM is snapping up physics students for a super-secret rocket program that our team is a front for - I'm just a mere software developer :-) )

I joined IBM from Uni almost 3 years ago - to give an idea of how the teams vary, I'm actually a chemistry/physics grad, so not everybody has to come from the traditional compsci/IT route. It's quite easy to move between teams (especially as a new graduate) - I had a couple of roles within other IBM product teams before I was lucky enough to be able to join the WAS Liberty team.

Write code, test code, drown myself in tea