3 ms·
Thanks. As far as I know they're collecting people for a new project and growing an almost-separate department, so it's definitely not a dead branch (unless the
by changingjobs 16y ago
Thanks. As far as I know they're collecting people for a new project and growing an almost-separate department, so it's definitely not a dead branch (unless the project fails that is...). It might be worth looking at the current leads / managers from that perspective though.
- brudgers 16y agoWhat I mean by "dead branch" is a department from which there is no mobility to elsewhere in the corporation because the skill set required and the experience gained within the department isn't transferable elsewhere in the organization - e.g. a ship's cook never rises to executive officer.
- pasbesoin 16y agoI wrote something longer, but I'll condense it to: I'd be very cautious of moving from development into a QC/testing role. Those roles are often treated as second-class citizens within a development environment. And even when development treats them well and allows them to really do their job, more general and senior management still sees them as second class citizens. I'd ask for a detailed description of the types of work you will be doing, and seek your own self-assurance (whatever they tell you) that your development skills won't atrophy. Moving from a QC/testing role to development can also be a hard sell. Don't get stuck/typecast. I suspect that, the larger the organization, the more true a lot of this is. For one thing, QC/testing changes from being a few individual roles to its own entity, depending on the organizational structure. If you can, spend some time networking with people in and about this kind of role. If you can make some safe connections to people at the potential employer, all the better. But also try to ascertain whether the move will have any negative career implications. (I'm just one introverted bloke, and my experience is likely biased.)