To answer “tell me about a time you led a project,” give the goal and why it mattered, the team and timeline, how you planned the work and kept it on track, the biggest obstacle and how you handled it, and a measured result. Interviewers are checking whether you can turn a goal into a plan, bring people with you and still deliver when something goes wrong. Choose a project you genuinely led, with a scope that matches the level of the job.
What the interviewer is checking
- Ownership of the outcome: you were accountable for the result, not just a task.
- Planning: scope, milestones, risks and how you tracked progress.
- People: roles, communication and keeping people engaged, often people who didn't report to you.
- The obstacle: what went wrong and how you responded.
- Delivery: a result you can measure, and what lasted.
The NSW Public Sector Capability Framework (Version 3, 2026) has a “Project management” capability, defined as understanding and using effective ways to plan, coordinate and control projects, and Amazon's “Deliver Results” principle asks leaders to deliver with the right quality and in a timely fashion and to rise to the occasion despite setbacks (both checked November 2026).
This is different from tell me about a time you showed leadership, which is usually about influence in a moment. Here the panel wants the arc of a project, from goal to delivery.
Match the project to the job level
| Level | A project that fits | What to emphasize |
|---|---|---|
| Entry-level or graduate | A class, volunteer, event or small workplace project with a few people over weeks | Organizing, follow-through, handling one surprise |
| Experienced individual contributor | A project within a team, with other departments involved | Planning, risks, stakeholders, a measured result |
| Project or program manager | A budgeted project with several teams and a sponsor | Scope, schedule and budget control; trade-offs; reporting |
| Manager or senior leader | A change across a site, department or customer base | Why it mattered to the business, adoption and what lasted |
If you are interviewing for a project role, expect several of these; our project manager interview questions cover the rest of the loop.
Picking the project
- You led it: you set the plan or were named lead.
- It had a deadline and involved other people.
- Something went wrong and you fixed it.
- The result can be counted: date met, people trained, adoption, cost, quality or satisfaction.
Avoid projects you joined halfway but describe as yours, projects where nothing went wrong, and projects so technical the panel can't follow. If your best project slipped, you can still use it; how to handle a project that is behind schedule shows how to tell the recovery.
A project-shaped STAR, with timings
| Part | What to cover | Time |
|---|---|---|
| Goal | What the project had to achieve and why it mattered | 15 seconds |
| Plan | Scope, milestones, team and how you tracked progress | 20 seconds |
| People | How you kept the team and stakeholders aligned | 15 seconds |
| Obstacle | The biggest problem and what you did about it | 30 seconds |
| Delivery | The result with a number, and what is still in place | 15 seconds |
| Lesson | One thing you would repeat or change | 10 seconds |
It is the STAR method stretched to fit a project: the goal is your situation and task; plan, people and obstacle are your action. Projects tempt people into three minutes of background, so cut the setup hard; how to stop rambling has techniques.
Five example project stories at different levels
We wrote these to show the shape in different jobs; they are not real candidates' stories. Use your own situation, your own numbers and your own words.
Entry-level: a university open day
Goal: As a final-year student ambassador, I was asked to lead my department's spring open day: tours, two taster lectures and a parents' Q&A for about 300 visitors, with 20 volunteer ambassadors and six weeks to plan.
Plan: I built a run sheet with a named owner for every slot, held two briefings for the ambassadors and set up a group chat for the day, with a backup for every tour guide.
Obstacle: Two days before, facilities closed the main lecture theatre for repairs. I found a smaller room nearby, split the taster lecture into two sessions, redrew the tour route, reprinted the signs that evening and emailed booked visitors their new times.
Delivery: Both sessions filled without overcrowding, the department's visitor survey rated the day above the previous year's, and my run sheet became the department's template. I now ask for a backup room at the start of planning, not the end.
Customer-facing: launching a pickup counter
Goal: I was front-of-house supervisor at a busy pizza restaurant when the owner asked me to lead the launch of a pickup counter for online orders, because pickups were crowding the host stand and slowing seated service.
Plan: I had five weeks. I mapped how an online order moved from ticket to customer, set the target that orders would be ready at the quoted time, and agreed with the kitchen manager that one person would bag and check orders at peak.
Obstacle: In the first test week, online tickets printed in the same queue as dine-in orders, so pickups ran late. I worked with our till system's support line to send online tickets to their own printer, and moved the pickup shelf next to the pass so the kitchen could see it.
Delivery: By week three, about nine in ten pickups were ready at the quoted time, the host stand was clear, and Friday-night table turns improved. The owner copied the setup at the second location.
Healthcare: moving a ward to bedside handover
Goal: As a senior nurse on a 28-bed surgical ward, I led our move from office-based shift handover to bedside handover, to involve patients and cut missed information between shifts.
Plan: I formed a working group with two nurses from each shift, adapted the hospital's handover template for surgical patients and planned a two-week pilot in one bay before rolling out to the whole ward.
Obstacle: Staff worried about privacy in shared bays and about handover taking longer. We agreed that sensitive information would be shared away from the bedside, and I timed handovers in the pilot to show they took about the same time once people were used to them.
Delivery: The whole ward switched within eight weeks, our monthly audits showed most handovers following the template by the end of month two, and patients began saying in feedback that they knew their plan for the day. Next time I would involve night staff earlier; they were the last to be convinced.
Office: moving a 60-person firm
Goal: I was operations coordinator at a 60-person architecture firm when our lease ended, and I was asked to lead the move across town without losing a working day.
Plan: I set a 12-week plan with milestones for fit-out, IT, furniture and the move weekend, kept a tracker the partners could see, and held a weekly fifteen-minute call with each vendor.
Obstacle: Three weeks out, the internet provider said our new line wouldn't be live until ten days after move-in. With our IT contractor, we set up temporary business mobile routers for the gap, tested them with the design software the weekend before, and told staff which large file transfers to schedule overnight.
Delivery: Everyone was working at their new desks at 9 a.m. on the Monday, the move came in within its approved budget, and the partners asked me to turn the plan into a checklist for the firm's other office. Lesson: confirm utility dates in writing at the very start.
Manager: rolling out a CRM to 45 sales reps
Goal: As sales operations manager at a wholesale distributor, I led the move from spreadsheets to a cloud CRM for 45 reps, with the target that every rep would log customer activity there within three months.
Plan: My project team was an IT administrator, two experienced reps and a finance analyst for pricing data. We migrated in three waves by region and agreed a weekly adoption measure with the sales director.
Obstacle: After wave one, adoption stalled at about half; reps said logging calls took too long on the road. I rode along with two of them, cut the call form from twelve fields to five and set up mobile logging. The two reps on the project team ran short sessions for their peers, which worked better than my training.
Delivery: By the end of month three, nearly every rep was logging activity weekly, and the sales director ran forecast meetings from the CRM. I learned that adoption is the project; installing the system is only the start.
Follow-up questions panels ask
- “How did you decide what was in and out of scope?” Name one thing you deliberately left out, and why.
- “How did you track progress?” The tool or rhythm, and the moment it told you something was off.
- “Who was hardest to bring along?” Have one stakeholder story ready; our guide to managing stakeholder expectations shows the shape.
- “How did you measure success?” The number you agreed at the start, ideally.
- “What would you do differently?” One concrete change, not “communicate more.”
Where project answers go wrong, and how to rehearse
- All setup, no obstacle.
- “We” all the way through: the panel needs to hear what you decided.
- Claiming a project you supported rather than led.
- No measure of success.
- Method names you can't explain. Mention Agile, PRINCE2 or a Gantt chart only if you used it and can describe it simply.
Prepare two projects of different sizes so you can match the interviewer's level, and rehearse each out loud to under two minutes. An AI mock interview builds questions from your résumé and the job description and scores each spoken answer out of 10. Drafting the parts first in the free STAR builder keeps the setup short.
Where CoPilot Interview fits
CoPilot Interview is an AI interview assistant. Use its free AI mock interview to rehearse project stories against the real job description: it reads each question aloud and scores your spoken answer out of 10. For a lighter start, the browser demo at /try has 145 questions in 10 tracks with typed answers scored out of 10, free and with no signup. The free plan gives 15 minutes a day of live help in sessions of up to 15 minutes, with AI mock interviews included. Paid plans are Standard at $24.99 a month and Pro at $39.99 a month.
For the real interview, follow your employer's rules on AI tools. AI can help you structure and tighten a story, but it must not invent one: every event, number and name in your answer has to be true and yours.
Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly.
Frequently asked questions
What is a good example of leading a project?
A project with a clear goal, a deadline and other people, where you set the plan, handled a real obstacle and can give a measured result, such as an event, a launch, a system rollout or a move.
What if I've never officially led a project?
Use a school, volunteer or workplace project you organized, and be precise about your role: “I coordinated the schedule and the volunteers” is more credible than claiming a title you didn't have.
How is this different from “tell me about a time you showed leadership”?
Leadership questions are often about one moment of influence. A project question wants the whole arc: goal, plan, people, obstacle and delivery.
Should I use a project that failed?
For this question, choose one that delivered. Keep a failed project for <a href="/blog/tell-me-about-a-time-you-failed">tell me about a time you failed</a>, where the lesson is the point.
How long should my answer be?
About 100 seconds to two minutes. Spend the most time on the obstacle and how you handled it.
Rehearse it out loud before the real one
The AI mock interview builds questions from your resume and the job description, reads them aloud and scores each spoken answer out of 10. Included on the free plan.
Start a mock interview