Profile picture

Performance Review Q&A and Videos

About Performance Review

This is an absolutely vital process for any employee in tech to understand, especially in a world of stack-ranking and layoffs.

Wary of current situation in terms of layoffs, need some advice wrt international relocation

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

I have been doing good at my current company, been here for 3+ years working initially as an Entry Level, then promoted after an year to a MidLevel Software Engineer. I have been receiving "Exceeds Expectations i.e. 4/5" rating since the beginning and "Superb i.e. 5/5" rating once.

I applied for international relocation to Singapore back in July. The manager and skip mentioned that while cost cutting is going on, they are making an exception for me and it should be processed completely by initial weeks of January 2023. In times of layoffs, and especially with my company's stocks not doing that good, I am afraid if it could lead to getting laid off. This is causing me a bit of anxiety.

Although it is being mentioned by leadership that no layoffs are happening, we are seeing projects getting cut off, rigorous re-orgs happening, and entire focus of the organisation is on cost saving, which I feel is great especially in current times.

I started the conversations for relocation when times were going good in terms of offers being posted in the market. The teams were thriving as well in terms of work. But by the time entire process got over, it seems the situations have changed. What should I do?

To add on, another thing I did sometime back was to share with my manager on how I am performing several roles of the next level and how it can be used to further the cause of promotion in the upcoming performance reviews. I tried to break down the career ladder doc into key umbrellas of behaviours needed, and assigned the initiatives I delivered under those. Now afraid if this was another way I shot myself in the foot by asking for more in times of cost-saving and probably being conservative. Please assist with your advice.

Show more
111 Views
2 Comments

Worried about Q1 2023 performance cycle

Mid-Level Software Engineer [SDE 2] at Amazon profile pic
Mid-Level Software Engineer [SDE 2] at Amazon

Since Dec 2021 to Aug 2022, My managers changed 4 times after and I got promoted from sde1 to 2. Due to multiple projects and managers, I could not take ownership as I was still in ramp up phase but manager was expecting more at the SDE2 level, pointing issues, demotivating. So I took internal transfer to a different team. I am in this new team for 3 months. 1 month - I took to even understand the basics. Manager left and new manager joined. I had to go on vacation for 15 days. I don't have metrics to show that I am performing at the SDE2 level because

  1. I didn't get design projects (design phase has already been completed by the time I joined this team).
  2. No OPS, this is a new product. There are no operational tasks. Working on beta launch.
  3. I am the last person who joined this team. I don't have anyone to become mentor since I have limited knowledge on this new team and work
  4. Have not taken interviews due to hiring freeze

Worried about Q1 performance cycle in 2023. 2022 was difficult for me to show any impact. Is there anything I can do now to not get low rating in Q1?

At this point, I am no more interested in work and just want to leave due to lack of mentorship. I have a buddy who answers questions if I ask in this team but I don't have anyone to mentor me to guide me to see what kind of projects I can work, coming up with the initiatives. I feel stuck. There are no hirings happening outside and inside the company. What can I do to proceed further?

Show more
137 Views
2 Comments

Per last performance review, how can I best demonstrate that I've improved since then to my manager?

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

I've gotten feedback from a mid performance review and my manager wants to see improvements in various areas. It includes improving my debugging skills by paying closer attention to pertinent details (and not getting distracted) for example.

Since then, I've become much more conscious and aware of the errors that I run into and much more deliberate in my debugging approach. This has resulted in me being able to diagnose problems much more accurately, and has also lended to me problem-solving much more effectively as well.

The problem is I'm not sure how to best demonstrate (or prove) that value improvement to my manager. Unlike PRs (which are often more visible in the value it demonstrates) -- you see what you get, my debugging skills/tactics are not readily obvious to the outside party unless they're observing my day-to-day activity. I can say that I've gotten better but if I have nothing to back that up with aren't they just words without weight? Who's to say that I'm even right in my own assessment without social feedback? I could be dunning kruger for all I know.

Is it enough for me to simply document those performance improvements and share (or talk about) them with my manager?

Note: My ultimate goal is to get promoted so I'm trying to (1) show that I've taken their feedback seriously and (2) demonstrate actual improvement since my last performance review.

Let me know if I'm thinking about this the right way or if am I overcomplicating it. Thanks!

Show more
104 Views
2 Comments

Measurement of impact for MLE?

Senior Software Engineer [E5] at Meta profile pic
Senior Software Engineer [E5] at Meta

I joined my team in June this year right after bootcamp. When I joined this team, we set the goals for the half, and then got reorg-ed to a different domain (think ML for ads vs ML for recommendations).

Our models had only shown limited success in the previous domain before the reorg, we spent around 2 months (July and August) just building new versions of these models for the new domain.

It's October already, the model hasn't shown any significant success in any of our projects with XFN. We are getting closer and closer as we understand the problems better. However with code freeze in November, December - it is unlikely it will reach production or even online experiments by then.

Does that mean I would have "no impact" at my first PSC? This would be the case for all of my teammates which seems bonkers.

I thought about writing a long note with all of the progress we've made in understanding the problem (which will result in a model that's cheaper than the current one and easier to understand), what are some results we have seen already, and hypothesis on where to go next.

Still to be honest I'm scared the results I got won't be good enough to get to production by PSC-time, and thus I'll be marked as no impact. In retrospective I should have studied the problem more when I joined but I was so new to Meta.

How can I mitigate this? Looking for a side-project now I can fully own (as E5, I don't think attaching myself to a teammate's project is good enough) is unlikely to get any results with the current model we have.

Show more
134 Views
1 Comment

Learn About Performance Review

A performance review is used by a company gauge an employee’s work performance and contributions during a certain period of time. In the software engineering world, the reviews provide a comprehensive overview of an engineer’s accomplishments and areas of improvement over a specific period.
Performance reviews serve as a platform for acknowledging an engineer’s contributions and achievements. Positive feedback during a performance review can lead to recognition, promotion, and new growth opportunities within a company.
Performance reviews also highlight areas where performance can be improved. Constructive feedback helps engineers identify their strengths and weaknesses, which will pave the way for professional and career growth.
Performance reviews can contribute to fostering a positive team culture. By recognizing and addressing individual contributions, team members can understand what steps they need to take to be rewarded because they have a model to follow.
To maximize performance reviews, software engineers should actively prepare by reflecting on their achievements and goals accomplished during the performance review period. This preparation ensures a comprehensive discussion that you can have with your manager.
You should have also been receiving ongoing feedback throughout the entire performance review cycle from your manager and peers. This creates a continuous improvement cycle and ensures there are no surprises during the formal review.
You should effectively communicate any achievements during this time, which can include improvements made to any software engineering processes or to team culture.
Performance reviews are pivotal in your software engineer carer because they provide opportunities for recognition, growth, and professional development. By addressing feedback throughout the year, you will be able to navigate the performance review cycle with confidence.
Show more