Questions to Ask in a Research Assistant Interview

The questions

Open any question to see why it works.

1. 1

   What would I be working on in the first month?

   Postings for research assistants are written broadly because the person writing them does not always know which project will need hands. A specific first month means the work exists now, while a vague answer often means the role will be shaped by whatever grant lands.

2. 2

   Is this position attached to one project, or spread across several?

   Being on one project gives you depth and a clear claim to the output. Being split across three usually means you become the person who does the shared tasks, which is useful experience and much harder to turn into a line on a paper.

3. 3

   How long is the funding, and what usually happens when it ends?

   Most research assistant posts are paid from a grant with a fixed end date. Ask what happened to the last two people when their funding ran out, since that shows whether renewals are routine here or whether the end date is real.

4. 4

   Who would I report to day to day?

   The principal investigator hires, but a postdoc or a senior doctoral student usually runs the daily work. That person shapes your experience far more than the name on the grant does, so it is worth asking to meet them before you accept.

5. 5

   Who else is in the group, and what does each of them do?

   The mix of postdocs, doctoral students, and technicians tells you where you would sit. A group with no postdocs asks more independence of you, while a group with many can mean you spend your time supporting other people's projects.

6. 6

   How often does the group meet, and how often would I meet with you?

   Frequency is the honest proxy for supervision, and the real range runs from weekly one-to-ones to almost nothing. If the answer is that the door is always open, follow up by asking when they last had a scheduled meeting with the current research assistant.

7. 7

   What does a normal week actually look like, hour by hour?

   Push for the split between bench or field work, analysis, participant scheduling, and administration. Almost every research assistant post contains more coordination and paperwork than the description suggests, and it is better to know the proportion now.

8. 8

   How much of the job is collecting data, and how much is analysing it?

   This is the single largest difference between two posts with the same title. If you want analysis skills for a graduate application, a role that is entirely collection will not build them no matter how strong the group is.

9. 9

   What do you expect me to know on day one, and what would I learn here?

   The honest answer separates a training post from a production one. If everything on the list is something you are expected to arrive with, the role is about output, and you should ask separately where growth is meant to come from.

10. 10

    Would I be trained on the protocols, or work from existing documentation?

    Some groups run structured handovers, others give you a folder and the departing person's last week. Ask who trained the current research assistant and whether that person is still around, since documentation quality stays invisible until you have to rely on it.

11. 11

    What ethics or compliance approvals would I need before I could start work?

    Human subjects and animal work require approvals and training that can take weeks to clear. Asking shows you understand the setting, and it tells you how much of your first month will be paperwork rather than research.

12. 12

    How do you handle it when someone makes a mistake in data collection?

    This is a culture question wearing the clothes of a procedure question. Groups with a documented way to flag and log errors tend to be groups where people admit them, and that matters more to data quality than anyone's technical skill.

13. 13

    What are the hours, and is there evening or weekend work?

    Participant scheduling, animal care, time-course experiments, and field visits all break the ordinary week in ways a posting rarely mentions. Ask when the current research assistant most recently worked a weekend and why.

14. 14

    How is authorship decided in this group?

    Norms vary by field and by group, from contribution criteria written down somewhere to whatever the principal investigator decides. Ask for an actual example: whether the last research assistant appeared on a paper, and in which position.

15. 15

    Would there be room to take on a small piece of work of my own?

    Some supervisors expect this and some treat it as a distraction, and neither is wrong. The answer tells you whether the post is a place to develop a question of your own or a place to execute someone else's carefully.

16. 16

    Where have previous research assistants from this group gone?

    This is the closest thing to an outcome record you will get. A group whose assistants regularly move into doctoral programmes has both the training and the letters behind it, and a group that cannot name any is telling you something.

17. 17

    Would you be able to write me a recommendation letter, and what would you need to see first?

    Ask now rather than in eighteen months. A supervisor who names what a strong letter would require is handing you the evaluation criteria for the job, which is more useful than any general statement of support.

18. 18

    What part of this job do people underestimate?

    The answers are usually unglamorous: recruitment that stalls, equipment that fails, data cleaning, or the repetitiveness of a protocol you run four hundred times. Whether they answer honestly also predicts how they will handle it when you struggle.

19. 19

    How will you know in six months whether this is going well?

    Research posts often have no formal review, so expectations stay implicit until something goes wrong. Getting two or three concrete markers now gives you something to measure yourself against and to point to later.

20. 20

    What happened with the person who had this role before me?

    A post created by someone leaving for a doctoral programme reads very differently from one created by someone leaving mid-project. If the role is new, ask what the group was doing instead until now.