Pavone

Answer Readability Analyzer

Check if your interview answer is clear, concise, and easy to follow when spoken aloud. Get actionable feedback to improve clarity.

Paste your answer and click "Analyze Readability" to see results

Interview answers are heard, not read

When you write, the reader sets the pace. They can reread a long sentence, pause over an unfamiliar word, and skip a parenthetical. When you speak, the listener gets each word once, at your speed, with no way back. Everything that makes writing dense, such as subordinate clauses, long noun phrases and asides, becomes a cost the listener pays in attention.

This is why a readability target for a spoken answer should be easier than for a written document on the same topic. An interviewer is also doing several things at once: listening, forming an impression, planning the next question, taking notes. The simpler your sentences, the more of their attention goes to the content of your answer rather than to decoding it.

Three differences matter most. A reader can take a 30-word sentence; a listener loses the subject by around word 20. A reader can look up a word; a listener experiences an unfamiliar word as a gap. A reader gets headings and paragraphs; a listener gets only the structure you say out loud. Short sentences, familiar words and explicit signposting are the spoken equivalents of good formatting.

What makes a spoken answer easy to follow

Sentence length

Aim for an average of 12 to 18 words, with some sentences shorter than that for contrast. The longest sentence matters more than the average: a single 40-word sentence will lose the room even if everything around it is tidy. A practical test is breath. If you need to breathe in the middle of a sentence, it is two sentences.

One idea per sentence

"I led the migration, which was delayed because the vendor changed their API, though we eventually shipped it in March after I renegotiated the timeline" contains four ideas: you led it, it was delayed, why, and how it was rescued. A listener can hold one at a time. Split it, and each idea lands before the next one arrives.

Signposting

Tell the listener the shape of the answer before the content. "There were two problems." "The short answer is yes, and here is why." "That was the situation; here is what I did." Signposts do the job that headings do on a page: they let the listener file what they hear as they hear it, and they make it obvious when you have finished.

Concrete over abstract

"I cut onboarding from three weeks to four days" is easier to follow and more convincing than "I improved operational efficiency." Numbers, names, dates and specific actions are easier to picture, easier to remember and harder to doubt. Whenever you hear yourself saying "improved", "optimised" or "enhanced", ask what actually changed and say that instead.

Active voice

"I fixed it" is three words. "The issue was resolved" is four, and it leaves out the only fact the interviewer wanted: who resolved it. Passive voice is not grammatically wrong, but in an interview it hides the thing you are there to show. If a sentence has no "I" or "we" doing something, rewrite it until it does.

Jargon, buzzwords and filler

Three kinds of words add length without adding meaning. Jargon is technical vocabulary the listener may not share; it is fine with a specialist interviewer and a problem with anyone else. Buzzwords are corporate words that sound substantial and mean nothing: synergy, leverage, drive alignment, value-add. Filler is the noise you make while thinking: um, like, basically, you know, sort of.

The fix for jargon is to assume the interviewer is intelligent but not on your team. The fix for buzzwords is to say the concrete thing the buzzword is standing in for. The fix for filler is silence: a pause reads as thoughtful, a filler reads as uncertain, and they take the same amount of time.

Instead ofSay
utilizeuse
facilitaterun, help, organise
leverageuse
implementset up, build, roll out
in order toto
at this point in timenow
going forwardfrom now on
on a daily basisevery day
stakeholdersthe people involved: the sales team, the client, my manager
synergieswhat actually got better, with a number
methodologymethod, approach
basically, essentially, actuallynothing; delete them

A before-and-after rewrite

Here is a real-sounding answer to "Tell me about a process you improved", written the way many people draft it:

"So, basically, in my previous role I was responsible for the implementation of a new onboarding methodology, which was something that had been identified as a priority by senior stakeholders due to the fact that the existing process was being perceived as inefficient, and it was ultimately successful in terms of reducing the time required."

That is 62 words in one sentence. It has three passive constructions, no number, no named action and no clear statement of what the speaker personally did. Read aloud, it takes about 20 seconds, and at the end of it the interviewer knows only that something about onboarding changed.

The same content, rewritten for speech:

"In my last role, onboarding took new hires three weeks. My manager asked me to fix it. I interviewed ten recent hires, cut the process to four steps and wrote the checklist myself. New hires were productive in four days instead of three weeks."

That is 45 words in five sentences, averaging nine words each. Every sentence is active, every claim is concrete, and the result is a number the interviewer can write down. The rewrite is shorter and carries more information, which is the usual pattern: clarity is not a matter of cutting content, it is a matter of cutting everything that is not content.

How to read your scores

The analyser above reports a handful of metrics. Here is what each one measures and what to aim for in a spoken answer.

MetricWhat it measuresTarget for spoken answers
Readability (Flesch Reading Ease)Sentence length and syllables per word, scored 0 to 100; higher is easier60 or above
Grade level (Flesch-Kincaid)The school grade at which the text is comfortably readable7 to 10
Passive voiceShare of sentences built around "was done" rather than "I did"Under 10 percent
Average words per sentenceTotal words divided by sentence count12 to 18
Long sentencesSentences over 25 wordsZero
Word countTotal length100 to 200 for most questions

