Resume examples/Research Assistant Resume
Research assistant resumes get read by two very different audiences and have to work for both. The PI or graduate student running the lab is reading for methods fluency — did you actually do the procedure, can you actually run the assay, do you know what the analysis pipeline does. The university HR system or program coordinator is reading for keyword density — does the resume have the methods, software, and lab skills the posting names. Most undergrad RA resumes lose to one or the other: too vague to clear HR, too generic to convince the PI.
The fix is the same fix that works for tech resumes: every bullet has a specific method, a specific tool or instrument, and a specific output. "Helped with research" gets cut. "Ran 32 western blots probing for phosphorylated ERK1/2 across a 4-condition treatment series; results were included in the lab's 2025 JBC submission" makes it through. This page walks through how to write that, plus a free tool that adapts your resume to lab-specific or methods-specific RA postings in two minutes.
The signal
Methods named explicitly — PCR, Western blot, ELISA, flow cytometry, qPCR, immunohistochemistry, mass spec, fMRI analysis, EEG, behavioral coding. PIs scan for these.
Software and tools by name — R, Python, MATLAB, SPSS, ImageJ, GraphPad Prism, FSL, FreeSurfer, Qualtrics, REDCap, DeepLabCut. Even better if a library or package is named.
Lab role and tenure — "Undergraduate Research Assistant, Smith Lab (Sep 2024 - Present, ~10 hrs/week)" — instead of "member of research team."
A specific output — a poster, a paper, a presentation, a thesis. "Conducted research" without an artifact reads as shadowing.
Awards or funded research — Goldwater, Beckman Scholar, undergraduate research grants, REUs (NSF, NIH). These trip both ATS and PI eyes.
Coursework that's relevant to the lab's domain — Genetics, Molecular Biology, Statistical Methods, Cognitive Neuroscience. A general bio major listing only intro classes is weak signal.
Before → After
These are the rewrites we actually return. No invented metrics, no buzzword padding — just the original work, surfaced more clearly.
Helped with experiments in a biology lab.
Performed 90+ Western blots and 60+ qPCR assays investigating ERK/MAPK signaling in a CRISPR-edited HeLa cell line panel; data contributed to the lab's manuscript currently in revision at Cell Reports.
Two methods named with counts, the model system (CRISPR-edited HeLa), the biological pathway (ERK/MAPK), and the publication outcome. "Helped with experiments" is invisible to a PI; this version reads like a senior undergrad.
Used R for data analysis.
Wrote R scripts (tidyverse + lme4) to fit mixed-effects models on a 412-subject longitudinal cognitive aging dataset; results were the foundation of an SfN 2025 poster I co-presented.
Specific R packages (tidyverse, lme4), specific model class (mixed-effects), dataset scale (412 subjects), and the conference output (SfN poster). "Used R" is a wasted keyword without scope.
Ran behavioral experiments with participants.
Recruited and ran 78 undergraduate participants through a 45-minute behavioral economics protocol in PsychoPy; coded the data into REDCap and ran preliminary analyses in R that the lab used to scope a follow-up fMRI study.
Participant count, session length, software used (PsychoPy + REDCap), the analysis tool (R), and the downstream impact (scoping a follow-up study). Each is keyword-rich and human-readable.
Member of the lab.
Drop. "Member of the lab" is an attendance record, not an accomplishment. Replace with a bullet that names the project, the method, and the output — even if it's small.
Keyword density
Each of these should appear at least once in your skills line and at least once in a bullet that proves you've used it.
What kills the score
RA postings often go through a department coordinator who knows the PIs in the field. Naming your PI ("Smith Lab, Department of Neuroscience") makes the credential checkable; omitting it makes the resume harder to verify. Always list the PI's last name and the department.
If you observed your senior grad student run a Western blot but never ran one yourself, don't list it. PIs ask method-specific interview questions and notice when an applicant can't answer them. "Observed" or "shadowed" is honest and still valuable; "performed" is a different claim.
"Performed statistical analyses" without a software, a method (t-test, ANOVA, mixed-effects, regression), or a domain tells the reader you used a calculator. Replace with specifics — even a basic t-test in SPSS named explicitly is a stronger bullet.
Posters and papers should include all author names in the actual presentation order, with yours in bold. "Presented research at SfN" hides your contribution; "Smith J, Patel A, Lee K, Cardenas M (Cardenas M presenting). Title. SfN, 2025." makes your role clear.
FAQ
Yes. Always. "Undergraduate Research Assistant, Smith Lab (Department of Neuroscience), Stanford University" is the standard format. The lab name and PI signal credibility and let the reader (often another academic) place the work in context.
Yes — but format them honestly. Posters that have been presented: list the venue and year. Papers in revision or under review: list with status ("in revision at Cell Reports" or "under review at JBC"). Don't list manuscripts that haven't been submitted; "in preparation" gets discounted.
If you've done a summer research program (REU, Amgen Scholars, university SURF), lead with that. If you've done coursework with a strong project component (a senior thesis class, an independent study), describe the project the same way you'd describe lab work — methods, output, tools. If you've done neither yet, apply to one this term — even a few weeks of basic lab work translates better on a resume than coursework alone.
If you're applying for a research-track role (RA, lab tech, post-bac, grad school), include it if it's above 3.5. PIs and admissions committees do read it. Below 3.5, it's optional — leave it off if your science GPA is stronger and list that instead, or if your research output is strong on its own.
A separate "Lab Skills" or "Methods" section under the experience section, organized by category — Wet lab (PCR, Western blot, cell culture), Software (R, Python, ImageJ), Statistics (mixed-effects models, ANOVA, regression). PIs scan this section first. Don't bury methods inside paragraph-form bullets.
Read the posting's required methods and software, and verify each one appears in your resume. Mirror the lab's domain language — if they say "computational neuroscience," use "computational neuroscience" rather than "neuro research." Lead with the project and methods that match the posting's focus. Or paste the posting into our tailor tool and we'll do the matching in two minutes.
Paste the JD, upload your resume, get the tailored version with match score, missing keywords, and rewritten bullets — usually under fifteen seconds. Your first one is free.
Related roles
real bullet rewrites, the section-leading and grading keywords on every TA posting, and a free tool that tailors your resume to any course or department in 2 minutes.
real bullet rewrites, the SQL/Python/Tableau keywords recruiters search, and a free tool that tailors your resume to any JD in 2 minutes.
Also worth reading