Leadership Interview Questions: 20 Common Questions & Worked STAR Answers

In my second year at university, I was elected president of our student entrepreneurship society with 200+ members. The society had run the same format events for three years, attendance had dropped to under 20 people per event, and the executive committee was frustrated and disengaged.

My goal was to rebuild the society's reputation and engagement within a single academic year, with the annual pitch competition in May as the flagship event — a concrete, measurable target.

I started by running a one-hour committee workshop to identify the root cause of the problem — we landed on the fact that our events weren't practical or relevant to what students actually needed. I restructured the programme around three pillars: industry speaker nights, CV and application workshops, and a mentorship scheme connecting students with alumni. I delegated ownership of each pillar to a committee member with autonomy and a quarterly review. I kept the team aligned through a shared project tracker and weekly 15-minute standups.

By the end of the year, average event attendance had risen from 18 to 75. Our annual pitch competition had 12 competing teams and 140 attendees — up from 3 teams and 40 the previous year. Three committee members went on to found their own ventures. The society was named "Most Improved Society" by the students' union.

During a summer internship at a logistics company, I was assigned to a cross-functional team of four people from operations, IT, and finance to redesign our returns tracking process. The project had already stalled twice — people disagreed on scope and priorities.

My role was as project coordinator, not manager — so I had no formal authority. I needed to establish a shared direction the team could commit to within a week, or the project would miss the quarter's deadline.

I ran a structured 90-minute session where I asked each team member to articulate what success looked like from their function's perspective, then mapped the overlaps and conflicts. From this I drafted a one-page project brief with three agreed objectives and a prioritised feature list. I sent it to the team for 48-hour async review, incorporated their edits, and got everyone to sign off on the final version. This created shared ownership of the direction.

The project delivered on time — a new returns dashboard that reduced processing time by 30% and eliminated the weekly manual reconciliation that had been taking a finance analyst four hours per week. The team's manager commented specifically on how I had aligned a difficult group.

During a charity fundraising event I was organising for 80 people, the venue cancelled with 48 hours' notice due to a double-booking. The team was panicking and several volunteers were suggesting we cancel.

I needed to find an alternative venue, communicate clearly to attendees and sponsors, and keep the volunteer team motivated — all within 48 hours.

I immediately called an emergency team meeting and explicitly framed it as: "We're not cancelling. Here's what we need to do in the next six hours." I split the team into three groups — venue, comms, and logistics — and gave each a clear owner and a three-hour deadline. I took the venue search myself, called 15 local venues, and secured a hotel function room at a discounted emergency rate. I drafted the attendee communication personally to control tone.

The event ran successfully with only a two-hour time change. We raised £4,800 for the charity — 15% above our original target — and several volunteers said afterwards that the crisis had actually made the team more cohesive. The event was written up positively in the university's student paper.

On a work placement at a retail company, I was acting supervisor for a shift when a member of staff had a personal emergency and needed to leave immediately — leaving us two people down during the busiest trading hour of the day.

I needed to immediately reallocate responsibilities across five remaining team members, manage customer expectations during the peak period, and make sure I handled the departing colleague with appropriate sensitivity.

I prioritised the customer-facing role first — I took the register myself and asked our most experienced team member to move from stock to the floor. I was transparent with the two remaining colleagues: "We're short-staffed for the next hour — I need extra support from everyone and I'll make sure we document it." I called our manager to brief them before they heard from someone else.

Customer wait times remained within acceptable levels. My manager commended the handling in our next one-to-one and noted that I had managed up appropriately by communicating proactively rather than letting them find out later.

During a university group project worth 40% of a module grade, two team members had a significant disagreement over the project direction — one wanted a quantitative analysis-heavy approach; the other felt qualitative case studies would score better. The conflict was causing delays and affecting team morale.

As the self-designated project lead, I needed to resolve the conflict, restore team cohesion, and make a clear decision on direction — without alienating either person — within one week before our interim deadline.

I met with each person individually first to understand their perspective fully — before making any judgment. I identified that the disagreement was partly substantive (genuinely different views on what would score best) and partly interpersonal. I then brought them together in a structured conversation where each had 5 minutes to present their case, and I facilitated the discussion toward a hybrid approach that incorporated both elements. I made the final call clearly, explained my reasoning, and assigned each person a section they'd advocated for.

