Here is the single fact that costs Indian students the most US internships, and almost nobody on campus says it out loud: applications for a US summer internship generally open between September and December of the previous year, with Amazon opening as early as July or August — and most programmes fill on a rolling basis long before the posted deadline. That window lands squarely inside your Indian odd semester, months before anyone at home starts thinking about summer. Preparation has to be finished when it opens, not started. This is the twelve-month stack that gets you there.

Key takeaways

  • The US application calendar runs a full year ahead of the Indian academic instinct — build in the even semester, apply in the odd one.
  • Startups hire off-cycle year-round, which is the opening for anyone who misses the big-programme window.
  • LeetCode is the Big Tech gate, not the startup gate: a working baseline is roughly 100–150 problems, not a thousand.
  • Résumé, personal site, GitHub and merged PRs are one system — each exists to make the next one easier to verify.

The calendar nobody explains on an Indian campus

US recruiting has two distinct clocks. The large-programme clock is early and rigid: tech applications open roughly September to December for the following summer, Amazon from July or August, and the advice from US careers offices is to apply within the first two weeks of any opening because rolling admissions fill seats before deadlines. Students are internalising this earlier every year — Handshake’s 2025 Internships Index found 41% of the Class of 2025 had applied to at least one internship by January, up from 34% two years earlier. The second clock is the startup clock, and it barely has a calendar at all: a seed-stage company hires when it raises money or when the roadmap outgrows the team, which can be any week of the year. For an Indian student, the startup clock is the more realistic target — but only if the preparation is already done, because those roles open and close in days.

The honest take on LeetCode

Every Indian prep forum converges on the same advice: grind five hundred problems. For Big Tech that is roughly correct — those companies still lean on algorithm screens. For the US startups most likely to hire a second-year student remotely, it is close to a waste of a semester. Reporting on 2025 technical hiring found 62% of AI-native startups founded in the previous two years had eliminated LeetCode-style questions or significantly reduced their weight, a 35% increase over 2023, shifting instead to take-home projects and real tasks. And 78% of developers say hiring assessments do not align with real-world work — small teams broadly agree with them. A sane allocation: about 100–150 problems covering arrays, strings, hashing, two pointers, trees, graphs and basic dynamic programming, enough to pass a screen if one appears. Every hour beyond that returns more if spent shipping something real.

Résumé, site and GitHub are one system

Think of these three artefacts as a funnel, each one buying attention for the next. The résumé is a 7.4-second document — that is the measured initial scan time in Ladders’ eye-tracking study — so it exists to get a link clicked, not to tell your life story. One page, US format, a live URL in the top three lines, education compressed to two lines, no JEE rank and no board percentages. The personal site is the click destination: about half of hiring managers say they are open to navigating to an online portfolio, and one page with three projects, a live link each, and a short “what I’m working on” note does the job. A weekend is plenty; a six-week redesign is procrastination. Then GitHub carries the actual verification — what recruiters check when they get there is pinned repositories, readable commits and evidence that other people’s code has passed through your hands.

internship-prep-stack-layers

The 12-month prep stack, month by month

  1. Months 1–2 — pick a stack and build one thing that runs. One language, one framework, one deployed project with a live URL. Depth beats breadth because founders hire for a specific gap.
  2. Month 3 — get real users. Twenty people who are not your friends. “Used by 200 students at my campus” is a sentence a US founder can evaluate; “built a clone of X” is not.
  3. Months 3–5 — merge three pull requests. Start with docs and small bugs to learn review culture, then take a real issue. The first-contribution guide covers finding them.
  4. Months 4–6 — LeetCode to baseline, then stop. 100–150 problems across the core patterns. Timebox it; do not let it eat the semester.
  5. Month 6 — clean the GitHub. Pin your three best repositories, write a README for each stating what it does and who uses it, and delete or archive the dead ones.
  6. Month 7 — build the one-page site in a weekend. Name, one line on what you build, three projects with live links, GitHub, email, timezone. Deploy it free and move on.
  7. Month 8 — write the one-page US résumé. Live links above the fold, outcomes not stacks, education in two lines, US spelling and date formats, no JEE rank.
  8. Month 9 — publish two short technical posts. A bug you debugged; a decision you made and why. This is your written communication evidence, which remote teams screen hardest.
  9. Months 9–10 — apply into the big-programme window. September onward, within two weeks of each opening. Treat it as free optionality, not the plan.
  10. Months 10–12 — run the startup track properly. Twenty-five shortlisted companies, six-sentence founder emails, one follow-up each, and a scoped trial task as the ask. See the cold email playbook and the YC startup route.

Where Tierones fits

Twelve months of this produces exactly one thing: evidence. The problem with evidence built alone is that a founder 12,000 km away has no cheap way to confirm any of it is yours. Tierones verifies that you are a real student at an IIT, NIT or IIIT through your .ac.in email, and Tier Rank turns commits, reviews and shipped projects into a signal a US employer can trust on sight. The calendar is the part you cannot outrun — the window opens in August whether or not you are ready. Start the stack in the semester before you need it, and you will be.

FAQ

When should an Indian student start applying for US internships?

Far earlier than most expect. Tech applications for the following summer generally open September to December, with Amazon as early as July or August, and rolling admissions fill seats before posted deadlines. That window sits inside your Indian odd semester, so preparation must be finished before it opens.

How much LeetCode do I actually need for a US startup internship?

Much less than for Big Tech. A majority of recently founded AI-native startups have cut or downgraded LeetCode-style questions, and 78% of developers say assessments do not resemble real work. Roughly 100–150 problems across the standard patterns is a sane baseline; hours beyond that return more if spent shipping something real.

Do I need a personal website, or is GitHub enough?

GitHub is the requirement and a personal site is the multiplier. About half of hiring managers say they would open a candidate’s online portfolio, and one link that loads a summary of what you shipped is easier to act on than a PDF. One page, three projects, a live link each — a weekend is enough.

Building in second year at an IIT, NIT or IIIT? Tierones is an invite-only network where verified students get matched to startups that hire on proof of work — request an invite with your .ac.in email and your GitHub.