What would I be working on in my first month?

A specific answer names a project, a technique, and a person. A vague answer usually means the role was posted because a grant allowed a hire, not because the work is defined, and you will spend your first month inventing your own job.

Is this position attached to one project, or does it float across the lab?

Single-project roles give you depth and a clean line on a CV. Floating roles give you variety and a real risk of becoming the person everyone hands their leftover tasks to. Neither is wrong, but you should know which you are accepting.

Who would I report to day to day?

In most labs the person hiring you is not the person supervising you. If the answer is a senior graduate student or a postdoc, ask how long that person has left, because your direct supervisor leaving in eight months changes the job entirely.

How many people are in the group, and what is the mix of students, postdocs, and staff?

The ratio tells you how much attention exists to go around. A large group with one faculty member means you learn from peers. A group that is mostly staff scientists is a more stable place to learn technique and a slower place to get on papers.

What does a typical week look like in terms of hours at the bench, at a computer, and on admin?

Many research assistant roles are half lab management: ordering, scheduling, compliance paperwork, keeping the freezer inventory honest. That is normal, but if it is sixty percent of the job you want to hear it now rather than discover it in March.

Professional & Academic

Questions to Ask an Interviewer for a Research Assistant Job

Questions for the end of a research assistant interview, when the principal investigator or lab manager turns it over to you: what the work really is, who trains you, how long the funding lasts, and whether the role leads anywhere.

20 questions, each with the reason to ask it · includes a conversation guide

Open any question to see why it works.

1
What would I be working on in my first month?
A specific answer names a project, a technique, and a person. A vague answer usually means the role was posted because a grant allowed a hire, not because the work is defined, and you will spend your first month inventing your own job.
2
Is this position attached to one project, or does it float across the lab?
Single-project roles give you depth and a clean line on a CV. Floating roles give you variety and a real risk of becoming the person everyone hands their leftover tasks to. Neither is wrong, but you should know which you are accepting.
3
Who would I report to day to day?
In most labs the person hiring you is not the person supervising you. If the answer is a senior graduate student or a postdoc, ask how long that person has left, because your direct supervisor leaving in eight months changes the job entirely.
4
How many people are in the group, and what is the mix of students, postdocs, and staff?
The ratio tells you how much attention exists to go around. A large group with one faculty member means you learn from peers. A group that is mostly staff scientists is a more stable place to learn technique and a slower place to get on papers.
5
What does a typical week look like in terms of hours at the bench, at a computer, and on admin?
Many research assistant roles are half lab management: ordering, scheduling, compliance paperwork, keeping the freezer inventory honest. That is normal, but if it is sixty percent of the job you want to hear it now rather than discover it in March.
6
How does training work for techniques I have not used before?
Listen for whether training is a named person and a timeline, or a protocol binder and goodwill. Ask how long they expect it to take before you run something independently, since that estimate reveals how they think about supervision.
7
What analysis or programming would you want me to pick up?
This is where the transferable skills live. If the answer is a specific language or pipeline, ask whether you will be doing the analysis or handing raw data to someone else, because those are very different lines on a graduate application.
8
How do authorship decisions usually get made here?
Ask about the process rather than asking for a promise. Labs vary from crediting anyone who ran a sample to reserving authorship for people who designed experiments. A principal investigator who has never thought about it is telling you something.
9
How long is the position funded, and what happens when that funding ends?
Many of these roles sit on a grant with a fixed end date. Ask what year of the grant you would be joining. Being hired in the final year of a five-year award is a one-year job whatever the posting says.
10
Where have the last few people in this role gone afterwards?
This is the single most informative question you can ask about a research assistant job. If recent people went to graduate or medical school, the lab knows how to build applicants. If nobody knows where they went, the role is a pair of hands.
11
How often would we meet one on one?
Ask for a frequency, not a philosophy. Weekly meetings with a principal investigator who travels constantly usually means monthly in practice, so follow up with how often the last meeting actually happened.
12
What happens when an experiment stops working for weeks at a time?
Troubleshooting is most of research and almost none of the job description. The answer tells you whether failure here is treated as normal debugging or as a performance problem, which is the difference between a good year and a miserable one.
13
How are data and records kept, and would I be responsible for any of that?
Electronic notebooks, sample tracking, and code version control are either a system or an accumulation of habits. Inheriting an undocumented freezer or a folder of spreadsheets named final_v3 is a real part of the workload.
14
Is there room for me to develop a question of my own, or is the scope fixed?
Some labs give assistants a small side project on purpose, as a recruiting tool for graduate school. Others cannot afford the reagents. Ask what a previous person's side project was, since a real example proves the offer is not just polite.
15
What trainings or approvals would I need before starting, and how long do they take?
Human subjects certification, animal handling, radiation or biosafety modules, and background checks can take weeks. This also quietly tells you what the work involves if the posting was vague about live animals or patient data.
16
What are the hours, and does anything need covering on evenings or weekends?
Cell culture, animal colonies, and time-course experiments do not respect a calendar. You are not asking to avoid it, you are asking whether it is once a month or every other Sunday, and whether it is shared fairly across the group.
17
What would you want someone in this role to have accomplished a year in?
This forces the interviewer to describe success concretely. If they cannot, there is no standard to meet and no way to earn a strong letter of recommendation, which for most people is the real payout of the job.
18
What is the hardest part of this job for the people who have done it?
Phrasing it about past people rather than about the lab makes it easy to answer honestly. Common real answers are isolation, repetitive protocols, and long gaps waiting on equipment or approvals, none of which appear in a job posting.
19
Why is the position open?
New grant, someone left for graduate school, or someone left early. The last one deserves a gentle follow-up about what they would do differently. Hesitation before the answer is usually the most useful part of the response.
20
What are the next steps, and when do you expect to decide?
Academic hiring runs slowly and often stalls on an administrative approval nobody mentions. Getting a date lets you follow up without guessing, and lets you tell another employer how long you can reasonably wait.

