Taro Logo
Editor's Choice

Explore Editor's Choice on Taro

This collection represents the best of what Taro has to offer, personally curated by Alex and Rahul. If you're short on time, go through the content here.

Mid Level to Senior Promotion - What should I keep in mind?

Senior Software Engineer at Grab profile pic
Senior Software Engineer at Grab

I am trying to get promoted to Lead Software Engineer, which relates to an E5 level at Meta, if I am not wrong. I have seen several engineers in my organisation coast at the current level I am.

I wanted to understand if there are some key things I should be doing in order to perform at a Tech Lead level, so that I am promoted to one as well. This would be a bit long question, but please bear with me.

Following are some of the things highlighted in a few discussions:

  1. Should have demonstrated complex backend system designs - How do I create this opportunity to build a complex system for myself? Often, the projects we are a part of don't require complex solutions.
  2. Have a very strong code quality
  3. Mentor other engineers - I started having 1:1s with Junior engineers on how to grow. Have not been doing this with Senior Engineers, but I try to jump in calls with them whenever they need some help. Often, the credit goes hidden, and sometimes it does bother me, but not sure if there is some way around it. What are your thoughts?
  4. Handling production outages and incidents - Trying to be on top of it. Recently, have been putting out short term fixes, but alongside working on some libraries to fix it in an extensible way and have a larger impact with other teams as well. Sometimes, having visibility for my work in other teams seems to be difficult, but trying my way around this. If there is something you can recommend, that would be great.
  5. Should I mention in my skip levels that this is something I am targeting for myself? - Right now, my focus is to try to uplift the code quality, work on larger designs (a question mentioned wrt this), trying to uplift the team (I have created a channel where I share stuff that can help the team upskill, brief nuggets of information on how to write good code etc. Doing this almost twice a week for around 2 months now), trying to mentor engineers within the team.

Another aspect is that my team would be getting changed soon due to organisational requirements. Given that, How do I make sure I am on the right trajectory to getting promoted ? (One thing on top of my mind is that I would be asking for junior engineers whom I can work with and try uplifting, alongside asking for opportunities/projects that would have large visibility and impact.)

Do you have any other advice for me?

973 Views
15 Likes
Editor's Choice
8 Comments
4 months ago

Should I quit to prep for interviews?

Data Engineer at Financial Company profile pic
Data Engineer at Financial Company

I’m currently working as a Data Engineer for a mid-sized (1500 people) investment-services corporation. The company has been around for a long time and makes money, but it definitely isn’t a tech-first company (e.g. it refers to the software side as “I.T.”, has tons of meetings, approvals needed to install almost anything on my computer, including VSCode).

I want to get into FAANG as a software engineer because I want to move away from the business/data side of things and closer to the engineer side of things. On my current team, I’m the lone data-engineer (will be joined by another in a few months) and as someone with <3 years of experience, I know that my growth is being stunted.

I’m currently grinding AlgoExpert to prep for interviews.

How should I think about the circumstances under which it would be worthwhile to quit in order to prep (full time) for FAANG interviews? Here’s what I can come up with in terms of current pros/cons of quitting:

Pro’s of quitting:

  • A LOT more time to prep for interviews, can probably increase my output of questions by 3x
  • Can do a lot more interviews without worrying about my job and scheduling
  • Do less business/data stuff which I plan on moving away from anyways
  • Get closer to a FAANG salary faster, which will likely be around 2x of my current salary

Cons:

  • Don’t know how long it will take me to get a job
  • Don’t know how easy it will be for me to get interviews without a job
  • Psychological benefits of having a job
  • Some learning on the job
  • Low-stress job, nice manager, no overtime
  • Already take an hour or two of my current job time to do AlgoExpert
  • Make some money right now

How does the answer change (if at all) if I manage to land interviews with a bunch of different FAANG companies (say 5+) and I’m struggling to schedule all the time for interviews, prep for them, and do minimal work at my current job?

Thoughts are appreciated!

424 Views
2 Likes
Editor's Choice
4 Comments
6 months ago