Weak versus strong STAR answers: 10 before-and-after examples
Many candidates choose a solid example and still give a weak answer.
You may have solved a difficult problem or prevented a serious risk. But if you rush past your decisions and describe everything as something “we” did, the interviewer has little evidence to assess.
Quick answer: A strong STAR answer gives enough context to understand the challenge, states your responsibility, focuses on the actions you personally took and ends with a result you can support. It does not rely on vague claims, invented metrics or sole credit for a shared outcome.
Quick checklist
Before using a STAR story, ask:
- Does it answer the capability behind the question?
- Is it about one specific situation?
- Is your responsibility clear?
- Do your actions and decisions get most of the detail?
- Can the interviewer separate your contribution from the team’s work?
- Can you verify every result you claim?
For the complete structure, read the practical guide to the STAR interview method.
What makes a STAR answer strong?
STAR stands for Situation, Task, Action and Result. The framework organises your evidence, but filling in all four sections is not enough. Your example still needs to answer the capability being assessed, and the result needs to be one you can support.
The examples below are illustrative. Use them to compare the wording, then build your answer from work you have done yourself.
| A weak answer tends to | A strong answer does instead |
|---|---|
| describe a broad project | focuses on one situation or decision |
| hide behind “we” | separates personal actions from shared work |
| list tasks | explains choices and judgement |
| claim success in general terms | names an outcome the candidate can verify |
| add an impressive but unsupported metric | uses an observable qualitative result when no reliable number exists |
1. Solving a difficult problem
Question: Tell me about a time you solved a difficult problem.
Weak answer
We had a major problem during testing. I worked with everyone, communicated regularly and made sure we solved it. Testing then went well and the project was successful.
Why it is weak
- The problem is not defined.
- “Worked with everyone” does not show what the candidate did.
- The answer claims project success without connecting it to the action.
- The interviewer cannot assess the candidate’s judgement.
Stronger answer
During user acceptance testing, two workstreams were applying different assumptions to the same business process. My responsibility was to help the teams agree on one approach before further test cases were completed. I documented the conflicting assumptions, traced each one to the relevant design decision and brought the workstream leads together to resolve the difference. I then updated the decision log and confirmed the agreed approach with the test team. Testing resumed using one interpretation, and the issue was no longer recorded as an open blocker.
2. Managing competing priorities
Question: Tell me about a time you managed competing priorities.
Weak answer
I am very organised and good at multitasking. When several priorities came up, I made a list, worked longer hours and completed everything on time.
Why it is weak
- It describes a personal trait rather than a specific example.
- It presents overwork as the main method.
- It does not show how priorities were evaluated.
- “Everything on time” may conceal trade-offs.
Stronger answer
In the same week, I needed to support a testing milestone, prepare a steering committee update and respond to a newly identified data risk. I ranked the work by delivery impact and decision deadline. I kept the testing milestone as planned, delegated the routine status collection and asked the sponsor to accept a shorter steering paper focused on the new risk. I also scheduled a decision session with the data owners. Testing proceeded, the committee received what it needed for its decision, and the data risk had an agreed owner and treatment plan.
3. Influencing without formal authority
Question: Tell me about a time you influenced someone without authority.
Weak answer
A stakeholder disagreed with me, so I explained why my approach was better. I persuaded them and we moved forward with my recommendation.
Why it is weak
- The stakeholder’s concern is missing.
- The answer sounds like winning an argument.
- There is no evidence of listening or adaptation.
- The candidate may be overstating decision authority.
Stronger answer
A workstream lead opposed another readiness review because they believed it would duplicate existing governance. I did not own the final decision, so I asked which parts of the current process they considered sufficient. I mapped the unresolved operational risks against the existing meetings and found two decisions with no clear forum or owner. After hearing their concerns, I reduced the proposed review to a short decision session rather than another reporting meeting. The lead supported the revised approach, and owners were assigned before the readiness checkpoint.
4. Identifying and reducing risk
Question: Give me an example of a risk you identified before it became a problem.
Weak answer
I am proactive and always look for risks. On one project, I found an issue early and saved the company a significant amount of money.
Why it is weak
- The risk and evidence are not described.
- The claimed saving is unsupported.
- The candidate’s actions are unclear.
- The answer relies on labels such as “proactive”.
Stronger answer
Before a data migration rehearsal, I noticed that the reconciliation criteria missed a group of records created through an older process. I raised the gap with the data lead, documented the affected record type and asked the team to include it in the validation sample. The extra check found inconsistent values before the rehearsal. We held the records back for correction, so the known defects did not move into the next stage. I had no approved information about the financial impact, so I would not claim a cost saving.
5. Working across teams
Question: Tell me about a time you worked effectively across teams.
Weak answer
I led a cross-functional project involving technology, operations and the client. I kept everyone aligned and delivered the outcome successfully.
Why it is weak
- “Led” may imply authority the candidate did not have.
- The coordination challenge is not clear.
- The actions are generic.
- The team outcome is presented as an individual achievement.
Stronger answer
A release required input from technology, operations and a client testing team, but each group tracked dependencies differently. I coordinated readiness rather than managing the functional teams. I brought the dependencies into one view, confirmed an owner and due date for each item, and reserved the weekly session for decisions and unresolved risks. The functional teams completed their own deliverables. I made the links between them visible and escalated decisions when dates conflicted. The release decision used that agreed readiness view.
6. Improving a process without a revenue metric
Question: Tell me about a process you improved.
Weak answer
Our reporting process was inefficient. I streamlined it, improved communication and increased productivity by 30 per cent.
Why it is weak
- The original problem is vague.
- The 30 per cent improvement has no stated baseline.
- “Streamlined” does not describe an action.
- The result may have been invented to sound stronger.
Stronger answer
Project decisions sat across meeting notes, emails and separate workstream trackers, which made the latest position hard to confirm. I reviewed where people recorded decisions and created one log with an owner, date, rationale and status. The leads agreed that meeting notes would link back to it. Once the log was in use, stakeholders had one place to check open and completed decisions, and we heard fewer repeated questions about the latest position in weekly meetings. We did not measure the time saved, so I would describe the improvement without attaching a number.
7. Handling a difficult stakeholder
Question: Describe a time you dealt with a difficult stakeholder.
Weak answer
A stakeholder was very difficult and kept changing their mind. I stayed calm, managed them closely and eventually got them to cooperate.
Why it is weak
- It labels the person rather than describing the issue.
- It presents the candidate as reasonable and the stakeholder as the problem.
- “Managed them” is vague and potentially dismissive.
- The result is unclear.
Stronger answer
A stakeholder repeatedly challenged the proposed cutover sequence because the support team might receive issues before training was complete. Rather than continue the debate in the larger meeting, I arranged a separate discussion to understand the operational concern. I worked with the training and support leads to map the planned coverage and found a real gap in the handover timing. We adjusted the handover and documented the remaining controls. The stakeholder then supported the revised sequence.
8. Owning a mistake
Question: Tell me about a mistake you made.
Weak answer
I sometimes care too much about quality. Once, I spent too long checking my work, but the final result was excellent.
Why it is weak
- It disguises a strength as a mistake.
- It avoids meaningful accountability.
- It gives no evidence of changed behaviour.
- It provides little insight into self-awareness.
Stronger answer
Early in a project, I issued a status update before confirming one dependency with the technical lead. I marked the item as on track, but the lead later told me that a prerequisite had slipped. I corrected the status with stakeholders that day and took responsibility for the error. After that, I required owner confirmation before publishing any high-impact dependency. In later reports, I included the owner’s confirmation date so readers could see what each status was based on.
9. Leading without a management title
Question: Tell me about a time you demonstrated leadership.
Weak answer
I led the team through a difficult period. I motivated everyone, assigned tasks and made sure the project stayed on track.
Why it is weak
- It may imply formal authority that did not exist.
- “Motivated everyone” is difficult to evidence.
- The challenge and actions are not specific.
- The project result is too broad.
Stronger answer
Several workstream actions stayed open because people assumed another team would complete them. I was not anyone’s line manager, but I took responsibility for clearing up the ownership. I brought the relevant people together, confirmed the decision needed for each action, recorded who had authority to close it and escalated two unresolved items to the sponsor. By the end of the session, the team had agreed responsibilities and the previously unowned actions had named decision-makers. I would call this coordination leadership, not people management.
10. Describing an outcome that was not yet known
Question: Tell me about a recommendation you made that influenced an important decision.
Weak answer
I developed a recommendation that transformed the process and delivered major long-term benefits.
Why it is weak
- The long-term result may not have been observed.
- “Transformed” and “major benefits” are unsupported.
- The candidate’s analysis is missing.
- The answer confuses recommendation acceptance with final impact.
Stronger answer
I reviewed a proposed support model and found that nobody had been assigned responsibility for two post-launch activities. I mapped the work, consulted the operational and delivery leads, and presented three ownership options with the risks of each. The steering group accepted my recommendation and added it to the implementation plan. My involvement ended before the model went live, so I can verify the decision but not the longer-term operational impact.
A five-minute STAR answer check
Use these questions before an interview:
- Is the example relevant? Which role requirement or competency does it demonstrate?
- Is it specific? Can you identify one event, period or decision?
- Is your responsibility clear? What were you expected to achieve or address?
- Are the actions concrete? What did you analyse, decide, change, create, facilitate or escalate?
- Is the result supported? What changed, and how do you know?
- Are the boundaries honest? What was shared, confidential, unmeasured or unknown?
Use how to choose your best STAR interview examples to select the right stories before refining the wording.
These questions help you shape the answer. Having the facts ready is harder. Ascending Careers gives you one private place to capture the work, decisions and outcomes you may need later.
Frequently asked questions
How long should a STAR answer be?
Give enough context to understand the challenge, then spend most of the answer on your actions and result. Leave room for follow-up questions.
Should I say “I” or “we” in a STAR answer?
Use both where they are accurate. Say “we” for shared work or a team result. Say “I” when you explain your responsibility, decisions and actions. The interviewer can then see your contribution without hearing you take credit for other people’s work.
What if I cannot quantify the result?
Describe a change you observed, such as an agreed decision, a resolved blocker or clearer ownership. Do not add a percentage unless you have a reliable baseline and source.
Can I use an example that did not end successfully?
Yes. This can work well for questions about mistakes, failure, feedback or resilience. Explain what happened, take responsibility for your part and say what you changed. Do not bolt on a positive ending that did not happen.
What if the final outcome happened after I left the project?
State the result you can verify, such as approval, handover or inclusion in an implementation plan. Then explain that you did not observe the longer-term outcome.
Should I memorise my STAR answers word for word?
Prepare the key facts and practise aloud, but avoid a rigid script that cannot adapt to the exact question.
Strong answers begin with credible evidence
A better STAR answer uses clearer evidence, not more impressive language.
Choose a relevant event and make your responsibility clear. Explain what you did and why. State the result accurately. If you cannot verify a metric, outcome or level of authority, leave it out or say where your knowledge ends.
Ascending Careers can help you turn work you have already recorded into interview-ready stories while keeping the original facts underneath them.
Build three credible STAR stories from your own work.
Create your first STAR stories
Editorial note
All workplace examples in this article are illustrative. They demonstrate answer structure and evidence boundaries. They are not claims about a real person, employer or project.
References
- Chartered Institute of Personnel and Development, Selection methods, 11 November 2024. https://www.cipd.org/en/knowledge/factsheets/selection-factsheet/
- US Office of Personnel Management, Structured interviews, accessed 3 September 2026. https://www.opm.gov/policy-data-oversight/assessment-and-selection/other-assessment-methods/structured-interviews/
- University of Wollongong, Behavioural interview preparation, accessed 3 September 2026. https://www.uow.edu.au/student/careers/applying-for-jobs/behavioural-interview-preparation/
- Indeed Australia, How to use the STAR interview response technique, accessed 3 September 2026. https://au.indeed.com/career-advice/interviewing/how-to-use-the-star-interview-response-technique