Self-Evaluation Examples You Can Adapt, by Skill and by Role

A strong self-evaluation example does three things in two or three sentences: it says what you did, what changed because of it, and what a colleague or a record could confirm. "I am a great communicator" does none of them. "I started a written Friday update for the billing migration, and finance stopped asking for status in our weekly call" does all three. Below are self-evaluation examples for work, first by skill and then by role, each as a weak version and a stronger rewrite you can adapt.

Every example here was written for this article, and its projects, numbers and people are invented: swap in your own figures, or drop any you cannot back up. For the full process, start with how to write a self-evaluation. If you are filling in a formal review form section by section, see the self-evaluation examples for a performance review.

What makes a self-evaluation example strong

Weak and strong self-evaluations usually differ in one thing: evidence. Gallup reported in 2017 that only 26% of employees strongly agreed that the performance reviews they receive are accurate (Gallup, 2017). Your self-evaluation is the one part of that process you control, and specifics are how you make it believable.

A 2022 study comparing 435 employee self-ratings with 448 managerial ratings found that "employees tend to give themselves more lenient ratings" (van Lill and van der Merwe, 2022). Its authors suggested it might be prudent to give manager ratings more weight, or ignore self-ratings, in high-stakes decisions. The sample is South African, so take the size of the gap loosely and let checkable results do the persuading.

A strong example usually follows one pattern:

1. What you did, in one concrete sentence, with the project or customer named.
2. What changed, ideally measured, otherwise described as something a colleague would notice.
3. What would confirm it: a ticket, a report, a dashboard or a colleague who saw it. Name it when it is not obvious.

When the result was mixed, add a fourth line: what you learned and what you will do differently.

Self-evaluation examples by skill

These cover competencies that appear on many review forms. The table sums up each pair; the full examples follow.

Communication

• Weak: "I am a strong communicator and always keep people informed."
• Strong: "I started a written Friday update for the billing migration in March. Finance stopped asking for status in our weekly call, and that meeting went from 45 minutes to 20 (see the March and April meeting notes)."

Collaboration and teamwork

• Weak: "I'm a team player who is always happy to help."
• Strong: "I paired with our two new support hires for their first month and wrote the refund checklist they still use. Their ticket history shows both handling tickets on their own by week three."

Problem-solving

• Weak: "I solve problems quickly and think outside the box."
• Strong: "When checkout errors spiked after the June release, I traced them to a currency-rounding bug, shipped a fix the same day and added a regression test so a repeat would fail the build."

Time management and reliability

• Weak: "I always meet my deadlines."
• Strong: "I delivered 11 of my 12 planned items for the year on time. The export redesign slipped two weeks because I underestimated the data cleanup, so I now add a buffer week to anything that touches legacy data."

Initiative

• Weak: "I take initiative and go above and beyond."
• Strong: "Nobody owned our onboarding docs, so in Q2 I audited them, deleted 14 outdated pages and set up a quarterly review. New-hire questions in the help channel went from 30 in Q1 to 12 in Q3."

Learning and growth

• Weak: "I am always eager to learn new skills."
• Strong: "I took over our sales dashboards this year without knowing SQL. I finished the internal SQL course in February, and I handled the last three reporting requests from sales without the data team."

Leadership, including without a title

• Weak: "I show leadership qualities."
• Strong: "I ran the review after the April outage, kept it blameless and turned it into five follow-up tickets with owners, all linked from the incident doc. Four are done; the fifth is planned for next quarter."

Self-evaluation examples by role

These examples cover roles in software and SaaS teams, with one strength and one area to improve each; the figures are invented, as throughout. Other jobs follow the same pattern.

Software engineer

• Weak: "I wrote a lot of code and fixed many bugs this year."
• Strong: "I led the move of our search service to the new queue. It shipped in September with no downtime, and p95 search latency fell from 900 ms to 350 ms on the service dashboard. I also reviewed about 120 pull requests, most of them for the two engineers who joined in spring."
• To improve: "I said yes to too many review requests in Q3, and my own work slipped. Next half I will keep two fixed review slots a day instead of reviewing on demand."

Product manager

• Weak: "I managed the roadmap and worked closely with stakeholders."
• Strong: "After interviewing 14 customers, I cut the Q2 roadmap from nine items to five, and we shipped all five. Team invites, the most requested of them, raised the share of trials that add a second user from 18% to 27%."
• To improve: "My specs reached design too late for them to explore options. From next quarter, design gets the problem statement two weeks before planning."

Designer

• Weak: "I created designs for many new features."
• Strong: "I redesigned onboarding and tested it with eight users before handoff. Completion of the setup steps went from 54% to 71% in the first month after launch."
• To improve: "I often showed polished screens when a rough sketch would have caught problems sooner. I will bring low-fidelity drafts to the first review."

Sales

• Weak: "I worked hard and hit my targets."
• Strong: "I closed $410,000 against a $360,000 target, 114% of quota, per the year-end CRM report. Two thirds came from the mid-market segment I asked to take on in January, where my average sales cycle was 38 days against a team average of 52."
• To improve: "My pipeline ran thin early in each quarter because I only prospected after closing. I now block two hours for prospecting every Tuesday and Thursday."

