Intercom

I'm aiming for a promotion in 5 months and to do that I've been told that I need to evidence execution on a few complex projects. As a team we're working on some big projects but I'm not sure how to approach identifying a sub-project, isolating and owning it.

Does anyone have any tips on this?

I recently made a string of silly mistakes related to a particular project that led to a few bugs being deployed to production. I think I incrementally got more and more overwhelmed and stressed by the project because my initial fix caused a bug and from there I fixed that bug and inadvertently caused others.

I'm concerned about how this might play out with my EM. How I can best approach owning this set of silly mistakes without it having a negative impact on my reputation due to my low code quality mistakes partly caused by the stress of the situation?

My tech lead asked me to write up a mini bug report for our our engineering retro and this morning my EM was asking about what the report was for because I had written it down as part of my weekly goals in our stand ups. My EM has low context on the complexity of the work we do and is far from the code - tending to over index on any signal he come across.

I just went through my performance review and I'm meeting expectations so I don't have a formal review for a while. I'm about to go on vacation for a while so I'm hoping this fades into the past but still I'm not sure exactly how to play this now so it comes out in my favour before I go away.

I feel like I lack clarity I know I should be taking the time to plan my day but I find myself getting pulled into the working context at any point in time. How do more senior engineers approach this? Are there personal rituals and routines that people use on a daily or weekly basis to move the needle?