Taro Logo
Promotion

Explore Promotion on Taro

The clearest way a company can acknowledge your growth. At the end of the day, you can't solely interview your way to a principal engineer; promotion is the true foundation of your pay and career.

Stuck as an Entry Level Engineer

Anonymous User at Taro Community profile pic
Anonymous User at Taro Community

Hello,

As the title says, I’m stuck as an entry level engineer in FAANG for almost 4 years now. I’ve been reflecting on what I’m doing wrong.

My first company I worked for 1 year and didn’t not like it because the lack of mentorship. I joined and my questions never got answered, the tech lead didn’t really care about giving mentorship, just gave me links and bug IDs. I was able to survive for 1 year but I left the company because I felt so lost. My manager mentioned that I was “on track” to getting promoted but I hated the culture.

Then worked for 1.9 years on another company, where I received awards for my projects and contributions. I did receive mentorship here, but I was not able to get promoted. At the end of the timeline my manager mentioned I was moving slower and slower. I was working as a full stack and I believe my error here was not playing my strengths, since every time I had to take another project it would be on a different area, such as server on a language I never used before. I had a few discussions with my tech lead and I felt I lost my team trust because they would give a lot of comments, and just get a lot feedback from other people. This kinda demoralized me and made it hard to keep working so I changed teams. My last team I worked for 8 months before getting laid off. Here I also received recognition for my projects. My first project I missed the deadline because the onboarding had nothing to do with my project. I integrated our tool with an external team, so most of the code base I worked was not even ours (the techlead and team didn’t have much knowledge). Then I was given another project where I was starting to get traction, onboarding and project matched, I had to ramp up again on the new tech stack and my manager was getting frustrated with me, my team was very helpful and I was slowly to become independent. I feel like people trusted me here and code reviews would go smooth this time, at the end I was finally getting positive feedback, but was affected by the layoffs. From reflecting, here is what I did wrong:

  • Not communicating well enough my work with my managers. Status updates I was blocked/learning and that would make me look slow.

  • Not very good mentorship, I feel like at the beginning I needed lots of 1:1 to be able to learn our teams codebase. Sometimes I got very good mentorship but not complete. So I learned well parts of the code base where the tech stack applied.

  • Switching projects too much, went from front end, full stack, server side with several languages. Every time I had to re learn a lot of new of the tech stack.

I did get several recognitions for my contribution with at least helps me think I’m not completely inadequate for the field.

I am looking for a new position, is there anything that could help me perform well as a mid engineer?

Thanks

239 Views
7 Likes
2 Comments
a month ago

What is the best way to let my management know I am looking for internal transfer?

Anonymous User at Taro Community profile pic
Anonymous User at Taro Community

For me i am looking for promotions. I architected, led a staff level project successfully with 5 engineers working with me over a period of 5 months.

Nor one person had a bad thing to say about me or the project and everyone agrees it was a major step for our team.

To be fair, I had a troubled relationship with a principal engineer who namecalled me in a public meeting with my engineering manager in that meeting and I decided to stop talking to him (i would avoid going to meetings with him instead of confronting him)

The principal engineer gave my managers feedback that I am trying to hoard information.

Now my manager is giving me the feedback that I don't go along well with more senior engineers (which is not true, it is just 1 person). I was denied promotion even though more senior engineers than me who I led are getting promoted.

There is also some resume driven development going on at the management level and pe level which is what I was asking questions about.

This was the reason for strong resistance against me and product.

From my end I have tried to normalize my relationships. But it seems my hard work may be better rewarded elsewhere.

I don't want to say all this but am curious how would one let their managers know that they are looking outside within the company. The reason for letting them know is they will get an email when I apply internally.

76 Views
2 Likes
1 Comment
a month ago

How to navigate promotion talks when no direct manager or director in sight for approx. 2-3 months while being a new member on a team?

Anonymous User at Taro Community profile pic
Anonymous User at Taro Community

I recently changed teams(been over 4 weeks). The current team did not have a manager/sr. engg manager to report to, and everyone reported to an Sr. director. This sr. director reported to a VP in my org.

Unfortunately during a round of layoffs, our director got laid off. So, now imagine my team is "headless".

