Andrew didn't ask, but I thought I'd just add my 2 cents:
I've been at Acquia for a few years and it's a fun place to be.
Running a system on such a large scale is one of the coolest things I've done in my career so far and there is something new and interesting happening every day.
Something that is appealing (at least to me), is that the team is running a very "professional" process.
All of the commits are code reviewed and have passing tests, the colleagues are all great and impressively capable engineers. Everybody is excited about adding things like code metrics, good refactorings and helpful tooling (travis ci, ...). Even though it's a somewhat "streamlined" process, there is still enough time to fix those annoying little things (Upgrading the Ruby version we use, restructure our puppet manifests for logical consistency, ...).
It's a great place to learn and work in a team that actually lives the whole DevOps idea.
Andrew (syrneus) is an Engineer and understands the problems that business requirements can have with the current way we're doing things.
Ok, enough now before the marketing department tries to get me to write a blog post ;)
I've been at Acquia for a few years and it's a fun place to be. Running a system on such a large scale is one of the coolest things I've done in my career so far and there is something new and interesting happening every day.
Something that is appealing (at least to me), is that the team is running a very "professional" process. All of the commits are code reviewed and have passing tests, the colleagues are all great and impressively capable engineers. Everybody is excited about adding things like code metrics, good refactorings and helpful tooling (travis ci, ...). Even though it's a somewhat "streamlined" process, there is still enough time to fix those annoying little things (Upgrading the Ruby version we use, restructure our puppet manifests for logical consistency, ...).
It's a great place to learn and work in a team that actually lives the whole DevOps idea.
Andrew (syrneus) is an Engineer and understands the problems that business requirements can have with the current way we're doing things.
Ok, enough now before the marketing department tries to get me to write a blog post ;)