Write your self review in two minutes.
Paste rough notes about what you worked on. Get a clear, first person self review grouped by theme, ready for your review form.
- Free, no sign up
- Never makes up numbers
- Nothing you paste is saved
Your self review appears here, grouped by theme and ready to paste into your review form.
- 1Paste rough notesBullet points, half sentences, ticket titles. Whatever you have.
- 2Get it grouped by themeA short opening, then clear points under two to four themes.
- 3Fill the placeholdersAdd the numbers it asks for, then paste it into your review form.
How to write a self review that gets noticed.
Your manager reads a stack of these, often in one sitting. These six habits make yours the one that is easy to say yes to.
- 01
Lead with what changed
Managers remember outcomes, not tasks. Start each point with the result, then say what you did to get there.
Worked on the webhook retry logic.
Ended duplicate charges by reworking the webhook retry path; p95 went from 1.4s to 860ms.
- 02
Use the numbers you have
A latency drop, a count of users, hours saved a week. If you don’t have the exact number, write where to find it and fill it in before you submit. Never guess.
Made the build a lot faster.
Cut CI from 28 minutes to 9 for every pull request, across [number] engineers.
- 03
Include the work nobody saw
Mentoring, interviews, incident calls and the decisions you pushed for rarely show up in GitHub, so they are the first thing people forget.
Helped onboard new people.
Onboarded 2 new joiners; both shipped to production in their second week.
- 04
Group by theme, not by month
Two to four themes read better than a long timeline: reliability, the mobile launch, growing the team. Each theme gets a few clear points.
- 05
Write it as you would say it
Plain first person sentences. If a sentence sounds odd out loud, rewrite it.
Spearheaded and leveraged synergies to drive cross functional alignment.
I got web and mobile to agree on one refunds API, which unblocked the mobile launch.
- 06
Keep it to about a page
Cut anything that doesn’t show an outcome, a skill or how you helped others. A page that is all signal beats three pages that are mostly noise.
Questions, answered.
Is the self review writer really free?
Yes. You get 3 free tries a day with no account. If you want Selfly to collect your work and keep your review ready all year, that is free during early access too.
Will the AI make up numbers or achievements?
No. It only uses what you write. Where a number would help but you didn’t give one, it leaves a placeholder in [brackets] for you to fill in. If a draft states a number you never wrote, it is thrown away.
Do you store what I paste?
Your notes go to our AI provider, Groq, only to write the draft, and Selfly does not save them. We only keep a short lived count of tries, tied to a one way hash, to enforce the daily limit.
How long should a self review be?
Most companies expect half a page to a page. Aim for two to four themes with three to five bullets each, plus a short opening.
What should I write if I can’t remember what I did?
Scroll your merged pull requests, closed tickets, calendar and sent messages for the period. Or keep a weekly record so you never have to rebuild it. That is exactly what Selfly does for you.
Everything for review season.
- Impact statement builderAI writerTurn “I made the API faster” into a statement that shows what changed. Plus 48 examples.Open tool
- Brag document builderBuilderAdd your wins and watch a clean brag document build itself. Copy it or download it.Open tool
- Self review phrasesLibrary64 ready phrases for impact, ownership, mentoring and growth. Click to copy.Open tool
Never start your self review from a blank page.
Selfly collects your pull requests and reviews every week. You confirm them in about 90 seconds, and your summary is ready when review season comes.
Free during early access · Private by default · Never reads your code