Customer support

• Weak: "I provide excellent customer service."
• Strong: "I handled about 2,100 tickets this year with a 94% satisfaction score. I also wrote nine help articles for our most repeated questions; password-reset tickets fell by about a third after the password-reset article went live."
• To improve: "I hold on to billing tickets too long because I want to solve them myself. I will escalate any refund over $500 within the first hour."

People manager

• Weak: "I support my team and help them grow."
• Strong: "I hired two engineers and nobody left the team this year. I held weekly 1:1s with all six reports, and one moved into her first tech lead role in August. We delivered 85% of planned work in Q3, up from 70% in Q1."
• To improve: "I stayed too close to the code and became a review bottleneck in Q2. I have handed review ownership for two services to senior engineers."

Employee self-evaluation comments for strengths and areas to improve

Short comments suit forms with a free-text box per competency. A strength comment still needs its evidence:

• "I own our release checklist. Since I took it over in May, no release has needed a rollback."
• "Colleagues bring me the hardest customer escalations; I resolved 14 of them this year, all logged in the support tool."
• "I mentored our intern through her first project, which shipped in August and is still in use."
• "I hit every payroll deadline this year, including the two months we changed providers."
• "I learned our new BI tool in Q1 and have built the monthly board report in it since April."

A common trap in the improvement section is the disguised strength ("I care too much"). A useful comment names one pattern, its cost and a concrete change:

• "I take on too much myself before asking for help. Next quarter I will flag a blocker after one day instead of three."
• "My written updates are long and bury the decision. I will lead each update with the one thing I need from the reader."
• "I start large tasks late in the week and finish them in a rush. I will break them into daily pieces with a Monday kickoff."

A full self-evaluation sample

This self-evaluation sample is for a hypothetical marketing operations specialist, written as free text: three short paragraphs, three pieces of work, every claim checkable.

Highlights. I rebuilt our lead-routing rules in the CRM in March. According to the CRM routing report, leads now reach a salesperson in under an hour instead of the next day, and sales has not raised a routing issue since May. I also moved 18,000 contacts to the new email tool with no lost unsubscribes, and automated the weekly campaign report that used to take half of each Monday. What did not go well. The webinar series launched three weeks late because I waited for final slides before building the registration pages. For the next series I will build the pages from a draft agenda. Next year. I want to own campaign reporting end to end, and I would like support for an analytics course in Q1.

How to adapt an example from your own evidence

An example is only a shape; the content has to come from what you did, and that is hard to remember. Software engineer Julia Evans, writing about keeping a brag document, says she always ends up finding things "that I completely forgot I did" (Evans, 2019).

1. Pull the record first. Before choosing examples, collect what exists: closed tickets, merged pull requests, CRM reports, sent updates, your calendar, praise in chat. If you kept a weekly report or a brag document, start there.
2. Pick three to five pieces of work. Choose the ones with the clearest result, not the ones that took longest.
3. Choose an example by its shape. Find the pair closest to what you did and keep only its structure.
4. Replace every number with yours, or drop it. If you have no figure, describe the change a colleague would see ("finance stopped asking for status"). Never estimate a number to make a sentence sound stronger.
5. Check each sentence against the record. Could your manager confirm it? If not, cut it or add the evidence.
6. Add one miss and what you changed. One is enough.

If your examples come out as lists of duties rather than results, our work accomplishments examples show how to turn "responsible for X" into what X produced.

Where DoneThat fits: the evidence, collected as you go

Step one, rebuilding months of work from scattered tools, is the slow part. DoneThat keeps that record as you go. It reconstructs your workday from screen and app activity, without timers, and writes a daily summary of what you worked on. Screenshots are processed and immediately deleted, never stored. At review time you can export that history as CSV, or query it through the API or the MCP server from an AI assistant. It will not write the self-evaluation for you, but the evidence is already collected.

Frequently asked questions

What should I write in a self-evaluation?

Write three to five pieces of work with their results, one thing that did not go well and what you changed, and one or two goals for the next period. Use specific projects, numbers and outcomes instead of personality traits, and keep each point to two or three sentences.

How long should a self-evaluation be?

Aim for a page or less unless your form sets a length. In a review cycle your manager is likely reading the whole team's self-evaluations at once, so a few well-evidenced points beat a long list.

Sources

• Evans, J. (28 June 2019). Get your work recognized: write a brag document. Personal blog of a software engineer and writer.
• Wigert, B. and Mann, A. (25 September 2017). Give Performance Reviews That Actually Inspire Employees. Gallup Workplace.
• van Lill, X. and van der Merwe, G. (29 November 2022). Differences in self- and managerial-ratings on generic performance dimensions. SA Journal of Industrial Psychology, 48, a2045. 435 employee self-ratings and 448 manager ratings, South Africa.

Written by Don, DoneThat's AI coach (LinkedIn) - so this article is AI-written. Every statistic is cited next to the claim and linked in the Sources list; the example self-evaluations, their people and their numbers are invented for illustration. Published by DoneThat (Letss B.V., Amsterdam). More about DoneThat; corrections and questions go to support.