Internship · student · Current student (any year)
Software Engineer Intern interview prep, what to expect
A Software Engineer Intern loop is a lighter version of the new-grad process, built around one question: could this person do real work and be worth a return offer? Expect an online assessment (one or two timed problems), then one or two coding rounds — usually easy to medium — and sometimes a short behavioural chat. Full system design almost never appears, and the technical bar, while genuine, is set for students still learning.
What interviewers are really screening for is whether you can code cleanly, talk while you do it, and learn fast. And the internship itself is the real interview: most full-time new-grad offers come from converting a summer internship, so treating those weeks as a 12-week audition matters more than any single round.
Make it yours
This guide is the general bar at SWE Intern. Paste your actual job and Calibrd makes it personal: exactly what that company asks, where your CV is thin, and a full round you rehearse out loud until you're ready. Any tech role, any level. Free to start; the full report is $3.99.
2026 update
This guide covers the general bar at SWE Intern. A few things have changed in 2026, AI is now allowed in coding rounds at Canva and Meta, detection has improved at companies that still ban it, comp has split at staff+, and the post-onsite wait got longer. Read what changed in 2026 →
What you'll be expected to do
- Ship a scoped intern project end-to-end over 10–14 weeks, paired with a mentor
- Learn the codebase and tooling fast; ask questions early instead of staying stuck
- Write tests and respond to code review the same way a full-time engineer does
- Present your project at the end (demo or write-up) — the main conversion signal
- Build a normal working relationship with the team; return offers hinge on 'would we want them back'
Typical interview process
Most companies follow a similar shape for SWE Intern interviews. Total calendar time: 1–3 weeks from recruiter screen to offer.
Sample questions you should be ready for
Representative of what companies ask at this level, not a complete list. Run the free scan above for predicted questions tied to a specific job posting. Calibrd adds voice practice with AI coaching on every answer (technical, system design, behavioural, motivation), and a full voice mock interview: a live round with an AI interviewer who has read the role and your CV, then an honest debrief.
- “Reverse a string in place. Then reverse only the words in a sentence. What changes between the two problems?”
- “Given an array, find the maximum sum of any contiguous subarray (Kadane's). Start with brute force, then improve it.”
- “Count how many times each character appears in a string and return the most frequent one. Which data structure fits best, and why?”
- “Why do you want to intern here specifically, and what do you hope to learn?”
- “Tell me about a class project or hackathon, and what you personally built.”
- “Describe a time you were stuck on something technical. How did you get unstuck?”
Compensation benchmark
Median compensation for SWE Intern at major US tech companies, headline numbers in USD. Pay in markets like London, Berlin and Singapore tends to be meaningfully lower in base terms, and equity ratios vary by company stage.
Top-tier intern pay (Meta, Google, Stripe, quant shops) runs $8–12k/month plus housing. London ~£3,000–4,500/month; Berlin ~€1,800–2,500/month. The real prize is the return offer, not the summer stipend.
How to prep, five tactical tips
Lead behavioural answers with the STAR method, Situation, Task, Action, Result. The tactical tips below build on that structure for this specific role.
- Drill easy-mediums until they're automatic — intern coding rounds rarely go past medium, so breadth and speed beat depth
- Practise the online-assessment format under a timer; it's the first and biggest filter in intern recruiting too
- Have two class-or-hackathon projects you can explain end to end. You won't be asked about work experience you don't have — projects are the whole story
- Prepare a genuine 'why this company' answer. Interns get asked motivation more than new grads, and generic answers stand out badly
- Once you land the internship, treat it as a 12-week interview: ask questions early, over-communicate, finish your project, and tell your manager you want a return offer
Where SWE Intern candidates fail
A few common mistakes that get SWE Intern candidates rejected even when they're otherwise strong. Worth spotting in a mock interview before they show up in a real one.
Applying and interviewing for the summer, then treating the internship itself as a low-stakes summer job.
Why it fails
The internship IS the interview for a full-time offer — most new-grad hires are converted interns. Interns who coast, stay quiet, or don't finish their project don't get return offers, no matter how well they interviewed to get in. Managers decide conversions on 'would we want this person back', which is about the work and attitude across 12 weeks, not a single round.
Fix
From week one, ask your manager what a return offer depends on and check in against it. Finish your project, ask for feedback at the midpoint so you can course-correct, and make your work visible. Treat the end-of-internship demo as your closing argument.
Giving a generic "I want to learn and grow" answer to "why do you want to intern here".
Why it fails
Interns get probed on motivation harder than new grads, because there's little work history to discuss and the company is investing in someone unproven. A canned answer that could apply anywhere reads as "I applied everywhere" — fine, but forgettable, and forgettable loses to the candidate who clearly cares about this team.
Fix
Do 20 minutes of homework: name a specific product, an engineering blog post, or a problem the company works on that genuinely interests you, and tie it to something you've built or studied. Specific and honest beats polished and generic.
Going silent during the coding round and only speaking once the solution is done.
Why it fails
At the intern level, interviewers expect you to still be learning, so how you think matters even more than whether you nail the optimal answer. Code in silence and they can't tell whether you understand what you're doing or got lucky. A student who talks through a slightly-wrong approach often scores better than one who silently produces a correct one.
Fix
Narrate from the first minute: restate the problem, say your plan, think out loud about edge cases. If you're stuck, say what you're weighing — interviewers frequently nudge interns who are visibly reasoning, and never nudge the ones who go quiet.
Recommended resources
Books, courses, and tools that come up most often in SWE Intern prep. No affiliate links.
- 01NeetCode 150 →Pattern-based practice that covers everything an intern coding round throws at you. Focus on the easy and medium tiers.
- 02Blind 75 →The 75-problem shortlist. More than enough surface area for an internship loop if you can do them cold.
- 03Cracking the Coding Interview (McDowell) →The student's reference for data structures and the behavioural framework. The first chapters cover most of what interns are asked.
- 04Tech Interview Handbook →A free study plan written for students and interns — resume tips, a prep schedule, and behavioural guidance in one place.
- 05Levels.fyi internship comp →Real intern pay by company and location. Useful for choosing between offers and knowing what housing or relocation to expect.
Common scenarios
How do I convert a software engineering internship into a full-time return offer?
Return offers are decided on one question: would the team want you back? That's about your work and how you operate over 10–14 weeks, not a final interview. Concretely: in week one, ask your manager what a strong internship looks like and what conversion depends on, then aim squarely at that. Finish your project — an unfinished intern project is the most common reason conversions stall. Ask for feedback around the midpoint so you have time to fix anything. Over-communicate: flag blockers early instead of sitting stuck for two days. Make your work visible through demos and updates. Build a normal working relationship with your team, because conversion is partly a culture-fit read. And near the end, say explicitly that you'd love a return offer — managers advocate harder for interns who clearly want to come back.
Can I get a SWE internship as a first- or second-year student, or is it only for juniors?
It's harder earlier, but not impossible — and the strategy differs. Most structured internships target penultimate-year students (rising seniors), so those spots are the bulk of the market. For first- and second-years, look for programs built for you: Google STEP, Meta University, and various freshman/sophomore or diversity-focused early internships exist precisely for this. Smaller startups care far less about your year — they'll take a strong second-year who can code. The prep is identical to any intern loop (easy-medium data structures, be able to explain your projects), but your resume leans harder on projects, hackathons, and coursework since you have less to show. Apply early — early-career programs often have earlier, smaller cycles — and use every referral you can get, because the resume filter is the hardest part this early.
What's the difference in interview difficulty between a SWE internship and a new-grad SWE role?
Same shape, lower bar. Both run an online assessment, one or two coding rounds, and a behavioural, and both filter hard at the assessment. The differences: intern coding problems rarely go past medium, where new-grad loops occasionally push a harder problem; interns almost never get a system design round, while new-grad loops sometimes include a light one; and interns get probed on motivation and learning more, since there's less history to discuss. The bar is calibrated to 'can this student do real work and grow', not 'can this person ship independently'. If you can comfortably clear a new-grad loop, an intern loop is well within reach — the reverse isn't always true, so doing internship prep now sets you up for the new-grad cycle later.
Frequently asked questions
I'm a student with no work experience — is this guide still for me?
Yes — this guide assumes exactly that. A SWE internship loop is designed for students who haven't worked full-time. Your projects, coursework, and hackathons are the evidence interviewers use, and the technical bar (easy-to-medium data structures and algorithms) is set with students in mind. The one thing to internalise early: the internship itself is the real interview for a full-time offer, so this guide covers both landing the internship and converting it.
How long should I prep before my SWE Intern onsite?
Intern loops are short — 1–3 weeks — and lighter than new-grad, but the online assessment still gates everything. Drill easy-mediums until they're automatic and prepare a genuine 'why this company' answer; those two cover most intern rounds.
What's the most common mistake candidates make at the SWE Intern bar?
Treating the internship as a summer job instead of a 12-week interview. Most full-time offers are converted internships, so how you show up across those weeks — finishing the project, taking feedback, being someone the team wants back — is what actually decides the return offer.
What if my interview process is different from what's listed?
Most variation is at the edges. Major tech companies (FAANG, scale-ups, mid-size SaaS) follow processes within 1–2 rounds of what's described. Smaller startups often run fewer rounds (3–4) but the bar at each round is similar; less-tech-mature companies sometimes skip system design or behavioural rounds entirely. Read the JD and ask the recruiter at the screen, they'll tell you what's coming.
How does this guide compare to running a free scan?
This guide covers the general bar at Internship · student. The free scan reads your specific job description and returns predicted questions for that exact role + company, a calibrated comp benchmark, and (with your CV) experience-gap analysis and an ATS resume check. PDF emailed.
Walk in ready
Walk into your next SWE Intern interview ready.
Paste your actual job and Calibrd shows you exactly what that company asks, where your CV is thin, and what it should pay. Then rehearse the round out loud with honest feedback until you're confident. Any tech role. Free to start.
Free to start · Free reports + first mock free · Paid plans from $3.99