New Grad Cover Letter: Turning Coursework Into Evidence
Write about your strongest project the way you would write about a job: the problem, the constraint you worked under, the decision you made, and what happened afterwards. Most new grad letters fail because they describe a degree instead of describing work, and a capstone described properly reads as work.
You have more evidence than you think
The problem is not that you have nothing. It is that the three things you do have — coursework, projects, internships — get written up in a way that strips out everything a hiring manager reads for.
A normal job bullet contains a situation with real constraints, a decision that could have gone the other way, and a result that outlasted you. A capstone, a semester-long team project, or an internship where you owned one recurring thing can all contain every one of those. Most new grads reduce them to a list of technologies and a sentence about teamwork, and the evidence disappears. Your job is not to invent experience. It is to retrieve detail from experience you have.
How to write about a capstone or class project
Here is the version almost everyone writes first.
For my senior capstone, I worked with a team of four to build a full-stack web application using React, Node.js, and PostgreSQL. This project gave me valuable experience in collaboration, problem-solving, and working under deadline pressure.
Nothing there is false. It is just not information. No problem, no user, no decision, no outcome — and the technology list is the one concrete thing in it, which the reader can already see on your resume.
My capstone team built the intake tool that our university's student legal clinic still uses. The clinic was turning away walk-ins because their paper form took a caseworker about eleven minutes per student. We sat in on four intake sessions before writing any code, cut the form from thirty-one fields to nine, and shipped inside a fourteen-week semester with no budget. Intake now takes under three minutes, and the clinic has kept it running since we handed it over in December.
Same project, same four people, same stack. The second reads as work because it has what a job bullet has: a real user with a real problem, a hard constraint, a judgement call that mattered more than the tech choice, and an outcome that survived the hand-off.
When you are stuck, answer these and then write the paragraph.
- Who had the problem? A department, a client, a lab, a student group, a user you defined yourself. Name them.
- What made it hard? Time, budget, undocumented data, a stakeholder who changed their mind.
- What did you decide? The judgement call, not the framework. Scope you cut, an approach you abandoned in week six.
- What happened? Adoption, a measurement you took, or an honest "we did not finish X, but Y worked".
Describe the project accurately
A class project is a class project. Do not give it a job title, do not list your university as an employer, and do not describe a prototype three people used as a deployed product. It is unnecessary and it unravels in an interview. "My capstone team built" is a strong enough opening.
Internships and campus jobs are undersold too
The standard internship sentence is "I completed a ten-week internship at X, assisting the team with various projects." That tells a reader you were present. What they want to know is what you owned, and nearly every intern owns one recurring thing: a report, a test suite, a mailbox, a dataset. Write about that.
On the pricing team at Halvern Insurance I owned the weekly claims-lag report. It arrived as three exports that an analyst reconciled by hand every Monday. I rebuilt it in SQL and Python so it ran on a schedule, which took about four hours a week out of that analyst's Monday and made the numbers consistent enough that the team stopped arguing about which version was right.
Campus jobs count for more than people assume. A residence hall desk shift is service under pressure with a written escalation path. Running a society's budget is stakeholder management with real money. If this is your strongest material, our guide on writing a cover letter with no experience goes further on building a letter from non-job evidence, and the internship cover letter guide covers the earlier version of this problem.
What to do with your GPA
A cover letter is almost never the place for it. A GPA is a line on a resume; a letter is where you say what you did. The exceptions are narrow but worth knowing.
| Situation | What to do |
|---|---|
| Posting states a minimum GPA | Put it on the resume. One clause in the letter at most, and only if you meet it. |
| Finance, consulting, law, graduate schemes | These screen on academics. Resume line, plus honours or class rank. |
| Strong GPA, no exception applies | Resume only. Spend the letter's space on a project. |
| Mediocre GPA | Leave it off both documents unless a minimum is stated. Do not explain it unprompted. |
| Low GPA, strong upward trend | Consider a major or final-year GPA on the resume, labelled accurately as such. |
Two things to avoid. Do not round up, and do not report a major GPA as an overall GPA — both are checkable against a transcript and both end applications late that would otherwise have been fine. And do not apologise for a number nobody asked about. A paragraph explaining a 2.9 draws far more attention to it than the 2.9 would on its own.
A grade describes how you performed inside a course. A project describes how you perform on work. Only one of those is the job.
Applying when the posting asks for two years
Apply. A "2+ years" line is usually a filter written to shrink a pile, and postings routinely describe the ideal candidate rather than the acceptable one. You may still be screened out. That costs you very little.
What matters is how you handle it. Ignoring it leaves the reader to notice the gap and decide what it means. Overclaiming — counting a semester project as a year of professional work — ends badly, because the distance between a letter and a reference check is where offers die. Naming it and moving straight to the closest real equivalent reads as confidence.
You are asking for two years in a production analytics environment and I have one internship. What I would point to instead is that both projects below shipped to people outside my team and are still in use — the constraint I have worked under most is handing something to someone who has to maintain it without me.
That concedes the fact, refuses to be defensive, and redirects to a capability the posting is actually buying. It also shows you read the requirement rather than mass-applying.
The graduation-timing question
Put the date in the first paragraph and then stop talking about it. Employers need it to plan, and hiding it makes a reader assume the worst version. Three cases:
Still studying. Month and availability in one clause: "I finish my BSc in June and am available from June 15." If the role starts sooner than you can, say so plainly and let them decide.
Just graduated. "I graduated in May", then move on. The letter's job is the work, not the ceremony.
Graduated a while ago. A gap before a first role is common and rarely disqualifying, but silence invites speculation. One honest sentence closes it — contract work, caring for a relative, a certification, or a plain "I spent nine months applying into a slow market and kept building; the second project below is from that period." No apology, no elaborate justification.
Keep a project inventory before you need it
Detail decays fast. Two weeks after a capstone ends you still remember the eleven-minute intake form; six months later you do not. Keep one running document holding, for every project and internship, the four answers above plus any number you legitimately measured. Resume bullets, letters and interview stories all get drawn from it. If you draft against a posting with a tool like SwiftCover, what comes back still depends on the raw detail you kept.
A full worked letter
Fictional candidate and employer: a statistics graduate applying for a junior data analyst role at a healthcare group whose posting asks for two years.
Dear Ms. Okonjo,
I finish my BSc in Statistics at Rowan State in June and am available from June 15. Your posting describes the core of this role as turning messy operational data into something a non-technical team will act on, which is what I have spent the last two years doing.
Last summer I interned on the pricing team at Halvern Insurance, where I owned the weekly claims-lag report. It arrived as three exports an analyst reconciled by hand every Monday. I rebuilt it in SQL and Python so it ran on a schedule, which took about four hours a week out of that analyst's Monday and made the numbers consistent enough that the team stopped arguing about which version was right. It was still running when I left in August.
My capstone is closer to your work. Rowan State's student health centre was losing roughly one appointment slot in six to no-shows and wanted to know which slots to overbook. My partner and I had one semester and a de-identified extract of about 40,000 appointments. We built a model that ranked slots by risk — and then the centre told us they would not act on a score they could not explain to a patient. We cut it back to five interpretable features and handed over a one-page rule sheet instead of a model. Their front desk has used it since March.
You are asking for two years of professional experience and I have one internship. Against that, neither project above ended when the term did. Both went to people who had to keep them running without me, which is the part of the readmissions reporting in your second bullet I would expect to be hardest.
I would be glad to walk through either project in more detail.
Sincerely,
Daniel Achebe
The first paragraph gives the date and mirrors the posting's own framing. The middle two are evidence, one internship and one capstone, each with a constraint and a hand-off. The fourth handles the experience gap without apologising, and the close is one line.
Notice what is absent: no GPA, no coursework list, no paragraph about being passionate and eager to learn, nothing about what the degree taught him — only what he built with it. For the structure underneath this letter, see how to write a cover letter.