How hard are intern coding questions?

Mostly easy to medium, with one or two follow-ups that push toward medium-hard. Interviewers care more about how you get unstuck than about the optimal answer first.

What if I have no projects?

Coursework counts if you can say what you decided and why. Better still, spend two weekends on one small project and push it with a README; it gives you a story for every behavioral question.

Which language should I interview in?

The one you write fastest without looking things up. Python is common because it is short; Java and C++ are fine if they are yours.

What happens after I pass the technical rounds?

At several large companies you enter host matching: teams read your packet and call you for a short fit conversation. It can take weeks, and an offer only comes with a match.

Is our internships timeline article still current?

Yes, our summer 2027 internships article has the month-by-month calendar. This article covers what happens once an application turns into an interview.

Internships · Interviews · Students

Internship interview questions

IT‑Career‑Gym Team 111 October 14, 2026 8 min read

Three students at a wooden table with laptops, sketches and floor plans pinned on the wall behind them — Three laptops, one table. Intern interviews reward the person who can explain their part out loud.

You sent the applications in October, and now the emails are coming back: an online assessment, then "we would like to schedule your interviews". For most large companies the intern loop is shorter than a full-time one, and easier to predict. It is usually two technical interviews of about 45 minutes, sometimes a short behavioral conversation, and at some companies a host-matching stage that decides whether an offer exists at all.

This article is about what gets asked in those 45 minutes, and what interviewers actually write in their notes. The calendar of when applications open is in our separate article on summer 2027 internships.

The usual loop, stage by stage

Stage	Length	What is tested
Online assessment	60–90 min	One or two algorithm problems, automatic scoring against hidden tests
Technical interview 1	~45 min	One coding problem with two or three follow-ups
Technical interview 2	~45 min	Another problem, sometimes a few minutes on your project
Behavioral (some companies)	20–30 min	Teamwork, a hard bug, why this company
Host matching (Google and others)	15–30 min per call	Fit with a specific team; can take weeks, an offer needs a match

One honest warning about host matching: candidates report waiting eight weeks or more, and some never get matched. Keep applying elsewhere while you wait. A passed loop without a host is not an offer.

Coding questions: the patterns that keep coming up

Intern problems are mostly easy to medium. What makes them hard is the follow-up: the second constraint that arrives at minute 25. Eight patterns cover most of what students report.

Pattern	Typical problem	Typical follow-up
Hash map counting	First non-repeating character	Now the input is a stream
Two pointers	Pair with a given sum in a sorted array	Count all pairs, or three numbers
Sliding window	Longest substring without repeats	At most k distinct characters
Stack	Valid brackets	Minimum removals to make it valid
BFS on a grid	Number of islands	Shortest path with obstacles
Binary search	Search in a rotated array	Find the rotation point
Intervals	Merge overlapping meetings	Minimum rooms needed
Simple recursion or trees	Depth of a binary tree	Check if it is balanced in one pass

Notice what is missing: dynamic programming beyond the basics, graphs with weights, segment trees. They appear, but rarely for interns. Spend the time on the eight rows and on talking while you code.

What interviewers write in their notes

Interviewers at large companies fill a short form after each round. The categories differ in wording, but four come up everywhere:

Problem solving. Did you clarify the input, consider edge cases, find a working approach before optimizing?
Coding. Readable names, no copy-paste branches, code that runs on the first or second try.
Communication. Could the interviewer follow your thinking without asking? Silence for five minutes is scored lower than a wrong idea said out loud and corrected.
Testing. Did you walk through an example by hand and catch your own bug?

The last one is the cheapest to improve. Before saying "done", trace one normal input and one edge case through your code out loud. It takes two minutes and interviewers notice every time.

Questions about your project and your motivation

Even purely technical loops often open or close with five minutes on your background. Have answers to these ready, each in under a minute:

"Walk me through a project on your resume." One sentence on what it does, then the hardest decision you made.
"What was the hardest bug?" Name the symptom, how you narrowed it down, and the fix.
"Tell me about working in a team." A disagreement in a course project works fine.
"Why this company?" One concrete product or engineering blog post you read, not "innovation".
"What do you want to learn this summer?" A specific area, ideally one the team works in.

Two weeks before the interview

Days	Focus	On IT Career Gym
1–4	Two patterns a day, three problems each	Express quizzes to find the weak pattern
5–7	Follow-ups: change one constraint on each solved problem	Daily challenge, solved out loud
8	First full mock, 45 minutes	Pair mock, swap roles after
9–12	Fix what the mock exposed; project answers	Pet project write-up
13	Second mock with a different partner	Pair mock
14	Rest. Check the setup, camera and editor

The short version

Two 45-minute rounds, one problem each, follow-ups decide the score. Learn eight patterns, talk while you code, test your own code before saying done, and have a one-minute story about your project. If the company does host matching, keep applying until there is a signed offer.

Questions readers ask

5 questions

How hard are intern coding questions?

Mostly easy to medium, with one or two follow-ups that push toward medium-hard. Interviewers care more about how you get unstuck than about the optimal answer first.
Link to this answer
What if I have no projects?

Coursework counts if you can say what you decided and why. Better still, spend two weekends on one small project and push it with a README; it gives you a story for every behavioral question.
Link to this answer
Which language should I interview in?

The one you write fastest without looking things up. Python is common because it is short; Java and C++ are fine if they are yours.
Link to this answer
What happens after I pass the technical rounds?

At several large companies you enter host matching: teams read your packet and call you for a short fit conversation. It can take weeks, and an offer only comes with a match.
Link to this answer
Is our internships timeline article still current?

Yes, our summer 2027 internships article has the month-by-month calendar. This article covers what happens once an application turns into an interview.
Link to this answer

Sources

Figures were checked against these pages in October 2026. Pay and dates change; the links show where to recheck.

← Back to the blog