3 ms·
I don't think you can put a static time on how long you should be at a company. If you're at a company that is still growing, increasing revenues and/or profit
by nemo44x 11y ago
I don't think you can put a static time on how long you should be at a company. If you're at a company that is still growing, increasing revenues and/or profits, increasing head count which leads to relatively fast promotions and bonuses and "going the right way", it's very likely worth staying at. Why introduce unnecessary risk? The trick is knowing when to abandon ship and to get out before it's a depressing place to be. It doesn't mean you shouldn't be willing to talk to other companies. But I'd not always recommend the grass is always greener.
- freehunter 11y agoYeah I should have clarified that "two, maybe three years" was not for leaving a company, but rather how long I think you should remain in one job. Moving from junior to associate programmer, going from analyst to engineer, even moving from helpdesk to development, it's a step up. In IBM terms, if you're a band 7 for three years, it might be time to look at other options. If I am Associate Middleware Software Engineer at Company X for four years, IMO, that's a little too long.