The 15 most common job interview questions, with model answers

Most job interviews are built on a handful of questions that repeat over and over. That makes them the most predictable exam you’ll ever face: work on your answers beforehand and you arrive with half the distance already covered. The goal isn’t to memorize scripts — that sounds fake and interviewers can tell — but to have your stories and key ideas thought through, so you’re not constructing them live with your nerves in charge.

Here are the 15 most frequent questions, what the interviewer is actually probing with each one, and model answers you can adapt to your own situation.

First, the STAR method

For any question that starts with “tell me about a time when…”, use this structure:

• Situation: the context, in one or two sentences.
• Task: what your specific responsibility was.
• Action: what you did (not your team in the abstract — you).
• Result: how it ended, with numbers if you have them.

A complete example, from a fictional warehouse supervisor named Carol:

“At the warehouse where I worked, we had frequent shipping errors and complaints were climbing (situation). As shift supervisor, reducing them fell to me (task). I introduced a cross-check before sealing: the person who packed an order couldn’t be the one who verified it (action). Within two months, wrong-shipment complaints dropped by more than half, and the system became standard across all three shifts (result).”

Forty seconds, concrete, verifiable. Prepare three or four stories like this from your own experience — well chosen, they cover most behavioral questions.

Questions about you

1. Tell me about yourself

This isn’t an invitation to recite your biography. They want a one-minute professional summary: present, relevant past, and why you’re here.

“I’m an accountant with six years of experience, the last three at logistics companies handling monthly closes and management reporting. Before that I worked at an audit firm, which drilled discipline with details and deadlines into me. I’m looking for a role with more involvement in financial planning, which is what drew me to this opening.”

Present, past, future connected to the role. Rehearse it out loud until it flows, because it’s almost always the first question and it sets the tone.

2. What are your strengths?

Pick two or three that are relevant to the role and prove each with a short example. “I’m organized” says nothing; “I’m organized — in my last job I coordinated three projects in parallel and none slipped” does.

3. What’s your biggest weakness?

The most feared question, and the one with the clearest formula: a real weakness + not critical for this role + what you’re doing about it.

“I struggle with delegating — I tend to want to review everything myself, and at one point that created bottlenecks. I’ve worked on it by defining which decisions each person on my team can make without me, and reviewing outcomes instead of every step. I still have to remind myself, but it’s improved a lot.”

Avoid clichés dressed up as virtues (“I’m too much of a perfectionist,” “I work too hard”) and weaknesses that are fatal for the specific role (don’t say punctuality is a struggle when applying for shift work).

4. Where do you see yourself in five years?

They want to know whether this role makes sense in your trajectory or whether you’ll leave in six months. You don’t need a master plan:

“I see myself having gone deeper into [the role’s area], ideally with responsibility for projects or people. What I know for sure is that I want to grow in this direction, and this role points exactly that way.”

Avoid both extremes: neither “no idea” nor “sitting in your chair.”

Questions about the role and the company

5. Why do you want to work here?

The question that separates people who researched from people who mass-applied. The answer needs something specific about this company — its product, how it works, a recent project — connected to you:

“I saw you’re expanding operations into [country/area], and my experience is precisely in building processes from scratch. I also like [something concrete: the product, the approach, what employees say about working there]. I feel I could contribute a lot and learn a lot at this stage.”

If your answer would work word-for-word for any other company, it isn’t ready.

6. Why did you leave (or want to leave) your current job?

Golden rule: never badmouth a previous employer, even if you have reasons. Whoever criticizes their old boss in an interview becomes, in the interviewer’s eyes, the person who’ll criticize them next. Frame the exit positively, facing forward:

“I learned an enormous amount over these three years, but I reached a point where the role had no more room to grow. I’m looking for a challenge with [what the new company offers: broader scope, a different industry, more responsibility].”

If you were laid off, say so without drama: “The company restructured and my position was eliminated” is a complete and sufficient answer.

7. What do you know about us?

Have two or three sentences ready: what they do, what sets them apart, and one recent fact (a launch, an expansion, something from their site or social channels). You don’t need a thesis; you need to show this interview mattered enough to you to spend twenty minutes researching.

8. Why should we hire you?

This is your closing summary: connect your two or three strengths to what the role needs, without comparing yourself to other candidates (whom you don’t know).

“Because I combine exactly what the posting describes: experience in [requirement 1] and [requirement 2]. And because of how I work: [a trait backed by your track record]. I believe I can contribute from week one.”

Questions about your experience

9. Tell me about an achievement you’re proud of

Pure STAR. Pick an achievement relevant to the role and, if possible, measurable. If your work doesn’t produce easy numbers, use other evidence: a process that became the standard, a client who asked to work with you again, internal recognition.

