The short version: confidence in an interview comes from preparation, not personality, and the biggest mistake people make is rehearsing polished answers instead of rehearsing clear thinking. Learn the shape of the answer, not the script, and have three or four real stories ready that you can bend to fit whatever question lands. Everything else, the posture, the eye contact, the handshake, is decoration on top of that.
Confidence is not a personality trait, it's a preparation habit
I've sat on both sides of the interview table for the best part of thirty years, first as a candidate, then running my own businesses, then as someone brought in to help hiring managers work out why their interview process kept producing the wrong hires. Here's what I noticed. The candidates who came across as confident weren't the naturally chattier ones. They were the ones who'd clearly done the work beforehand. Confidence, in an interview, is 90 percent preparation wearing a calm face.
I remember interviewing a woman for a marketing coordinator role years ago at a small agency I was consulting for. She wasn't the most naturally outgoing person in the room, quite quiet, but every answer she gave had a shape to it: a situation, what she did, what happened, what she'd do differently now. She got the job over two candidates who were far more sociable but whose answers wandered all over the place. Confidence read as competence. It nearly always does.
Start with the questions that get asked
Most interviews, whatever the industry, circle around the same handful of questions. If you prepare for these, you can handle almost anything else that gets thrown at you:
- Tell me about yourself
- Why do you want this job?
- What's your biggest weakness?
- Tell me about a time you dealt with conflict
- Where do you see yourself in five years?
- Why should we hire you over someone else?
Notice none of these are about facts and figures. They're all fishing for the same thing: can this person think clearly under a bit of pressure and talk about themselves without either bragging or shrinking. That's the whole game.
"Tell me about yourself" is not an invitation to your life story
This one trips up more people than any other question, because it sounds open-ended and people treat it like small talk. It isn't. It's a request for a 60 to 90 second professional summary: what you do now, one or two relevant achievements, and why you're sitting in that chair for this specific job. Not your childhood in Manchester, not your divorce, not your gap year. I've heard candidates burn four minutes on this question and watched the interviewer's eyes glaze over by minute two.
Time yourself practising this one out loud. Sixty to ninety seconds. Say it into your phone, listen back, cut anything that isn't earning its place.
The uncomfortable truth about the STAR method
Everyone tells you to use STAR, situation, task, action, result, for behavioural questions like "tell me about a time you handled conflict." It's decent advice as far as it goes. But here's what nobody says out loud: interviewers can hear a memorised STAR answer from a mile off, and it often costs candidates the job rather than winning it for them.
I've watched hiring managers physically switch off when a candidate's answer sounds too clean, too rehearsed, like they've recited it in the mirror forty times. It comes across as coached rather than genuine, and interviewers start wondering what the real, messier version of the story looks like. The fix isn't to abandon structure, it's to know the bones of three or four real stories from your work history well enough that you can tell them slightly differently every time, in whatever order the question demands, with the natural pauses and ", let me back up" moments that real speech has. Structure in your head, not a script in your mouth.
Pick stories from your actual work. A time a project went sideways and you fixed it. A time you disagreed with a manager and how it resolved. A time you had too much on and had to prioritise ruthlessly. Know these four inside out and you can answer probably 80 percent of behavioural questions by picking the closest fit and adjusting the ending.
Handling "what's your biggest weakness" without lying or oversharing
This question has become a bit of a joke because everyone's heard the trick answer, "I work too hard" or "I'm a perfectionist." Interviewers hear that and mentally roll their eyes. It signals you either didn't prepare or you think they're stupid.
The better approach: name something real but not disqualifying for the role, and show what you've done about it. If you're going for a role that requires a lot of client-facing work and you know you tend to avoid confrontation, say that, then give a specific example of a time you pushed through it and what changed. It's more convincing because it's specific and it's true, which is exactly what confidence sounds like when you hear it out loud.
Prepare differently depending on the type of role
The questions shift depending on what you're going for, and treating every interview the same is a mistake I see constantly. Someone interviewing for a remote data analyst role is going to face technical scenario questions about how they'd handle messy data or conflicting stakeholder requests, and needs to prep concrete examples, not soft skills waffle. Someone interviewing for a work-from-home medical transcriptionist position is far more likely to get questions about accuracy under time pressure and how they manage a home working setup with no one checking on them. And someone going for one of the many virtual assistant roles aimed at parents working flexibly will get questions about juggling multiple clients and boundaries, because that's the actual worry on the hiring manager's mind, whether they say it out loud or not.
Work out what the hiring manager is nervous about for this specific role and prepare an answer that quietly puts that nervousness to rest, even if they never ask the question directly.
Use AI to rehearse, not to write your answers for you
This is where I'll say something that might sound odd coming from someone who talks about AI for a living. I think AI is brilliant for interview prep and terrible if you use it wrong. Plenty of candidates now ask a chatbot to write out perfect answers to common questions and then try to memorise them word for word. Don't. It comes across exactly as stiff and unnatural as it sounds when you read it back, because it is.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
What works instead: describe your actual work history to an AI tool and ask it to pull out three or four strong behavioural examples you might be underselling, or ask it to play interviewer and fire follow-up questions at your answers so you get used to being pushed for specifics. I've written before about good ways to prompt AI tools for useful business thinking, and the same principle applies here: ask it to challenge you, not perform for you.
The mechanics that change how confident you sound
Some very unglamorous, practical things make a bigger difference to how confident you come across than any clever answer content:
- Pause before answering, even for a second and a half. Silence reads as thoughtful, not slow.
- Slow your speech down by about 20 percent from how you'd talk to a friend. Nerves speed people up and it makes you sound flustered even when you're not.
- Answer the question that was asked first, in one sentence, before you go into the story. "Yes, I've handled that before" then tell the story. Don't make them wait to find out if you're answering yes or no.
- Bring one question back for them at the end that shows you've thought about the role beyond the job description. Not "what's the culture like," something specific about a challenge the team is likely facing.
Where the nerves come from, and what fixes them
Most interview nerves aren't about the questions at all, they're about not knowing what's coming. That's fixable with volume of practice, not affirmations. Do five or six mock interviews with a friend, a partner, a career coach, whoever, using the actual questions above, out loud, not in your head. The difference between someone who's said an answer out loud five times and someone who's only thought it is enormous, and it's the single biggest lever for sounding confident that I know of.
I'll also say this because it doesn't get said enough: some nerves in an interview are fine, expected, even a slightly good sign. Interviewers aren't looking for zero nerves, they're looking for someone who can function well despite them. Trying to eliminate every flicker of nervousness is the wrong goal and it makes people over-rehearse to the point of sounding robotic, which brings us right back to the STAR problem above.
What good preparation looks like the night before
Not cramming. Not rereading the job description forty times. Three specific things: reread your own CV and remind yourself of the details you might have forgotten, look up the company's last twelve months, any funding, any launches, any leadership changes, and run through your three or four core stories out loud once, timing yourself. Then stop. Interviews rewarded to the most well-rested, calm version of a prepared candidate, not the most exhausted, over-drilled one.
Frequently asked questions
How do you stop your voice or hands from shaking in an interview?
Slow your breathing before you walk in, four seconds in, six seconds out, for a minute. Physically it lowers your heart rate and your voice steadies with it. It's not a trick, it's basic physiology, and it works better than any positive thinking exercise.
Is it okay to say "that's a great question, let me think for a second" before answering?
Yes, and it's better than filling silence with "um" while you scramble. A short pause reads as composed. Just don't overuse the phrase itself, once or twice in an interview is fine, five times sounds like a verbal tic.
What's the biggest mistake people make when answering "why should we hire you"?
Listing qualities about themselves without tying them to what the role needs. Match your three strongest points directly to the job description language, and give one brief example for each, rather than a general list of adjectives.
Should you memorise your answers word for word?
No. Memorise the structure and the key facts of your stories, not the sentences. Word-for-word answers sound flat and fall apart the moment an interviewer asks a follow-up question you hadn't scripted for, which happens in almost every interview.
Related reading: What Is the May 13 Date Shown on Instagram Reels? and How Do You Learn Prompt Engineering Basics for AI Tools? A Straight Guide for 2026.
