Explain your strengths. Be honest about your weaknesses.

For a strength, choose something relevant to the job and find an incident that demonstrates it. “Communication” is a label. Explaining how you uncovered a disagreement and helped people resolve it gives the interviewer something concrete to ask about.

Use work, study or volunteering experience, and name the setting accurately. Write down what happened, your responsibility, what you personally did and what you know about the result. A missing percentage is a reason to describe the evidence you have, not to invent a number.

Try this outline in your own words:

• The strength: what do you do well that matters for this role?
• The example: when did you use it?
• Your action: what did you decide or do yourself?
• The evidence: what happened, and how do you know?

The following example is fictional. Use it to examine the structure, not as experience to claim as your own.

“I’m good at cross-team communication. Our launch went smoothly.”

This names a strength and a team outcome but leaves the candidate’s contribution unclear. If the candidate had actually collected conflicting launch dates and brought the team leads together, they could explain that action:

“When two teams were working toward different launch dates, I wrote down the mismatch and brought the team leads together to agree on one date. I’m good at making coordination problems explicit so the people responsible can resolve them.”

The answer adds a specific action without inventing a business result. Now test it: “Why involve both leads rather than choose a date yourself?” The candidate still needs to explain their responsibility and reasoning.

Choose a real limitation you can discuss professionally. Explain how it affected your work, what you are doing about it and what still needs attention. You do not need to turn a strength into a pretend weakness or claim the problem has disappeared.

Here is another fictional example:

“I sometimes spend too long polishing an early draft before asking for feedback. On a student project, I refined the presentation before checking the argument with my teammate, and we had to rework it. I now share a rough outline before working on the wording. I still catch myself over-editing, so I use that outline review as a checkpoint.”

A useful follow-up is: “Tell me about a time you used that checkpoint.” If you cannot give an actual example of your new approach yet, say that you have started trying it. Do not describe an intention as a proven improvement.

Write four factual notes, then put the full draft away and answer aloud. Ask a practice partner to select a detail from your answer and question it. If you are alone, put a follow-up on a separate card and turn it over after answering.

• “What did you personally do?”
• “Why did you choose that approach?”
• “What evidence tells you it helped?”
• “What are you still working on?”

Notice the point where you reach for a memorised sentence. Is the phrase unfamiliar? Is your contribution missing? Does the result sound stronger than your evidence? Clarify that part using your real experience, then answer again.

The goal is an account you can support in your own words. For a repeatable exercise, try practising one interview question with an unexpected follow-up.