How to Write a Self-Evaluation (with Examples by Role)
A self-evaluation is your chance to tell your manager what you achieved, what you do well and what you are working on, in your own words, before they write theirs. Most people either undersell themselves or write vague praise nobody believes. The fix is simple: concrete examples, honest development points and goals someone could actually check. Below is a structure that works, examples you can adapt and a free tool that drafts yours from your own answers.
What a good self-evaluation includes
- Two or three results from this period, with numbers or a before-and-after where you have them.
- Your strengths, each backed by one specific example, not a list of adjectives.
- One or two areas you are developing, with what you are already doing about them.
- Goals for the next period that are specific enough to check: what, by when, and how you will know.
- A calm, factual tone. Confident about results, honest about gaps, no exaggeration.
A simple structure
- Opening (2–3 sentences): what you focused on and your main result.
- Key achievements: short bullets, each with a number or a concrete outcome.
- Strengths: a heading and two sentences each, with an example.
- Areas I'm developing: what you noticed and what you are changing.
- Goals for next period: two or three, each measurable.
Self-evaluation examples by role
Team manager
This year I focused on getting the team through the move to the new support platform without hurting response times. Average first response stayed under four hours throughout the migration. Strengths: I make clear decisions when information is incomplete; during the migration I set a fallback plan in the first week, which we used twice. I explain priorities so the team can act without checking back with me. Developing: I tend to avoid difficult conversations. Since September I have held a monthly one-to-one with each person that includes one honest piece of feedback in both directions. Goals: by June, run a short 360 with my team and agree two changes from it; delegate the weekly report to a team member by March.
Individual contributor (software engineer)
I focused on reliability this period. I led the fix for the checkout timeouts, which cut failed payments from 2.1% to 0.4%. Strengths: I find the root cause rather than patching symptoms; for the timeouts I traced the problem to a connection limit, not the code everyone suspected. My work rarely needs rework after review. Developing: my technical explanations can be too detailed for non-engineers. I now start design reviews with a one-sentence summary and the decision I need. Goals: write the on-call runbook for the payments service by April; present one technical topic to the product team each quarter.
Sales or customer-facing role
I reached 112% of my annual target and renewed all five of my largest accounts. Strengths: I build trusting relationships; two clients introduced me to other departments, which became new deals. I follow up within a day, and clients mention it. Developing: I have relied on a few large accounts. Since October I spend Friday mornings on prospecting new mid-size companies. Goals: open eight new mid-size accounts by the end of Q2; ask three clients a year for a structured feedback call.
New in role or first-time manager
This was my first year leading a team of five. My priority was keeping delivery steady while I learned the role, and we met every release date. Strengths: I listen before deciding and team members bring problems to me early. I lead by example on quality. Developing: I still do too much of the hands-on work myself. I now plan each sprint with one task I would normally take that someone else owns instead. Goals: complete a management fundamentals course by May; hand over the release process to a team member by September.
Phrases to avoid and what to write instead
- Instead of "I am a hard worker", name what the work produced: "I closed 40 more tickets than last year."
- Instead of "I always go above and beyond", give one example of when you did.
- Instead of "I have no weaknesses", name one real area and what you are doing about it.
- Instead of "I will improve communication", write a goal someone could check: "I will send a weekly status note to stakeholders from March."
- Avoid blaming others or circumstances. Say what you learned and what you will do differently.
Write yours from your own answers
AI360Feedback drafts a self-evaluation from your own self-assessment. You answer 20 short questions about how you work (about 5 minutes, no account), get an instant self-report, then click "Write my self-evaluation" and, if you like, add your main achievements. The draft follows the structure above and uses only what you told us: where an example is needed and you have not given one, it leaves a note for you to fill in instead of inventing it. You edit it and paste it into your company's form. It is free, in English, French, German and Spanish.
Before your review, you can also invite 3–6 colleagues to answer anonymously and see where their view differs from yours. That is often the most useful thing to bring to the conversation.
Frequently asked questions
How long should a self-evaluation be?
Usually 300 to 600 words, or whatever your company's form allows. Short, specific sections with examples are read; long lists of adjectives are skimmed.
Should I mention weaknesses in my self-evaluation?
Yes, one or two, framed as areas you are developing with what you are already doing. It shows self-awareness, and your manager will probably raise them anyway.
Can AI write my self-evaluation?
It can draft one, but generic tools produce generic text. The AI360Feedback writer builds the draft from your own ratings, comments and achievements, never invents results, and marks where you should add a real example. Always edit the draft so it sounds like you.
Write your self-evaluation from your own answers
Answer a short self-assessment, get your free self-report, then turn it into a draft self-evaluation for your review. No account needed.
Start my free self-assessment