Research and lab assistant positions are among the most common early-career roles for students in science, social science, and policy programs. They are also among the most poorly written on resumes. The typical bullet reads something like this:
- Assisted professor with ongoing research on climate adaptation policy.
That sentence tells a hiring manager almost nothing. It does not say what you did, what you produced, or what skill you demonstrated. Here is how to fix it.
Why Research Bullets Go Flat
Research work often feels like a supporting role, so candidates default to passive language: assisted, helped, supported, contributed to. The problem is that these words describe your relationship to the project, not your actual work. Every research assistant "assists." What distinguishes you is the specific task you owned and the output you produced.
The other common mistake is leading with the research topic rather than the action. The topic is context, not evidence of skill.
The Fix: Lead With the Task, Not the Topic
Start your bullet with a verb that names something you actually did: coded, analyzed, collected, synthesized, maintained, built, ran, cleaned, wrote, presented. Then describe the object of that action. Then add context or scale if you have it.
Before: Assisted professor with ongoing research on climate adaptation policy.
After: Coded and categorized 400 interview transcripts using NVivo to support a federally funded study on municipal climate adaptation strategies.
The revised bullet tells a reader you know qualitative data software, you handled a meaningful volume of material, and the work had real stakes (federal funding). None of that required inventing anything. It just required naming what you actually did.
What to Pull Out of a Research Role
Think through the following questions to find your bullets:
- What did you do every week? Data entry, literature searches, running samples, writing summaries?
- What tools or software did you use? SPSS, R, NVivo, lab equipment with a specific name, citation managers?
- What did you produce? A database, a literature review, a dataset, a protocol, a poster?
- What scale can you attach? Number of sources reviewed, samples processed, participants recruited, hours of audio transcribed?
- Did anything you built get used downstream? If your literature summary fed into a paper or grant, say so.
A Few More Rewrites
Before: Helped run psychology experiments on memory and attention.
After: Administered standardized memory and attention protocols to 60 undergraduate participants and entered response data into a shared SPSS database.
Before: Supported lab team with general tasks.
After: Prepared reagent solutions, maintained equipment calibration logs, and trained two incoming assistants on lab safety procedures.
Notice that the last example also includes a brief training responsibility. If you ever explained a process to someone else, that is a real skill worth naming.
When You Cannot Quantify
Not every research role produces clean numbers. If you do not have a count, focus on the specificity of the task instead. "Conducted a systematic literature review across three databases" is more credible than "reviewed literature" even without a source count. Specificity does the same work that numbers do: it signals that you actually did the thing.
Research experience is strong evidence of analytical ability, attention to detail, and comfort with ambiguous problems. Your bullets just need to show the work, not just the fact that you showed up.