Archipelago Learning interview questions

1. Due to the fact that the company is in the process of being bought out. It's a very High Risk Job. When companies buy each other out, most of the time they eventually consolidate their IT shops. So it seems pretty wild that they aren't clearer to candidates about their situation. 2. I don't think they really interview well. This position was a director level position. yet, i must have met with 20 to 30 people during the interview process. That sounds all fine and dandy, but in reality. When can you ever get that many people to agree on anything, and if you ever get to the point where you do.. you have to realize that after 20 plus candidates go through that many interviews.. the people interviewing.. seem to "relax" their standards.. cause they start getting to the point where they just want to get it over with.. It's always a bad idea to have that many people involved. I understand getting buy in on a candidate but that approach isn't the best. 3. The office, downtown and it looks like crap. Even the VP's office the spot reports to is basically in a closet. in fact this "director" spot will be assigned a cube.. 4.. Director level spot.. but hey.. they only have 2 QA people.. that's not really reflective of QA Director level need.. really that's what people call a QA Lead.. 5. The pay is also on the low end for Director Level. 6. Communication. They don't communicate very well at all. which should give you insight on how life would be working there. 7. When discussing the rates for contractors they want to hire.. Their rate expectations are WAY out of wack.. and are inflexible. Meaning that they arent really receptive to sound advice and that in reality their budgets are going to be unrealistically aligned with their objectives Not a good fit for me obviously.

Consisted of a phone interview, and then a panel interview 3 people from HR and 1 team member. Most interview questions were behavioral. Interview was easy.