Back to resources

What I learned Trying to Upskill a Tech Support Person to Engineering

Alignment
Different Skillsets
Conflict Solving
Onboarding
Coaching / Training / Mentorship
Career Path

4 February, 2022

Rajat Chowdhary
Rajat Chowdhary

Engineering Manager at Atlassian

Rajat Chowdhary, Engineering Manager at Atlassian, shares an unsuccessful attempt to onboard a tech support member into his engineering team.

Tailoring an Onboarding Process for a Non-Engineer

Previously in my career, I was the head of an engineering team in a hyper fast-growing startup. It had come to my attention that an individual within the tech support org was enthusiastic about engineering. They had been writing code during their personal time but wanted to upskill themselves and make larger engineering contributions.

I brought them onto my team and gave them some time to ramp up with a three-month onboarding plan. The first month was dedicated to learning the basics of my team's technical frameworks. The second focused on a deep dive into the code itself, since each codebase has unique identities. The third month concentrated on acknowledging and fixing any problems with code.

My three-month plan was thoughtfully created and ran past other members of my team. We had ensured that the process was thorough and did not overlook any areas necessary to become a serious engineer.

How the Onboarding Process was Unsuccessful

The new team member was really successful when it came to modifying existing code. They could engage with bug fixes relatively quickly, but when it came time for them to deliver their own features, we began to encounter challenges. Feature delivery was strictly based on writing new code, and the team member struggled in that department.

We were swamped with legacy bugs at the time and it was a short-term win to put this person on fixing these bugs and manning the slack channels. It was bad for the long term since it delayed getting the above-mentioned signal which resulted in going overboard the initial agreed-upon evaluation timeframe of 3 months.

For a while, this worked, but deadlines began approaching, and our team needed to zone in on feature delivery.

When I spoke to this individual that did not have an engineering background, I felt that visibility was lacking. Without my team's deep-rooted technical skills through education and experience, this individual could not speak on the same level as the rest of my team, decreasing collaboration and innovation. Through the lack of these interactions, I learned that there's merit in having the ‘engineering craft': the way engineers design their code, abstractions, and interfaces.

Eventually, after about five months, the time came to make a decision regarding the new team member. It came down to the fact that they were not able to meet the performance of the rest of the team, and if I let them stay, I would be lowering the standards for everyone. My decision was made with the entire team in mind, as the group works as a whole unit rather than singularly.

While it was a tough decision to make, the individual stayed with the company in their tech support role, creating a positive outcome.

Enforce Guidelines During Onboarding

  • Be very stringent about milestones when onboarding new members. It would have been a win-win if we had made that decision in 3 months.
  • I recommend that others assign a mentor to new teammates from the beginning. They should connect with the mentor about any challenges or problems faced. If milestones aren't completed, there should be clear communication regarding the next steps.

Discover Plato

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


Related stories

A Day in the Life of a Product Lead in FinTech – A Series

31 January

Discover the daily struggles, challenges, and moments of delight encountered when delivering banking products around the world. I will share my story candidly and honestly, without filter as much as I am allowed, and offer insights into my approach while providing retrospectives of the results.

Strategy
Embracing Failures
Cultural Differences
Career Path
Loussaief Fayssal

Loussaief Fayssal

Director of CX at FLF PRODUCT DESIGN

Ten quotes from Adam Grant relevant while dealing with layoff

27 January

Layoffs are tough. Dealing with situation we go through different emotions. First is disbelief, followed by anger, leading to frustration and finally accepting the news. Following quotes seemed relevant to review and again a perspective as we pass through hard times

Career Path
Praveen Cheruvu

Praveen Cheruvu

Senior Software Engineering Manager at Anaplan

I was passed for Promotion. What now ?

26 January

Passing for promotion happens to everyone in their career lifespan. If someone does not had to go through the situation, consider them they are unique and blessed. Managing disappointment and handling situations in professional setting when things don’t pan out, is an important life skill.

Changing A Company
Handling Promotion
Feelings Aside
Feedback
Coaching / Training / Mentorship
Fairness
Career Path
Praveen Cheruvu

Praveen Cheruvu

Senior Software Engineering Manager at Anaplan

15 Tips to improve profile discovery on LI

20 January

Recently, I have read the book ‘Linked’ from Omar Garriott and Jeremy Schifeling on audible. The audio book is 7 hours long. If you dont’ have time or need a brief summary, read on

Hiring
Changing Company
Career Path
Praveen Cheruvu

Praveen Cheruvu

Senior Software Engineering Manager at Anaplan

The art of Happiness

20 January

Happiness is a choice. Our upbringing and the surroundings have made it conditional. The first step is to get over the hump is self-awareness. Self-awareness is a journey by itself. The ability to identify what we can control, and we can’t is important.

Personal Growth
Career Path
Health / Stress / Burn-Out
Praveen Cheruvu

Praveen Cheruvu

Senior Software Engineering Manager at Anaplan