Numbers appear constantly in technical discussions — uptime SLAs, latency percentiles, throughput multipliers. Saying them correctly signals fluency and prevents misunderstandings in incident reviews and stakeholder meetings.
0 / 5 completed
1 / 5
An SRE reports: "Our service has achieved 99.9% uptime this quarter." How is 99.9% spoken aloud in a presentation?
99.9% → "ninety-nine point nine percent":
Reading decimal percentages in English follows a clear pattern:
The decimal point "." is always spoken as "point" — never "comma" (that's European convention)
"percent" is always singular — never "percents"
Each digit after the decimal point is read individually: ".9" = "point nine", ".95" = "point nine five"
SLA uptime examples and how to say them:
Written
Spoken
99.9%
"ninety-nine point nine percent"
99.99%
"ninety-nine point nine nine percent" (four nines)
99.999%
"ninety-nine point nine nine nine percent" (five nines)
100%
"one hundred percent"
Informal shorthand: "Four nines" = 99.99%, "five nines" = 99.999% — common in SRE conversations:
"We target four nines availability"
"We're at three nines right now"
2 / 5
A performance engineer says: "The P99 latency is 450ms." How is P99 spoken aloud?
P99 — "P ninety-nine" (casual) or "ninety-ninth percentile" (formal):
In performance engineering, Pxx notation stands for percentile:
P99 = the 99th percentile — 99% of requests complete in less than this time
Casual speech: "P ninety-nine" — the letter P then the number
Formal speech: "the ninety-ninth percentile" — used in presentations and reports
The full percentile vocabulary:
Written
Casual
Formal
P50
"P fifty"
"fiftieth percentile" (= median)
P95
"P ninety-five"
"ninety-fifth percentile"
P99
"P ninety-nine"
"ninety-ninth percentile"
P99.9
"P ninety-nine point nine"
"ninety-nine point ninth percentile"
Usage in context:
"Our P99 latency is under 200 milliseconds"
"The P50 (median) is 20ms, but the P99 is 450ms — there are outliers"
3 / 5
An engineering manager presents: "The new architecture gives us a 3x throughput improvement." How is 3x said aloud?
3x → "three ex" or "three times" — both are used:
The "x" multiplier notation is common in tech contexts and has two natural spoken forms:
"three ex" — casual, common in engineering conversations: "We got a three-ex speedup"
"three times" — formal, clear for mixed audiences: "three times faster", "a three-times improvement"
The multiplier vocabulary:
Written
Casual
Formal
2x
"two ex"
"twice" or "two times"
3x
"three ex"
"three times"
10x
"ten ex"
"ten times" or "an order of magnitude"
0.5x
"point five ex"
"half the speed"
Note on "2x": For exactly double, "twice" is the most natural English form — "twice as fast", "twice the throughput" — rather than "two-ex" or "two times".
4 / 5
A developer describes a bug: "It only affects 0.5% of users." What are the accepted ways to say 0.5%?
0.5% — "zero point five percent" or "half a percent":
Both forms are widely used and correct. Context and register determine which fits best:
Form
When to use
"zero point five percent"
Technical reports, dashboards, precise data contexts
"half a percent"
Presentations, casual team discussions, explaining to non-technical stakeholders
"nought point five percent" (British)
British English — "nought" = 0, very common in UK professional contexts
British vs American "zero":
American English: "zero" for 0 — "zero point five"
British English: both "zero" and "nought" /nɔːt/ for 0 — "nought point five" is very common in formal UK contexts
More small percentages:
0.1% = "zero point one percent" or "one tenth of a percent"
0.01% = "zero point zero one percent" or "one hundredth of a percent"
1% = "one percent" — simple!
5 / 5
A backend engineer reports: "After optimisation, we now handle 2.5K RPS." How is 2.5K RPS spoken in full?
2.5K RPS — multiple correct spoken forms:
K in tech contexts means "kilo" = 1,000. So 2.5K = 2,500.
Both ways of expressing this are correct:
Spoken form
Natural in...
"two point five thousand requests per second"
Technical conversations, keeping the K notation
"two thousand five hundred requests per second"
Formal presentations, stakeholder meetings
"two-five hundred RPS" (informal)
Engineering team chat — very casual
How to expand RPS: "R-P-S" = requests per second — always spell out the full phrase in formal speech, but "R-P-S" is fine in team conversations.