Our VP did mention that they will try to bring in someone interim. Say that happens, and I am able to make a good connection with this "new" but temporary manager, but after a few months, we get a "permanent" manager, my questions and/or concerns around these are

  1. This would be my first time I will be in this situation mine is a tier-3 company, also not a tech-first company, is this how even Big Tech works? How do you all navigate this change, and continuous (non-technical) context switch of leadership?
  2. As you might have guessed how do I best make sure that my accomplishments(refers to the brag doc*) gets clearly communicated between my old manager, me, and my new manager?
  3. Does it make sense to even "talk" about getting promoted with the old manager if I have been on this team for 4 weeks?
  4. Re. to point 3, some notes about my accomplishments: I already was able to find bugs in their pipelines, and communicated about this to cross functional teams too, and everyone acknowledged this, and we have been able to avoid a major failure while shipping to prod environment, thereby saving us time(in months). What I am trying to say is I have been making(in my humble opinion) impact from day 1. I also am contributing to an internal library which will be used for onboarding several teams(cross regional too) in my company. I am the second developer on this repo. I already am keeping track about all of this in my "brag doc", I have been clearly communicating about my work with my scrum master, my current Principal Engineer, and other engineers.
  5. This is painful to write but, we have 3 engineers including me who are on the same level as mine(level 2), 1 Level-1, and 1 Principal Engg. Now, I am not comparing, but how do I put my best foot forward so that I too get a shot of pushing forward my promo packet along with others? There is a notion in my company(I dont know about Big Tech) that we "tend to" not have more than 2 level-3 engineers on a team, so should I just give up of not hoping to get promoted, and instead keep my head down and wait for new year or until I quit? Sorry if I sound negative, but its what it is.

Some more information about me:

YOE: 6+ this is what has been killing me from inside, 6+ yoe, and stuck on Level-2, I agree things were not hunky dory with me(been through a lot of personal s***), and couldn't focus on this side of my life.

I agree this is my mistake, but I know myself, and I know I can make it work,I can push myself and make it work, but asking for a guidance is all.

Appreciate you all for reading till the end, can't thank this community especially Rahul,and Alex.

52 Views
0 Likes
3 Comments
2 months ago

Exceptional Team Member in team slowing promotion?

Entry-Level Software Engineer [L3] at Snap profile pic
Entry-Level Software Engineer [L3] at Snap

I have 2.5 years of experience and working as an L3 engineer at Snap. To give you a bit more context about the structure of my team, We have 2 L3s, 2 L4s and 1 L5 in the team.

We just had our half yearly performance review. The review I got from my manager for the half yearly performance reviews was “exceeds expectations”. Clearly, I am a high performer, and in any other case, having 2.5 years of experience, I would be looking at a promotion in the next 6months-1year. However, the other L3 in the team got “redefines expectations” in his performance review.

We have same years of experience. He is a better engineer than me. He manages projects better than me, his output delivery is faster than me, he’s really good at writing technical docs as well as communicating stuff to the important stakeholders. There is no debate as to who is the better software engineer in team.

My question is, how much having him in the team affects the speed of growth from my career ? I am completing 3 years of experience soon and want to get promoted to L4. However I don’t see any situation where I am promoted before him, and I worry that this means delay of my promotion considering he'd be promoted before me and we already have many L4s in the team.

Am I overthinking this? I just want to know if switching companies or teams would be more beneficial for me than waiting in this team. Should I discuss about this with my manager ? While he is very focussed on making sure that the teams does well, I don't get the feeling from him that he cares too much about my professional growth.

762 Views
23 Likes
2 Comments
2 months ago

Should I leave my startup after 3 years for big tech?

Anonymous User at Taro Community profile pic
Anonymous User at Taro Community

I’m considering leaving a startup because of 2 things I’ve seen on Taro:

  1. faang+ as a long term investment in your career
  2. .

2019 Goal of Joining a Startup

  • Learn a lot about how to be a good software engineer

  • Be an early employee at a startup that makes it big

  • Quickly become an Engineering Manager because I like working with people, helping others

2023 Thoughts on Staying as an Eng Manager or Joining Big Tech

  • Dream of being an EM, is happening on small start up scale with a growing number of reports who like my management so far

  • The dream is to be early at a unicorn and that is close, but

    • The new standard should be 10B not 1B

    • Doing this with a first job is not necessary and high risk

  • In 2-4 years I’d likely still be a engineering manager from a no-name startup

  • L5+ engineer in big tech may fit well with my personality right away based on Taro, where I love collaboration, helping people, product and technical challenges

    • I like not just spending 80% of my time heads down coding and that may be possible and expected right away in big tech, no need to be a manager
  • Getting a 2 FAANG+ badges on my resume over the next 4 years would be more way more worth it than even a million dollar payout from a startup

    • Could have many doors opened for high level roles at startups OR faang depending on what I feel like at the time

    • Big tech stock offer may also easily be worth 1M in 4 years

