How to Use Your Job Description to Write a Better Self-Review

A self-review is much easier when you know what your company expects from you. Your job description, level guide, or performance rubric can give you that outline. Instead of staring at a blank page, you can match your real work to the skills your role calls for. This guide shows you how to find those skills, choose strong examples, write about gaps, and build a review that sounds like you—not like a copied job post. You can finish with less stress and fewer guesses.

Your job description is a ready-made outline

Most self-reviews ask some version of the same question: How well did you do the job? Your job description already lists what the job includes. A level guide or review rubric may go further and explain what good work looks like at your level.

Use those documents to decide what deserves space. If your Role expects customer judgment, planning, and leadership across teams, your review should show those three things. You do not need to list every task from the year.

This also helps with memory. It is easy to remember the last month and forget a quiet win from spring. The Role expectations give you a set of questions to search against.

Step 1: Find the five or six ideas that matter most

Do not copy every bullet from the job post. Group similar lines into simple ideas. “Lead the roadmap,” “set priorities,” and “make tradeoffs” may all fit under Planning and Judgment.

• Planning and judgment: choosing what the team should do and what it should stop doing.
• Results: improving a customer, team, product, or business outcome.
• Teamwork: helping people reach a decision and move together.
• Communication: making hard ideas clear to the right people.
• Craft: doing high-quality work in your field.
• Growth: taking on wider or harder work over time.

Your list will depend on the Role. An engineer may use system quality, ownership, teamwork, and mentoring. A salesperson may use pipeline, customer trust, deal leadership, and account growth. Use the words your company uses when they are clear. Translate them when they are not.

Step 2: Turn each expectation into a simple question

A label such as “strategic leadership” can feel vague. Turn it into a question you can answer with real work. Ask, “When did I help the team choose a better direction?” or “When did my choice change a result beyond my own tasks?”

• Planning: What important choice did I help make?
• Results: What became better because of my work?
• Teamwork: When did I unblock people or bring teams together?
• Communication: When did my explanation help someone decide?
• Craft: What hard problem did I solve well?
• Growth: What can I handle now that I could not handle a year ago?

Questions are easier to search than business labels. They help you look through your calendar, documents, tickets, email, and career notes with a purpose.

Step 3: Match real work to each question

Choose two or three strong examples for each main expectation. A strong example has a date, a project, your part, and a result. It may also have a source such as a document, pull request, chart, email, or ticket.

• Planning: “Cut two low-use ideas from the June launch so the team could ship before the freeze.”
• Results: “Raised onboarding completion from 54% to 68% after the new flow launched.”
• Teamwork: “Brought Product, Design, and Engineering to one launch plan after two weeks of disagreement.”
• Communication: “Wrote the one-page decision note the VP used to approve the smaller launch.”
• Growth: “Led the launch across three teams instead of owning only one feature.”

Two clear examples are better than eight vague ones. Your manager should be able to understand each example without opening five links. The links are there to support the story, not replace it.

Step 4: Write one clear paragraph for each theme

Start with the result, then explain your choice and the people involved. End with what the work shows about your growth. Keep the paragraph focused on one main idea.

For example: “I kept the June onboarding launch on schedule and helped raise completion from 54% to 68%. When the team fell behind, I brought Product, Design, and Engineering together to choose the three changes customers needed most. We cut two lower-use ideas and shipped before the app-store freeze. This was a step forward in leading a full product decision, not only managing my own part of the roadmap.”

That paragraph works because it connects the company expectation to a real project. It gives the team credit, makes your own part clear, and shows why the work matters for your level.

A full example for a Senior Product Manager

Suppose the Role description says: “Own a product area, improve activation, lead work across teams, explain tradeoffs, and help newer product managers grow.” You might group that into four themes: product results, judgment, leadership, and mentoring.

Product results

“I raised onboarding completion from 54% to 68% during the second quarter. Customer interviews showed that the original flow asked for too much too early. I led a simpler version, worked with Analytics on the test, and moved the winning version to all new users.”

Judgment

“When the June launch fell behind, I cut two ideas that added build time but did little for first-time users. That choice let the team protect the three changes most likely to improve activation and ship before the app-store freeze.”

Leadership across teams

“I created one weekly decision note for Product, Design, Engineering, and Support. It replaced separate status threads and made risks visible earlier. The team reached key launch choices in days instead of carrying them across several meetings.”

Mentoring

“I helped Maya lead her first customer test from planning through readout. By the end of the quarter, she ran the next study on her own and shared the method with another product manager.”

Each section uses the Role description as a guide, but the words come from real projects. The review does not sound like a job post because it names what happened.

Write about gaps without tearing yourself down

A self-review does not need to pretend everything went perfectly. One honest growth area can make the rest of your review more believable. The key is to show that you understand the gap and have a next step.

Weak: “I need to get better at leadership.” Better: “I was slow to bring Support into the onboarding plan, which caused late changes to help content. For the next launch, I have added Support to the first planning review and will ask them to test the draft before design is final.”

• Name the gap in normal language.
• Explain the effect without making excuses.
• Choose one or two actions you can actually do.
• Add a date or upcoming project where you will practice.

What if the job description is old or vague?

Many job descriptions are written before the real work begins. If yours no longer fits, use it together with your team's current goals, your level guide, and the topics your manager brings up in one-on-ones.

Do not force a project under the wrong label. If the Role says “strategy” but your best work was rescuing a launch, look for the judgment inside that work. Maybe you chose the right scope, aligned three teams, and protected the key customer result. That may still show strong strategy in practice.

If you are unsure how your manager views the Role, ask before review season. A simple question works: “What are the three outcomes you most want someone at my level to own?” Their answer can improve both your review and your next quarter.

Keep different Roles and time periods separate

If you changed jobs or teams during the year, label each period. A Growth PM Role from January through June may have different goals from a Platform PM Role from July through December. Mixing them can make good work look unfocused.

Give each Role its own expectations and examples. You can still tell one growth story at the end. For example, you may show how customer testing in the first Role helped you make better platform choices in the second.

How Bloomly uses Role context

In Bloomly, you can add a job description, performance guide, or Role expectations to the right Role. Bloomly can use that background with your entries and saved work when it helps draft reports or answer questions in BloomBar.

That saves you from pasting the same background into every prompt. It also helps keep your day job, startup, and side work from blending together. You should still check the source and edit the final words before sharing them.

What if you joined late or the result is not ready?

You may not have a full year of results. If you joined the team recently, show how you learned the work, built trust, and took on more responsibility. A good early example might be creating the first clear project plan, finding a hidden customer problem, or taking over a task without close help.

Some projects also need more time before the final number appears. Say what has happened so far and what you will check next. For example: “The new onboarding flow launched two weeks ago. Early completion is up six points, and I will review a full month of data before calling the result final.”

This keeps your review honest. It shows progress without pretending the story is finished. You can add the final result during your manager conversation or in the next check-in.

A short checklist before you submit

• Did you cover the few expectations that matter most?
• Does every section include a real project or result?
• Is your own part clear without taking all the credit?
• Can you support the numbers and claims?
• Did you include one honest growth area with a next step?
• Does the review sound like you rather than a copied job description?

Your job description should guide your review, not write it for you. Pull out the few expectations that matter most. Match each one with real work, a clear result, and a source you trust. Be honest about one or two areas you still want to grow. Once you build that map, the self-review stops feeling like a memory test. It becomes a clear story about the work you did and how you are growing in the Role.