1

I'm working on E4 level scope to get Promoted, and I need help with creating Eng Plan for Projects

Profile picture
Entry-Level Software Engineer [E3] at Meta24 days ago

Hi, I started working on E4 level scope, and for some projects, the TL can tell me to create the Eng Plan for Execution Independently. How can I do this with certainty and confidence without missing any case/scenario during the creation of the ENG Plan?

Also, our team roadmapping is upcoming, how can I contribute to the team roadmap as an E4?

I want to increase my impact and contribution overall.

Thank you!

40
2

Discussion

(2 comments)
  • 0
    Profile picture
    Tech Lead @ Robinhood, Meta, Course Hero
    22 days ago

    For creating the engineering plan, I recommend this: System Design Masterclass: Shipping Real Features To Production

    If this is too heavy (likely given that you are E3), they are probably looking for the more local version which is having very detailed tasks. Here's an example from the code quality course: https://www.jointaro.com/course/level-up-your-code-quality-as-a-software-engineer/lay-out-the-plan/

    Also, our team roadmapping is upcoming, how can I contribute to the team roadmap as an E4?

    My expectation for an E4 in those meetings is to have some sort of opinion. I don't expect them to drive any part of those meetings, but if they are a leading voice on certain projects, that's obviously nice. 2 things to have an opinion on:

    1. Project ideas to add to the roadmap
    2. Arguments for or against a project already on the roadmap (presented diplomatically of course)
  • 0
    Profile picture
    Tech Lead/Manager at Meta, Pinterest, Kosei
    19 days ago

    On the roadmap topic, one way to contribute at an E4 (mid-level) level:

    • Bring Technical Insights: You're probably deep in the code. Use your familiarity with parts of the codebase to offer insights into the technical feasibility and potential challenges of proposed projects.
    • Identify Technical Debt and Improvements: You are likely close enough to the code to identify areas of technical debt or potential improvements that could benefit the team in the long run. Propose projects to address these.

    You can likely do some legwork ahead of the roadmap meeting by researching more about the proposed projects.