[tomfakes]

I just had a discussion with someone else about fast release schedules and QA teams.

If an organization wants to ship often, then QA teams don't work. You need the developers to write and own the test system. The new feature isn't done until the developer has tests for it and all the existing tests pass (even if this means changing those tests due to functionality changes). If this is passed off to a QA team, the whole process will always be broken.

Your organization is broken, and you are setup to fail (2 QA and 25 engineers!)

You can stay and try to help fix it, but this will be hard for you, since you are new, and change needs to come from the top management, or an engineer that the team will listen to. Even the top engineer will find it hard, since a lot of programmers get used to having a QA team to avoid this process!

If it was me, I'd be looking for my next opportunity and planning to leave pretty soon.