Priorities 2019

  • Supportiveness of team

  • Growth opportunities

  • Company prestige

  • Maximum outcome (Risk)

  • Compensation

  • Company ethics

  • Product space

  • Technical space

  • Work-life balance

  • Level/title

  • Benefits

  • Location

  • Stability

  • Remote work


Priorities 2023

  • Supportiveness of team +0

  • Work-life balance +7

  • Compensation +2

  • Company prestige -1

  • Growth opportunities -3

  • Stability +7

  • Company ethics -2

  • Remote work +6

  • Level/title +1

  • Benefits +1

  • Location +1

  • Product space -5

  • Technical space -5

  • Maximum outcome (Risk) -10

Taro priorities video is

Startup Stats

  • 150 people, 25 engineers (doubled from a year ago)

  • Fall 2021 had 50% investment at 250M valuation

  • Dec 2022 450M valuation

  • Revenue has since doubled in last year to 125M

  • Profitable per years with 20% gross margin

  • Growing industry

  • Not venture backed, so not expecting 20x growth

  • Estimated in 2-4 years to sell for 1-2B

How to evaluate a startup video

Current job stats

  • Team lead for a year after 2.5 years as Software Engineer

  • 0.1% equity, 100k cash

  • 18th employee, 4th engineer

  • Dream of being an early employee at a unicorn, seems close

  • Would lose all stock if I leave before acquisition/ipo

  • Biggest point for discussion: ***2-4 years of being manager at a small startup may not qualify me to be an EM in big tech***


FAANG+ Offer

  • L4 equivalent

  • 190k cash, 350k stock over 4 years, 60k sign on bonus

  • Work life balance is supposed to be great

  • Great food, big tech lifestyle that I’ve always heard/dreamed about

  • Would work to be promoted to L5 in 1-2 years, then manager a year after that.

  • Being a new person at a fresh company sounds very exciting now, I know the business fully and the tech stack of the current place to the point where many things Ive see before and feel stale/boring


Questions

  1. Based on my write up about values, priorities, liking collaboration, would I like being an IC L4 coming from being a manager where I have solid tech skills but strong soft skills that I enjoy using.

  2. If I stay at the start up would I be able to get a big tech EM offer with 3-4 years of management experience at the start up? Note this question shows what I’m learning now as a manager.

  3. Should I down level myself from L5 to L4 if I think I could get the offer at L5 but am not sure about the certainty of success? (Question asked separately )

177 Views
3 Likes
5 Comments
3 months ago

How to prioritize Growth vs. Technical Learning?

Mid-Level Software Engineer at Citrix profile pic
Mid-Level Software Engineer at Citrix

I am currently on a team where I am assigned to work on a different area of the product(s) in each quarter as per the priorities of the leadership for that quarter. This has resulted in me gaining a good full-stack overview but not much depth on any specific components/technologies. I've been on this team for around 18 months right out of college but 80% of the technical work I've delivered till now has just been pattern-matching based on the existing code and infrastructure, although the outcomes have been impactful for the business. I feel like I'm not learning anything technically significant beyond company/product-specific knowledge which are not transferable to other companies. When I check out job postings from other companies for my level of experience, there always seems to be a focus on having expertise in some technology, which I can't confidently claim. This brings me to the following questions:

1. Should I stay at my current company? My career growth prospects seem great here as I have a very good reputation in my team and sibling teams, and have gotten very good feedback and visibility from managers and seniors. I also work as the lead developer for a legacy product which is not that robust and has hard-to-reproduce customer bugs, but the leadership has taken a renewed interest in adding new features to it, resulting in more potential scope for me. The main downside is low technical-learning as mentioned above, and I've heard this same remark being mentioned by senior engineers who have joined from other companies as well.

2. If I decide to switch companies, how do I bridge the lack of technical expertise that's expected for my level? When a recruiter views my resume, the technologies that I've used at work and as part of side-projects are all over the place, without a clear specialization. Although I'm confident that I can pick up these stacks without trouble on the job if needed, I feel underconfident in them in an interview setting.

