Reading - Long Text

The Interview That Writes Back

People talk about job interviews as if they were neutral instruments: you turn up, you answer questions, you are measured, and a decision is made. That is the official story, anyway. In practice, the interview is a piece of writing in disguise. It has a narrative arc, a cast of characters, a hidden genre (thriller, farce, courtroom drama), and—crucially—an author. Sometimes that author is you. If that sounds fanciful, consider what most candidates do in the first five minutes. They choose a version of themselves and then spend the rest of the meeting trying to keep that version consistent. They edit as they go, trimming awkward details, expanding the parts that sound purposeful, and inserting linking phrases that make the plot hang together. ‘I was looking for a new challenge’ is not information; it is a transition. ‘I thrive in ambiguity’ is not a fact; it is a tone. Even silence can be punctuation. The interviewer, meanwhile, is rarely the detached reader candidates imagine. They are usually a co-writer with deadlines. They have a vacancy to fill, a team to protect, and a set of constraints they may not disclose. Their questions often look open-ended—‘Tell me about a time you handled conflict’—but function like prompts in a structured exam. They are checking for evidence, yes, but also for coherence: can you select relevant detail, can you sequence it, can you land on a point without wandering into subplots. This is why the most common interview advice is both true and misleading. ‘Be yourself’ is true in the sense that fabrication is exhausting and easy to detect. It is misleading because you cannot bring your entire self into a forty-minute slot any more than you can fit a novel into a paragraph. What you can do is choose an angle that is honest and useful. The strongest candidates do not sound like flawless heroes; they sound like reliable narrators. They admit uncertainty where it existed, show what they did with it, and make the outcome legible. Yet interviews are not only about the candidate’s story. They are also about the organisation’s. A company that asks nothing beyond technical trivia is often signalling that it values immediate output over growth. A panel that keeps interrupting may be revealing more about its internal culture than about your communication skills. Even the way feedback is handled—whether you receive a clear rejection, a vague ‘we went another way’, or silence—tells you what kind of writing you can expect once you are inside: precise, evasive, or absent. The awkward truth is that many interviews fail because both sides cling to clichés. Candidates arrive armed with ‘strengths and weaknesses’ that could belong to anyone, and interviewers respond with generic questions that produce generic answers. The result is a meeting full of language that sounds professional but communicates very little. When that happens, decision-making gets outsourced to gut feeling: who felt ‘confident’, who seemed ‘a good fit’. That is not necessarily malicious; it is what people do when the text in front of them lacks detail. A better approach is to treat the interview as collaborative drafting. Candidates can prepare a small set of stories that demonstrate specific behaviours—prioritising under pressure, learning fast, recovering from mistakes—and adapt them to the prompts they are given. Interviewers can ask fewer questions and listen longer, pushing for concrete examples rather than polished slogans. When both do this, the interview produces something closer to a shared document: a realistic picture of how the person works and what the role actually demands. Ultimately, interview writing is not about sounding impressive; it is about being interpretable. The best interviews leave both parties with a clear sense of what happened, what could happen next, and what the risks are. That clarity is not a talent reserved for extroverts. It is a craft: selecting, shaping, and telling the truth in a way that can be understood under time pressure.

Questions