Usual length
Most often two to six months. Three is the norm: enough time for someone to settle in and show what they can do, and for the company to decide whether to keep them.
Under two months rarely works: the first weeks go on finding out where everything lives. Beyond six is also rare — by then you're either hired or parted with.
Student programmes follow the academic calendar: summer ones run two or three months, winter ones are shorter.
What the length depends on
- Company size. Large programmes have a fixed, published duration. Small ones negotiate as they go.
- Your hours. Full-time is shorter, part-time longer.
- The discipline. A tester often needs two months to start being useful. A backend developer needs longer just to understand how the system fits together.
How it ends
Three outcomes:
- A job offer. That's the point of the whole exercise. In good programmes a meaningful share of internships end this way.
- An extension. They keep you on for another stretch — usually when they like you but there's no budget for a permanent seat yet.
- Parting ways. Not necessarily because of you: sometimes a direction gets closed or plans get cut.
If no offer comes
First, ask for feedback and a reference. Even without an offer you keep the important part: a line of real experience and someone who can vouch for you.
Then don't linger. Start looking a month before the internship ends, not after. Fresh experience with a clear account of what you did works best immediately.
Getting the most out of it
- Write down what you do. Three months later the details blur, and interviews ask about exactly those.
- Ask for reviews of your work. People who regularly get comments on their code grow faster.
- Remember what didn't work. An honest account of a failure and what you concluded leaves a better impression than a list of wins.
If no internship happened
Work on a shared project gives comparable density: the same few months, the same tasks, code discussion and deadlines. The difference is it doesn't end on a schedule — and the person you worked with can confirm what you did.
Открытые роли по теме статьи
Читать полезно, а делать — ещё полезнее. В эти команды можно написать прямо сейчас:
- iOS-разработчик — MAIBO - MedTech-пилот для клиник
- Контент-маркетолог / комьюнити — CohortX — платформа командных пет-проектовмаркетингtelegramseoконтент
Похожие статьи
- Changing careers after thirty: what's realisticAge as a real obstacle and as an exaggerated fear, how your previous experience helps, and how long it takes.
- Смена профессии после тридцати: что реальноВозраст как реальное препятствие и как преувеличенный страх, чем прежний опыт помогает и сколько это занимает.
- Choosing a direction: front-end, back-end or testingA practical way to decide instead of reading comparisons: what to try, what to notice, and why the choice isn't final.