Application English

Your RA Cover Letter Got Rejected in 15 Seconds — Here's the Sentence That Killed It

An international student's RA cover letter dies in paragraph one — not because of grammar, but because you're asking for permission instead of offering capacity.

You emailed a dozen PIs. Not one replied. You blamed spam filters, your CV, your English. You're wrong. The PI's eyes hit your first sentence, pattern-matched you to the "needs hand-holding" pile, and moved on. The real problem with international students' RA cover letters isn't language. It's register. You wrote a permission slip. They wanted a work handoff.

Here's the opener that kills 90% of these emails: ❌ "I am writing to express my strong interest in the research assistant position. I believe my academic background has well prepared me for this opportunity." Zero information. "Strong interest" is noise — the PI knows you're interested, you applied. "My background has prepared me well" is also noise — they have your CV. By sentence two, the PI has learned nothing about what you'd actually do for them.

✅ Rewrite: "I noticed your lab is now running phase 2 of the [specific project] pipeline. During my MA thesis I built a comparable extraction protocol in Python — I'd be glad to share the repo if it maps onto your current workflow." No "interest." No "opportunity." You've proven you read their paper, you've done adjacent work, and you're already thinking like a collaborator. That's what the first paragraph is for — proving you're on the inside of the problem already.

Second killer: excessive hedging. International students are terrified of overclaiming, so every sentence gets padded. ❌ "I would be most grateful if you could consider my application, as I believe my skills may perhaps be relevant to your ongoing project." You've dissolved yourself into zero. You're asking them to consider whether you might possibly be useful. That's not a capable colleague talking; that's a student auditioning for a teacher's approval. ✅ "I have 40 hours/week available this term and 2 years of [method] experience. I can integrate with your Phase 2 scripts within a week." Period. You just described a colleague's availability, not a supplicant's plea.

Third trap: the CV in prose form. ❌ "During my undergraduate studies at [university], I achieved a GPA of 3.8 and completed coursework in statistics, programming, and research methods." The PI has your CV. Restating it in a letter is a signal you don't know what else to say. ✅ Pick one experience that maps directly to what this lab does: "For [course] I built a codebook for the [dataset] and replicated [specific paper]'s model in R — I think there's a coding error in their Section 4 robustness check that I can flag if useful." One verifiable detail beats ten lines of credentials.

Fourth trap: the ending collapses back into deference. ❌ "Thank you so much for taking the time to consider my application. I look forward to the possibility of working with you." You thanked again, you hedged again, you reintroduced "possibility." A capable person's sign-off is concrete: ✅ "My CV and the codebook are attached. I'm happy to talk by email or drop by your Thursday office hours." No "thank you so much." No "look forward to." A specific next step. The power dynamic should be horizontal by line 12.

After rewriting, push the draft through easydue — not to generate text for you, but to kill the residual "student voice" you accidentally preserve after editing: the too-uniform sentence lengths, the softening filler, the excessive politeness markers. That pass takes four minutes and saves the forty you'd spend reading aloud, still uncertain. Then spend your real time on the one thing that actually moves PIs: read their last two papers, cite a specific figure or method, and show you're already part of the conversation. Your RA email doesn't fail on grammar. It fails because you never stopped asking for permission.