Developers at Microsoft (in systems) spend less than 18 weeks a year writing new code. The rest of the time is design and bug fixing, often on projects that have 100s of developers working on them. Sometimes 1000's. It's not uncommon for a large project to have 100,000 bugs found, tracked, fixed and regressed over the course of a release. When you are writing code for yourself, it's nice to be dense, to have a lot of code fit on one page, use single letter variable names, not spend the time to write paragraphs about what is obvious to you and so on. We've all been there. But when a huge percentage of your time is spent on code others wrote, or you are looking for potential bugs or security flaws and have to be very very clear about exactly what the assumptions are at every line...
DB code has a ton of math in it. The code itself is fine, quite readable, but complex. It's hard for someone like me to come along and see what's going on right away. In production code, its very common for there to be more lines of comments than code in a source module, sometimes by a factor of 5 or more.
You get used to Hungarian, you learn to love it and miss it. It's not used everywhere and as more projects are being done in managed code and C#, things may change. But the vast majority of stuff is still C or C++. There, Hungarian in the norm.
As far as my job, I did a whole pile of difffernt things over the years in groups from Windows to Xbox, mostly designing software and managing software development groups. I even had a hand in VB 1.0. Most of my tenure was on Exchange Server in various roles. It's been a while since I wrote production code, so I'm rusty, but once you learn how to ride a bike...
Send me a resume when/if you are ready. I'll get it to the right people.