Part of our guide hub: IT internships
At the end of every intake there is a conversation about which interns to keep. It is rarely close, and it is almost never decided by technical skill alone. Having sat in that room many times, here is what actually moves it.
The decision is made in the first three weeks
Not officially, but by week three, a view has formed about whether you are someone who creates work or removes it. Everything after that is confirmation. Which means the strongest single move available to you is to be visibly reliable early, before you know much.
The six things that get people hired
1. You finish things
Interns who complete unglamorous tasks fully (including the boring last 10%, the edge case, the documentation) are rarer than you would expect. Finishing is a reputation you can build in a fortnight, and it does not require talent.
2. You ask questions in a way that costs the other person nothing
Compare: “It’s not working” versus “The endpoint returns 401 after login. I checked the token is in localStorage and the header is set. I think the middleware isn’t reading it. Should I look there or am I in the wrong place?”
The second takes twenty seconds to answer. That difference, repeated fifty times over an internship, determines how much senior attention you get, and senior attention is how you improve.
3. You do not disappear when stuck
The rule most teams want: try for a bounded period (usually thirty to sixty minutes), then ask. Interns who burn two silent days on a blocker cause more damage than interns who ask too often, because the schedule has already moved on.
4. You leave the codebase better than you found it
Fix the typo. Add the missing README line. Write the test nobody wrote. Small unprompted improvements are read as ownership, and ownership is the thing being assessed.
5. You take feedback without defending
Code review is not criticism, and treating it as such is the fastest way to be quietly written off. The right response is a question: what would you have done instead? Interns who visibly improve from review are the easiest hiring decision a manager makes.
6. You understand the business, not just the ticket
Knowing which client the work is for, what they are trying to achieve, and why the deadline exists changes the quality of your decisions, and it is immediately obvious to anyone senior. Ask what problem a feature solves before you build it.
The four things that quietly disqualify people
- Inconsistent attendance and unexplained absence. Fairly or not, this outweighs almost any technical strength.
- Needing to be asked twice. Follow-through is the entire signal.
- Overstating progress. Saying something is done when it is not damages trust permanently. “Sixty percent, blocked on X” is always the better answer.
- Treating it as a certificate exercise. Visible waiting-for-the-letter behaviour is read instantly.
Three weeks before the end
Do not wait for a decision to happen to you.
- Ask directly. “I would like to continue here full time. What would you need to see from me to make that possible?” It is a fair question and it forces a real answer you can act on.
- Write down what you delivered. Features shipped, bugs fixed, what you learned. Managers advocating for you need specifics, and they will not remember them for you.
- Fix your weakest visible gap. You already know what it is. Closing it in the final weeks is itself the argument.
If the answer is no
Ask for two things before you leave: a written reference, and an honest answer on what would have made it a yes. The second is the more valuable. Teams also rehire: several of our strongest engineers were interns who were not kept the first time, closed the gap, and came back.
Technical skill gets you the internship. Reliability, communication and ownership get you the offer. The second set is entirely within your control from day one.
Ezitech converts interns into full-time engineers, designers and marketers every intake. See open tracks or view current roles.