Hello people, I was wondering how do your companies deal with the life cycle of developers. After you reach certain seniority, what else can you do?
FMPOV a senior is comfortable with:
- understanding (most of) the business.
- understanding (most of) the technology.
- relatively good communication skills.
- being able to deliver.
- writing nice code (this is subjective and possibly not empirically true, there are probably many seniors who do not necessary write good code)
It seems to me that many devs, after 3 or 4 years in a place get into a stagnation point where they look for new challenges.
What else can be done?
I think many companies (including mine) offer the "communicator" grow path. Where your role is more about talking/being a guru, but what if you are a good engineer and want to continue doing that?
Does anyone have ideas over this topic?
Thanks
FMPOV a senior is comfortable with:
- understanding (most of) the business.
- understanding (most of) the technology.
- relatively good communication skills.
- being able to deliver.
- writing nice code (this is subjective and possibly not empirically true, there are probably many seniors who do not necessary write good code)
It seems to me that many devs, after 3 or 4 years in a place get into a stagnation point where they look for new challenges.
What else can be done?
I think many companies (including mine) offer the "communicator" grow path. Where your role is more about talking/being a guru, but what if you are a good engineer and want to continue doing that?
Does anyone have ideas over this topic?
Thanks