Back to resources

Upskilling a Junior in 90 Days

Meetings
Collaboration
Feedback
Coaching / Training / Mentorship
Juniors
Performance

7 December, 2021

Manan Patel

Manan Patel

Software Engineering Manager at Coinbase

Manan Patel, Software Engineering Manager at Coinbase, shares how he upskilled a junior that recently transitioned to his team, creating a plan dedicated to the process.

Problem

Some time ago, my team had an individual looking to explore engineering from another role within our company. My team helped this junior learn about engineering and navigated them to become productive members of my team. They had shifted from technical program management and wanted to start coding and shipping the features. It was difficult to adapt to the engineering mindset and solving problems in this new headspace. My team was small and had to compromise other tasks in order to upskill the new junior engineer.

Actions taken

In my first action step, I created a plan for the new member to transition within a ninety-day period. This plan consisted of actions I, my team, and the junior would take. The first part of the plan was dedicating a mentor to this individual. The mentor would meet with the junior on a weekly basis and review their programming and tasks they had been working on. I also created a reverse shadow system where the new member of my team observed the mentor while they worked on their projects. This allowed the trainee to understand the technical aspects of the role and involved a skilled employee who could answer any questions.

The next step was ensuring that all the tasks assigned to the trainee were well defined and understood the time frame. This allowed the new member of my team to recognize the expectations of the role and the workload. I did this myself, assigning them tasks with a well-defined scope and timeline. The most challenging piece was getting the individual user to the regular developing lifecycle, as well as getting them in the loop to test things easily. Initially, this was missing from my plan, as they had trouble entering the loop to test their iterations. After adding them into this loop helped them produce code much faster and make a greater impact.

The other actions were more aligned towards optimizing products they were working on to give them the opportunity to touch different parts of the codebase. Whether this was local storage, networking, or experimentation, I wanted them to be exposed to everything, so they were not just learning about one aspect of the role. After doing this, my trainee apprehended everything they would need to do going forward. I began holding monthly check-ins, three in total for the ninety days. These meetings were two-way communication where the trainee explained how the position was going and anything off track with the training. In turn, I gave my insight on their performance and any advice that I had.

Lessons learned

  • Be aware of your team's bandwidth and how it relates to working with a new teammate. When I took on the responsibility of the junior, my team was rather small and had to make tradeoffs to train them.

Discover Plato

Scale your coaching effort for your engineering and product teams
Develop yourself to become a stronger engineering / product leader


Related stories

How to measure Engineering Productivity?

30 November

When you grow fast, its normal to focus on Value delivery aka "Feature Releases". Too many releases too soon will inevitably lead to piling tech debts and before you know, inefficiencies creep in, performances goes down, and ultimately any new release takes too long. Sounds familiar? Then read on..

Productivity
Prioritization
Performance
Ramkumar Sundarakalatharan

Ramkumar Sundarakalatharan

VP - Engineering at ITILITE Technologies

How to improve engagement and retention in remote engineering teams?

25 October

Mrunal Kapade, an Engineering leader, based in Silicon Valley, shares tips that helped reduce attrition in the remote engineering teams while leading multiple teams from startups to Fortune 500 companies.

Remote
Company Culture
Collaboration
Motivation
Team Processes
Mrunal Kapade

Mrunal Kapade

Director of Engineering at Inspire Energy

Mindsets of High Performance team

14 October

Teams have tremendous impact on the products on they build. T.E.A.M definition - Together Everybody Achieves More is true. A collaborative and empowered team builds great product versus the good ones.

Innovation / Experiment
Mission / Vision / Charter
Building A Team
Productivity
Feedback
Motivation
Praveen Cheruvu

Praveen Cheruvu

Senior Software Engineering Manager at Anaplan

High Performance Team in Action

13 October

A high performance team refers to “ a group of goal-focused individuals with specialized expertise and complementary skills who collaborate, innovate and produce consistently superior results.”

Managing Expectations
Building A Team
Company Culture
Feedback
Coaching / Training / Mentorship
Praveen Cheruvu

Praveen Cheruvu

Senior Software Engineering Manager at Anaplan

Developing an Early Career Program in Technology Organizations

12 October

Why companies should invest in early career programs ?

Building A Team
Hiring
Coaching / Training / Mentorship
Juniors
Career Path
Praveen Cheruvu

Praveen Cheruvu

Senior Software Engineering Manager at Anaplan