Your probationary review: 5 questions to pre-answer

Most first-job probationary reviews are not about whether you’re smart. By Day 90 that’s already settled. The review is about whether you’re trainable.

A manager wants to know: can I give this person a piece of scope and not worry about it? The review is where they either confirm that answer or get a quiet alarm bell.

The good news: the questions are predictable. Pre-answer them and the meeting becomes a formality.

The five questions (and how to pre-answer them)

1. “What have you shipped?”

You need a list. Not “I worked on the Q1 launch.” A list of specific outputs with specific outcomes.

Template per line:

I shipped [thing]. It did [measurable outcome or signal]. The reason it mattered was [team impact].

Aim for five to eight bullets. Mix of big and small. Include “invisible” wins — the process doc you wrote, the Slack recap habit you started, the question you raised early that prevented a bigger problem.

Bring a one-page doc. Email it the morning of the review:

“Wanted to share my first-90-days recap before we meet. Happy to walk through it or skip to the parts you care about.”

Managers love this. You just wrote their prep doc for them.

2. “What did you struggle with?”

This is a trap, but a friendly one. “Nothing” makes you look unaware. A long list makes you look fragile.

The right answer: one specific gap, and how you closed it.

“My first month, I was slow on [tool / domain / process]. I spent two weeks going through [specific thing] and pair-coding with [person], and I’m now doing those tickets at the team’s normal speed.”

Translation: “I noticed a gap, I had a plan, I executed.” That’s what they want to hear.

3. “What do you want to work on next?”

Have one concrete answer. Not “more responsibility.” A specific piece of scope that would be a stretch.

“I’d like to own the weekly [recurring thing] end-to-end next quarter. I’ve been shadowing [person] on it for six weeks. I think I can take it cleanly, and it would free up [their] time for [higher-leverage thing].”

That answer shows three things: you know what’s happening around you, you know what’s valuable, and you’ve already been doing the pre-work.

4. “What do you need from me?”

Most juniors answer “nothing, I’m good.” Don’t. Your manager is asking what the coaching looks like:

“Two things. First, faster feedback on drafts — I’d rather hear ‘this is off’ at 30% than at 90%. Second, I’d like to sit in on [meeting type] so I can see how decisions get made one level up.”

Specific. Coachable. Doesn’t cost them much.

5. “Where do you see yourself in a year?”

This one gets answered badly a lot. “I want to be promoted” is lazy. “I want to be a VP someday” is cringe.

The right answer is tied to the role, not to a title:

“In a year, I’d like to own [specific scope] independently, be the go-to person on [specific domain], and be mentoring the next new hire on [specific thing]. I’m not in a rush on titles — I just want the scope to keep growing.”

That reads as mature. It’s also easier for your manager to engineer, because it’s specific.

The two questions you should ask

The review is a two-way conversation. Your prep isn’t complete without these.

“What would make me ‘easy to promote’ when the next cycle opens?”

If the answer is vague (“just keep doing what you’re doing”), push once: “Is there a specific scope or behavior that would change the answer to yes if someone asked?”

“If you could change one thing about how I operate, what would it be?”

Your manager has a piece of feedback they’ve been saving for the review. Ask for it directly and they’ll give it to you — better than hearing it in six months after it’s already hurt you.

The 24 hours before

• Send the one-page recap the morning of
• Re-read your last eight weeks of Slack messages and PRs. Pick two quotes or moments that show the story you want to tell
• Write your “struggles” answer out loud. The first time you say it should not be in the room
• Don’t send the recap to your skip-level. Just your manager

The 24 hours after

• Send a follow-up email summarizing what you heard: priorities for the next quarter, any commitments on either side. One paragraph
• If you heard something surprising, don’t respond that day. Sit on it overnight
• If you got a promotion signal, write down the exact criteria you heard. Save it. Reference it at the next review

If the review goes badly

A bad probationary review is not a firing. It’s a warning with a timeline. Three moves:

1. Ask for it in writing. “Can you send me the two or three areas we discussed so I have them clearly?”
2. Ask for a 30-day check-in. Not the next quarterly review. Sooner.
3. Pick one area and visibly fix it in the next two weeks. Progress on one thing beats incremental progress on three.

If it feels off-track after a real effort, that’s also useful data. The best time to start looking for the next job is when you still have this one.

—

The review meeting your manager dreads running is not the one where the recap doc shows up in their inbox at 9am. Spend the prep time, walk in with the five answers, and you’ve turned a meeting they were nervous about into a meeting they’re impressed by. Same 30 minutes on the calendar. Wildly different outcome on the rating.

For the weekly update habit that makes the recap easy to write, use the Status update template. For the 1:1 structure that builds the relationship the review depends on, use the Manager 1:1 agenda.