The New York Times

This is a company that believes in its journalistic mission as a means of enriching society. It's important, and it's a great feeling that you are a part of that.

In the NYT, you get to work with many technologies covering latest 3rd party APIs, internal APIs, EC2, PHP, JavaScript, mobile (iOS, Android), internal CMS, feed services, and more.

Colleagues are sharp, good-natured, and great to work with. Management within the software group are themselves software devs.

Depending on your project, you get to collaborate with editorial and build one of the largest news sites on the planet.

Finally, there is an active roadmap to harnessing developer ideas and using that to drive innovation on the website and within the organization.

Nothing worse than what you'd expect at other companies, and you would learn to navigate around it. Product and Ad people try to get last-minute features included after requirements freeze. Sometimes there are too many people at too many meetings (easy to avoid once you recognize they don't need to be there).

As the company continues its push to digital first/print second, there are a number of depts from the print side that are struggling to stay relevant and thereby attaching a voice to projects they don't need to be in. Again, avoidable once you realize this.

Listen to your developers more. Send more devs to conferences as advocates. Arrange more social events. Continue to foster the culture of innovation that you have begun.

On a larger note, cut the fat if you are serious about the business. Lots of big meetings with people who add nothing to them or the company. You're splintering focus with both editorial and software having people on "emerging platforms" etc. who don't talk or know of the other. You're afraid to fire people on the editorial side, so instead, you promote them out or promote horizontally out, which is still damaging.