The Embellisher

Who The Embellisher is

This candidate did real but smaller work and consistently inflates it - a flaky test suite becomes 'I architected the entire automation framework', a team of 8 becomes 'I led QA org-wide'. The exaggeration is plausible and only collapses under specifics: numbers, timelines, and ownership boundaries don't add up.

How they mask it

You won't see the pattern in the room. You'll see the mask - the version they've rehearsed to keep it hidden. Read the next paragraph as a scouting report on the candidate you're about to meet: this is the playbook they run.

Speak confidently in big-scope language ('I owned', 'I built from scratch', 'company-wide'). On general questions sound impressive. When asked for concrete numbers (test counts, team size, coverage %, timelines) or the exact boundary of what YOU did vs the team, get fuzzy, round generously, or quietly shrink the claim ('well, the core of it'). Never admit you exaggerated.

How to catch it

The mask holds on general questions and cracks under specifics. Here is where good interviewers push, and what gives the pattern away:

Strong interviewers will: ask for specific metrics and dates, ask 'what part did you personally write vs review?', ask the same scope question twice and check the numbers match, drill into one claim end-to-end ('walk me through the first commit to that framework'). They notice the scope quietly deflates the more concrete the questions get.

Reading this won't be enough

You now know the tells. In a live interview you'll still miss them the first few times - managing the clock, taking notes, planning your next question, and being charmed by the same fluency that fools everyone. Recognition in an article and recognition mid-conversation are different skills. The second one only comes from reps.