# How to get a robotics internship in India

> What internship ads ask for, the portfolio proof that gets replies, and a week-by-week plan to apply without spamming.

Canonical: https://roboticsengineering.in/robotics-internship-india-how-to-get/ | Published: 2026-10-27 | Updated: 2026-10-28 | Author: Jignesh Panchal

**A robotics internship in India is usually won by a short, specific request that arrives when a team has work and nobody to do it.** A generic application sent through a portal competes with hundreds at the same moment. A two-paragraph email to a lab, a small product company or an integrator, sent in the month it needs hands, often does not. Here is the timing, the channels, the portfolio threshold and the email itself.

## When to apply, by semester

The academic calendar shapes this more than any portal does. Summer internships are usually decided between January and March for a May start, and most colleges lock final-year project teams a semester in advance.

| When you are | What you should already have | What to send, and when | Realistic target |
| --- | --- | --- | --- |
| Summer after first year | One build that works, basic C | Short emails to college labs and robotics clubs, two months ahead | A lab assistant role, sometimes unpaid |
| After semester 3 or 4 | One documented build with a test log | Emails to startups and labs three months before the break | A 4 to 8 week summer internship |
| After semester 5 or 6 | Two builds, Git, one bus or framework used properly | 10 to 15 targeted emails from January onwards | A paid two-month internship |
| Semester 7 | A project already under way | A proposal tied to the company’s own product | Final-year project with an industry mentor |
| Semester 8 | Completed project and report | A conversion conversation, then full-time applications | An offer, a contract role or a named reference |

*Typical patterns in Indian engineering colleges, not a rule. Campus placement calendars vary by institution.*

## Where are robotics internships actually posted?

Ranked by how often they lead somewhere, not by prestige:

- **Faculty labs and funded projects.** Ask the professor directly, with one link to your work. This is the easiest first internship and the least advertised.
- **College placement cell.** Formal and slow, but the listing is real and the process is documented.
- **Small product startups.** Ten to forty people, no HR, and an engineer reads the email. Specific asks get replies.
- **System integrators and machine builders.** They need wiring, documentation and site help, and they teach you more about machines than a desk role will.
- **Competition organisers and robotics clubs.** They know which team is short of hands this month.
- **Open-source robotics projects with mentoring programmes.** A merged contribution is a portfolio item and an introduction.
- **Public research institutions with published summer programmes.** Apply on the stated window; late emails are ignored.

Treat three things as red flags: a company that charges a fee for training and placement, full-time unpaid work with no defined task, and a “hardware internship” that turns out to be content writing or data entry.

## The portfolio threshold before you email anyone

You need one build that another person can inspect, not three that only you understand. The threshold is lower than most students assume:

- A repository with a README: photograph, pin map, bill of materials in rupees, and the steps to flash it.
- A one-page test log with measured numbers, not adjectives.
- A video under 60 seconds that shows it working and one case where it fails.
- One failure you can describe in detail, including how you found the cause.
- An honest list of what does not work yet.

