OfferDrill.

Interview questions

The hard ones

How to answer "tell me about yourself" without rambling.

This is the first question in almost every interview, and most people either recite their resume or freeze. Here's a three-part structure, three sample answers for different situations, and the specific mistakes that cost people the room in the first ninety seconds.

Why they ask it

They're not asking for your life story. They're asking you to do the work of connecting your background to their job, so they don't have to. The best candidates hand them the connection. Everyone else hands them a timeline and hopes.

There's a second thing happening. This is the only question where you choose what the conversation is about. Whatever you put in this answer becomes the next ten minutes. If you mention the project you're proudest of, they'll ask about it. If you mumble through your last three jobs, they'll pick one at random and you'll be improvising.

And yes, they're checking whether you can talk like a person. Can you organize a thought? Do you stop when you're done? That sounds small. It isn't. If you ramble for four minutes here, the interviewer spends the rest of the hour wondering how you'd do in a client meeting.

What not to say

"Well, I was born in Ohio, went to school for business, wasn't sure what I wanted to do..."

The chronological life story. By the time you reach anything relevant, you've used your best three minutes on things that don't matter. Start at the part that's about them.

Walking through your resume job by job, start to finish.

They have the resume. Reading it out loud tells them nothing new and signals you didn't prepare anything. Pick two or three things worth expanding on and skip the rest.

"I'm a hard-working people person who's passionate about excellence."

Every candidate says this, so it doesn't separate you from anyone. Adjectives never land a point. One concrete thing you did beats five words about what kind of person you are.

Leading with the layoff, the gap, or the apology. "So, unfortunately, I was let go in March..."

You've made your job loss the topic of the interview before they even asked. They probably will ask, and you should answer it plainly then. But this question is your opening. Use it for the strongest true thing about you.

Trailing off into "...so, yeah, that's kind of me, I guess."

Three good minutes end on a shrug and the whole thing feels uncertain. Write your last sentence in advance and stop talking after it.

How to build a strong answer

  1. Start with where you are now, in one sentence.
    Your current or most recent role, and what it actually involves. "I'm a warehouse operations supervisor. I run a shift of twenty-two people and I'm accountable for our on-time dispatch numbers." If you're between jobs, say the role you had: "I spent the last six years as a claims adjuster, most recently handling commercial property." No apology, no throat-clearing. One clean sentence so they know what box you're in.
  2. Give one or two pieces of proof, not a full history.
    Pick the things that matter for this job specifically. A problem you solved, something you built, a number that moved. "Last year we were missing our dispatch window about a fifth of the time. I changed how we staged the morning loads and we got that down to [the actual figure]." If you don't have a number, use a concrete before-and-after instead. One vivid detail beats three vague claims. If you've made a career change or a big jump, this is where you explain the through-line in one sentence: "Both jobs were really about getting technical people and non-technical people to agree on a deadline."
  3. Say why you're in this room, about this job.
    Name something specific you know about the role or the company, and tie it to what you just told them. "That's why this posting caught me — it's the same problem at about four times the scale." This takes ten seconds and it's the part almost nobody does. It turns a monologue into an answer. If you're not sure what to point to, use the job description itself: "The posting talks about rebuilding the reporting process, and that's the part of my last job I liked most."
  4. Land it, then stop.
    End with a full stop, not a trail-off. "So that's the short version — happy to go deeper on any of it." Then close your mouth. Silence for two seconds feels like an hour to you and normal to them. Aim for sixty to ninety seconds total. Say it out loud with a timer three times, not into a mirror and not from a written script. You want the shape in your head, not the words.

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, laid off, hasn't interviewed in years.

I've spent the last nine years in accounts payable, the last four as a team lead at [company], where I ran a group of five and owned the month-end close. The thing I'm proudest of there is the invoice backlog. When I took over, we were about [the actual number] invoices behind and vendors were calling constantly. I rebuilt the approval routing and got us current in [the actual timeframe], and we stayed current after that. My role was cut in [month] when they consolidated the finance team into the Dallas office. I've been using the time to finish my [certification or course, if true]. What drew me to this role is that you're describing a similar cleanup — the posting mentions standardizing the AP process across three sites, and that's the work I'm best at. That's the short version.

The layoff gets one flat sentence in the middle, stated as a business decision, with no apology and no explaining. It's answered, so it's defused. The center of gravity is the backlog story, which is what they'll ask about next. Use your real numbers and your real dates — the structure is what you're borrowing, not the content.

Recent grad, one internship.

I finished my marketing degree at [school] in May. The most useful thing I did there wasn't a class — it was my internship at [company], where I spent the summer on their email program. I ended up rewriting the subject lines for their weekly newsletter and testing them, and open rates went from about [figure] to [figure] over six weeks. It was the first time I saw how small a change can be and still move a number. Outside of that I've been running the Instagram for [organization], which is about [size] followers and taught me a lot about what people actually click on. This role stood out because it's hands-on with the email and social side rather than strategy from a distance, and that's the part I want to get good at first.

It doesn't apologize for being new. It picks the one experience with a real result and goes deep on it instead of listing coursework. The last line says something honest about what they want to learn, which reads as self-aware rather than overconfident. Swap in your real project — the point is picking one thing, not covering everything.

Changing fields, or coming back after time away.

For eleven years I was a high school science teacher, and for the last three of those I ran our department's scheduling and testing logistics — about [number] students, a lot of moving parts, a lot of people who needed different things at the same time. I left teaching in [year] and moved into project coordination at [company], where I've been managing [type of project] timelines for the last [timeframe]. The honest connection between the two is that both jobs are mostly about keeping fifteen things visible at once and telling people bad news early. I saw this role is coordinating across the clinical and IT teams, which are two groups that don't naturally speak the same language, and that's the specific thing I'm good at. Happy to go into any part of that in more detail.

It names the career change directly instead of hoping nobody notices, then answers the question the interviewer was already forming: what carries over? The through-line is one sentence and it's concrete. If there's a gap in there, you can name it the same way — one sentence, plainly, then move to what's next.

What comes next

Answer this one well and the interviewer usually goes here:

  • What made you leave your last role? (Or: why were you let go?)
  • Walk me through that project in more detail — what was your actual part in it?
  • What have you been doing since [the end of your last job]?
  • Why this company? Why this role, specifically?
  • What would you want to be doing in three years?
  • What's something you're not good at yet?
  • Tell me about a time that went badly.

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 get to decide what this answer is about, which makes it the one question you have the most control over — spend twenty minutes on it tonight and you'll walk in already ahead of where most people start.