How internship selection works at a large company

Stage 1. The application form

The first filter is administrative. They look at your field, year, location and availability. This stage screens out people who don't fit the conditions, not people who lack knowledge.

Fill it in carefully and don't inflate your level with technologies: it will surface at the interview and leave a worse impression than a modest, honest form.

Stage 2. The test

Usually an hour or so: logic puzzles, a little maths, simple programming. What's measured isn't breadth of knowledge but whether you can think quickly against a clock.

Prepare for the format specifically: work through twenty or thirty simple problems and practise speed. Knowledge is rarely the bottleneck here — time is.

Stage 3. The technical interview

Forty to sixty minutes. Fundamentals in the language you listed, a simple problem talked through, sometimes a couple of database questions.

The main thing is to reason out loud. The interviewer needs to follow your thinking: how you break down the problem, what you clarify, how you check your answer. A silent correct answer scores lower than a talkative search for one.

Stage 4. The team conversation

About motivation, how you learn, and how you work with people. Expect questions on why development, how you studied, what you built, and how you coped when things didn't work.

Answer like a human being. Rehearsed phrasing is audible and works against you.

Timelines

Three weeks to two months from application to answer. That's normal. Plan so that other applications run in parallel, or the intake will close while you wait on one reply.

What strengthens an application

A finished project, contributions to open source, and experience working in a team. That last one especially: an internship puts you into a team, and being able to negotiate there matters more than one more memorised algorithm.