Hiring Reality · Reading Between the Lines
What 600 Reviews Taught Me About Reading Between the Lines
Quick summary — what 600 reviews taught me
The strongest reviews describe behaviour, not adjectives. After reading 600 candidate reviews, I learned that the line "would hire again" is safe, while "I'd fight to hire again" almost always follows a story of how the candidate handled something difficult.
In this guide you will learn:
- Why surface praise hides more than it shows — and why interviewers learn to skip it.
- The behaviour line — the one sentence that reveals real ownership.
- Seven patterns from 600 reviews — that recur across roles.
- How to read between the lines — as an interviewer.
- How to write a better review — as a colleague.
SECTION 01Why surface praise hides more than it shows
A review that says "very confident candidate" tells you almost nothing. A review that says "handled the client escalation alone on day three" tells you almost everything. The first is an adjective. The second is evidence.
After reading 600 reviews, I noticed a pattern: the reviews that praised skills rarely predicted performance. The reviews that described behaviour under pressure did.
| Review Line | What It Suggests | What It Hides |
|---|---|---|
| "Very confident candidate" | Positive presence | Whether confidence was backed by depth |
| "Strong technical skills" | Prepared | Whether the depth survived a follow-up |
| "Good communication" | Fluent | Whether fluency came with clarity or with deflection |
SECTION 02The behaviour line that reveals ownership
There is one review line that consistently predicted strong hires better than any other. It is not about skills. It is about what the candidate did when something went wrong.
Surface review:
"Confident candidate. Strong communication.
Good technical skills. Would hire again."
Signals: nothing specific.
Reads like a template.
Predicted poorly in 600 reviews.Behaviour review:
"When the deployment broke on day two,
they took ownership, traced the issue
through the logs, and led the fix.
They explained the trade-offs clearly
to the client and stayed calm."
Signals: ownership, debugging,
communication under pressure,
real judgment.
Predicted strongly in 600 reviews.SECTION 03Seven patterns from 600 reviews
These seven review patterns recurred across roles — from data analysts to DevOps engineers to business analysts. Each one reveals more than the review line above it.
| Surface Line | Behaviour Line | What It Reveals |
|---|---|---|
| "Very confident" | "Handled the tough question by pausing, then answering." | Judgment under pressure |
| "Good communicator" | "Explained the trade-offs to a non-technical client." | Stakeholder awareness |
| "Strong technical skills" | "Traced a bug through the logs without help." | Real debugging depth |
| "Team player" | "Volunteered to own the hardest piece." | Ownership, not just presence |
| "Learns fast" | "Asked three sharp questions about the domain in week one." | Curiosity with intent |
| "Reliable" | "Delivered the same quality on the last Friday as the first Monday." | Consistency under fatigue |
| "Would hire again" | "I'd fight to hire again." | Strong, earned impression |
SECTION 04How to read between the lines
Reading between the lines is a skill that can be built. The next time you read a review, ask three questions.
- Is there a specific situation? — a client call, a deployment, a deadline, a failure.
- Is there a decision? — what did the candidate choose, and why.
- Is there a trade-off? — what did the candidate accept in exchange for the outcome.
If a review cannot answer these three questions, it is surface praise. If it can, it is a real signal.
SECTION 05How to write a better review
If you write reviews — for peers, for reports, or for hires — here is the single most important change: replace adjectives with behaviour.
-
Before: "Very confident."
After: "When a senior challenged their answer, they paused, restated the assumption, and then defended it clearly." -
Before: "Good communicator."
After: "Explained a complex migration to a client in plain language, without losing the technical nuance." -
Before: "Would hire again."
After: "Handled the hardest week of the project better than anyone on the team. I would hire them again without hesitation."
SECTION 06Interview Q&A — reading between the lines
Q1Why do surface reviews fail?
Because they are not specific. "Confident" or "good communicator" is the same for a strong candidate and a well-rehearsed one. Only behaviour differentiates them.
Q2What is the single best question to ask when reading a review?
"What did the candidate actually do?" If the review cannot answer this, it is surface praise and should be treated with caution.
Q3What is the strongest review line?
"I'd fight to hire them again." It is rare, and it is almost always earned. It signals that the candidate made a lasting, specific impression.
Q4How many reviews before patterns appear?
Around 200–300 reviews — you start noticing the same surface adjectives and the same underlying behaviours. By 600, the pattern is unmistakable.
Q5Can this skill apply to my own resume?
Absolutely. The same logic applies: write behaviour and outcome, not adjectives. "Improved the dashboard" becomes "reduced load time by 40% by restructuring the query."
SECTION 07Test yourself — reading between the lines quiz
Five questions. No sign-up.
0 / 5Pick an answer to see why it is right or wrong.
SECTION 08Frequently asked questions
Why do behaviour lines reveal more than adjectives?
Because adjectives are generic. Behaviour lines describe what the candidate actually did, in a specific situation. They are harder to write and much harder to fake.
What is the difference between a positive review and a strong review?
A positive review is polite. A strong review is specific. A strong review tells you what the candidate would look like on their worst day — not just their best.
Can I use this framework for my own work?
Yes. Whenever you describe your work — in a resume, a review, or an interview — replace adjectives with specific behaviours and outcomes.
What if I have never written a review?
Start with your own projects. Write one line about the decision you made, one line about the trade-off, and one line about the outcome. That practice will carry into reviews.
How does this relate to interviews?
Interviewers use the same principle. They probe for behaviour, decisions, and trade-offs — not adjectives. Candidates who prepare behaviour stories are the ones who stand out.
SECTION 09Related reads
Classroom & online · Noida
Learn to read the signal, not the noise
Our Data Analytics Training Course teaches you how to build behaviour stories, interview with specificity, and read signals in your own work and others'.
₹15,500 · full programme- Behaviour-based interview practice
- Specific review writing
- Mock interviews with feedback
- Weekday & weekend batches