You got the internship. Congratulations, genuinely. Now the panic sets in: everyone else seems to already know how things work here, the codebase is huge, and you have no idea what you're allowed to ask without looking clueless.
Every intern feels this in week one. What separates the ones who have a great internship from the ones who spend three months quietly terrified isn't skill. It's how they handle exactly this stretch.
1. You're an Exchange Student, Not a Transfer
Think about what it's like being an exchange student at a new school abroad. You don't already know the unwritten rules: how strict this teacher actually is, which shortcuts are fine, which ones aren't, what the local slang means. A smart exchange student spends the first weeks watching and asking quiet questions before assuming their old school's rules apply here.
An internship works the same way. Every team has its own unwritten culture: how they review code, how blunt or gentle their feedback is, what "done" actually means to them. You're not expected to know it on day one. You're expected to notice you don't know it yet, and to learn fast without pretending otherwise.
2. Nobody Expects You to Already Know Everything
This is worth repeating because it doesn't sink in easily: you were hired as an intern, not as a finished engineer. The company already knows you're learning. The pressure you feel to seem competent from day one is almost entirely self-imposed.
What they actually expect:
- Curiosity and real effort
- The ability to ask for help instead of silently spinning your wheels
- Steady improvement over the weeks, not instant mastery
- Being pleasant and reliable to work with
Nobody is quietly judging you for not knowing the codebase on day two. They'd be far more concerned by someone who pretends to understand something they don't.
3. The First Week Is for Watching, Not Proving
Resist the urge to immediately prove yourself with something big. The first few days are better spent learning the terrain:
- Read the onboarding docs fully, even the boring parts
- Set up your development environment and get the existing project running locally
- Read through the codebase you'll be working in, even without changing anything yet
- Notice communication patterns. Which channel do people use for what? How formal or casual is the tone?
- Meet your team, even briefly. A short chat with each teammate is worth more than it seems
You're not being unproductive by doing this. You're building the map you'll need before you can move confidently.
4. Ask Questions the Smart Way
Asking questions is expected and encouraged. How you ask them is what actually gets noticed.
Weak: "This doesn't work, what do I do?"
Better: "I'm trying to do X. I expected Y to happen, but I got Z instead. Here's what I've tried so far. Do you know what I might be missing?"
The second version shows effort, gives your teammate enough to actually help quickly, and doesn't waste their time on back-and-forth just to understand the problem. A good rule: try for fifteen to thirty minutes on your own first, then ask, rather than either giving up instantly or silently struggling for hours.
5. Take Notes Like Your Future Self Depends on It
You'll be told a lot of things in your first weeks: where things live, how to run tests, who owns which part of the system, small quirks that aren't written down anywhere. Write it all down.
Keep a simple running document:
- Setup steps you had to figure out
- People and what they own or know well
- Terms and acronyms specific to this company
- Mistakes you made and how you fixed them
Two benefits: you stop asking the same question twice, and by week four you'll have an informal manual that would have saved you a lot of confusion in week one.
6. Understand Before You Touch
When you're finally given a task, resist jumping straight into code. Spend a few minutes making sure you actually understand what's being asked:
- Restate the task in your own words to whoever assigned it
- Ask about edge cases or ambiguous parts before you start
- Check how your task fits into the bigger picture, if that's unclear
A short clarifying conversation up front is far cheaper than building the wrong thing and needing to redo it later.
7. Handling Feedback and Code Review
Your code will get reviewed, and comments will come back. This is one of the best parts of an internship, not a punishment.
- Don't take it personally. A comment on your code isn't a comment on your worth
- Ask "why" when a suggestion isn't clear, rather than silently changing it without understanding
- Say thanks, even for blunt feedback. It signals you're coachable, which people notice and remember
- Apply the same feedback proactively next time, which shows you're actually learning, not just fixing one instance
The interns who grow fastest are the ones who treat every review comment as a small, free lesson.
8. Manage Up a Little
You likely have a manager or a mentor assigned to you. Don't wait passively for them to check on you constantly. A little initiative goes a long way:
- Give a short update on your progress every few days, even unprompted
- Flag early if you're stuck or blocked, rather than waiting until a deadline is at risk
- Ask what "good" looks like for your specific tasks, so you're not guessing at the bar
A quick, honest "here's where I am, here's what I'm stuck on" message is one of the simplest ways to look reliable, regardless of your actual skill level yet.
9. Build Relationships, Not Just Output
Your internship isn't only about the code you ship. It's also your first real chance to build a small professional network, which I've written about in more depth separately.
- Say yes to coffee chats, casual lunches, or team social time when you can
- Ask people about their own path into the field. Most people enjoy being asked
- Be genuinely helpful to other interns too, not just senior engineers
These relationships often outlast the internship itself, sometimes becoming references, referrals, or simply people glad to hear from you again later.
10. Document Your Work as You Go
Don't wait until the final week to remember what you did. Keep a running log:
- What you built or fixed, in plain language
- What you learned that you didn't know before
- Any measurable impact, if you can point to one honestly
This becomes the raw material for your resume, your final presentation if there is one, and interview stories for your next application. Trying to reconstruct three months of work from memory in the last week is much harder than logging it along the way.
11. Common Mistakes First-Time Interns Make
- Pretending to understand something you don't. It always surfaces later, at a worse time.
- Disappearing when stuck. Silence looks worse than admitting you're blocked.
- Over-promising on timelines to seem capable, then scrambling to deliver.
- Only talking to your immediate team. Meeting people elsewhere in the company opens doors later.
- Comparing yourself to full-time engineers. They've had years of practice you haven't had yet.
- Not asking for feedback proactively. Waiting for a scheduled review means missing months of smaller course corrections.
12. Using AI Tools During Your Internship
Many companies now allow AI coding tools, some don't, and some have specific rules about what data can go into them. Before using anything, ask what's allowed. Once you know the rules:
- Use it to understand unfamiliar code faster, not to avoid understanding it
- Never paste proprietary code, credentials, or customer data into a tool without explicit permission
- Still be able to explain your own work in review, since "the AI wrote it" isn't an answer your reviewer wants to hear
Week One Checklist
- [ ] Get your environment set up and the project running
- [ ] Read the docs and skim the codebase before writing code
- [ ] Meet your team, even with a short message or call
- [ ] Start your running notes document
- [ ] Ask at least one question you were nervous to ask
- [ ] Send a short first-week update to your manager or mentor
You're Allowed to Not Know Things Yet
Every senior engineer on your team was once exactly where you are now, confused by a codebase, unsure what to ask, quietly worried they didn't belong. The only real difference between you and them is time and a lot of exactly these small, uncomfortable first weeks.
Show up, ask honestly, take notes, and give it real effort. That's genuinely all anyone is expecting from you right now.
Let's Connect
I'm Prayush Adhikari, currently grinding through computer engineering, leading an IT club, and building my own company on the side. I write about Linux, productivity, and the honest side of being a developer.
If you're starting an internship soon, tell me in the comments what's making you most nervous. I'll do my best to help.
- LinkedIn: linkedin.com/in/adhikareeprayush
- GitHub: github.com/adhikareeprayush
- Portfolio: prayushadhikari.com.np
What should I write next: how to survive group projects with a difficult teammate, or how to turn an internship into a full-time offer?
Top comments (0)