Node.js + NoSQL?
We have some huge clients that require legacy browser support (IE6 and above) so it's a mix of typical front-end stuff, a ton of VM's for testing and if we're working on a new build website with no history or few existing users using legacy browsers some Backbone.js, Modernizr and LESS/SCSS. Like most developers, we use a lot of jQuery and custom JS on our sites, but we also make sure our sites function correctly when JS is disabled.
The back-end stack is ASP.NET using C#. As we have a mixture of inter-agency work and our own stuff we use a bit of everything really. Sometimes we use Entity Framework, sometimes we're limited to .NET 2 and sometimes we're working on large-scale websites using Sitecore. The main CMS of choice is Umbraco, and over the past couple of years I've really started to enjoy using it. The IDE of choice is, obviously, Visual Studio 2010, and with ReSharper installed I'm yet to use anything even remotely as good.
For personal projects I tend to use Python and Django. I've toyed with writing some tools using Google App Engine as the primary store, but I usually work with PostgreSQL. Version control wise, at home I'm a Git guy, whereas at work we use Mercurial. Most of my code is written using Komodo Edit and PyCharm. I've got a few desktop projects I'm looking to start soon, and I'm hoping to either use F# or Haskell, depending on whether I can fix my Ubuntu box or whether I'm limited to my Windows 7 box.
Groovy/Grails, Java/Spring, Ruby/Rails, Python/Django|Tornado|Web2Py, Node.js, Meteor
Haven't had to do anything requiring significant amounts of message passing yet, so no ZeroMQ, RabbitMQ yet.
Current fortune 500: Java/Dojo
Personal Project #1: Python/Django/Backbone
Personal Project #2: Node