If you are wondering what do research interns do all day, the honest answer is less glamorous — and more useful — than most students expect. An intern does not run a laboratory or publish a paper in eight weeks. An intern works on one small piece of a larger project, under a scientist’s guidance, for about two months: reading, hands-on work, analysing data, meeting the group, and writing up what happened. This guide explains what a realistic week looks like, how the work changes by field, what mentors expect, and what you should not expect.
On this page
- The answer in short
- What do research interns do in a typical week?
- How the work differs by field
- What your mentor actually expects
- What not to expect
- Your first week: a checklist
- What to do next
- Frequently asked questions
- Sources checked
The answer in short
A research intern spends about two months — eight weeks in the TIFR Hyderabad VSRP, two months in the Science Academies’ SRFP and the JNCASR programme — working on one small, defined task inside a scientist’s larger project. A typical week is reading papers, hands-on work, recording results, analysing data, one group meeting, and a short written summary. You will not be given your own independent project on day one, and you will not be left alone. Your mentor, a PhD student or a postdoc sets the task and checks your work. The point is training in how research is done, not a finished discovery.
What do research interns do in a typical week?
Most internships follow a similar weekly rhythm, whatever the field.
| Day | What usually happens |
|---|---|
| Monday | Read the key paper; plan the week with your mentor |
| Tuesday–Thursday | Hands-on work; record results as you go |
| Friday | Group meeting and a short summary |
Reading. Every week starts with reading. Before you touch an instrument or write code, read the one or two papers your mentor gives you, and note the question, the method and the result in your own words. Expect the first week to be mostly reading.
Hands-on work. The middle of the week is the largest block of time. In a wet lab it means following a protocol: preparing samples, running an assay, measuring, repeating. In a computational group it means writing code, cleaning data and checking the output. The work is often slow and repetitive — a failed experiment, a bug, a calculation that does not close — and fixing it is part of the training.
Recording and analysing. Results go down the same day, in a lab notebook or a dated digital file: the date, the method, and what actually happened — including what went wrong. At the end of the week you analyse the data: plot it, compare it with what was expected, and note the difference. A result you cannot explain is still a result, if you recorded it honestly.
Meetings and writing. Most groups meet once a week, and interns are usually asked to present briefly — five minutes on what they did, what they found, and what they plan next. Short writing runs through the whole internship: a weekly summary, a methods note, and a short report at the end. That report is what your mentor will base a recommendation on.
How the work differs by field
Wet lab (biology, chemistry, materials). Days are set by the experiment: preparing reagents, running assays, waiting for incubations, measuring results. Safety rules come first — gloves, waste disposal, labelling — and you will not work alone with hazardous material until your supervisor is satisfied you know the procedure.
Computational (data science, bioinformatics, simulation). Days are spent at a computer: writing code, running it on data or a model, checking the output, fixing errors. Progress is measured in working code and clean plots. You will spend more time reading documentation and debugging than writing new code.
Theory and mathematics. Days are spent reading, working through derivations, and discussing them — with your mentor, a PhD student, or at a blackboard. There is no instrument and no dataset; the output is an argument, a calculation, or a proof. The main skill is checking your own reasoning before you present it.
Fieldwork (ecology, geology, earth science). Days are spent outdoors: collecting samples, taking measurements, keeping field notes. The discipline that matters most is the field notebook — a sample without a date, a location and a method is useless back in the lab.
What your mentor actually expects
Show up and be on time. Groups run on shared instruments and time. Arriving when you said you would — and warning your supervisor in advance when you cannot — is the first thing they notice.
Keep honest notes. A mentor would rather see a failed experiment recorded carefully than a successful one recorded vaguely. Your notebook is the record of the project; if it is missing, the work is missing.
Ask questions early. Ask when you do not understand a step, before you do it — not after something has gone wrong. A two-minute question can save a week of wasted work. No one expects you to know everything; they expect you to say what you do not know.
Report problems the same day. A failed experiment, a code that will not run, a lost sample — report it the day it happens. Hiding a problem is the one thing that genuinely damages trust.
Finish small tasks on time. Mentors give small, bounded tasks first — read this paper, run this analysis, prepare these samples — because finishing them earns trust for larger ones. A small task finished on time matters more than a large one promised and not delivered.
What not to expect
Your own independent project from day one. You will work on a piece of someone else’s project. That is normal: two months is too short for an independent project, and the point is to learn how research is done inside a working group.
An authorship guarantee. Authorship depends on your contribution and on the group’s and the journal’s rules. Careful, well-recorded work may be acknowledged or lead to authorship — but no programme promises this.
A publication in eight weeks. Most projects take months or years. Your report at the end of the internship is the realistic output, and it is what your mentor will base a recommendation on.
Being left alone. If you are left alone for days with no task and no one checking your work, ask your supervisor for a meeting and a defined next task. Do not expect your mentor to sit with you all day either; their job is to guide, not to supervise every step.
A salary. Structured programmes pay a modest fellowship towards living costs, and the amount varies. Informal internships arranged directly with a professor may pay nothing. Check the terms before you accept, so there are no surprises in the second week.
Your first week: a checklist
- ☐ Meet your mentor and your day-to-day supervisor
- ☐ Read the key papers; note the question, method and result
- ☐ Learn the safety rules and working hours before any hands-on work
- ☐ Set up your dated notebook with the project title
- ☐ Ask for your first small task and agree when to report back
- ☐ Note the weekly group meeting time, and ask whether you will present
- ☐ Confirm the practical terms: stipend, accommodation, and the last working day
What to do next
Read the guide on how to email a professor, which explains how to find a group and make contact, and the guide on what to put on your CV, which explains how to present the projects you already have. Check the Internships hub for current calls.
Frequently asked questions
Do research interns get their own project?
Usually not. Interns work on one small, defined task inside a scientist’s larger project. The task is real research, but the question, the method and the timeline are set by the group.
How many hours a day does an intern work?
There is no fixed number. Programmes describe the work as full-time research training, so treat it as a working day and agree the timing with your mentor in the first week.
Will I be an author on a paper?
Not necessarily, and no programme guarantees it. Authorship depends on your contribution and on the group’s and the journal’s rules.
What if I have no lab or coding experience?
Say so honestly when you apply and when you arrive. Mentors expect beginners; they need to know what you can already do, so they can set a task at the right level.
Sources checked
- Science Academies’ Summer Research Fellowship Programme 2027 — official application portal, https://webjapps.ias.ac.in/fellowship2027 — checked 19 November 2026 (two-month fellowships; selected candidates work with an assigned guide, preferably during the summer; round-trip train fare and a monthly fellowship).
- JNCASR Summer Research Fellowship Programme — official page, https://www.jncasr.ac.in/academic/fandeprogrammes/srfp/ — checked 19 November 2026 (two months of research training under the guidance of scientists, April to July; fellowship of ₹12,500 per month with travel support).
- TIFR Hyderabad Visiting Students’ Research Programme — official page, https://www.tifrh.res.in/academics/vsrp/ — checked 19 November 2026 (Summer Research Programme, 8 weeks, May–July; a science project through which students get trained in research; semester and long-term visiting students for final-year projects).
Note: the descriptions of a typical week, the field-by-field differences, what mentors expect and what interns should not expect in this guide are editorial guidance from IISER Connect, based on how these structured programmes describe the work — two months of research training under a scientist’s guidance — not rules stated by any institute. They are labelled as guidance, not as sourced facts.