New Grad & Intern Interview Prep: What to Prioritize When Time Is Short
Internship interview prep for CS students: order of topics, project storytelling, and how to balance LeetCode with communication before new grad coding interviews.
Internship interview prep and new grad loops reward signal density: you have limited time between classes, projects, and fatigue. The mistake is copying staff-level grinds. The win is prioritizing what actually moves an entry-level bar: solid mediums, clean communication, and credible projects—not 400 random problems.
Use this alongside the 90-day coding interview plan scaled down (e.g. 45-day sprint), problem reading, and thinking out loud.
Priority stack (if you only have 6 weeks)
| Week block | Primary focus | Why |
|---|---|---|
| 1–2 | Arrays, strings, hash maps, basic trees | Highest frequency at intern/new-grad bar |
| 3 | Binary search patterns, heaps intro | Unlocks many “medium” templates |
| 4 | Graph BFS/DFS basics | Common differentiator without going olympiad |
| 5 | Timed mediums + verbal recap | Converts knowledge to performance |
| 6 | Mocks + weak-tag review only | Fidelity > new intake |
Defer hard-only marathons until return offers or competitive programs demand them.
Projects: minimum viable credibility
Interviewers want one project you can debug live:
- README with run steps, what you built, what you’d improve
- One technical decision you can defend (why SQLite vs Postgres, etc.)
- Tests or deterministic demo—flaky demos erode trust
For take-home style submissions later, see take-home tips.
Behavioral: short and real
You still need STAR stories—even internships. Prepare four:
- Conflict / teamwork
- Failure / bug you caused
- Time pressure (midterms + deadline)
- Learning something new quickly
Details in behavioral STAR guide.
Communication: cheap edge
Many new grads lose on explanation, not algorithms. Budget 15 minutes daily speaking your approach before coding—no IDE. Pair with live pressure drills.
Company context without obsession
Skim FAANG coding differences once; don’t rebuild your plan around logo myths. Level-appropriate mediums transfer.
FAQ
How many problems?
Aim for ~80–120 thoughtful solves + review rather than 300 shallow—quality > trophy count.
Do I need system design?
Intern loops: rare deep SD; new grad sometimes high-level discussions. Touch foundations only if recruiter signals—see system design prep order.
Best mock format for students?
Voice + code sessions train nervous speech under time—try TechInView between peer practices (AI vs human).
GPA / resume?
If screening is tight, use ATS resume checklist—then return focus to interview performance.
Summary: Internship interview prep should front-load high-frequency DSA, one credible project, four STAR stories, and daily spoken reasoning—then mocks that mirror real new grad coding interviews, not influencer problem lists.