2

How do I create impact as a junior engineer in a team full of very experienced folks?

Profile picture
Entry-Level Software Engineer at Taro Community5 months ago

I am moving teams for the first time in my three-year long career and the team I am moving to is full of very experienced folks(15-20) with the least experienced person with 10 YoE. Some of these folks have also been in the same team for years. I will be new in the team as well as tech stack.

How do I create impact, learn from these people, be able to create my own identity and not be shrugged off as a "junior engineer" who is not given important tasks?

Any additional tips on how can I leverage this move as a fresh start? Like relationship with manager, team and my attitude towards the work?

57
3

Discussion

(3 comments)
  • 2
    Profile picture
    Tech Lead/Manager at Meta, Pinterest, Kosei
    5 months ago

    My advice is to pick an area, however small, and become an expert in it. If you pick an area small enough, you can become the expert among a group of 15-20 people within a few weeks. This is where the Taro Expertise Theory comes in.

    Taro Expertise Theory: You can become more knowledgeable than anyone

    • Within a group of people P (e.g. the team of 10)
    • Within a certain domain D (e.g. the build system)
    • Within a certain time T (e.g. a week)

    Your goal is to maximize P and D while minimizing T. You can also ask about neglected areas from people on the team as a way to build the relationship and figure out where you should become the expert.

    (I highly recommend going through the entire onboarding course!)

  • 1
    Profile picture
    Tech Lead @ Robinhood, Meta, Course Hero
    5 months ago

    I like the go-getter attitude here! My main advice is to not rush it. Impact should come naturally and not feel forced. What should happen is that you come in full of positive energy, build up relationships, do great work, and then you'll earn trust over time.

    After you have the trust, you can start asking your manager, tech lead, etc for more opportunities (and they'll likely just suggest some to you proactively).

    In terms of a roadmap, it would go something like this:

    1. [Course] The Complete Onboarding Guide For Software Engineers
    2. [Course] Level Up Your Code Quality As A Software Engineer
    3. [Course] Nail Your Promotion As A Software Engineer

    For the promotion course, I highly recommend the lesson about impact as junior engineers aren't really held responsible for it (quality of work is far more important): https://www.jointaro.com/course/nail-your-promotion-as-a-software-engineer/impact/

  • 0
    Profile picture
    Entry-Level Software Engineer [OP]
    Taro Community
    5 months ago

    Thank you so much! I have already started looking into the course.