T format cover letter: the two-column requirement-match letter and when it works

What a T format cover letter actually looks like

The letter opens with a short paragraph, usually two to four sentences, stating the role you want and a single strong reason you are a fit. Below that sits a two-column table. The left column is headed something like 'Your requirements' or 'What you need'. The right column is headed 'My experience' or 'What I bring'. Each row pairs one requirement from the job posting with one concrete piece of your background. After the table, a closing paragraph of two to three sentences invites next steps.

The name comes from the shape: the opening paragraph runs the full width like the top of a T, and the two columns form the stem. Some writers skip the closing paragraph and end with the table, but that reads as abrupt. Keep the closing.

• Opening paragraph: role, employer, one headline qualification
• Left column: exact language from the job posting, three to six rows
• Right column: specific evidence matched to each row
• Closing paragraph: availability, call to action, contact

When the T format works best

The format earns its keep in three situations. First, when the job posting is highly specific. If a posting lists six discrete requirements with clear language, a T format lets you address each one without burying them in prose. Second, when you are a career changer. Mapping transferable skills directly against stated needs removes the guesswork for a reader who might otherwise dismiss your background. Third, when you know the letter will be read by a non-specialist first, such as a recruiter who is screening against a checklist rather than evaluating depth.

It works less well for creative roles, senior leadership positions, or any application where the employer signals they want to understand your thinking and voice. A chief marketing officer role, for example, calls for a letter that demonstrates strategic reasoning, not a table. Academic applications in the UK and Australia, where a personal statement is the norm, are also poor fits.

• Good fit: technical roles with a defined skills list
• Good fit: government and public sector jobs with published selection criteria
• Good fit: career changers mapping transferable skills
• Poor fit: creative, editorial, or design roles
• Poor fit: executive and C-suite applications
• Poor fit: academic or research positions

How to build the table row by row

Pull the requirements directly from the posting. Use the employer's exact words in the left column, not your paraphrase. If the posting says '5 or more years of experience with SQL', write that. Do not soften it to 'database experience'. Matching the language helps with any automated screening and shows you read carefully.

In the right column, lead with a number or a named outcome wherever you can. Vague claims like 'strong SQL skills' waste the space. Specific claims like '7 years writing production queries at a fintech startup, including a migration that cut report run time by 40%' give the reader something to verify and remember. Aim for one to two sentences per row, no more. If you cannot be specific, that requirement may be a gap worth addressing in the opening paragraph instead.

1. Copy the requirement verbatim from the posting into the left cell
2. Identify the single strongest piece of evidence you have for that requirement
3. Open the right cell with a number, a named employer, or a named outcome
4. Keep the right cell to one or two sentences
5. Repeat for three to six requirements, stopping before the table becomes exhausting to read

Formatting rules that keep it readable

Keep the table simple. One border style, no shading, no merged cells. Most applicant tracking systems in 2026 still struggle with complex table formatting, and a corrupted table looks worse than no table at all. If you are submitting through an ATS portal, paste the letter as plain text and replace the table with a bulleted list using a clear label before each pair, for example: 'Requirement: 5 or more years SQL. My experience: 7 years, including...'

Font size should match the rest of your application documents, typically 10 to 12 point. The table should not run longer than half a page. If you have more than six rows, cut the weakest matches rather than shrinking the font to fit. A tight, confident table of four rows beats a sprawling one of nine.

The opening and closing paragraphs

The opening paragraph does two things: it names the role and it gives the reader one reason to keep reading. Do not list three reasons. Pick the strongest one. For example: 'I am applying for the Senior Data Engineer role at Meridian Health. I have spent the past six years building real-time pipelines in healthcare data environments, which maps directly to the infrastructure work described in your posting.' That is enough. The table will carry the detail.

The closing paragraph should be two to three sentences. Confirm your availability for an interview, note any relevant constraint if it is relevant (such as a notice period), and give your preferred contact method. Avoid phrases like 'I look forward to hearing from you at your earliest convenience'. They add nothing. Try instead: 'I am available for a call any weekday after 10 a.m. Eastern. You can reach me at the email above.'

Using Break-In Bad to match requirements accurately

The hardest part of a T format letter is identifying which requirements to include and finding the right evidence from your own history. Break-In Bad's assistant Omar reads the full job posting, including buried requirements around location, visa status, and experience level, and writes a tailored cover letter from facts you confirm. Because the letter is built from what you have actually said about your background, the right column of your table stays honest and specific rather than generic. Each letter costs credits from a pack starting at $9 for 25, and there is no subscription.