10. Describe a workplace conflict and how you resolved it

They’re not assessing whether you’ve had conflicts (everyone has) but your maturity in handling them. The structure that works: legitimate disagreement + you listened to the other side + solution + lesson.

“A colleague in sales and I kept clashing because he promised delivery dates that operations couldn’t meet. Instead of escalating, I suggested we sit down together and review the real turnaround times for each order type. We built a minimum-lead-time table he could check before committing to anything. The friction dropped, and we actually ended up working really well together.”

Avoid stories where you’re the flawless victim and the other person is the villain — they sound like an edited version of events.

11. How do you handle pressure or tight deadlines?

Don’t answer in abstractions (“I stay calm”). Tell a real high-pressure situation and what you concretely did: how you prioritized, what you communicated, what you let go. Admitting that pressure exists and showing your system for managing it is far more credible than declaring yourself immune.

12. Tell me about a time you failed

The trap sits at both extremes: denying you’ve ever failed (reads as arrogance or zero self-awareness) or choosing a devastating failure. Pick a real, medium-weight mistake, own your part without excuses, and spend half the answer on what you changed afterward:

“In my second year as a project lead, I underestimated the timeline for an implementation and committed to a date we missed. I hadn’t consulted the technical team before promising. Since then I don’t confirm deadlines without validating them with the people doing the work — I’d rather commit to a realistic date than look good for five minutes.”

Closing questions

13. What are your salary expectations?

Research the market range beforehand for that role, in that country or city, at your experience level (job boards and industry communities are a good starting point). Then answer with a range, not a single figure:

“Based on what I’ve researched for this type of role and my experience, I’m thinking of a range of X to Y. That said, I care about the full package, and I have flexibility if the project is worth it.”

If they press for a number before you know enough about the role, you can gracefully return the question: “Do you have a budgeted range for the position?” Quite often, they’ll tell you.

14. Do you have any questions for us?

Never say no — it reads as lack of interest. Bring two or three prepared, and borrow from these if you need inspiration:

• “What does success in this role look like at six months?”
• “What’s the biggest challenge the team is facing right now?”
• “What does the process look like from here, and on what timeline?”

Save vacation-and-benefits questions for when there’s an offer on the table; in the interview, ask like someone who already pictures themselves working there.

15. When could you start?

This one only requires honesty and precision: factor in the notice you owe your current employer and any pending commitments. “I need to give two weeks’ notice, so I could start from [date]” is exactly what they want to hear. Don’t promise availability you can’t deliver later.

Mistakes that ruin good answers

• Marathon answers. Past the two-minute mark, the interviewer checks out. If a topic deserves more, close with “happy to go into more detail if you’d like.”
• Speaking in “we” the whole time. Teamwork matters, but they’re evaluating you. Alternate: what the team did, and what you did.
• Criticizing past employers. We said it already, but it sinks more interviews than anything else, so it bears repeating.
• Lying or inflating. Invented stories fall apart under two follow-up questions. A modest, real achievement beats a spectacular one that can’t survive scrutiny.
• Asking nothing at the end. That’s leaving free points on the table.

Frequently asked questions

Should I memorize my answers word for word?

No — memorize structures and ideas, not scripts. Practice each answer out loud two or three times, using different words each time. That way you’ll sound prepared but natural in the interview, and you won’t freeze if you forget “the exact phrase,” because there isn’t one.

What do I do if they ask something I didn’t prepare?

Buy time naturally: “Good question — let me think about that for a second.” Three seconds of thoughtful silence come across far better than a rushed answer. And if you don’t know something technical, honesty with a plan wins: “I haven’t worked with that tool, but I know [equivalent] well, and this is the kind of thing I pick up quickly.”

Do my answers change depending on whether I’m talking to HR or my future manager?

The core content is the same; the emphasis shifts. With HR, your trajectory, motivation, and company fit carry more weight; with the direct manager, technical details and concrete examples of how you work matter more. Prepare your stories with both layers: the summary, and the technical detail in case they ask for it.

What if they ask something inappropriate (marital status, plans for children)?

In many places those questions don’t belong in a hiring process. You can redirect without confrontation: “I’d rather focus on the professional side — as for my availability and commitment to the role, [answer].” How they handle your redirect also tells you something valuable about that company.

---

Preparation doesn’t eliminate nerves, but it converts them into usable energy: you walk in knowing that no core question will catch you blank. Rehearse out loud, ideally with someone firing the questions at you, and remember that every interview — however it goes — is training for the next one. And to make sure there is a next one, RápidoEmpleo lists new openings from around the world every day so you can keep applying.