Videos and discussions from Taro to grow your tech career.
See relevant discussions involving LinkedIn engineers on Taro.
The name of the performance evaluation document at LinkedIn is called CPT (Career Progression Tracker). Software engineers are evaluated on the following 3 axes: execution, leadership, and craftsmanship.
In the past few years, LinkedIn is moving toward a metrics-oriented performance culture, similar to Meta, but without the generosity of large equity refresh grants 😠So it's important to maintain a document throughout the half of various accomplishments and metrics that came from your work.
This is the most important axis going from L3 [SWE] -> L4 [Senior SWE].
This reflects your core ability to deliver work on time and land impact.
For L2 and L3 engineers, mastering this axis for promotion largely revolves around the tactics in this guide: [Masterclass] How To Write Better Code Faster As A Software Engineer
This is the main axis evaluating growth past L4 [Senior SWE] levels (getting to staff, senior staff, and so on).
This is your ability to bring stakeholders and other teams together. The more people underneath your scope here, the better your rating in this axis.
If you're looking to ramp up your leadership skills, check out this in-depth explainer: "How to develop soft skills like leadership, stakeholder management, etc.?"
This is generally regarded as the least important performance axis at LinkedIn.
This axis covers the quality and elegance of your solutions. Here are some things that reflect well for craftsmanship:
The most basic aspect of this axis is code quality. Watch this video to understand what it takes to write clean code at a FAANG-level company: One Diff, One Thesis - What Every Code Review Should Be Like.
Performance feedback is collected entirely in Workday.
Your self-review is a crucial tool for your manager to fight for a good rating for you. Follow this advice to optimize it.
The self-review has prompts, but you don't have to use them. Most engineers will do a free-form response following the LEC format (leadership - execution - craftsmanship).
The length of your self-review is important. The specifics depend on the org, but managers are often required to condense self-reviews to 1500 characters. So it’s very important to be concise to make your manager's life easier, or provide them with a draft of what they could write.
The more senior you are, the more peer feedback you need.
3 - 5 pieces of peer feedback is a good range for most people. However, this can vary:
Watch this video to determine the optimal "bench" of peers for your packet: Assembling The Feedback "Avengers" For Your Promotion Case
You only see the feedback the manager writes. You don’t see feedback from your peers - The manager compresses it for you and gives you a high-level recap.
Every year, your compensation is increased across the following 3 axes:
LinkedIn is unique as it formally splits up "Infra" and "Apps". Engineers across the 2 types are paid different with infra engineers being paid ~10% more than apps.
For each level, LinkedIn has a TAC (Total Annual Compensation), which is a pay band that universally cuts across level and geography. LinkedIn uses this TAC to calculate compensation adjustments.
LinkedIn is now targeting to identify and remove the bottom 10% of engineers every cycle.
As long as you're getting "Achieves" (3) on all 3 axes, you should be safe from a PIP or performance-based firing. Don't fall below "Improvement Goals" (2) on any axis, and you should be okay.
The key to avoiding PIP is to stay in sync with your manager - Learn how to do that with this video.
Unlike most Big Tech companies, PIP was known to be quite doable at LinkedIn in the past and not a death sentence. This is probably less so the case in the current economy.
LinkedIn was known to be more relaxed before the layoff-era: