What a new grad loop actually looks like
Most new grad pipelines in 2026 run four stages, and only two of them are the ones candidates spend their time on.
| Stage | Typical format | What it is really testing |
|---|---|---|
| Online assessment | 60-90 min, 2-4 auto-graded problems | Can you produce working code without a human prompting you |
| Recruiter or HireVue screen | 15-30 min, recorded or live | Communication, interest in the company, obvious red flags |
| Technical phone screen | 45 min, 1-2 problems, shared editor | Pattern recognition plus whether you think out loud |
| Final loop | 3-5 rounds across a day | Coding depth, basic design sense, behavioral consistency |
The online assessment is where most new grad candidates are eliminated, and it is the stage people practise least deliberately. It is also the one stage where nobody can help you mid-problem, which makes it a pure test of preparation.
The coding questions you should expect
New grad coding questions cluster tightly. Across the loops we see described publicly, the same handful of patterns carries the majority of problems:
- Arrays and hashing - two sum variants, grouping, frequency counting. Nearly guaranteed somewhere in the pipeline.
- Two pointers and sliding window - longest substring problems, container problems, sorted-array merges.
- Trees and graphs - breadth-first and depth-first traversal, level-order printing, simple path problems. Rarely anything exotic.
- Binary search - on a sorted array, and the harder variant of searching on an answer range.
- Dynamic programming, lightly - climbing stairs, house robber, coin change. New grad loops ask the entry-level DP problems, not the hard ones.
That is roughly the shape of the Blind 75, which is why it remains the standard recommendation. Our 15 patterns guide covers the recognition step, which is the part that transfers to problems you have never seen.
The behavioral questions, which carry more weight than you think
With no professional track record to interrogate, interviewers fall back on school, projects and internships. The questions are predictable:
- Tell me about a project you are proud of - and expect follow-ups about what you specifically built versus what your teammates built.
- Describe a time you disagreed with someone on a team project.
- Tell me about something technical you had to learn quickly.
- What is a bug that took you far too long to find, and what did you change afterwards?
- Why this company, and why this team?
Answer in STAR form and keep the situation short. The common new grad failure is spending three minutes setting up a class project and thirty seconds on what they actually did. Interviewers are scoring the second part.
A preparation order that fits a semester
- Weeks 1-3: patterns, not problems. Work the Blind 75 by pattern group and re-solve anything you needed a hint for.
- Weeks 4-5: timed online assessment practice. Two problems, 70 minutes, no interruptions, no looking things up. This simulates the stage that eliminates the most people.
- Week 6: write five STAR stories from real projects and say them out loud. Not notes - out loud, timed to about two minutes.
- Week 7 onward: mock rounds under real conditions. If you have nobody to practise with, our notes on practising without a partner cover the workable substitutes.
If you have longer, the 8-week FAANG plan is the same shape with more depth per stage.
Where CoPilot Interview fits
Disclosure: we build an interview assistant, so treat this as a disclosed pitch. Preparation handles the questions you anticipated. The hard moment is the one you did not, at 10am, with an interviewer waiting. CoPilot Interview is a native Windows and macOS app that puts suggested answers on your own screen in about four seconds, across coding, system design and behavioral rounds, with a permanent free tier that needs no credit card.
There is a longer discussion of where this sits ethically in our honest take on AI in interviews, including the cases where you should not use it at all.
Frequently asked questions
How many LeetCode problems should a new grad do?
Between 75 and 150, worked properly, beats 400 skimmed. The Blind 75 covers every major pattern at least once; the NeetCode 150 adds depth where 75 leaves gaps. The number that matters is how many you can re-solve from scratch a week later, not how many you have seen.
Are new grad interviews easier than experienced ones?
The coding bar is similar, sometimes slightly lower on hard dynamic programming, but the loop is less forgiving in other ways. You have no work history to fall back on, so a weak project explanation costs more than it would for a mid-level candidate.
Do new grads get system design questions?
Usually not a full system design round. Some loops include a lightweight design discussion - model a parking lot, sketch a URL shortener - which tests whether you can structure a problem, not whether you know distributed systems.
What is the most common reason new grads get rejected?
The online assessment, by a wide margin. It happens before any human sees you, there is no partial credit for a good approach, and most candidates practise it far less deliberately than they practise interview-style problems.
Walk into the round with a second pair of eyes
CoPilot Interview is a native Windows and macOS app that puts suggested answers on your own screen in about four seconds, across coding, system design and behavioral rounds. The free tier is permanent: 15 minutes a day, no credit card.
Try it free