What the number is measuring
Speaking pace is reported in words per minute: the number of words in your transcript divided by how long you spoke. Veracue scores interview pace against a target band of 140 to 170 words per minute. Sitting inside that band is what the feedback treats as a well-paced answer; noticeably above or below it is what gets flagged.
That band isn't arbitrary, but it isn't a law of nature either. It reflects where relaxed, articulate conversational English tends to sit — fast enough to carry energy, slow enough that a listener can process meaning in real time while also forming a judgement about you. Audiobook narration and news reading are typically slower, because the listener has no other job. Excited conversation between friends runs faster, because comprehension matters less than momentum. An interview needs both, and that dual load is what makes the middle range work.
Treat it as a target band, not a score to optimise. A 172 wpm answer is not worse than a 168 wpm one. What the number is good for is catching a pattern you can't see from the inside — that you consistently run at 195, or drop to 110 when a question catches you off guard.
What rushing signals
Speaking quickly is not itself a flaw. Plenty of sharp, senior people talk fast and are perfectly compelling. The problem is what fast speech signals in an interview specifically, where the listener has no prior read on you and is looking for evidence.
- It reads as nervousness. Rightly or not, an accelerating answer is heard as an anxious one. The interviewer has no way to distinguish "this person is naturally quick" from "this person is uncomfortable" in the first sixty seconds, and in the absence of other information they tend to assume the second.
- It reads as wanting the answer to be over. This is the more damaging one. Rushing communicates that you'd like to stop talking, which sits awkwardly next to a claim that you're enthusiastic about the role.
- It genuinely reduces comprehension. This part isn't perception. Above a certain speed, listeners retain less — particularly with unfamiliar names, numbers, and technical detail, which is exactly the content that makes an answer specific and credible. A rushed answer can contain excellent evidence that simply doesn't land.
- It removes the emphasis. Meaning in spoken English is carried substantially by contrast: the slight slowdown before an important phrase, the pause after it. At a uniformly high speed there's no contrast left, so everything arrives at the same weight and nothing stands out.
The opposite failure is real too, though less common. Consistently very slow speech — well under the band, with long gaps mid-sentence — tends to read as hesitancy or as searching for the answer rather than knowing it. If your pace is low, check the transcript before deciding to speed up: often the issue isn't the speed of the words but the gaps between them, and the fix is having a clearer plan for the answer rather than talking faster.
How to slow down without sounding laboured
The instruction "slow down" is nearly useless on its own, because most people execute it by stretching each word — which sounds patronising and is exhausting to maintain. Speaking slowly is not the same as speaking deliberately, and the second is what you're after. Better levers:
Add pauses instead of stretching words. This is the single most effective change. Keep your natural word speed and put a genuine stop at the end of each sentence, and a shorter one at each comma. Pauses lower your words-per-minute figure while making you sound more considered, not slower. Stretched words do the reverse. If you want one thing to practise from this article, it's this.
Breathe at punctuation. A full breath at the end of each sentence forces a pause, refills the air you need for the next sentence, and interrupts the rushing cycle at its source. Most fast speakers are actually breath-starved speakers — hurrying to reach the end of a sentence before running out of air, which then guarantees another shallow breath. Fix the breath and the pace often corrects itself without any conscious slowing.
Shorten your sentences. Long, subordinate-clause-heavy sentences push you to speed up because you can feel the distance to the end. Shorter sentences give you natural, frequent stopping points. This is a planning change more than a speaking one — it happens when you decide what you're saying before you start saying it.
Land the first sentence deliberately, then let go. Consciously controlling pace for a whole ninety-second answer is unsustainable — you'll drop it the moment the content gets demanding. Pace only the opening sentence deliberately. It sets the tempo for the rest, and a controlled opening tends to hold. This pairs with the pause before answering: take the two or three seconds, then start slowly.
Vary it on purpose. A monotone 155 wpm is technically in-band and still flat. Slowing for the important sentence — the decision you made, the result — and moving briskly through context is what makes an answer sound like a person talking rather than a script being recited.
Pace is difficult to self-assess because your internal sense of speed adjusts to whatever you're doing. Veracue reports your words per minute against the 140–170 band for every answer, so you can see whether an adjustment actually held or just felt like it did.
A practical way to work on it
Record one answer as you'd normally give it, and check the figure. If you're above the band, re-record the same answer with one instruction only: full stop at the end of every sentence, and a breath there. Don't try to speak more slowly. Compare the two figures.
Most people find the second attempt drops 15 to 30 words per minute without feeling slower to deliver — which is the point. The goal is not to perform a different speed; it's to remove the thing that was pushing the speed up. Then repeat it on a question you haven't prepared for, because pace under a familiar answer proves very little.