Sign Performance Review Self-Assessment Template Made Easy

Sign performance review self assessment template

hey this is gargay with the pragmatic engineer we'll walk through in creating a self review for your performance review its sections and share a template in the end that you can use here's how it'll look like you probably don't need to print your own version so before we start why do you need to write a self performance review especially if it's not required at your company well i'm an engineering manager and i really try to do fair performance use for engineers on my team so for every person on team i go through code documents my notes a bunch of stuff and i still missed a lot of things either because people forgot to tell me what they did or i just forgot now anyone who sent me their self review i always read it while i was doing their performance review a self review can only help you now you might be asking i have a manager who's not so great why should i bother doing a self review here's the thing even if they're not going to read that self review you're going to get ammunition for your performance review conversation when you go into that conversation you're gonna have all these facts in your head in fact if you feel you're not getting a fair review and i and you can't convince your manager on the spot you can have a meeting with them and bring this review with you to show the facts so here's a structure of the review i recommend with four sections for the first section start with expectations and goals for the period now you might think why not just start with my achievements by starting with your understanding of the expectations you're setting a baseline if your company has expectations for this level or you've had expectations with your manager mention this if you don't have these expectations or you didn't agree on goals with your manager write down what you thought the goals were now some advice if you didn't set any goals and there's no clear expectations of your role this section is even more important and if this is the case after the performance review you probably should sit down with your manager and get goals and expectations for the next period it's only going to help you in this example review this person listed the baseline expectations shipping a large project keeping the quality high and goals they agreed together with their manager next list your accomplishments list out your main results and your larger work efforts try to do this in priority order use numbers where you can to make things more specific and to add more context now numbers could be a bunch of different things they could be related to the code they could be related to people or related to business impact the point of these numbers is to quantify your work not just by its effort but also by the results which is something your manager will care about now if you have a work log document you can link it to the bottom there's a link to an example work log at the bottom of this video if you started to build this work log beforehand your performance review will just be so much easier to write you can see how this example self-review mentions specifics numbers on the business impact of the project links to complex pull requests and rfcs they even collected stats on their code contribution now don't get me wrong i'm not saying you need to keep track of the number of pull requests or how many code reviews you did and you need to add it on your self review but the more specifics you have on your impact the better in this example review it's not just about the number of pull requests but the business impact as well if you specify the business impact you can use it not just on your performance review but also in your resume later now at this point most people will be happy with dell soft review they have expectations set accomplishment lists and they would just call it a day now i suggest adding one more section where you can list the qualities of impact of your work these are things that might have not had huge business impact but they show the small but important pieces of work things like teamwork collaboration and helping others list examples of you helping people and this is also a great place to list thanks that you've gotten from others in emails or chat messages you can even quote those now this section is important because your manager probably doesn't know half of the positive interaction that you've had with other people show it to them in this example review you can see this person listed specific examples of code reviews examples where they helped alex and how they onboarded sam they talk about being the point of contact for stakeholders and another example of help for the final part i recommend reflecting on levels and competencies assuming your company has them your manager will have to end with some kind of rating against expectations or competencies get ahead of this and make their job easier while also giving indication of what you think your rating should be now if you have good trust with your manager you could also add self ratings of what you think if you're meeting or are above expectations if you have less of this you could just list areas where you've really focused on either way be sure to list specifics that reflect on these expectations for this review we assume that there are six competencies at the company now even if you don't have competencies specified you can still do an overall assessment and write down how you feel about your progress at your level towards the next level this is a good indication for your manager this person then reflects on each of the competencies note how they mention specific work they did now they don't do a self-assessment rating but they are clear on what areas they've really focused on this period it was designed in architecture and the results and impact areas you can find links to example documents and templates under the video be sure to check out my longer article on how to write good performance reviews which is also linked under the video if you like this video subscribe to my channel for more content on software engineering and engineering management thanks