MyInternships.in
126 QUESTIONS · 9 TOPICS · JUNIOR TO SENIOR

Internship Prep Interview Questions and Answers

A complete, practical guide to landing a technology internship — coding rounds, online assessments, system design, behavioural interviews, resumes and portfolios, application timelines and trackers, quant interviews, the named company programmes candidates search for, and the eligibility rules that decide which roles you can actually apply to. Every answer is written to be useful on its own, with the reasoning an interviewer is listening for and the mistake most candidates make.

Start with DSA & Patterns →Browse Internships

All 9 topics

126 questions in total, each with a model answer. Pick the services your target role actually uses — or work top to bottom for a full sweep.

01DSA and Coding Interview Patterns20 questions02Online Assessments (HackerRank, CodeSignal, Karat)13 questions03System Design and Low-Level Design for Interns16 questions04Behavioural and HR Interview Questions14 questions05Resume, Portfolio and GitHub for Tech Internships14 questions06Application Strategy, Timelines and Internship Trackers14 questions07Quant, Trading and Financial Engineering Interviews12 questions08Named Company Internship Programmes11 questions09Eligibility, Locations, Remote Work and Internship Cycles12 questions

Which interviews is this for?

These questions are drawn from the rounds candidates actually sit for cloud engineer, DevOps engineer, SRE, data engineer, cloud architect and platform engineer roles — from fresher and internship screens through to senior and architect-level design discussions. They map to the interview loops run at:

  • Zerodha
  • Razorpay
  • Swiggy
  • Zepto
  • Meesho
  • CRED
  • Groww
  • PhonePe
  • Postman
  • BrowserStack
  • Freshworks
  • Zoho
  • Fractal Analytics
  • Sarvam AI
  • Skyroot Aerospace
  • Ather Energy
  • Delhivery
  • Nykaa
  • PhysicsWallah
  • Zetwerk

They also line up closely with the certification syllabuses, so this doubles as revision before a certification exam.

18 of the most-asked Internship Prep interview questions

A sample from every topic. Open any topic above for the full set of answers on that service.

1
Junior level

How many LeetCode problems should I actually solve before an internship interview?

Answer: Between 120 and 200 problems solved properly is far more effective than 500 rushed. Work through a curated list — Blind 75 first, then NeetCode 150 — because they are chosen to cover each pattern once rather than to repeat the same idea.

Why interviewers ask this: Interviewers are testing pattern recognition, not recall. A candidate who has solved 150 problems across all patterns will recognise an unseen question; one who has solved 500 problems in three patterns will freeze on the fourth. Track which pattern each problem belongs to, and revisit any pattern where you needed the solution.

2
Junior level

What is the difference between Blind 75 and NeetCode 150, and which should I do first?

Answer: Blind 75 is the minimum viable coverage — one representative problem per core pattern. NeetCode 150 is a superset that adds a second and third problem per pattern so the pattern actually sticks. Do Blind 75 first to map the territory, then NeetCode 150 to build fluency.

Why interviewers ask this: If you have under four weeks, finish Blind 75 and revise it twice rather than starting NeetCode 150 and leaving it half done. Partial coverage of every pattern beats complete coverage of half of them.

3
Junior level

What is a CodeSignal score and what counts as good for an internship?

Answer: CodeSignal reports a General Coding Assessment score from 300 to 850, derived from how many of four tasks you complete correctly and how quickly. Most companies that screen on it set their bar between 600 and 700; 750+ clears essentially every internship threshold.

Why interviewers ask this: The four tasks rise in difficulty, and the last is often not solvable in the time left. Banking tasks 1 to 3 cleanly usually beats gambling the clock on task 4 — partial credit exists for passing test cases, so submit something that runs rather than leaving an elegant half-finished attempt.

4
Junior level

How do I raise a CodeSignal score from around 600 to 750+?

Answer: Almost always by going faster on tasks 1 and 2, not by getting stronger at task 4. Practise implementation-heavy string and array simulation problems until they take five minutes rather than fifteen, and keep a snippet file of your language's parsing idioms.

