3 ms·

> And what period of time did this happen over? I am in this company only for 4 months and he is asking me to "help"/help with other team issues. > get the la

> And what period of time did this happen over? I am in this company only for 4 months and he is asking me to "help"/help with other team issues. > get the lay of the land, contribute value I am trying to do this in my current team, did a research, found couple of issues, introduced some solutions, but I still see lots of things need to be improved. Part of me thinks, problem lies in me. I just need to understand what exactly is happening, if some problem, then I am more than willing to work on my skills and improve, if everything is indeed good and he just needs me in another project, then I need to evaluate the offer. I just can't understand if this is common with managers to keep pushing engineer to other teams, or does it happen rarely when manager is not satisfied

ethbr0 3y ago
IMHO, your job as a higher level engineer is to: 1. Quickly understand the problem and details 2. Come up with a plan to solve the MOST IMPORTANT problem(s) 3. Work through the plan with the implementation team, to identify any gaps / things they can't do 4. Cover the gaps, to ensure the project can move forward without you 5. Regularly check-in after you shift off, to make sure it's still moving forward 2, 3, and 4 are most of your value, because they're where you can use your experience and skills to produce better outcomes. I'd care less about whether your boss likes you, and more about whether he thinks you're doing valuable work. And one way to clarify that with him would be (every time he puts you on a new project) to decide what the end goal is. Project started? Project done? Team gets over a hurdle? Then when he moves you to a new project, politely remind him of the project you're currently on, and the end goal you two discussed, the fact that it's not done, and the time until you expect it to be completed. He can still move you, but hopefully he'd start realizing he's prematurely shifting you around.

ethbr0 3y ago

IMHO, your job as a higher level engineer is to: 1. Quickly understand the problem and details 2. Come up with a plan to solve the MOST IMPORTANT problem(s) 3. Work through the plan with the implementation team, to identify any gaps / things they can't do 4. Cover the gaps, to ensure the project can move forward without you 5. Regularly check-in after you shift off, to make sure it's still moving forward 2, 3, and 4 are most of your value, because they're where you can use your experience and skills to produce better outcomes. I'd care less about whether your boss likes you, and more about whether he thinks you're doing valuable work. And one way to clarify that with him would be (every time he puts you on a new project) to decide what the end goal is. Project started? Project done? Team gets over a hurdle? Then when he moves you to a new project, politely remind him of the project you're currently on, and the end goal you two discussed, the fact that it's not done, and the time until you expect it to be completed. He can still move you, but hopefully he'd start realizing he's prematurely shifting you around.