The [free project pack](https://roboticsengineering.in/free-project-pack/) has the test log and BOM sheets for this, and the [report format guide](https://roboticsengineering.in/robotics-project-report-format/) shows how much measurement an examiner or an interviewer expects.

## The cold email, line by line

Keep it under 150 words, use one link, and do not attach a file to the first email. Every bracket below must be replaced with something true about that company.

| Part | What it must do | Wording to adapt |
| --- | --- | --- |
| Subject line | Say who you are and what you want, in one line | [Branch] student, [build] with test log, seeking [4/6]-week internship in [month] |
| Opening | Prove you looked at them, not at a list | I am [name], a [year] [branch] student at [college]. I read about your [product or paper] and I have a question about [specific detail]. |
| Proof | One build and one measured result | I built [project] on [board]. My test log shows [measurement]. The hardest part was [problem]; I fixed it by [method]. |
| The ask | Small, dated and specific | I am looking for [4/6/8] weeks between [dates]. I can take on [sensor bring-up / wiring harnesses / test rigs / documentation]. I am in [city] and can travel at my own cost. |
| Close | Leave a door open without pressure | If there is no slot this term, what would you want to see from a student before you would consider one? |

*A structure, not a script. The second line is the only one that has to be written from scratch each time.*

Address a person by name when a name is published. Do not send the same email to twenty companies with the name swapped; the specific detail in the opening is the part that earns a reply, and it cannot be copied.

### Follow-up rules that do not annoy people

- Follow up once, five to seven working days later, and add something new: a fixed bug, a new measurement, a better video.
- Never send “just checking in”. Send a one-line update with a link.
- Two follow-ups is the maximum. After that, keep the contact for next term and move on.
- If the answer is no, ask one question: what would make a student worth a slot next time? The answer is worth more than the internship.
- Log every contact in a sheet: company, person, date, what you sent, what came back.

### What to do this month

- List twelve targets: three labs, three startups, three integrators, three others. Find one named person at each.
- Read one thing that person made: a product page, a paper, a repository. Write the opening line for each target separately.
- Finish the one-page PDF: photo, pin map, BOM, test numbers, what fails.
- Send six emails in the first week, on Tuesday to Thursday mornings.
- Record which opening line got replies, and rewrite the rest from the winner.

## The first week, and how to turn it into a job

- **Day one:** clone the repository and build it before you ask anything. Note every error; those notes are your first useful artefact.
- **Ask what done means** for your first task, and get it in writing.
- **Ask what you may not touch.** Customer units and production firmware are not test benches, and one careless flash can end the internship.
- **Label every wire you add** and keep a daily log of what you changed and what broke.
- **Close one small ticket in week one.** A resolved issue, a fixed procedure, a working test rig: anything that makes you the person who finishes things.

An internship converts when you become the person who handles one thing without supervision. Ask for one owned deliverable by week two, show the result in week four, and ask for a specific next step two weeks before the end: a full-time role, a contract extension, or a named reference. Do not ask for a job in week one; ask what a good outcome would look like.

Ask for the reference while the work is fresh. A request for two sentences about what you delivered is easy to answer in the final week and awkward to answer six months later. If the company has no opening, that reference and the work sample are what carry you into the next application. The [final-year project list](https://roboticsengineering.in/final-year-robotics-projects/) is useful here: an industry-linked project is often the second internship, and the [careers page](https://roboticsengineering.in/careers/) maps which role family each kind of work leads into.

## Common questions

### Do unpaid internships count?

They count as experience if the work is real and someone supervises it. They are a poor deal when the task is undefined, when you replace a paid employee, or when the company also charges you for training. A short paid trial month is a better signal than three unpaid months, and it is a fair thing to propose.

### Can I get an internship with no portfolio?

In hardware, rarely. The exception is your own college lab, where a professor who has seen you work will take you on trust. Build one robot with a documented test log first; that single artefact changes the reply rate more than any certificate. A line follower with a real test log is enough to start with, and it is the build we use as the baseline in the [line follower guide](https://roboticsengineering.in/projects/line-follower-robot-arduino/).

### Is a remote robotics internship realistic?

For software, simulation, testing and documentation work, yes. For anything involving wiring, calibration or a physical machine, no, and a “remote hardware internship” that never sends you hardware is usually content work. Ask what you will physically have access to before you accept.

Last reviewed: October 2026. Timings reflect common Indian academic calendars; confirm dates with your own institution and each employer.

AMR and warehouse automation companies are among the more accessible internship targets; the [warehouse robotics guide](https://roboticsengineering.in/warehouse-robotics-india/) lists the vendors and what they build.

Employers screen interns on the basics listed in [how to become a robotics engineer in India](https://roboticsengineering.in/how-to-become-a-robotics-engineer-in-india/).

Prepare with the [robotics interview questions](https://roboticsengineering.in/robotics-engineer-interview-questions-india/) before the first call.

Internship applications live or die on project evidence, and the [resume guide](https://roboticsengineering.in/robotics-resume-fresher-india/) shows how to write it.

Internship applications land better with two documented builds; see [how to structure a robotics portfolio](https://roboticsengineering.in/robotics-portfolio-projects-guide/).

If you are comparing pay across role types and want the conversion checklist, see [robotics internship stipends in India](https://roboticsengineering.in/robotics-internship-india/).

## Sources and further reading

Background documents used for this page:

- [IFR World Robotics](https://ifr.org/worldrobotics/) — international data on robot installations and demand for skills.
- [National Career Service, Government of India](https://www.ncs.gov.in/) — public job listings and career resources.