Why interviewers ask this: The GCA rewards speed on the easy half. Candidates plateau because they train hard algorithms while losing ten minutes to fiddly index handling in task 2. Time yourself; if task 1 takes more than eight minutes, that is the thing to fix.

5
Junior level

Do internship interviews actually include system design?

Answer: Full distributed-system design rounds are uncommon for interns. What is common is a scoped design discussion — "how would you build a URL shortener" or "design the classes for a parking lot" — testing structured thinking rather than production architecture experience.

Why interviewers ask this: Treat it as a conversation about trade-offs. Nobody expects an intern to size a Kafka cluster; they expect you to ask what the requirements are, propose something reasonable, and know why you chose it.

6
Mid level

How do I structure a system design answer in 30 minutes?

Answer: Spend five minutes on requirements and scale, five on the API and data model, ten on the high-level design, five on one deep dive the interviewer picks, and five on bottlenecks and trade-offs. Write the requirements down and confirm them before designing.

Why interviewers ask this: The most common failure is drawing boxes before agreeing what the system must do. Asking "read-heavy or write-heavy?" and "how many users?" changes the entire design and shows the interviewer you know that.

7
Junior level

What is the STAR method and how do I use it without sounding rehearsed?

Answer: Situation, Task, Action, Result: set the context in one or two sentences, state what you specifically had to do, spend most of the answer on your actions, and end with a concrete outcome. Keep it to about two minutes.

Why interviewers ask this: The common imbalance is a ninety-second Situation and a ten-second Action. The interviewer is assessing what *you* did, so use "I" rather than "we" for your own contribution, and quantify the Result whenever you honestly can.

8
Junior level

How many stories should I prepare, and which ones?

Answer: Five to six flexible stories cover almost every question: a technical challenge you solved, a conflict or disagreement, a failure and what changed afterwards, a time you led or took initiative, a time you learned something quickly, and a project you are proud of.

Why interviewers ask this: Prepare stories, not answers. One good project story can be told as a technical-challenge answer, a teamwork answer or a learning answer depending on which part you emphasise. Memorising per-question scripts breaks the moment the wording changes.

9
Junior level

What does "ATS-friendly" actually mean for a resume?

Answer: It means the applicant tracking system can parse your text reliably: a single-column layout, standard section headings, a common font, no text inside images or text boxes, and a PDF export with selectable text.

Why interviewers ask this: Test it by opening your PDF and copying all the text into a plain editor. If the order is scrambled or content is missing, the parser will see the same mess. Two-column templates are the most frequent cause — the parser interleaves the columns.

10
Junior level

Should a student resume be exactly one page?

Answer: Yes. For an internship with no full-time experience, one page is the expectation, and a second page dilutes rather than adds. Cut older school achievements before cutting projects or skills.

Why interviewers ask this: Recruiters spend well under a minute on a first pass. Everything below the fold on page one is already at risk; page two is rarely read at all for intern applications.

11
Junior level

When do Summer internship applications actually open?

Answer: For US-headquartered tech companies the cycle starts unusually early: many Summer roles open between July and September of the previous year, with the bulk of large-company postings live by October. Indian product companies and campus processes run later, typically August to January.

Why interviewers ask this: The practical consequence is that applying in January to a cycle that opened in August means competing for the remaining seats. Set up alerts in June and check weekly from July rather than waiting for placement season.

12
Junior level

Which community internship tracker lists are worth following?

Answer: The best known are the SimplifyJobs Summer internships repository, the Pitt CSC list it grew from, and several GitHub "New Grad and Intern" boards. They are community-maintained, updated daily during the season, and list postings with direct application links.

Why interviewers ask this: Treat them as a discovery feed, not a database of truth — entries can be stale, and closed roles linger. Always verify on the company's own careers page before investing time, and never pay for a "premium" mirror of a free public list.

13
Mid level

How is a quant interview different from a software engineering interview?

Answer: Quant interviews weight probability, statistics and mental mathematics far more heavily, and often include market-making or betting games that test decision-making under uncertainty. Quant developer roles add serious C++ and low-latency systems depth.

