# Cover letter The letter is forward-looking, not a CV repeat. It says which of the employer's tasks the candidate will solve and how, and backs that with one or two past examples. ## Length **250-300 words of body text**, one page with the signature. Count with code. Three blocks (opening, body with bullets, closing); add a fourth only if the others are short. When adding company content, cut elsewhere instead of growing. To trim, in order: sentences that restate a bullet; a bullet that hits no posting keyword; a bullet that does, last. ## Structure 1. **Headline**: the candidate's title plus one keyword from the posting ("Platform engineer specialising in Kubernetes cost control"). 2. **Reference line**: role title and the requisition ID where the posting has one. 3. **Salutation**: the named contact ("Dear Ms Example,"); else the team ("Dear hiring team,"); never "To whom it may concern". 4. **Opening** (2-3 sentences): the role, then the single strongest match to the posting. Specific to this company, never a template opener. 5. **Why this company**, early, right after the opening: what in its work, product or direction the candidate wants to contribute to, in the posting's and the company site's terms. Only verified facts. Focus on what the candidate gives, not what they gain. If the candidate spoke to someone there, reference it here. 6. **Body**: the tasks from the posting the candidate will take on and how: approach, methods, tools. 3-5 bullets, each opening with a bold label or a verb, each specific. One or two past examples back the forward claims; include one that shows initiative. 7. **Logistics** the posting raises, in one or two sentences: start date or notice period, location or commute fit, clearance willingness, languages mapped to the employer's footprint. 8. **Closing**: brief and confident ("I would welcome the chance to discuss how I would approach ."). No begging, no over-enthusiasm. 9. Sign-off in the posting's language and local convention. ## Requirements and gaps - Every stated requirement is addressed across CV and letter (see the coverage table). A requirement the candidate lacks gets an honest bridge, since omission reads as hiding once an interviewer asks: " is not in my daily toolkit yet; it is a direct extension of my work with ." - Nice-to-haves are engaged by name where there is honest adjacency. - The posting's own terms are used where they truthfully apply. ## Voice - First person, active, warm but direct. - "I bring X, demonstrated by Y", never "I think I could". - Match the posting's language and write it natively, not as a translation. ## Checklist - [ ] 250-300 body words, counted with code - [ ] Headline is title plus one posting keyword - [ ] Requisition ID and start date present where relevant - [ ] Why-this-company section comes early and holds only verified facts - [ ] Forward-looking; at most 1-2 past examples, each backing a forward claim - [ ] Every requirement matched or bridged; no contradiction with the CV - [ ] Company name, role title and contact name correct throughout - [ ] No em dashes, no banned phrases, British spelling, Oxford comma - [ ] Language matches the posting