1.2K Views
4 Likes
3 Comments
3 months ago

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?

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

Second switch in a short time for promotion ?

Entry-Level Software Engineer [L3] at Snap profile pic
Entry-Level Software Engineer [L3] at Snap

Apologies for the long post.

Before Snap, I was working as an Entry Level Software Engineer in a company that had just IPO'd. The growth opportunity was amazing, and I was learning a lot, but I wanted to work for Big Tech for better compensation.

I worked in that company for 2 years after my graduation. And then I switched to Snap Inc as an L3 engineer. At my previous company, I was up for promotion in a few months, and I probably made the bad (in hindsight) decision to switch at that time instead of waiting for a few months, getting promoted and then trying for L4 at Snap (I don't know if Snap would still have offered L4)

Now I am almost completing 6 months at Snap (so total 2.5 years of experience) and I talked about promo with my manager. And he told me that he isnt putting me up for promotion in the next cycle (in 6 months) as I need more than >1 year experience (around 1.5 years) in the company for promotion. So this means the realistic cycle for which he would consider me would be a year from now (at that point I'd be 3.5 years work experience). Which to me feels way too late. For some context, I am a high performer with "exceeds expectations" feedback from my manager, so the only thing stopping me from getting promoted is my tenure in the company (acc to my manager)

My question is, should I wait for another year or should I start looking outward and considering I am 2.5 years right now (and 3 years by the time I get an offer) I should be able to get L4 in a Big Tech (I think?) I am not super certain about the future of the company as well so I will most probably be switching even after promotion.

All my college friends are L4's and SDE2's so I feel like I am behind in my career.

90 Views
2 Likes
2 Comments
6 months ago

How do I turn SWE roles behaviors/descriptions into concrete actions in a startup environment?

Entry-Level Software Engineer at Series B Startup profile pic
Entry-Level Software Engineer at Series B Startup

Question: "For being promoted from SWE I to SWE II, how do I take the behaviors my company has associated with each role (below) and make that more concrete for a growth plan, taking into account the changing & flexible timelines startups have?"

For context, I already have weekly one-on-ones with my manager (who is new at being a manager & is also my mentor), and a growth plan (that I created with him) that roughly outlines (meets most expectations, meets expectations and exceeds expectations for my role). Additionally, keep in mind I work at a startup w/ <30 people so highly specific concrete goals set on a particular date can change in 2-3 weeks as priorities change. Also, my company has defined a series of behaviors as to what each SWE level should be able to accomplish. Here it is.

Software Engineer I (<1 year - 2 years)

  • Technical Skill
    • Broad knowledge of CS concepts
    • Focus on growing as an engineer, learning existing tools, resources, and processes
  • Getting Stuff Done
    • Develops their productivity skills by learning source control, editors, the build system and other tools as well as testing best practices.
    • Capable of taking well-defined sub-tasks and completing these tasks
  • Impact
    • Developing knowledge of a single component of our architecture
  • Communication & Leadership
    • Effective in communicating status to the team
    • Exhibits company’s core values, focuses on understanding and living these values
    • Accepts feedback graciously and learns from everything they do

Software Engineer II (2-6Years+)

  • Technical Skill
    • Writes correct and clean code with guidance; consistently fellows stated best practices
    • Participates in technical design of features with guidance
    • Rarely makes the same mistake twice, begins to focus on attaining expertise in one or more areas(eg. embedded , testing, algorithm, support code, commlink).
    • Learns quickly and makes steady progress without the need for constant significant feedback from more senior engineers.
  • Getting Stuff Done
    • Makes steady progress on tasks; knows when to ask for help in order to get themselves unblocked.
    • Able to own small-to-medium features from technical design through completion.
    • Capable of prioritizing tasks; avoids getting caught up in unimportant details and endless “bikeshedding”.
  • Impact
    • Self-sufficient in at least one large area of the codebase with a high-level understanding of other components
    • Capable of providing on-call support for their area including systems that they are not familiar with.
  • Communication & Leadership
    • Gives timely, helpful feedback to peers and managers
    • Communicates assumptions and gets clarification on tasks up front to minimize the need for rework.
    • Solicits feedback from others and is eager to find ways to improve
    • Understands how their work fits into the larger project and identifies problems with requirements.
97 Views
1 Like
1 Comment
6 months ago