Why interviewers ask this: The three tracks differ: quantitative researcher is mathematics and statistics heavy, quant developer is systems and C++ heavy, and trader is games, mental maths and risk judgement. Prepare for the one you applied to — the preparation is not interchangeable.

14
Mid level

What probability topics come up most?

Answer: Conditional probability and Bayes, expectation and linearity of expectation, variance, common distributions (binomial, Poisson, normal, exponential), random walks, Markov chains and optimal stopping.

Why interviewers ask this: Linearity of expectation is the single highest-leverage tool — it works even when events are dependent, which is what makes hard-looking problems collapse. The classic worked example is the expected number of coin flips to see a given pattern.

15
Junior level

What is Google STEP and who is eligible?

Answer: STEP (Student Training in Engineering Program) is Google's internship for students early in their undergraduate degree — typically first and second years — rather than penultimate-year students. It pairs a project with structured mentoring and is aimed at broadening access to the industry.

Why interviewers ask this: Its distinguishing feature is that it targets students who would normally be considered too early. Google also runs a standard Software Engineering Internship for later-year students, so apply to whichever matches your year — applying to the wrong one is a common, avoidable rejection.

16
Junior level

How does the Amazon SDE internship process work?

Answer: Typically an online assessment with coding problems and a work-simulation section, followed by one or two interviews mixing data structures and algorithms with leadership-principle behavioural questions.

Why interviewers ask this: Amazon weights the leadership principles genuinely — behavioural answers are scored against named principles, not treated as small talk. Preparing five detailed STAR stories mapped to principles matters as much here as the coding practice.

17
Junior level

Which year of study can apply for a tech internship?

Answer: It varies by programme. Most standard internships target penultimate-year students, but several large companies run dedicated first and second-year programmes, and Indian startups frequently hire from any year based on skill.

Why interviewers ask this: Read the eligibility line on the posting itself. Applying a year early to a penultimate-year role is usually filtered automatically, whereas the early-year programmes exist precisely for that group and are less crowded.

18
Junior level

What are the main internship cycles?

Answer: Summer is the largest cycle. Winter and Spring internships exist but are smaller. Six-month industrial training or co-op placements are common for Indian engineering students in their final year, and startups hire off-cycle year-round.

Why interviewers ask this: Off-cycle and Winter roles have materially less competition. If you missed the Summer window, target six-month industrial training and startup roles rather than waiting a full year.

Internship Prep interview FAQs

How long does it take to prepare for a tech internship interview?

Six to eight weeks of consistent work is realistic if you already know one language well: roughly four weeks on data structures and algorithms by pattern, one on CS fundamentals and basic design, one on behavioural stories and your resume, and continuous applying throughout. Starting to apply only after you feel ready is the most common scheduling mistake, because pipelines open early and fill on a rolling basis.

What is the single highest-impact thing I can do?

Apply early in the cycle. Most large-company internship pipelines review on a rolling basis, so the same application submitted in week one and month four faces very different odds. After that, practising problems by pattern with spaced repetition beats raw problem count.

Do I need a CS degree to get a software internship?

No. Non-CS engineering branches, science graduates, bootcamp graduates and self-taught developers are all hired, particularly by startups and mid-size product companies. What substitutes for the degree is demonstrable work — projects you can explain in depth, a readable GitHub, and solid fundamentals.

How many internships should I apply to?

For an off-campus search, a few hundred applications across a season is normal, split between a small set of tailored applications to target companies and a broader base. Response rates of 3 to 8 percent are common and are not a judgement on your ability — track your funnel so you know whether to fix your resume or your assessment speed.

Are unpaid internships worth taking?

Generally not in technology, and never one that asks you to pay a fee or buy a course to participate. Legitimate Indian technology internships pay a stipend. If an offer requires payment from you, treat it as a training sale rather than a job.

What matters more — projects or LeetCode?

Both, at different stages. Projects get your resume shortlisted and give you something to discuss in behavioural and technical deep-dive rounds; algorithmic practice gets you through the coding round and online assessment. Neglecting either one is where most candidates stall.

Prepared? Now find the role.

Cloud internships and fresher jobs across India, updated daily.

Browse Internships