It is a ten-week evaluation, not a final review
Interns often treat weeks one to eight as learning and week nine as the moment that counts. It is the reverse. Your manager forms a view early - usually by the end of week three - and spends the rest of the internship confirming or revising it. Early impressions are cheap to set and expensive to overturn.
What managers actually weigh
| Signal | Weight | Why |
|---|---|---|
| Did you ship something real | High | The single clearest evidence, and it is binary |
| How you handled being blocked | High | Predicts what you cost the team as a full-timer |
| Quality of your questions | High | Cheap for them to observe, hard to fake |
| Response to code review | Medium-high | Defensiveness here is a common quiet killer |
| Raw coding speed | Medium | Expected to be low; rarely decisive |
| Sociability | Low-medium | Helps at the margin, substitutes for nothing |
Notice what is not near the top: how clever your code is. Teams are deciding whether you will be a net positive in six months, and almost everything on that list is about how you operate rather than how much you know.
What to do, week by week
- Week 1: get your environment working and ask for the smallest real task available. Do not spend the week reading the codebase - you cannot learn it that way and nobody can see that you tried.
- Weeks 2-3: ship something small and complete. Small and finished beats ambitious and half-done, and this is the window where your manager's view forms.
- Mid-internship: ask directly what would make this a strong internship. Most managers will tell you plainly, and you still have time to act on the answer.
- Weeks 7-8: make sure one thing you built is visibly in use, and that your manager can name it without prompting.
- Final week: write a short summary of what you shipped and send it. Managers write return recommendations from memory, and memory is improvable.
The unblocking rule, which is what most of it comes down to
Struggling silently for two days looks identical to being incapable. Interrupting every twenty minutes looks like you cannot work independently. The calibration that works is to set yourself a window - an hour for something small, half a day for something large - and when it expires, ask with a specific question that shows your work: what you are trying to do, what you tried, what you ruled out and what you think the problem might be.
That question takes a senior engineer two minutes to answer and makes you look like someone worth hiring. The same habit is what interviewers are probing with "what do you do when you are stuck", covered in software engineer intern interview questions.
If the return offer does not come
It happens for reasons that frequently have nothing to do with you - headcount, a reorganisation, a team that never had a requisition. Worth doing, in order:
- Ask for specific feedback, framed as wanting to improve rather than wanting to appeal. You will usually get something honest and useful.
- Ask whether it was performance or headcount. Many managers will tell you, and the answer changes what you do next.
- Keep the relationship. Teams get headcount later, and a manager who liked you is a referral for somewhere else.
- Start the full-time cycle immediately, since it runs early - see the SWE internship recruiting timeline, which covers the new grad calendar as well.
An internship without a return offer is still a real internship on your resume, and it is a substantially stronger position than not having done one.
Where CoPilot Interview fits
Disclosure: we build an interview assistant, so treat this as a disclosed pitch. A return offer skips the interview entirely, which is the best possible outcome. If you are back in the loop instead, CoPilot Interview is a native Windows and macOS app that puts suggested answers on your own screen in about four seconds during live rounds, with a permanent free tier that needs no credit card.
Frequently asked questions
How are internship return offers decided?
Across the whole internship rather than in a final review. Managers typically form a view by about week three and spend the remaining weeks confirming it, weighting whether you shipped something real, how you handled being blocked, and the quality of your questions far above raw coding speed.
What should I do in the first week of an internship?
Get your environment working and ask for the smallest real task available. Reading the codebase for a week feels productive but teaches you little and gives your manager nothing to observe, and the first week is when their impression forms.
How often should I ask for help as an intern?
Set yourself a time window - an hour for something small, half a day for something large - then ask with a specific question stating what you tried and what you ruled out. Struggling silently for two days looks the same as being incapable; asking every twenty minutes looks like you cannot work alone.
What should I do if I do not get a return offer?
Ask for specific feedback framed around improving, and ask whether the decision was performance or headcount, since many managers will tell you and the answer changes your next step. Keep the relationship, since teams get headcount later and a manager who liked you is a referral elsewhere.
Walk into the round with a second pair of eyes
CoPilot Interview is a native Windows and macOS app that puts suggested answers on your own screen in about four seconds, across coding, system design and behavioral rounds. The free tier is permanent: 15 minutes a day, no credit card.
Try it free