OfferDrill.

Interview questions

The hard ones

Tell me about a time you led a team, when you've never had the title.

This page gives you a way to answer the leadership question honestly when "manager" was never in your job title. You'll get the trap answers to avoid, a four-step build, and three sample answers you can shape around your own work.

Why they ask it

They are not checking whether you had direct reports. If they wanted that, they'd ask "how many people reported to you?" The word "led" is doing different work. They want to know if you can get a group of people to a finish line.

Underneath, they're testing three things. Do you take responsibility when nobody assigned it to you. Can you get cooperation from people who don't have to cooperate. And when it went sideways, did you handle it or wait for someone else to.

Here's the part that helps you: influence without authority is harder than managing with it. You couldn't order anyone to do anything. You had to convince them. Interviewers know that. If you tell that story well, it often lands better than "I had six reports and we hit our targets."

What not to say

"I've never really led a team, but..."

You just told them no and then asked them to keep listening. Most people stop listening. You also handed them a reason to pass on you that they hadn't thought of. Open with the work instead: "Last spring I ran the migration project. Four of us, none reporting to me."

Describing what the team did instead of what you did.

"We rebuilt the onboarding flow and cut drop-off" tells them nothing about you. The interviewer is trying to find your fingerprints. Say what you decided, what you asked people for, what you did when someone missed a date.

Inflating it into a management role you didn't have.

It falls apart in the follow-up. They ask who did your reviews, or how many people reported to you, and now you're backing off a claim. That costs you more than never having managed. Name the arrangement plainly — "I led the project, my manager owned the people" — and keep going.

A story where everything went smoothly.

Smooth stories are forgettable and slightly suspect. The interesting part of leading is the part where somebody didn't deliver, or two people disagreed, or the deadline moved. If you skip it, you've skipped the evidence. Pick a story with one real problem in it.

How to build a strong answer

  1. Pick the story where you were on the hook.
    Not the biggest project. The one where, if it failed, people would have looked at you. Common versions: you ran a cross-team project, you trained or onboarded new people, you took over when a lead left, you were the one client or vendor came to, you organized a fix during an outage or a crunch. Interns and new grads: a group project where you set the schedule counts, so does a shift you coordinated, so does a student org. Say what it actually was.
  2. Name the setup in one sentence, including the no-authority part.
    "Five of us across three teams, none of them reported to me, and we had [the actual timeframe] to ship it." That single sentence does a lot. It's honest, it sets the difficulty, and it stops them from wondering later. Then move on. Don't apologize for it or explain it twice.
  3. Spend most of your time on the specific things you did.
    Use verbs that only a leader uses. I split the work this way and here's why. I set a standing 15-minute check-in on Mondays. I went to [the person] directly when the design was two weeks late. I made the call to cut the second feature so we'd hit the date. Three or four concrete actions beat a paragraph of adjectives. If you say "I kept everyone aligned," follow it immediately with how.
  4. Include the friction, then the result with a real number or date.
    One problem, one sentence on how you handled it. Then land it: what shipped, when, and what changed. If you don't have a metric, use a fact — "we launched on [date], and it's still what the team uses." Made-up numbers get caught. Real dates never do. Then stop talking. Let them ask the follow-up.

Examples to adapt

These are shapes, not scripts. Say them in your own words with your own facts — anything in brackets is a detail only you know, and it has to be the true one.

Mid-career individual contributor who ran a project across teams.

The clearest one is the billing system migration last year. I was a senior engineer, not a manager. Five of us on it, from three different teams, and nobody reported to me. My director asked me to own the delivery. First thing I did was get all five of us in a room and write down who owned which piece, because two people thought they owned the same thing. Then I set a Tuesday standup, fifteen minutes, and a shared doc with dates. About six weeks in, the data team fell behind and we were going to miss the window. I didn't escalate right away. I sat down with their lead, found out they'd been pulled onto something else, and we agreed to cut the reporting piece from phase one so we could still ship the core. Then I told my director what we'd cut and why. We went live on [the actual date], about [the real gap] behind the original plan, with no rollback. What I'd do differently is set up the dependency check earlier. I found that problem late.

It names the no-title setup in the first three sentences and never brings it up again. Every action is something a leader does: assigning ownership, setting a rhythm, going to a person directly, making a scope call, telling leadership. The problem is real, the fix is specific, and the self-critique at the end is a genuine one, not a humblebrag.

Recent grad or early career, one internship or a school project.

During my internship at [company], three of us interns got handed the customer feedback backlog — about [the real number] of tickets nobody had sorted. There was no lead. I asked if I could take the coordination piece and my manager said go ahead. I built a simple tagging system so we weren't each inventing our own categories, and I split the backlog by product area so we weren't tripping over each other. One of the other interns was much faster than the rest of us, so I gave him the messiest section. About halfway through, we realized our tags weren't matching what the product team actually used, so I went and asked them, and we redid maybe [the real amount] of the work. It cost us a few days. We finished the whole backlog before the internship ended, and the product manager told me they were still using the tagging. I'd never organized other people's work before. The thing I learned is that checking with the person who'll use the output is worth doing on day one, not day ten.

It doesn't pretend to be bigger than it was, and it doesn't shrink either. "I asked if I could take the coordination piece" shows initiative honestly. There's a real mistake with a real cost. The closing lesson is something a 24-year-old would actually learn, which makes it believable.

Someone who filled a gap when a manager left or was out.

When our team lead left in [the month], the role sat open for about [the real length of time]. I was the most senior person on the team, so I picked up the pieces that would have dropped — the client status calls, the weekly priorities, the handoff to the other office. I want to be clear I wasn't the manager. I didn't do reviews or hiring, and people didn't report to me. But the work had to keep moving. The hardest part was that two people on the team disagreed about how to handle [the actual issue], and normally the lead would have decided. I got them both on a call, had each of them make their case, and then I made the call and said it was mine to own if it went wrong. It didn't go wrong, but the point was that they needed someone to decide. We kept the client through the gap and hit every delivery date in that stretch. When the new lead started, I wrote up everything I'd been holding and handed it over.

The honesty about what they didn't do makes everything they did do more credible. The disagreement story is the strongest part — taking ownership of a decision you might be wrong about is exactly what interviewers are looking for. The clean handoff at the end signals someone who isn't territorial.

What comes next

Answer this one well and the interviewer usually goes here:

  • How did you handle someone who wasn't pulling their weight, when you couldn't discipline them?
  • Give me an example of a decision you made that turned out to be wrong.
  • Have you ever had to give someone difficult feedback? How did it go?
  • How did you handle disagreement between two people on the team?
  • Do you want to manage people? Why or why not?
  • What would the people on that project say about working with you?
  • How is leading without authority different from managing, in your view?
  • What would you do differently if you ran that project again?

Say it out loud before it counts.

Reading a good answer and giving one are different skills, and the gap shows up in the room. Offer asks you this question out loud, on a clock, and tells you what landed. The first one is free.

Practice this out loud

You've probably done more leading than your job titles show, and the only work left is saying it plainly enough that someone else can see it.