Interviewing for a research assistant role

Practical guidance for the conversation itself.

What to read before you go

Look at who is on recent papers

Scan the author lists on the group's last few publications for names that are not students or postdocs. Technicians and research assistants who appear repeatedly tell you the lab credits that work. If those names never appear, note it and ask about authorship directly.

Find the funding end date if you can

Public grant databases list award periods for federally funded work. Knowing whether the supporting award has three years left or eight months changes what the phrase ongoing position means in the interview.

Prepare one technical question about their actual work

Ask about a specific figure or method from a recent paper rather than the topic in general. It shows you read something, and it usually turns the last ten minutes into a conversation between two people interested in the same problem.

Signals worth noticing

Whether you get to speak with a current member of the group without the principal investigator in the room. If that is refused, that is the answer.
How the lab describes people who left. Warmth about former assistants tends to predict good letters of recommendation.
Whether anyone asks about your own goals. A group planning to help you get into graduate school will ask what you want next.
The state of the physical space, if you get a tour. Shared equipment that is booked solid means waiting is part of the job.
Whether salary and end date are discussed plainly. Discomfort about either one usually means the answer is worse than you hoped.

Before you accept

Get the funded end date, the title, and the salary in writing, since academic offers often arrive as a friendly email and nothing else.
Ask whether the title is research assistant, technician, or study coordinator on paper. Some titles are hourly, some are salaried, and the difference shows up in overtime and benefits.
Ask directly whether they are willing to write letters of recommendation and how many they wrote last year.
If two labs are competing for you, compare the supervisor and the funding runway before you compare the science.
Ask who to contact with questions between the offer and the start date, because administrative onboarding is usually the slowest part.

The questions

What would I be working on in my first month?

Is this position attached to one project, or does it float across the lab?

Who would I report to day to day?

How many people are in the group, and what is the mix of students, postdocs, and staff?

What does a typical week look like in terms of hours at the bench, at a computer, and on admin?

How does training work for techniques I have not used before?

What analysis or programming would you want me to pick up?

How do authorship decisions usually get made here?

How long is the position funded, and what happens when that funding ends?

Where have the last few people in this role gone afterwards?

How often would we meet one on one?

What happens when an experiment stops working for weeks at a time?

How are data and records kept, and would I be responsible for any of that?

Is there room for me to develop a question of my own, or is the scope fixed?

What trainings or approvals would I need before starting, and how long do they take?

What are the hours, and does anything need covering on evenings or weekends?

What would you want someone in this role to have accomplished a year in?

What is the hardest part of this job for the people who have done it?

Why is the position open?

What are the next steps, and when do you expect to decide?