The project was submitted on time and received a First Class grade (72%). More importantly, the team finished in good working order — both members sent positive messages afterwards about how the conflict had been handled. The hybrid approach was specifically highlighted positively in the marker's feedback.

As chair of a student committee, one of our longest-standing members was consistently missing deadlines and not delivering on commitments. The rest of the committee was frustrated, and it was affecting our project timeline.

I needed to have an honest performance conversation with a peer — someone who wasn't formally "below" me — without damaging the relationship or causing them to disengage entirely.

I scheduled a private one-to-one in a neutral setting and led with curiosity rather than accusation: "I've noticed things have felt harder for you recently — I want to understand what's going on before we talk about anything else." It emerged they were going through a difficult personal period. We agreed a reduced and restructured set of responsibilities for the rest of the term, with explicit deadlines, and I checked in weekly.

They completed their remaining commitments on time and thanked me for the conversation at the end of year. The rest of the committee could see that the situation had been handled, and it reinforced trust in how I was running the committee. I learned that difficult conversations handled with empathy first are more effective than accountability-first approaches.

During an internship, I identified that our team's client reporting process was producing inconsistent outputs — each analyst formatted reports differently, which was causing confusion in client meetings. I was the most junior person on the team.

I wanted to propose and implement a standardised template without stepping on colleagues who had more experience and longer tenure. I had no authority to mandate any change.

I built a prototype template in my own time, gathered specific examples of the inconsistency problem (including client feedback that had mentioned confusion), and presented it to one trusted senior analyst first to get their input and buy-in. With their support, I presented the template at a team meeting framed as "something I've been experimenting with — I'd value everyone's input." I incorporated the feedback from that session and sent the revised template to the team lead for approval.

The template was adopted and became the team standard for the rest of my internship and beyond. The team lead cited it specifically in my end-of-internship review as an example of initiative and stakeholder management. I learned that presenting a draft solution (rather than just a problem) dramatically increases the probability of adoption.

During a group university project, one team member became noticeably less engaged after we received critical feedback on our midpoint presentation. They stopped contributing in meetings and submitted work late.

As the group's informal lead, I needed to re-engage them before the final submission in three weeks — both for the project's sake and because their disengagement was affecting team dynamics.

I met them informally over coffee rather than in a formal team setting. I asked how they were finding the project and listened rather than immediately problem-solving. It emerged that they felt the critical feedback had been "aimed at them" specifically. I reframed the feedback as a team-level issue and explicitly told them what I valued about their contribution. I then gave them ownership of a specific section they were interested in and encouraged them to take the lead on presenting it.

They re-engaged significantly in the final three weeks and delivered the presentation section confidently. Our final submission received a high 2:1 (67%). They thanked me after, saying it was the first time they'd felt recognised on a group project. I reflected that recognition — not pressure — is what drives re-engagement in most cases.

As a senior member of my university's debate team, I worked with a newer member who had strong arguments but struggled with nerves during speeches — they would lose their structure under pressure.

I volunteered to mentor them for two months before a regional competition in which they would compete for the first time.

I ran weekly 30-minute sessions with them — not on argument construction (which was already strong) but specifically on managing nerves: structured breathing exercises before speaking, a three-word keyword system to hold structure when under pressure, and deliberate practice under uncomfortable conditions (presenting to a larger group than they were used to). I gave them specific, actionable feedback after every practice rather than general encouragement.

At the regional competition, they advanced to the semi-final — the furthest any first-year team member had progressed in three years. They credited the structured preparation specifically. I learned that targeted skill development — focused on one specific constraint rather than overall improvement — drives faster progress.

During a part-time retail job, I noticed that our store's returns process was being handled differently by different staff — some offered exchanges, some refunds, and some escalated to the manager for every case. Customers were receiving inconsistent service and managers were being interrupted constantly.

No one had asked me to address this — it wasn't my responsibility as a part-time sales assistant. But the inconsistency was clearly causing customer dissatisfaction and manager frustration.

I drafted a simple one-page decision tree for returns based on our existing policy and asked my manager if I could share it at the next team briefing. They agreed. I presented it informally, framed it as a helpful reference rather than a formal process, and asked for feedback. Within two weeks it had been printed and placed at every till.

Manager interruptions for returns decisions dropped noticeably. Customer complaints about inconsistent treatment reduced. My manager mentioned it specifically in my performance review as an example of taking initiative beyond my role. I learned that a simple, practical solution shared in the right framing can have an outsized impact.