Competency Based Interview Questions: 30 Examples With Model Answers (2026)
Competency-based interviewing (CBI) is now the dominant interview methodology used by large employers worldwide. Organisations including the UK Civil Service, KPMG, Deloitte, Unilever, NHS Trusts, Amazon, and thousands of mid-market companies all run structured competency interviews as a core part of their selection process. Understanding how CBI works — and preparing specific, evidence-backed answers — is the single most effective thing you can do to improve your interview performance.
This guide explains what CBI is, how it differs from general behavioural interviewing, the top 10 competencies companies assess, and 30 questions with model answers organised by competency. It also covers how to build an evidence bank and how to tailor your preparation by industry.
What Is Competency-Based Interviewing?
A competency-based interview (also called a structured behavioural interview) is a formal interview in which every question is designed to assess a specific, pre-defined competency. Unlike casual interviews where questions vary by interviewer mood or intuition, CBI follows a fixed question set for all candidates. Each answer is scored against a defined rubric — often using a 1–5 rating scale — so that decisions are based on evidence, not impression.
The term "competency" refers to a cluster of knowledge, skills, behaviours, and attitudes that are required for effective performance in a role. Examples include: leadership, communication, resilience, analytical thinking, customer focus, and commercial awareness.
SHRM research on structured interviewing consistently shows it to be 2–3x more predictive of job performance than unstructured alternatives. The reason is simple: when every candidate answers the same questions, which are evaluated against the same criteria, bias is reduced and comparison is fair.
CBI vs. General Behavioural Interviews
The terms are often used interchangeably, but there is a meaningful distinction:
- Behavioural interviews ask about past behaviour ("Tell me about a time you...") but the question set may vary between interviewers and is not necessarily linked to a formal competency framework.
- Competency-based interviews are behavioural interviews tied to a specific organisational competency framework. Every question maps to a named competency. Scores are recorded and aggregated. Pass marks may be required on specific competencies to proceed.
In practice, if you are interviewing with a large employer — especially in financial services, consulting, government, healthcare, or technology — you are almost certainly facing a CBI. The preparation approach is the same as for behavioural interviews, but you can be more targeted: find out what competencies the employer uses (often on their website, graduate recruitment pages, or job descriptions) and prepare specific examples for each one.
The Top 10 Competencies Companies Assess
1. Leadership
The ability to guide, motivate, and develop others — including in situations where you do not have formal authority.
What assessors want to see: Taking ownership of outcomes, inspiring effort, making unpopular decisions when necessary, developing the capabilities of others.
2. Communication
The ability to convey complex information clearly, listen actively, and adapt your communication style to different audiences.
What assessors want to see: Structured explanations, active listening behaviours, tailoring message to audience, written and verbal clarity.
3. Teamwork and Collaboration
The ability to work effectively with diverse colleagues, contribute to shared goals, and support others.
What assessors want to see: Specific contributions to team outcomes, managing conflict within a team, building on others' ideas, putting team goals before personal recognition.
4. Problem-Solving and Analytical Thinking
The ability to identify root causes, structure complex problems, and generate practical solutions.
What assessors want to see: Systematic thinking, data use, weighing multiple options, making reasoned decisions under uncertainty.
5. Adaptability and Resilience
The ability to perform effectively during change, uncertainty, and setback.
What assessors want to see: Coping with rapid change, recovering from failure, maintaining performance under pressure, updating approach based on new information.
6. Initiative and Drive
The ability to identify opportunities and act on them without being asked.
What assessors want to see: Going beyond the job description, proactively identifying improvements, taking ownership before being told to.
7. Customer Focus
The ability to understand, anticipate, and respond to customer needs in a way that builds lasting relationships.
What assessors want to see: Listening to customers, going the extra mile, balancing customer needs with business constraints, learning from customer feedback.
8. Commercial Awareness
The ability to understand how the business makes money, where the risks and opportunities lie, and how your role connects to financial outcomes.
What assessors want to see: Connecting your work to business metrics, awareness of competitor landscape, thinking about cost, revenue, and risk.
9. Planning and Organisation
The ability to manage time, resources, and priorities effectively to deliver on commitments.
What assessors want to see: Prioritisation under competing demands, proactive risk management, delivering on time consistently.
10. Developing Others (Coaching and Mentoring)
The ability to support the growth and development of colleagues, direct reports, or peers.
What assessors want to see: Identifying development needs, giving actionable feedback, adapting coaching style, celebrating others' growth.
30 Questions With Model Answers by Competency
Before diving in, a note on format: all model answers follow the STAR structure (Situation, Task, Action, Result). Adapt the specifics to your own experience. Use ClavePrep's AI mock interview tool to practise delivering these out loud.
Leadership (Questions 1–4)
Q1: Tell me about a time you led a team through a significant challenge.
S: I was Engineering Manager at a B2B SaaS startup when we experienced a critical outage affecting 300 enterprise clients over a weekend. The on-call engineer had identified the symptom but not the root cause.
T: My role was to coordinate the incident response and ensure client communication while the team worked on resolution.
A: I set up a dedicated Slack channel, assigned one engineer to client comms and two to root-cause investigation. I personally called the five largest affected clients within 90 minutes. We ran hourly status updates on our status page. Once the root cause — a misconfigured load balancer rule — was identified, I made the call to roll back a recent deployment rather than patch forward, accepting a data loss of 30 minutes of non-critical logs.
R: Service was restored in four hours. All 300 clients were back online by Sunday afternoon. Three clients sent unsolicited emails praising our communication. We lost zero accounts as a direct result of the outage. I then led a blameless post-mortem and implemented a runbook for load balancer configuration changes.
Q2: Describe a time you had to make a difficult leadership decision.
S: As project lead on a £1.2 million infrastructure modernisation project, I discovered at week eight of a 20-week timeline that a key vendor was four weeks behind schedule due to internal resourcing issues.
T: I had to decide whether to wait, find a replacement vendor, or descope.
A: I ran a rapid risk assessment over 48 hours: the vendor's delay was structural, not recoverable. I presented three options to the project steering committee with a cost-benefit analysis for each. My recommendation was to engage a secondary vendor for the delayed workstream while retaining the original vendor for components already in progress. This required an additional £85,000 but preserved the overall timeline.
R: The committee approved the recommendation. The project delivered on the original 20-week timeline. The £85,000 cost was offset by avoiding the penalty clauses for late delivery, which would have totalled £130,000.
Q3: Tell me about a time you motivated a demotivated team.
S: I joined a customer service team at a telecoms company as team lead following a poorly managed restructure. Four of my eight team members had submitted informal expressions of dissatisfaction, and response times were at an 18-month low.
T: I needed to reverse the performance decline without the authority to change compensation or headcount.
A: In my first week, I held individual one-to-ones with each team member to understand their specific concerns. The consistent theme was that no one felt their work was visible to senior leadership. I created a weekly team impact digest — a one-page summary of metrics, customer wins, and individual contributions — that I sent to the director and shared back with the team. I also implemented a peer-recognition system where team members could nominate each other for a monthly spotlight. I cleared unnecessary bureaucratic hurdles that had been added during the restructure by working directly with the process team.
R: Within eight weeks, average response time improved from 4.2 hours to 2.6 hours. Two of the four who had submitted expressions of dissatisfaction withdrew them. Team NPS (internal) rose from 42 to 71 over the subsequent quarter. No team members resigned in the 12 months I led the team.
Q4: Describe a time you developed a team member's skills.
S: I was a senior data analyst managing one junior analyst who was technically strong but struggled to present findings to non-technical stakeholders — a skill critical for promotion to mid-level.
T: Develop their presentation skills within a six-month development cycle.
A: I started by observing a presentation they gave to the marketing team and noted specific gaps: they opened with methodology rather than insight, used jargon without defining it, and did not structure recommendations clearly. I shared written feedback immediately after. We then agreed on a structured development plan: they would present to me first before every stakeholder presentation for two months, with a 15-minute debrief after. I modelled the "insight-first" structure in my own presentations and explicitly pointed it out to them in real time.
R: After three months of practice presentations and debriefs, they presented an analysis to the Head of Marketing independently and received direct praise for clarity. They were promoted to mid-level analyst four months later, with "communication with stakeholders" cited as a key development in their review.
Communication (Questions 5–8)
Q5: Tell me about a time you communicated a complex idea to a non-expert audience.
S: I was a cybersecurity analyst required to present a risk assessment on proposed BYOD (Bring Your Own Device) policies to a board of directors — none of whom had a technical background.
T: Translate a 40-page technical risk report into a 10-minute board presentation with clear recommendations.
A: I restructured the report into three sections: what the risk is in plain language, what it would cost us if the risk materialised, and what the mitigation options cost. I replaced technical CVE scores with a simple red-amber-green risk matrix. I used a single analogy — comparing network security to physical building security — to explain access controls without jargon. I rehearsed with a colleague who had no technical background and amended anything they had to ask me to explain.
R: The board approved the recommended BYOD policy framework in the same meeting — the first technology policy approved at board level without a referral for further review. The Finance Director commented that it was "the clearest technical presentation we have received."
Q6: Give me an example of a time you had to deliver a difficult message.
S: As a consultant, I had to tell a client CEO that the market research they had commissioned — and for which they had significant internal buy-in — showed the product they were about to launch had a critical flaw in the pricing model.
T: Deliver findings that contradicted 18 months of internal conviction without damaging the relationship or causing the client to dismiss the research.
A: I requested a private meeting with the CEO before the full team presentation. I led with the strength of the underlying data rather than the conclusion, walking through the methodology. I then presented the finding as a risk to be managed rather than a reason to abandon the launch. I came prepared with two alternative pricing scenarios that the data supported. By the time I named the specific concern, I had established that the research was solid and that there was a path forward.
R: The CEO did not dismiss the findings. She delayed the launch by eight weeks to retest pricing with a target segment. The revised model tested 31% better with target customers. The product launched at the revised price point and hit its first-quarter revenue target within 10 weeks of launch.
Q7: Describe a time you had to adapt your communication style.
S: I was leading a project with a mixed team — three senior engineers in Germany and two junior business analysts in the UK. Early project meetings were ineffective: the engineers communicated in precise, technical terms; the analysts felt lost and disengaged.
T: Improve the quality of cross-team communication without losing the technical rigour the engineers needed.
A: I introduced a "translation rule" for our project calls: after any technical explanation, the speaker had to offer a one-sentence plain-language version. I created a shared glossary in Confluence for project-specific terms. I also restructured the agenda so that technical deep-dives happened in breakout sessions with just the engineers, while cross-team calls focused on decision-making and status — the content where both groups needed to align.
R: Meeting satisfaction (measured through a post-call pulse check) rose from 3.1 to 4.4 out of 5 within four weeks. The project delivered on schedule with no major miscommunication incidents. The restructured agenda format was adopted by two other project teams in the department.
Q8: Tell me about a time your written communication had a significant impact.
S: After a supplier dispute at a manufacturing company, I was asked to write the formal letter to the supplier outlining our position before potential legal escalation.
T: Produce a communication that was assertive, legally defensible, and left the door open for negotiation.
A: I worked with the legal team to understand our contractual position, then drafted the letter in plain English rather than legal language — reasoning that a more accessible tone was more likely to prompt a response than dense legalese. I structured it as: what was agreed, what was delivered, what the gap is, and what we need to resolve it. I kept it to one page.
R: The supplier responded within three days — significantly faster than previous communications — and proposed a resolution. The dispute was resolved without legal proceedings, saving an estimated £75,000 in legal fees. The supplier relationship continued for two more years.
Teamwork and Collaboration (Questions 9–11)
Q9: Tell me about a time you worked as part of a high-performing team.
S: At a digital agency, I was part of a five-person team that won and executed a £400,000 rebranding project for a FTSE 250 client, with a 14-week delivery window.
T: Contribute as the strategy lead while collaborating with design, copy, project management, and client services.
A: My role was to lead the strategic discovery phase: stakeholder interviews, competitor audit, and brand positioning workshop with the client. I shared all research materials with the full team in a shared Notion workspace rather than keeping it in the strategy silo. I attended design review sessions even though that was not my function — I provided context on strategic rationale that helped designers make faster decisions. When timelines compressed in week 10, I took on additional tasks outside my core remit to help the copy team hit their deadline.
R: The project delivered in 13 weeks, one week ahead of schedule. The client extended the engagement with a follow-on digital execution project worth £180,000, citing "seamless team cohesion" as a key factor.
Q10: Describe a time you had to resolve a conflict within your team.
S: On a product development team, two senior engineers had an ongoing disagreement about architectural approach that was slowing decision-making and affecting team morale.
T: As team lead, I needed to resolve the conflict and move the team forward.
A: I met with each engineer individually to understand their position and the reasoning behind it — making clear I was not there to take sides. Both had legitimate technical concerns. I proposed a structured technical spike: each engineer would prototype their approach over three days, and we would evaluate both against agreed criteria (performance, maintainability, deployment complexity). I set the evaluation criteria collaboratively so both felt the process was fair.
R: The spike produced clear evidence that one approach had a 40% performance advantage for our use case. The other engineer acknowledged the data and supported the decision. Morale improved — the rest of the team noted that decisions were being made again. The architectural framework chosen has supported the product for two years without major rework.
Q11: Tell me about a time you supported a struggling colleague.
S: A peer in my team — a talented analyst — was visibly struggling after returning from parental leave. Deadlines were being missed and their confidence was low.
T: Support their transition back without overstepping or making them feel singled out negatively.
A: I approached them informally and asked how they were finding the return. They shared that they felt out of touch with changes that had happened during their leave. I offered to run them through a "catch-up session" — an informal 90-minute overview of what had changed in systems, process, and priorities. I also offered to peer-review their first two deliverables back so they could get private feedback before anything went to leadership. I did not tell anyone else I was doing this.
R: Within four weeks, their delivery quality and confidence had visibly recovered. They later told me the catch-up session had been "exactly what I needed." They went on to deliver one of the quarter's highest-rated analysis pieces and received a performance rating of "exceeds expectations" for the half-year.
Problem-Solving and Analytical Thinking (Questions 12–14)
Q12: Describe a time you identified a problem before it became a crisis.
S: As a supply chain analyst, I noticed during routine data review that one of our three key raw material suppliers had increased lead times by an average of six days over the past eight weeks — a change that had not been flagged by procurement.
T: Assess the risk and act before it affected production.
A: I ran a scenario model to understand what would happen to our production schedule if lead times extended further — specifically if they hit 20 days (up from our contractual 12). The model showed that at 20 days, we would miss our contractual delivery window for our largest customer. I presented the risk to the procurement and production leads with three mitigation options: build inventory buffer, qualify a secondary supplier, or renegotiate lead times with the primary supplier. I recommended the second option given cost efficiency.
R: Procurement began the secondary supplier qualification within two weeks. The primary supplier's lead times reached 23 days six weeks later — but we had sufficient buffer stock. We met every customer delivery commitment. The secondary supplier was formally qualified and has since reduced our single-supplier dependency risk.
Q13: Tell me about a time you used data to make a decision.
S: As a marketing manager, I was asked to decide which of three paid channels to scale for the next quarter: paid search, paid social, or influencer partnerships. All three were showing positive ROAS on the surface.
T: Identify which channel would produce the best incremental return on a £150,000 incremental budget.
A: I ran a multi-touch attribution analysis over the previous six months to understand channel contribution at each funnel stage. I then conducted a holdout test — pausing spend in one geography for each channel for two weeks — to isolate incrementality. Paid social showed high attributed conversion but very low incrementality (customers would have converted anyway). Paid search showed the highest true incrementality. Influencer had moderate incrementality but the best CAC for new customer acquisition.
R: I recommended splitting the incremental budget: 65% to paid search, 35% to influencer. The reallocation increased net new customer acquisition by 28% in Q3 compared to Q2, while overall cost per acquisition fell by 17%.
Q14: Give me an example of a time you found a creative solution to a difficult problem.
S: At a non-profit, we needed to produce an annual impact report — typically a professionally designed print document — but our design budget for the year had been cut by 80%.
T: Produce a credible, high-quality impact report that could be shared with major donors on a budget of £600 instead of the usual £3,000.
A: I identified Canva Pro as a tool several team members already had access to. I found a free report template that matched our brand guidelines. I wrote all the copy myself, trained one team member on the design tool in two hours, and co-produced the report over four evenings. I negotiated with a local printing company for a reduced rate in exchange for a "printed by" credit on the document.
R: The report was produced for £580 all-in. Two major donors specifically mentioned it in their renewal letters — one called it "the most readable impact report we receive." Donations from the donor cohort rose 12% year-on-year.
Adaptability and Resilience (Questions 15–17)
Q15: Tell me about a time you worked effectively under significant pressure.
S: As a financial analyst, I was given 72 hours to produce a financial due diligence pack for a potential acquisition that would normally take two weeks. The acquisition window was time-sensitive.
T: Deliver a credible due diligence pack within 72 hours.
A: I immediately triaged the due diligence checklist into three tiers: must-have for the investment decision, useful but not blocking, and available post-acquisition. I cleared my calendar for 72 hours, delegated three non-time-critical tasks to colleagues, and worked a structured 14-hour day with clear stopping points to maintain accuracy. I checked in with the deal lead at 24 and 48 hours to reprioritise based on any new information.
R: The pack was delivered in 68 hours. The deal team proceeded to the next stage of negotiations. The acquisition completed successfully. My manager cited the deliverable in my annual review as evidence of "exceptional performance under pressure."
Q16: Describe a time you adapted to a major change at work.
S: Our company switched from a custom-built CRM to Salesforce in a seven-week rollout that was far shorter than the industry standard. I was the operations lead responsible for ensuring the sales team of 45 could function without disruption.
T: Manage the transition so that sales productivity did not fall below 80% of baseline during the rollout.
A: I ran a pre-migration data audit to identify which records were incomplete or duplicated before they were imported into Salesforce — avoiding a corrupted starting point. I created a one-page "cheat sheet" for each of the 12 most-used workflows rather than sending people to the full Salesforce training library. I established a daily drop-in session for the first three weeks where reps could bring live issues and get them resolved in real time.
R: Sales productivity fell to 87% in week one and recovered to 96% by week three — better than the 80% target. Zero major data loss incidents occurred. The daily drop-in sessions became a permanent weekly office hour that the team requested to continue.
Q17: Tell me about a time you recovered from a professional setback.
S: I was passed over for a promotion I had worked toward for 18 months. The feedback was that my strategic thinking was strong but my stakeholder management needed development.
T: Process the setback constructively and address the specific gap identified.
A: After an initial period of processing the disappointment, I asked my manager for a specific example of where my stakeholder management had fallen short. I was told that I had not kept the Head of Finance adequately informed during a cost-reduction project, which led to a surprise in a budget review meeting. I accepted this as accurate. I enrolled in a structured stakeholder mapping course, implemented a weekly "no-surprises" email to any senior stakeholder on my projects, and took on a cross-functional project specifically to practise lateral stakeholder management.
R: When the next promotion cycle came around nine months later, I was promoted. My manager specifically cited improved stakeholder management in the promotion rationale. The "no-surprises" email became a practice I have kept in every role since.
Initiative (Questions 18–20)
Q18: Tell me about a time you went above and beyond your role.
S: As a junior account manager at a PR agency, I noticed that our monthly client reporting was being compiled manually by senior staff — a process that took roughly eight hours per month per account.
T: There was no assigned task. I identified the opportunity independently.
A: I spent two evenings building a reporting template in Google Sheets that pulled key metrics from our media monitoring tool and social analytics via API. I tested it on two accounts and documented the process. I then presented it to my line manager as a working prototype, not a proposal, showing that it reduced reporting time from eight hours to approximately 90 minutes.
R: The template was adopted across all 12 accounts. The senior team reclaimed an estimated 78 hours per month. I was asked to lead a process improvement taskforce — a role typically held by managers — and was promoted to Senior Account Manager at my next review, six months ahead of my original timeline.
Q19: Describe a time you identified a new business opportunity.
S: While managing an existing account at a software consultancy, I noticed in our quarterly business review that the client was using a third-party tool for data visualisation — a service we were capable of providing.
T: This was not part of my remit — my role was account management, not business development.
A: I researched the third-party tool to understand what the client was using it for and estimated what it was costing them annually (approximately £60,000). I built a one-page business case showing how our team could deliver equivalent functionality for £38,000 — saving the client £22,000 and adding £38,000 in revenue for us. I shared it with our account director and asked to be part of the conversation with the client.
R: The account director presented the case. The client signed a new statement of work for the visualisation work within three weeks. The engagement expanded further over the following 18 months to £210,000 ARR. I was formally recognised in the company's quarterly awards for the origination.
Q20: Tell me about a time you took ownership of a problem that was not yours to solve.
S: At a healthcare company, the clinical team was struggling with a recurring data quality issue in our patient intake forms — a problem that technically sat in the IT domain, not mine as a clinical operations analyst.
T: The IT team had deprioritised the fix for three quarters. The clinical team had no technical resource to escalate further.
A: I mapped the data quality issue in detail, identifying that 23% of intake records had incomplete fields in three specific areas. I traced the source to a form logic issue — a conditional field was not displaying correctly on tablet devices. I wrote a one-page bug report with screen recordings and submitted it directly to the IT team with a clear articulation of the clinical impact (delayed triage for patients). I also offered to be the point of contact for questions so the clinical team did not need to manage the back-and-forth.
R: The bug was fixed in the next sprint — three weeks after I submitted the report. Incomplete record rates dropped from 23% to under 3%. The clinical lead cited the fix as having a material impact on patient triage times. My manager used the incident as an example of cross-functional ownership in my annual review.
Customer Focus (Questions 21–23)
Q21: Tell me about a time you went the extra mile for a customer.
S: As a customer success manager at a HR software company, one of my accounts — a mid-market manufacturing firm — was on the verge of churning after a product implementation that had delivered lower-than-expected results in their first 90 days.
T: Retain the account and restore confidence in the product.
A: Rather than scheduling a standard check-in call, I flew to their site for a half-day review. I ran a process audit with their HR team to understand how they were using the product and identified three workflow misconfigurations that were causing the underperformance. I fixed two on the day and escalated one to our implementation team with a two-day SLA. I also co-created a 30-day quick-win plan with their HR manager that gave them concrete milestones to track.
R: The account renewed at full contract value 60 days later. The HR manager sent an email to our CEO praising the on-site visit as "the turning point." The account subsequently expanded their seat count by 40%, adding £24,000 to ARR.
Q22: Describe a time you received negative customer feedback and what you did with it.
S: During our quarterly NPS survey at an e-learning platform, I received a score of 4 out of 10 from an account I had managed for two years — a significant drop from their previous 8.
T: Understand the root cause and address it before renewal.
A: I called the client within 24 hours. They were frustrated that their custom content had taken six weeks to produce rather than the four-week SLA. I apologised directly without making excuses, then investigated the internal cause. The delay had originated from a resource bottleneck in our content studio that had not been communicated to the account. I worked with the studio manager to implement a client notification system that would flag any SLA risk at the two-week mark. I also arranged a credit for the delay and expedited the remaining deliverables.
R: The account renewed and gave an NPS of 9 at the next survey cycle. The notification system I proposed was implemented company-wide and reduced SLA breach incidents by 35% over the following two quarters.
Q23: Tell me about a time you balanced customer needs against business constraints.
S: A key enterprise client at a logistics company requested a custom reporting dashboard as part of their contract renewal negotiation — a feature that our development team estimated would take eight weeks and £40,000 to build. The renewal itself was worth £180,000 ARR.
T: Find a way to meet the client's underlying need without committing to a development timeline that was unrealistic.
A: I held a discovery call with the client to understand what decisions the dashboard would inform — not just what they wanted to see. Their core need was real-time shipment tracking consolidated into a single view. I identified that our existing analytics platform could deliver 80% of that functionality through a configuration change, not a build. I worked with the solutions team to set up a pilot configuration in three days and demonstrated it to the client.
R: The client accepted the configured solution as a "phase one" dashboard and agreed to defer the custom build to a future contract year. They signed the renewal within a week. The configuration approach saved the £40,000 development cost and delivered the client's core need in three days rather than eight weeks.
Commercial Awareness (Questions 24–26)
Q24: Tell me about a time you identified a cost-saving opportunity.
S: As an operations manager, I was reviewing our vendor contracts ahead of the annual budget process and noticed that we were paying for three overlapping SaaS tools in our marketing tech stack — all of which had been acquired at different points without a consolidated review.
T: Identify consolidation opportunities and produce a recommendation for the CFO.
A: I audited usage data for all three tools and found that one had under five active users despite a £24,000 annual licence. I also found that our primary tool — which we were using at full capacity — had recently added features that replicated the functionality of the second tool. I produced a consolidation roadmap: terminate tool A immediately, migrate off tool B over 60 days, and negotiate a volume discount with the primary vendor given the expanded use case.
R: The CFO approved all three recommendations. Net annual saving: £36,000. The migration was completed in 55 days with no disruption to the marketing team.
Q25: Describe a time you demonstrated commercial awareness in your work.
S: As a product manager, I was presenting a roadmap to the leadership team and was challenged by the CFO on the revenue impact of a proposed feature.
T: Demonstrate that the feature investment was commercially justified.
A: I had anticipated the question and prepared an analysis: the feature would reduce churn in accounts that had flagged it in exit surveys (11% of churning accounts cited this gap). At our average ACV of £42,000, reducing churn by even 2% was worth £840,000 in retained ARR annually. The development cost was estimated at £120,000. The payback period was under two months. I presented this analysis during the session.
R: The CFO approved the feature for the next quarter roadmap. The feature shipped on time and reduced the churn cohort that had cited the gap from 11% to 4% over the following two quarters.
Q26: Tell me about a time your understanding of the market influenced your decision-making.
S: As a marketing director at a fintech startup, I was tasked with allocating a £500,000 marketing budget for the coming year. We were in a market where two well-funded competitors had recently launched aggressive acquisition campaigns.
T: Allocate the budget to maximise our competitive position given the changed market dynamics.
A: Rather than matching competitors on acquisition spend — which we could not sustain given our smaller budget — I reviewed our data and found that our retention rate (92%) was significantly higher than the industry average (78%). I proposed a reallocation: reduce acquisition spend by 30%, increase investment in a customer advocacy programme (case studies, referral incentives, community events), and launch a comparison campaign that highlighted retention as a differentiator. I backed this with research showing that 67% of B2B buyers in our sector rated "reliability of support" as a top-three purchase factor.
R: The reallocated budget produced a 34% increase in referral-sourced revenue over 12 months. Average deal size from referred customers was 22% higher than from paid channels. We grew ARR by 41% year-on-year without increasing total marketing spend.
Developing Others (Questions 27–30)
Q27: Tell me about a time you mentored someone effectively.
S: I was a senior consultant asked to formally mentor a junior consultant who had strong technical skills but was struggling to build relationships with clients — a critical skill for progression to manager level.
T: Help them develop client relationship skills over a six-month mentoring engagement.
A: In our first session, I asked them to define what "good" looked like to them in client relationships — and helped them realise they had no clear model for it. We spent the first month on observation: they joined my client calls as a silent observer and noted specific behaviours that built rapport. In month two, they led the small-talk portion of client calls while I was present. In month three, they ran project update calls independently. I debriefed after each call with specific, behavioural feedback ("when the client mentioned the implementation risk, you moved on — try pausing and asking what concerns them most").
R: By month five, the client they were assigned to specifically requested them as the lead point of contact — a first for a junior consultant in our team. They were promoted to manager level at the end of the following review cycle.
Q28: Describe a time you gave constructive feedback that made a difference.
S: One of my direct reports — a mid-level engineer — was technically excellent but routinely delivered code that was difficult for others to maintain. This was causing friction in code reviews and slowing the team.
T: Address the issue in a way that improved outcomes without demotivating a high performer.
A: I avoided raising it in a team setting. In their next one-on-one, I shared specific examples — three PRs where other engineers had spent significant time untangling the logic — and framed the conversation around impact on the team rather than a personal failing. I asked them to walk me through their thinking on one of the examples, which revealed that they were optimising for cleverness rather than readability. We agreed on a new standard: each PR would include a 3-line comment explaining the reasoning for non-obvious logic.
R: Code review turnaround time for their PRs fell from an average of 4.2 days to 1.8 days over the following six weeks. Two team members independently commented on the improved quality. The engineer cited the conversation as "genuinely helpful" in their next 360 review.
Q29: Tell me about a time you identified a development need in your team and acted on it.
S: After conducting a mid-year team retrospective, I identified that our five-person team collectively had low confidence in data analysis despite data literacy being increasingly important for our work as HR business partners.
T: Close the skills gap without a formal training budget.
A: I surveyed the team to understand the specific gaps: most were comfortable with Excel but unfamiliar with basic SQL and data visualisation. I reached out to our data analytics team and arranged a three-session informal training series delivered by one of their analysts (in exchange for one of my team members running a soft skills workshop for their team). I also created a shared team library of learning resources and organised a fortnightly "data challenge" where we each analysed the same small dataset and compared approaches.
R: Within three months, four of five team members reported increased confidence in data analysis (measured through the follow-up retrospective). Two began accessing HR analytics dashboards independently for the first time. The fortnightly challenge became a standing team practice.
Q30: Describe a time you created conditions for a team to perform at their best.
S: I took over as head of a customer service team that had been through three managers in 18 months. Psychological safety was low — team members were reluctant to flag problems or admit mistakes, which was leading to issues being caught late.
T: Create an environment where the team felt safe to raise concerns and make decisions.
A: In my first team meeting, I shared a mistake I had made in a previous role and described what I learned from it. I then introduced a standing agenda item — "what got in the way this week" — to normalise discussing friction. When team members raised issues, I responded with curiosity rather than evaluation: "Tell me more about what happened" rather than "Why did that happen?" I also shifted the team's escalation culture: any team member could make a decision up to a defined threshold without approval, and I would back them publicly even if I would have decided differently.
R: Within 90 days, the number of issues surfaced before they became customer-facing problems rose by 60%. The team's average resolution time for complex issues fell from 6.4 hours to 3.8 hours. In a company-wide engagement survey, the team scored 91% on psychological safety — up from 52% under the previous manager.
How to Prepare Your Evidence Bank
An evidence bank is a structured personal document containing your STAR stories, organised by competency. Before any CBI, you should have 15–20 stories across all major competencies. Here is how to build one:
- List every role on your CV. For each, write down five significant things you did or achieved.
- For each story, draft a STAR outline: two sentences on situation, one on task, four to six bullet points on action, one or two sentences with numbers on result.
- Map each story to at least two competencies. A story about navigating a team conflict might cover "teamwork," "communication," and "resilience."
- Identify gaps. If you have no stories for "commercial awareness," revisit your experience. You likely have something — a budget decision, a cost-saving idea, a market insight.
- Practise out loud. Stories that read well often sound stilted when spoken. Use ClavePrep's AI mock interview tool to practise and refine delivery before the real interview.
Industry-Specific Tips
Financial services (banking, insurance, asset management): Assessors weight commercial awareness, analytical thinking, and risk awareness heavily. Quantify every result in financial terms where possible.
Consulting: Communication, problem-solving, and client focus are paramount. Be prepared to discuss your approach to ambiguous problems and how you structure thinking.
Public sector and NHS: Adaptability, teamwork, and customer (patient/citizen) focus are heavily assessed. Emphasise collaboration across diverse stakeholders and use of constrained resources.
Technology: Problem-solving, initiative, and adaptability are highly valued. Include technical context but translate outcomes into business impact.
Retail and consumer goods: Customer focus, resilience, and commercial awareness dominate. Use retail-specific metrics: conversion rates, basket size, NPS, footfall.
Whatever your industry, ClavePrep offers mock interviews tailored to your target role and sector, giving you feedback on both content and delivery before the real thing.