What Intern Managers Look for When Deciding Return Offers

You finished your intern project. You think it went well. Your mentor seemed happy. Your manager said nice things in your final 1:1. Two weeks later, no offer.

This happens more often than you'd expect, and the interns it happens to are almost always confused. They did good work. They wrote clean code. They showed up on time. What went wrong?

Usually nothing dramatic. They just optimized for the wrong things. The return offer decision is less about your technical output than you think, and more about a set of signals your manager was tracking from week one.

The evaluation is not a performance review

Full-time engineers get evaluated on impact, scope, and leadership. Interns get evaluated on something different: whether the team would want to work with you again, for real, for years.

Most companies use a simple rubric with three tiers:

• Meets expectations. You did what was asked. Your code worked. You didn't cause problems. At most companies, this is not enough for an offer. It puts you in the "maybe" pile, and the maybe pile empties fast when headcount gets tight.

• Exceeds expectations. You delivered more than your assigned scope, or you delivered your scope with noticeably less hand-holding than expected. You asked for feedback and applied it. You contributed to the team beyond your project. This is the threshold for a return offer at most big tech companies.

• Greatly exceeds expectations. You performed at the level of a junior full-time engineer. You identified problems nobody asked you to look at. You shipped work that the team will use long after your internship ends. This gets you an offer even during hiring freezes.

Your manager is grading you against this rubric whether or not they tell you about it. The interns who ask "what does exceeds look like for this internship?" in their first week are the ones who know what they're aiming at.

What your manager is watching (that you probably don't realize)

Your manager has limited time with you. Ten to twelve weeks. They're also managing their full-time team, shipping their own deliverables, and probably running one or two other interns. They cannot observe you closely every day.

So they rely on signals. Some are obvious. Others are not.

How fast you unblock yourself. Every intern gets stuck. Your manager knows this. What they're watching is the gap between "stuck" and "asked for help." An intern who loses two days to a problem they could have resolved with a 15-minute conversation is an intern whose judgment the manager now questions. The right gap is a few hours, not a few days. Try to solve it, document what you tried, then ask.

Whether you seek feedback or wait for it. Managers notice this difference. The intern who asks "how am I doing, and what should I change?" in week three shows they care enough to course-correct before it's too late. The intern who waits for the mid-point review to hear feedback for the first time is leaving their fate to luck.

How you handle code review comments. This is a proxy for coachability, and managers weight it heavily. An intern who responds to feedback with "good point, fixing now" reads very differently from one who argues about why their approach was technically valid. Both might be right. Only one is getting an offer.

Your final presentation. At most companies, your end-of-internship presentation is attended by your skip-level and sometimes other team leads. This is often the only time these decision-makers see your work directly. A sharp, well-structured presentation can tip a "maybe" to a "yes." A rambling, unfocused one can tip a "yes" to "let's see if we have headcount."

How the decision actually gets made

The process is simpler than you'd think. It's also more political than you'd hope.

Step 1: Your manager forms an opinion. They've been forming it since week one. By the time the formal review happens, they already know. The review just forces them to articulate it and defend it.

Step 2: They gather input. Your mentor's feedback is the most important external data point. If your mentor says "I'd love to have this person on my team," that carries enormous weight. If your mentor says "they were fine," that's a soft no. Your manager will also check with anyone else who worked with you: code reviewers, project collaborators, the engineer who helped you debug that production issue.

Step 3: They look at headcount. This is the part you can't control. Even a "greatly exceeds" intern might not get an offer if the team has no open headcount, if there's a hiring freeze, or if the company is cutting costs. Your manager might fight for you. They might create a headcount that didn't exist. But they also might not be able to.

Step 4: The offer goes to HR/recruiting. Your manager submits their recommendation. Recruiting generates the offer letter. At some companies, a hiring committee reviews intern offers, similar to how full-time offers get reviewed. At others, it's the manager's call alone.

The entire process typically happens in the last two to three weeks of your internship or shortly after. Some companies extend offers on your last day. Others take a few weeks post-internship. If you haven't heard anything within a month, follow up with your recruiter.

The five things that tip the scale

Your manager sees dozens of interns over the years. The ones who get offers share certain patterns.

They ask what "great" looks like in the first week. Not in a performative way. A simple question in their first 1:1: "What would make this internship a success from your perspective?" or "What separates a strong intern from an average one on this team?" The answer gives them a target. Most interns never ask.

They make their manager's job easy. The return offer decision requires your manager to write something about you, present your case, and defend it to their manager. The intern who sends weekly updates, documents their work, and tracks their accomplishments gives their manager ammunition. The intern who does good work but leaves no trail makes the case harder to build. This is the same principle behind converting any internship into a full-time offer: make your impact easy to articulate.

They treat the internship like a job, not a class. Show up to meetings on time. Respond to messages within a reasonable window. Follow through on commitments. These behaviors seem basic, but managers report that a surprising number of interns treat the internship with the casualness of a college project. The bar is low. Clear it.

They build a relationship with their mentor, not just a workflow. Meet with your mentor regularly. Ask about their career, not just your project. When they help you, follow up with what you did with their advice. Write them a thank-you note before your last day. Specific, not generic. "Thank you for explaining how the deployment pipeline works. I used that framework to structure my entire project" is better than "Thanks for everything this summer."

They say they want to come back. Explicitly. Clearly. In a 1:1 with their manager, around the midpoint. "I want to come back full-time. What do I need to do to make that happen?" Your manager is not a mind reader. If you don't say it, they might assume you have other plans, and they'll save the headcount fight for someone who's expressed interest.

What you can't control (and how to handle it)

Sometimes the decision has nothing to do with you. Hiring freezes happen. Budgets get cut mid-quarter. Your team gets reorged and the manager who championed you moves to a different org.

If this happens:

• Ask your manager to connect you with other teams that have open headcount. A strong recommendation from one manager often translates across teams.
• Ask your manager and mentor to be references for your job search. A reference from a big tech manager who supervised your internship is valuable.
• Keep the relationships warm. Engineers who didn't get offers due to headcount constraints have gotten called back months later when positions opened up.

The thing to avoid is taking it personally. A "no" due to headcount is not a judgment of your abilities. It's a budget line item. The manager who didn't have headcount for you might be the one who refers you to your next role.

The meta-skill your manager is really evaluating

Strip away the rubric, the code, the project. Your manager is asking one question: "Can I picture this person as a full-time member of my team?"

That covers a lot of ground. Can you handle ambiguity? Will you ask for help when you need it? Will you give and receive feedback without drama? Will you contribute to the team culture or just occupy a desk?

You answer that question with twelve weeks of behavior, not with one impressive demo. The interns who understand this are the ones who come back.