What the score cannot tell you

The formula counts syllables and sentence length. It does not know whether the content is any good. An answer with no example, no result and no evidence of what you did can still score an A. Use the score to catch structural problems, then judge the content yourself: is there a specific story, did you say what you personally did, and is there an outcome the interviewer could repeat to a colleague?

How to practise clearer answers

Readability on the page is the first check, not the last. Once the text scores well, the question is whether the clarity survives being spoken under pressure.

  • Read the answer aloud. Anywhere you stumble, the sentence is too long or the word is wrong. Simplify and read it again.
  • Record yourself and listen back the next day. You will hear where you lost the thread far more clearly than you felt it at the time.
  • Apply the one-breath test: if any sentence needs a breath in the middle, split it.
  • Deliver the same answer three times, each time shorter. The third version is usually the one to keep.
  • Ask a friend to listen once and repeat the answer back to you. Whatever they leave out is the part that did not land.
  • Practise the pause. Before each answer, breathe out, then begin. That one habit removes most filler.

Check how it sounds, not just how it reads

This analyser scores the text. What matters in the room is the voice. Pavone runs mock interviews that transcribe your spoken answers and score pace, filler words and structure, so you can confirm that an answer which reads clearly also sounds clear when you have to say it to someone.

Frequently asked questions

What is a good readability score for an interview answer?

Aim for a Flesch Reading Ease score of 60 or higher. That corresponds to plain, conversational English that a listener can follow in real time. Written documents can get away with 50; spoken answers should be easier, because the listener cannot go back and reread a sentence they lost.

What is the Flesch Reading Ease score?

A formula that scores text from 0 to 100 based on average sentence length and average syllables per word. Higher is easier. Around 60 to 70 is plain English, 80 or above is very easy, and below 30 is dense academic prose. It is a rough proxy, not a judgement of quality, but it reliably flags long sentences and heavy vocabulary.

What grade level should my interview answer be?

A Flesch-Kincaid grade level of 7 to 10 is a good target for spoken answers, regardless of how senior the interviewer is. Grade level measures sentence and word complexity, not intelligence. Senior people appreciate clear speech more than most because they listen to a lot of it.

How long should a spoken interview answer be?

Most answers should take 60 to 120 seconds, which is roughly 100 to 200 words at a normal speaking pace. Short factual questions need less. If the analyser shows more than 300 words you are almost certainly saying things the interviewer would rather ask about.

How many words per sentence is ideal when speaking?

An average of 12 to 18 words, with no single sentence over 25. The average matters less than the longest sentence: one 40-word sentence will lose a listener even if everything around it is short. If you need a breath in the middle of a sentence, it is two sentences.

Is passive voice bad in interviews?

Mostly, yes. "The project was delivered on time" hides the thing the interviewer wants to know: who delivered it. Active voice ("I delivered it on time") is shorter, clearer and takes credit where you earned it. Keep passive constructions under about 10 percent of your sentences.

Why does my answer sound fine written down but confusing out loud?

Because a reader controls the pace and a listener does not. On paper you can reread a long sentence, skim a parenthetical, and look up a word. Spoken, each of those becomes a gap where the listener loses the thread. Writing that reads well is usually too dense to be spoken well; spoken answers need shorter sentences, more familiar words and explicit signposting.

How do I stop using jargon in interviews?

Assume the interviewer is smart but not from your team. For every technical term, ask whether they would use it themselves; if not, replace it with what it means. Corporate words such as leverage, synergy, stakeholder and methodology are worse than technical jargon because they signal nothing at all. Swap them for the concrete thing: the sales team, the method, the result.

How do I stop saying um and like?

Filler words are a habit for avoiding silence. Replace the filler with the silence: pause, breathe, then continue. Record yourself answering three questions and count the fillers; most people are surprised. Awareness and a deliberate pause before each answer cut them quickly.

Does a high readability score mean my answer is good?

No. The score measures sentence length and word complexity. An answer can score an A and still have no example, no result and no reason to hire you. Use the score to catch structural problems, then judge the content separately: is there a specific story, did you say what you personally did, and is there a concrete outcome?

Does the analyser work for languages other than English?

The syllable counting and the complex-word list are built for English, so scores for other languages are not reliable. The underlying advice still transfers: short sentences, one idea per sentence, active voice and concrete words make a spoken answer easier to follow in any language.

Can I use this for presentations or sales pitches?

Yes. Anything that will be heard rather than read benefits from the same checks: presentation scripts, pitch openers, demo narration, voicemail scripts. The targets are the same, and the before-and-after pattern in the guide above applies directly.

Start practicing in minutes

AI Roleplays for any scenario

  • Build a roleplay from your scenario
  • Practice with AI, voice to voice
  • Get instant, structured feedback after practice
  • Free to start — no credit card required