A cover letter has one useful job: connect your strongest evidence to one employer's actual need. It isn't a second resume. It isn't a storage box for every task you've ever handled. Think of it as a short case for why the role fits you and why hiring you could make sense to the team.
Write one when the employer requires it, asks for it, or gives you a real reason to add context. An optional letter earns its place when it explains a career move, ties a project to the job, or shows that this employer was a deliberate choice. Generic enthusiasm is not enough. Use that time on the resume instead.
Many readers skim. Put the proof close to the top.
Should you send a cover letter?
Start with the application instructions. A job board or an employer's ATS may provide a separate upload field, a text box, or no place for a cover letter at all. Follow that setup rather than forcing an attachment into the wrong part of the application.
A required letter is non-negotiable. An optional one needs to add evidence that the resume cannot show easily. If nobody asks for one, leaving it out is usually fine, particularly when the platform limits documents or says not to attach additional files.
Your decision can be simple:
- Required: Send a tailored letter.
- Optional: Send one if it strengthens your case.
- Not accepted: Do not work around the application.
- No instruction: Use your judgment, based on the role and your story.
Generic letters create more reading without much more information. A focused letter shows how your experience connects to the actual work.
Gather evidence before drafting
Turns out, the blank page feels less intimidating after you collect the raw material first. Start with the job posting, your resume, and information the employer publishes about itself. Add your own notes, too.
| Source | What to capture |
|---|---|
| Job posting | The role title, main responsibilities, repeated skill terms, and the problem the hire will solve |
| Resume | Two or three achievements with real measures, tools, scope, or business results |
| Employer research | The product, customer, team, or initiative that gives you a specific reason to apply |
| Your own notes | Why this role fits, what you want to explain, and which gap needs an honest bridge |
Pay attention to verbs and nouns that appear more than once. Repeated language often points to the work the employer cares about most. Borrow those terms only when your experience supports them.
For technical applications, the University of Chicago Career Advancement resume and cover letter resources recommend highlighting specific tools and projects and linking a relevant portfolio. Your letter should explain what that evidence means. A project link alone is not a story.
Use a simple cover letter structure
Most letters fit comfortably into 250 to 400 words on one page. Relevance matters more than hitting an exact count.
Keep the header compact. Include your name, phone number, email address, date, employer, and role. If you can verify the hiring manager's name, use it. If you cannot, "Dear Hiring Manager" works. Guessing does not.
Give the first paragraph one job: identify the role and establish your strongest connection. Use the next one or two paragraphs for selected proof. Close by connecting your interest to the employer and inviting a conversation.
A useful letter answers four questions:
- What role do you want?
- What have you already done that relates to it?
- Why does this employer make sense for you?
- What would you like to discuss next?
Your resume records the evidence. The letter explains the connection.
A seven-step workflow for writing the letter
-
Read the posting for the actual problem.
Look past the title. Is the employer trying to improve delivery, support more customers, replace a departing specialist, or build a new function? If the posting makes that need clear, answer it in your opening. -
Mark the language you can support.
Pull out the skills, tools, responsibilities, and outcomes that match your background. Use "stakeholder management" only if you have managed stakeholders in a meaningful setting. -
Choose two or three proof points.
Do not select every achievement you like. Choose the ones closest to this role. Each should show what you changed, how you changed it, and what happened next. -
Write the opening around evidence.
Begin with a result, relevant project, or clear reason for applying. The first sentence does not need to announce that the job exists. -
Connect the evidence to this employer.
Explain why your example matters here. The connection could involve the company's customer, product, workflow, technical environment, or stated priority. -
Handle gaps without apologizing.
Career changes, limited experience, and employment gaps need context. They do not need a long defense. Name the transferable skill, then show where you have already used it. -
Trim, test, and proofread.
Remove repeated resume bullets, vague praise, and unsupported claims. Check every name, title, tool, number, and attachment before submitting.
Write an opening that earns the next paragraph
A good opening gives the reader one reason to continue. That is enough.
| Weak opening | Stronger direction |
|---|---|
| "I am writing to apply for the position." | Lead with a relevant result or responsibility: "In my current role, I reduced [process or cost] by [verified measure] by [method]." |
| "I have always admired your company." | Name a specific product, customer, or priority: "Your work on [specific initiative] connects directly to my experience with [relevant area]." |
| "I am a hardworking team player." | Show the behavior: "I coordinated [project or group] across [teams] to deliver [verified result]." |
| "Although I lack direct experience, I am eager to learn." | Bridge the gap: "My background in [related field] has prepared me to handle [shared responsibility]." |
Two or three sentences can do the job. Stop when the match is clear.
Turn resume achievements into useful evidence
Choose a few accomplishments, then explain why they belong in this letter. More skills do not automatically make a stronger case. They can make the letter harder to follow.
Use this pattern:
What you did + how you did it + measurable result + why it matters here.
Here is the basic shape:
At [employer], I redesigned [workflow] using [tool or method], changing [verified measure] from [before] to [after]. That experience matches your need for someone who can [responsibility from the posting].
Metrics may describe time, quality, volume, revenue, cost, adoption, or scope. Use real numbers only. If you cannot verify a figure, describe the result honestly without adding false precision.
Context helps even when a number is unavailable. "Improved efficiency" tells the reader very little. "Reduced manual reporting time for the finance team" gives the result a clear setting.
The letter can also hold work that never fit neatly into a resume bullet. Explain the difficult handoff you untangled, the project you owned from start to finish, the customer problem you solved, or the decision that changed the outcome. That extra meaning is where the narrative earns its space.
Make the letter ATS-friendly without chasing a score
Thing is, no cover letter can be optimized for every applicant tracking system. Some systems may index uploaded text. Others may store the letter as a separate attachment for a recruiter to open later.
Use a clean document that works in either situation.
| Formatting choice | Use this approach | Avoid this approach |
|---|---|---|
| Keywords | Repeat relevant job terms naturally and spell out an acronym once when useful | Stuffing every phrase from the posting into one paragraph |
| Layout | Use a single column, readable font, standard margins, and normal section labels | Text boxes, decorative graphics, columns, or images containing text |
| Contact details | Put your name and contact information in the document body | Relying only on a header or footer |
| File format | Follow the employer's stated format and preview the uploaded file | Sending the wrong file type or an unreadable scan |
| Content | Match skills you can discuss in an interview | Adding tools, certifications, or experience you do not have |
Use the spelling from the posting when it accurately describes your background. Spell out "customer relationship management (CRM)" once if useful, then use CRM afterward when the paragraph gets crowded.
An ATS matching tool can reveal vocabulary differences between your letter and the posting. Its score is not a hiring verdict. A readable, truthful letter matters more than a striking number from a third-party checker.
Use AI as an editor, not as your source of facts
AI can compare a job description with your resume, suggest a structure, and flag missing evidence. It cannot verify your work history. It also cannot decide whether a claim sounds like you.
A prompt pattern described by ResumeGenius's ChatGPT cover letter guidance starts with the job description and resume. That is a sensible way to provide the inputs. The result still needs your review.
Try a prompt like this:
Using the job description below and my resume, identify three genuine matches between my experience and the role. For each match, quote the relevant job requirement, name the evidence from my resume, and explain the connection. Then draft a one-page cover letter using only those facts. Flag any requirement I cannot support instead of inventing experience. Keep the tone direct and natural.
Ask for the gaps first. Ask for polished prose second. That order usually gives you a more useful draft.
Read every sentence afterward. Delete inflated language, unsupported results, and phrases you would never say aloud. AI can produce a draft in seconds, yes, and that can save time, but the finished paragraph may still have stretched the result, missed the logic, or borrowed a voice that does not belong to you.
To be honest, rewriting one awkward paragraph yourself can be faster than polishing ten generic ones. Keep confidential employer information and unnecessary personal data out of the tool.
Cover letter example for a software engineering role
This sample uses placeholders. Replace every claim with a detail you can verify.
[Your Name]
[Email] | [Phone] | [LinkedIn or portfolio]
[Date]
Dear [Hiring Manager Name],
[Company] is hiring a [Software Engineer role] to improve [specific product, service, or workflow], and that need connects closely with my work on [relevant area]. At [Employer], I [specific action] using [relevant tools], changing [verified measure] from [before] to [after].
My work also crosses [engineering, product, QA, or customer teams] to turn [technical or customer need] into [deliverable]. On [project], I [specific contribution], which resulted in [verified outcome]. Your posting emphasizes [job term one] and [job term two]. I have used both in [specific context], rather than simply listing them on my resume.
[Company] interests me because [specific, researched reason tied to its product, customer, or engineering priority]. I would welcome a conversation about how my experience with [relevant strength] could support [team goal]. Thank you for your time and consideration.
Sincerely,
[Your Name]
The first paragraph establishes fit. The second supplies proof. The last explains motivation without piling on praise.
Adapt the message to your situation
The structure can stay familiar while the evidence changes. Your strongest example depends on the kind of transition you are making.
| Situation | What to emphasize | Example direction |
|---|---|---|
| Entry-level | Coursework, internships, volunteer work, campus projects, and tools you have actually used | "In my capstone project, I used [tool] to solve [problem], then presented the result to [audience]." |
| Career change | Transferable responsibilities and a clear reason for the move | "Managing [old function] taught me to [shared skill], which is why I am moving toward [new role]." |
| Remote role | Written communication, independent planning, documentation, and distributed collaboration | "I coordinated [work] across [teams or locations] using [tools], keeping decisions documented and visible." |
| Internal promotion | Results already delivered, institutional knowledge, and the next responsibility you are ready to take on | "Since joining [company], I have [verified contribution], and I am ready to apply that experience to [new scope]." |
To be honest, an entry-level applicant does not need to pretend a class project was a full-time job. State the setting clearly. Then show the work and the result.
Career changers should name the transferable skill directly. Do not make the reader connect every dot alone.
Remote applicants should show how they organized work, communicated progress, documented decisions, or kept a project moving without constant supervision. "Self-motivated" by itself is weak evidence.
Common mistakes and their repairs
Most of these problems have a quick repair. First, identify what the sentence fails to prove.
| Mistake | Better repair |
|---|---|
| Repeating the resume in paragraph form | Select two or three achievements and explain why they matter to this role |
| Opening with generic enthusiasm | Start with a result, relevant project, or employer-specific connection |
| Using every keyword in the posting | Choose terms supported by your actual experience |
| Claiming a precise result you cannot verify | Use a truthful description or confirm the number first |
| Explaining a career gap for half the letter | Give brief context, then return to the value you bring |
| Addressing the wrong person | Verify the name or use "Dear Hiring Manager" |
| Letting AI write in a polished but unfamiliar voice | Rewrite the draft until the wording sounds natural to you |
| Sending the same letter everywhere | Keep a base template, but change the opening, proof, and employer connection |
A template can save time. It should not erase why this application is different.
Submit the file carefully on job boards and hiring platforms
Good writing can still fail during upload. Follow the employer's requested file type, then inspect the preview after submission.
A text box calls for short paragraphs and plain formatting. An attachment should have a clear filename, such as FirstName_LastName_CoverLetter.pdf, unless the employer gives you another convention.
Keep a master document. Make a separate copy for each application. Before sending, check that the role title, employer name, contact name, and examples all belong to the current job.
For an email application, use a subject such as [Role] - [Name]. Attach only the documents requested. Open the final version yourself first; a successful upload does not prove that the file is readable.
Questions job seekers often ask
Do recruiters still read cover letters?
Reading practices vary by employer, role, and application process. Write one when it is required or when it adds useful context. It should not be expected to rescue a weak or poorly matched resume.
How long should a cover letter be?
Aim for roughly 250 to 400 words and one page for most roles. A shorter letter is fine when the evidence is clear. Go longer only when the employer asks for more detail.
Can ChatGPT write my cover letter?
It can compare the job description with your experience and create a first draft. You remain responsible for every fact, number, name, and claim.
Do applicant tracking systems read cover letters?
Some systems may index the text. Others store the letter separately. Use normal formatting and relevant keywords, but write for the human who may open the file.
Open the job posting and copy five repeated terms into a blank note. Write a verified resume example beside each term. If you cannot find evidence for one, do not force it; choose another strength or address the gap honestly. Then draft the opening from your strongest match and open the uploaded file once more before you click submit.