aaryamansingh.com / the first internship playbook

the firstinternshipplaybook

Getting the offer is one thing. Nobody teaches you how to actually be good once you're there.

0 of 0 done

Most interns spend week one trying to look like they already know everything. That's the wrong game. Nobody expects you to know the systems, the acronyms, or the org chart — they expect you to be easy to work with and easy to trust with more.

This is the whole arc of a first internship, in order, with the actual messages to send. Tick things off as you go; the page remembers where you are.

before day one

week 0

Low effort, high return. An hour here saves you most of week one.

Work out who you report to and who you sit withThey're often not the same person. Find your manager and three teammates on LinkedIn so names aren't a blur on day one.
Write one sentence on what the team actually doesNot the company — the team. If you can't write it, that's your first question, and it's a good one to ask.
Open a notes file before you have anything to put in itOne file, dated entries. This becomes your update log, your performance review, and your resume bullets later.
Don't cram technicallyYou'll be taught the internal tools, and no course covers them. Learning them fast in week two beats pretending in week one.

week one

week 1

You will produce almost nothing this week. That is correct and expected. Spend it on information.

Ask your manager two questions on day one"What does a good outcome for this internship look like to you?" and "How do you like to be updated?" Both answers shape everything after.
Write down every acronym you hearYou'll hear forty in week one and nobody repeats them. Keep a running list; look them up on your own time.
Book 15 minutes with three people on your teamNot networking. Just "I'm new, what do you actually work on?" People like explaining their job, and you'll learn the real org chart.
Don't stay late in week oneYou'd be setting an expectation you have to hold for four months. Leave on time and be sharp instead.
Find out how work actually gets assignedTicket queue, standup, someone tapping you on the shoulder. Knowing the channel is how you get more of it later.

your first real task

weeks 2–4

This is where most interns quietly lose a week building the wrong thing.

Never leave the briefing without four thingsWhat the finished output looks like, who it goes to, when it's due, and one example of a good version. Ask for the example — it's the one people forget to offer.
Use the 30-minute rule when you're stuckTry it yourself for 30 minutes, write down what you tried, then ask. "I tried X and Y, X failed because Z" is a completely different message from "I'm stuck".
Send your first draft at 60%, not 95%Finding out you built the wrong thing at 95% costs a week. At 60% it costs an hour. Say "sanity check before I go further" and send it.
Ask in the channel, not the DMWhen the answer would help someone else, ask publicly. You look like you're contributing rather than consuming attention.
Repeat the task back before you startOne line: "So you want A, formatted as B, by Thursday, for C." Roughly a third of the time something in there is wrong.

making the work visible

the middle

Good work nobody knows about counts for nothing at review time. This is the part people find awkward and skip.

Keep a log of what you shipped and what it changedEvery Friday, three lines. What you finished, what it improved, who asked for it. In month four you will not remember month one.
Update your manager before they askFive lines, three headers: done, in progress, blocked. Weekly. Managers who never have to chase you give you better work.
Flag blockers the day they happenBeing blocked isn't failure. Being blocked for four days while your manager assumes it's on track is. Say it early, say it plainly.
When you finish early, say so and ask for more"I'm done with X and have capacity — anything you want picked up?" This is how you get responsibility without asking for a title.
Find one thing nobody owns and quietly own itA broken process, an undocumented step, a report someone builds by hand every week. Fixing it is how interns get remembered.
Ask for feedback at the halfway point, not the endAt the end it's a review. At the halfway point it's something you can still act on.

leaving with people wanting you back

last 2 weeks

Start this earlier than feels natural. Many teams decide on returns before your final week.

Write the handover docWhat you built, where it lives, how to run it, what's half-finished. Almost no intern does this and every manager notices the one who did.
Ask about returning while there's still time to matterAsk your manager directly what the process looks like and when decisions get made. Asking in your last week is asking too late.
Turn your log into numbersHours saved, errors caught, time cut, volume handled. Rough and honest beats precise and invented — and you'll need them for every interview after this.
Line up two people who'd vouch for youAsk while the work is fresh: "would you be open to being a reference?" A yes six months later is much harder to get.
Thank people specifically, not genericallyName the thing they helped with. Connect on LinkedIn the same week, not in December when you need something.

the messages

copy + edit

Steal these. Change the names, keep the shape.

Day one, to your manager

Sets expectations before anyone sets them for you.

Hi [name] — really glad to be starting.

Two things so I can set myself up properly:

1. What would a genuinely good outcome for this internship look like from your side?
2. How do you prefer to be kept updated — a weekly written summary, or something looser?

Happy to work to whatever's easiest for you.

The Friday update

Five lines a week. The single highest-return habit on this page.

Week of [date]

Done
– [thing], [what it changed]
– [thing]

In progress
– [thing] — on track for [day]

Blocked
– [thing] — waiting on [person/access]. Let me know if there's a faster route.

When you don't understand the task

Asks for the answer without announcing you're lost.

Before I get going on this — want to make sure I've got it right.

My understanding: you want [output], formatted as [format], by [day], for [audience].

Two things I'm unsure on:
– [specific question]
– Is there an existing version I could look at as a reference?

When you're actually stuck

After your 30 minutes. Shows the work, so it doesn't read as giving up.

Hit a wall on [task] — wanted to flag it rather than sit on it.

I've tried [X] and [Y]. [X] didn't work because [reason], and [Y] got me to [point] but not past it.

Is there something obvious I'm missing, or is this one to bring to [person]?

Asking for more responsibility

Framed as capacity, not ambition. Much easier to say yes to.

I've wrapped [thing] and I've got some room this week.

If there's anything on your plate you'd want taken off it — even something unglamorous — happy to pick it up. I'd also be keen to get closer to [area] if there's a way in.

Asking for feedback that's actually useful

"Any feedback?" gets you "you're doing great." This doesn't.

Could I get 10 minutes at some point this week?

Specifically: if I were coming back in a more senior role, what's the one thing I'd need to be doing differently? Would rather hear it now while I can still act on it.

The return offer conversation

Send this with weeks left, not days.

I've really enjoyed working on [team] — [specific thing you liked, not generic].

I wanted to ask directly: what does the process look like for coming back, and when do those decisions usually get made? Just want to make sure I'm not missing a step on my end.

Last week, to someone who helped you

Specific beats warm. This is the one people remember in a year.

Wrapping up this week — wanted to say thanks properly.

The [specific thing] you walked me through in [month] changed how I approached basically everything after it. Genuinely appreciated it.

Sending a LinkedIn request — would be great to stay in touch.

what actually loses people the return offer

avoid

Going quiet when something goes wrong, and hoping it resolves before anyone notices.
Sitting on a blocker for days because asking felt embarrassing.
Doing good work that nobody above your manager ever hears about.
Saying yes to everything, then delivering four things late instead of two things well.
Treating admin work as beneath you. Someone is watching how you handle the boring task.
Only talking to the other interns.
Pretending to understand in the moment, then rebuilding it wrong for a week.
Leaving on the last day with no documentation and no reference secured.

that's the whole thing

Being good at the work and being good at being an intern are two different skills. Most people only find that out on the way out.

Follow @byaaryaman

Other things I keep updated: