I've got 24 hours to choose between two positions to transition to at the end of the project I'm on (which is a couple weeks). It's a big decision because it basically is deciding if I head into management or keep on as a hardcore techie.
They are:
1) Tech Lead for the next version of our flagship software. It's a huge opportunity, with ~20 devs reporting to me technically. This is different from being a functional manager which deals with vacations, HR, etc because it's focused entirely on the product and people's contribution to it. I would get final say on architecture decisions, who works on what, what kind of features we're able to add, etc. There is still development here, but it's secondary to managing the other developers on a technical level.
Pros: Much higher visibility, probably greater path for career advancement
Cons: Less development (which I love), and more people
2) Solo R&D developer. I would be a team of one, but able to interact with any team within the company. It's a freestyle position where I sort of pick my own direction and run with it, provided it's related to our company and its long-term goals.
Pros: Open-ended development on cutting-edge stuff (awesome). No managing anyone else.
Cons: Less visibility, probably less room for career advancement.
One wrench into the works is my manager really, really wants me to do the R&D position as it's his baby. He's been "asked" by upper management to see if I was interested in the tech lead position, which is what they would like me to do. I'm not giving this a lot of weight, but it's still something I'm taking under consideration.
I'm leaning towards the tech lead position currently, because of the potential for advancement trumps technical interest. I figure I can always develop on my own time…
They are:
1) Tech Lead for the next version of our flagship software. It's a huge opportunity, with ~20 devs reporting to me technically. This is different from being a functional manager which deals with vacations, HR, etc because it's focused entirely on the product and people's contribution to it. I would get final say on architecture decisions, who works on what, what kind of features we're able to add, etc. There is still development here, but it's secondary to managing the other developers on a technical level.
Pros: Much higher visibility, probably greater path for career advancement
Cons: Less development (which I love), and more people
2) Solo R&D developer. I would be a team of one, but able to interact with any team within the company. It's a freestyle position where I sort of pick my own direction and run with it, provided it's related to our company and its long-term goals.
Pros: Open-ended development on cutting-edge stuff (awesome). No managing anyone else.
Cons: Less visibility, probably less room for career advancement.
One wrench into the works is my manager really, really wants me to do the R&D position as it's his baby. He's been "asked" by upper management to see if I was interested in the tech lead position, which is what they would like me to do. I'm not giving this a lot of weight, but it's still something I'm taking under consideration.
I'm leaning towards the tech lead position currently, because of the potential for advancement trumps technical interest. I figure I can always develop on my own time…
Comment