Every year, thousands of Indian engineering students land their first software internship. And every year, most of them spend the first month feeling like they have made a terrible mistake. Not because the internship is bad — but because nobody prepared them for what it actually feels like.
This piece is the honest version. Not the LinkedIn celebration post. Not the "grateful to announce" update. The part that happens before the post: the confusion, the panic, the slow realization that you are not as good as your resume suggested — and that this is exactly where growth starts.
The prestige trap
There is a hierarchy in Indian tech culture. Google and Microsoft sit at the top. Then Amazon, Adobe, and the rest of FAANG. Then the unicorns. Then everyone else. Students spend years chasing the top of this pyramid — and many who get there discover it was the wrong pyramid.
The prestige trap works like this: you want the logo because it signals success. But the logo does not determine what you learn, who manages you, or whether the team has bandwidth to mentor an intern. A mediocre project at Google teaches you less than a high-ownership project at a Series B startup.
Reality vs. Instagram
The Instagram version: you arrive, get a shiny laptop, are assigned a meaningful project, and spend the summer building features that users love. The reality: you spend the first week setting up your dev environment, the second week reading documentation nobody has updated in two years, and the third week realizing your "project" is fixing bugs in a codebase that scares you.
This is not a sign that you are in the wrong place. It is a sign that software engineering is messy, and your courses did not prepare you for mess. The students who thrive are not the ones who code the fastest — they are the ones who get comfortable with ambiguity the fastest.
The imposter syndrome curve
Week 1-2: Panic. Everyone seems to know things you do not. The codebase is enormous. The terminology is foreign. You will Google "what is a microservice" at 2 AM even though you have theoretically studied distributed systems.
Week 3-6: Doubt. You start understanding the codebase but your code keeps getting rejected in code review. You will feel like the slowest person on the team. You are not. You are just the person whose mistakes are most visible because you are new.
Week 7-10: The click. Somewhere around week 7 or 8, the pieces start fitting together. You stop asking "how do I do this" and start asking "what is the best way to do this." This is the inflection point. Everything before this was warmup.
What you will actually learn
Here is what most interns learn, ranked by usefulness:
- How to read other people's code. This is 80% of the job. Your courses taught you to write from scratch. Industry requires you to understand, modify, and debug code written by ten people over three years.
- How to ask for help without looking helpless. The magic phrase: "I have tried X, Y, and Z. Here is what happened. What should I try next?" This shows effort, not helplessness.
- How to communicate technical ideas. Explaining your approach in a standup, writing a clear PR description, and documenting your decisions. These skills compound more than any algorithm.
- How to ship imperfect work. Your assignments had "correct" answers. Real products have tradeoffs. Learning to ship something good enough, on time, is a superpower.
The projects that matter
Not all intern projects are created equal. The best projects have three qualities: they ship to real users, they require you to work with multiple teams, and they have a measurable outcome (even if small).
The worst projects are internal tools that nobody uses, proof-of-concepts that get shelved, or "research" tasks with no deliverable. If you realize you are on a bad project by week 3, talk to your manager. Ask for something with user impact. Most managers respect this if you frame it as wanting to learn, not wanting an easy task.
When to leave
Most internships are 8-12 weeks. You should finish what you started. But if you are in a toxic environment — no mentorship, no real work, unreasonable hours — document your work and leave gracefully. A bad internship is not a career death sentence. It is a data point.
Signs of a toxic internship: your manager cancels 1:1s repeatedly, your code reviews are personal attacks, you are asked to work weekends as "standard," or you are given no context for tasks and then blamed for not knowing.
Walking into your first internship next week?
Talk to someone who interned where you are going — and ask them what nobody told them. On Amigzo, book 20 minutes with a working engineer who remembers the first-week panic.
The honest version
- Your first two weeks will feel overwhelming. This is normal.
- The prestige of the company matters less than the quality of your manager and project.
- Imposter syndrome peaks at week 3-4 and fades by week 7-8.
- The skills that matter: reading code, asking for help, communicating clearly, shipping imperfect work.
- If your project has no user impact, ask for one that does.
- Bad internships happen. Document and leave gracefully if needed.
Frequently asked questions
Quick answers about Career switch.
Is it normal to feel completely lost in the first two weeks?
Yes. The codebase, tooling, and culture are all new. Most interns feel productive only around week 4-5. If you still feel lost by week 6, talk to your manager.
How much coding will I actually do?
Less than you think, more than you fear. Most intern time is split: 40% reading code, 30% writing code, 20% meetings and communication, 10% debugging.
What if my manager does not give me real work?
Ask for it. Say: "I would love to work on something that ships to users. Is there a task I can own end-to-end?" Most managers appreciate initiative.
Should I take an unpaid internship?
Only if the learning is exceptional and you can afford it. In India, most software internships pay ₹15,000+/month. Unpaid roles are usually not worth the tradeoff.
How do I turn an internship into a full-time offer?
Ship something measurable, build relationships with your team, and explicitly ask your manager about the PPO process by week 6. Do not wait for them to bring it up.