Writing a self evaluation is one of the few moments in a performance cycle where the employee controls the narrative. Done badly, it reads like a job application or an apology. Done well, it changes the entire conversation. This guide gives you concrete self evaluation examples organised by role and competency, with the exact phrasing choices that make the difference between a review that gets filed and one that actually influences what happens next.
The goal here is not inspiration. It is specificity. Every example below is built to answer the question reviewers are actually asking when they read your self evaluation: what did you do, what did it produce, and what are you doing about the gap?
What makes a self evaluation example worth using?
A good self evaluation example is one that a manager cannot write themselves. It contains evidence they did not observe, context they did not have, and a plan they had not considered. The formula is: action plus outcome plus reflection.
Most templates fall apart because they stop at action. "I supported my team during a difficult quarter." That tells a reviewer nothing useful. Compare it to: "When two senior engineers left in Q3, I rewrote the onboarding documentation and ran four knowledge-transfer sessions, reducing average ramp-up time for the two replacements from six weeks to four." The second sentence is a self evaluation. The first is noise.
The single most important structural rule is to pair every strength with evidence and every weakness with an active response. Strengths without evidence sound like self-promotion. Weaknesses without a plan sound like complaints. The combination of the two, written with precision, is what makes a self evaluation credible enough to influence a pay or promotion decision.
This structure also matters for the people reviewing them. HR teams processing dozens of evaluations simultaneously cannot chase context. They need the argument delivered on the page.
How do you write self evaluation examples for goals and targets?
Write this section by treating each goal as a mini case study: what was the target, what was the result, and what explains the gap or the surplus. A single honest paragraph per goal is enough.
Here is an example for a sales role:
"My target for Q4 was 12 new enterprise accounts. I closed 9. Two deals that were tracking to close slipped into Q1 after procurement cycles extended beyond the expected timeline at both organisations. The third shortfall came from a territory I was covering for a colleague on leave, where I had less established pipeline. To address the conversion rate issue, I have started using call recording review as a weekly habit and have already identified two recurring objections I was not handling consistently."
Notice what that example does. It names the number. It explains the shortfall without making excuses. It distinguishes between factors outside the employee's control and one that is genuinely developmental. And it ends with a concrete action plan already in motion.
For a project manager, the same structure applies to a different set of metrics:
"Three of my five projects this year delivered on time and within budget. One ran six weeks over schedule after a supplier dependency was flagged later than it should have been. I have since added a vendor risk check to the project kickoff template, which is now standard across the team. The fifth project was descoped by the client in month two, so timeline comparisons are not meaningful there."
The phrase "which is now standard across the team" is doing significant work here. It turns a personal lesson into an organisational contribution, which is exactly the signal that reviewers look for when assessing readiness for broader responsibility.
How do you write self evaluation examples for communication and collaboration?
This is where most self evaluations become vague. "I am a strong communicator" appears in roughly half of all self evaluations, and it convinces no one. The section needs to be written in terms of specific situations and observable behaviours.
For a mid-level marketing manager:
"This year I introduced a weekly written update for our three agency partners that replaced the standing Monday call. The agencies reported in our Q3 relationship review that response times improved because they had written briefs to work from rather than notes from a call. Internal stakeholders said the format gave them a shareable record they could pass to legal and finance without setting up additional briefings."
For a customer success manager:
"I handled escalations for two enterprise accounts in danger of leaving. In both cases, I brought the relevant product and engineering contacts into a joint call within 48 hours, rather than managing the client relationship in isolation. Both accounts renewed. The approach has since been documented as a case study in our renewal playbook."
For a software engineer who is less client-facing:
"I ran three internal tech talks this year on topics the team had identified as knowledge gaps in our quarterly retrospectives. Attendance averaged 14 people per session. I also reviewed 47 pull requests outside my immediate team, and I have made a point of leaving explanatory comments rather than just approval or rejection signals. Two junior engineers specifically mentioned this in their peer feedback."
The pattern across all three is the same: a behaviour, a mechanism, and a measurable or observable result. Employee sentiments gathered through peer feedback are legitimate evidence and worth citing explicitly, as the engineer example shows.
How do you write self evaluation examples for leadership and development of others?
Leadership self evaluations are tricky because the best leadership often looks invisible. The work was done by someone else. Your contribution was the conditions you created.
For a team lead:
"I managed four direct reports this year. All four completed at least one external learning course, which I funded from the discretionary training budget and scheduled around their project load rather than treating it as optional. One was promoted to senior level in November. I ran fortnightly one-to-ones with each of them, but I changed the format in June after asking them directly whether the sessions were useful. Two said they wanted more focus on career progression than on immediate task review, so I restructured the agenda."
For a department head:
"I inherited a team where recognition was inconsistent. Some people received visible praise regularly, others almost never. In January, I introduced a structured peer recognition slot in our fortnightly all-hands, with three to five specific callouts per meeting. By Q3, engagement scores on the recognition question in our pulse surveys had increased from 52% favourable to 71% favourable. I do not claim this is solely the result of that change, but the timing is consistent with the shift."
That last sentence matters. Intellectual honesty in a self evaluation builds more trust than overclaiming. A reviewer who trusts the writer's account of their weaknesses is also more likely to believe their account of their strengths.
For anyone managing a team through significant change, continuous feedback becomes a relevant example to draw on:
"When we restructured the team in March, I ran a weekly anonymous check-in for the first eight weeks using a single three-question format. It let me catch concerns before they became resentments. Three people raised workload concerns in week two that I would not have surfaced in a normal one-to-one. We adjusted resource allocation in response."
How do you write self evaluation examples for innovation and problem-solving?
Innovation claims are the second-most common source of hollow self evaluations. "I brought creative solutions to complex problems" says nothing. "I identified that our client onboarding was creating a three-day delay because two teams were duplicating a data entry step, built a shared spreadsheet to eliminate the duplication, and reduced average onboarding time from nine days to six" says something.
For a product manager:
"I proposed cutting one feature from the Q2 roadmap that had been scoped but not yet built, after reviewing usage data that showed a similar existing feature was used by fewer than 4% of active users. The decision freed up three sprint cycles that we redirected to a reliability issue that had been affecting 30% of our enterprise tier. The trade-off was uncomfortable at the time because the feature had executive sponsorship, but the reliability metrics at the end of Q2 justified it."
That example demonstrates something beyond problem-solving. It shows the employee navigating organisational dynamics honestly, which is a leadership signal even in an individual contributor role. Real time analytics provided the evidence. The courage to act on it is the competency being evaluated.
For a finance analyst:
"I noticed that our monthly close process involved four separate spreadsheet reconciliations that were essentially checking the same figure through different routes. I mapped the process, found the redundancy, and proposed consolidating into two reconciliations with a documented audit trail. Finance leadership approved the change. We reduced close time by approximately half a day per month, which over the year is roughly six days of analyst capacity returned to higher-value work."
How do you write self evaluation examples for areas of development?
This is the section most people write badly. Either they pick something so safe it is meaningless ("I sometimes take on too much because I care about quality") or they list a genuine weakness with no plan attached, which just makes the reviewer anxious.
The framework: name the gap clearly, give one real example of where it showed up, and describe the action plan with enough specificity that a reader can see you have thought about it.
For time management:
"My planning at the start of the year was too optimistic. I consistently underestimated how long stakeholder review cycles would take, which pushed three deliverables past their internal deadlines. I have started building buffer time into every project plan by default and flagging scope creep to my manager within the same week I see it, rather than trying to absorb it quietly. This is a work in progress, but my Q4 delivery record reflects the improvement."
For public speaking and presentation:
"I am less confident presenting to senior leadership than I am in smaller group settings. I avoided two opportunities to present to the board this year, which I regret. I have signed up for a presentation skills course in January and have asked my manager to put me forward for the next internal briefing opportunity, even if I am not the most obvious choice for it. I want the exposure more than I want to be comfortable."
That last sentence is the kind of honest, forward-leaning statement that turns a weakness into evidence of self-awareness and ambition. It is exactly what reviewers want to see.
For delegation:
"I held on to too much execution work in H1 and should have delegated more to my team earlier. The practical effect was that two team members were underutilised for the first half of the year, which I heard in their midyear feedback. In H2, I was more deliberate about assigning stretch tasks and following up with coaching rather than taking the work back when it was slower than I would have done it myself. Employee feedback from my team in Q4 was noticeably more positive on autonomy and development than it was in Q2."
What do self evaluations look like in a continuous feedback culture?
In organisations that use continuous feedback rather than annual reviews, the self evaluation looks different. It is less retrospective and more conversational. The evidence is closer to the surface because it has been accumulating in real time through regular check-ins, pulse surveys, and structured feedback requests.
The benefit is accuracy. Annual self evaluations rely on memory, which is systematically biased toward recent events. A self evaluation written in a continuous feedback environment can reference specific conversations, documented feedback, and tracked progress against action plans that were set and measured throughout the year.
A good example from this kind of environment:
"Over the four quarterly reviews this year, I worked on three specific development goals that my manager and I agreed in January: improving my written communication, building stronger relationships with the product team, and getting more consistent at hitting weekly project milestones. The continuous feedback I received from the product team in Q2 and Q3 showed clear progress on the relationship goal. My milestone hit rate went from 68% in Q1 to 89% in Q4, which I can track because we logged it. Written communication is still a work in progress, and I want to carry it forward into next year with a more structured approach."
That evaluation could only have been written by someone operating inside a properly designed performance management system. It is evidence-rich because the infrastructure made evidence collection easy. HR teams that invest in building that infrastructure get better self evaluations back, which means better review conversations, which means better outcomes for everyone.
Company culture shows up in self evaluations too, though rarely explicitly. The degree of honesty a person is willing to put into a development section is a direct measure of how psychologically safe they feel. In a workplace culture where admitting a gap is used against you, nobody writes honest self evaluations. In a culture where gaps are treated as development opportunities, people write the kind of evaluations that actually make performance management work.
Communication tools matter here as well. If the process for submitting a self evaluation is confusing, delayed, or disconnected from the rest of the review workflow, people rush it. The quality of the output reflects the quality of the system.
Frequently Asked Questions
What is a self evaluation in a performance review?
A self evaluation is a structured written reflection where an employee assesses their own performance against agreed goals, competencies, or behaviours. It is submitted before or during a review cycle and gives managers context they cannot observe directly, making performance conversations more balanced and productive.
How long should a self evaluation be?
Most self evaluations run between 300 and 600 words in total. Each competency or goal section should have two to four sentences: one stating what you did, one quantifying the impact if possible, and one or two sentences on what you would do differently or are working to improve.
What is the difference between a self evaluation and a self appraisal?
The terms are interchangeable in most organisations. Both describe the same process: an employee rating or narrating their own performance before a formal review. Some companies use "self appraisal" when a numeric rating is included and "self evaluation" when the format is purely written, but there is no universal standard.
How do you write a self evaluation without sounding arrogant or too self-critical?
Anchor every claim to evidence. Instead of "I am a strong communicator," write "I led six cross-functional project updates this quarter and received consistent feedback that the format was clear." Specificity replaces tone. For weaknesses, pair the gap with the action plan you are already running.
Can self evaluations improve employee engagement?
Yes, when the process is designed well. Research consistently shows that employees who feel heard and whose input shapes their performance conversations report higher engagement scores. Self evaluations are one of the most direct mechanisms for turning employee feedback into a two-way dialogue rather than a top-down verdict.
How often should employees complete a self evaluation?
Most organisations run self evaluations annually or twice yearly, aligned to formal review cycles. Teams that use continuous feedback and pulse surveys often add lighter quarterly check-ins, which reduce the pressure on any single self evaluation and produce more accurate, less retrospective reflections.
What should you never write in a self evaluation?
Avoid vague superlatives ("I always go above and beyond"), unverifiable claims ("I am the best at X"), and unqualified criticism of colleagues. Never leave a weakness section blank and never fabricate metrics. Reviewers notice both dishonesty and excessive modesty, and both undermine the credibility of the entire document.
How do managers use self evaluations in performance management?
Managers compare the employee's self evaluation with their own observations, 360 feedback, and output data. Significant gaps between self-perception and manager perception are often the most valuable signal in the conversation. HR teams use aggregated self evaluation data to spot patterns in development needs and to build targeted action plans.
Put Better Self Evaluations Inside a Better System
The examples in this guide are only as useful as the environment they land in. A thoughtful, honest self evaluation filed into a process nobody reads, with no structured follow-up and no connection to the employee's development goals, is wasted effort. The writing matters. So does the system that holds it.
Kodecrew is built around exactly that connection - linking employee feedback, pulse surveys, recognition, and continuous feedback into one place so that self evaluations feed into action plans rather than archives. Explore Kodecrew and see how the system can make every review conversation more honest, more useful, and more likely to actually change something.
