How to Know If You're Ready to Apply for Internships

Most tier-2 and tier-3 students don't apply for internships because they feel unready, not because they lack skills. That feeling has no threshold, so it never resolves — you can wait a full year and still feel the same. Readiness is a set of observable signals: can you solve two medium problems in 45 minutes, explain one project end-to-end for 10 minutes, and produce a one-page resume with two quantified bullets? This post gives you a pass/fail self-test, role-wise bars, and a 14-day sprint to close the biggest gap before you mass-apply.

Why 'not ready' is the most expensive tier-3 trap

Waiting for 100% readiness is a strategy that fails quietly. You don't get rejected — you just never enter the funnel, so you never collect the feedback that would tell you what's actually missing. Students who apply to 10+ internships before final year consistently report higher interview confidence than those who wait, because the first three interviews teach more than three months of solo prep.

There's a second cost. Referrals and cool-off periods are finite. If you burn a senior's referral at a company you weren't ready for, you don't get a second shot in the same cycle. The fix isn't "apply everywhere" or "wait until perfect" — it's a threshold you can actually measure, plus a small number of practice applications to calibrate.

If you want the full sequencing picture before you start, the software internship roadmap for tier-3 students lays out the year-by-year plan this post plugs into.

The 5-item internship readiness self-test

Run this today. Each item is pass/fail, and you need at least 4 of 5 to mass-apply. Anything less means you're applying to learn, which is fine — but do it deliberately, to companies you don't care about.

• DSA: Solve two medium problems (arrays, strings, hashing, two pointers, basic trees) in 45 minutes without looking at solutions, and explain your approach out loud.
• Project depth: Walk through one project end-to-end for 10 minutes — problem, architecture, one hard bug, what you'd change.
• Resume: One page, two quantified bullets per project, no spelling errors, and a senior can understand each project in 30 seconds.
• GitHub: At least one pinned repo with a real README, a deployed link, and commits in the last 3 months.
• Behavioral: Answer "tell me about yourself" in 90 seconds and "why this company" in 60 seconds without rambling.

If you fail two or more, don't mass-apply yet. Spend 14 days on the biggest gap — the sprint plan is below.

The role-wise readiness bar — SDE vs data vs QA vs startup generalist

There is no single internship skills checklist. A QA intern and an SDE intern at the same company are screened against different bars, and using one checklist for all four role types is why students over-prepare for the wrong thing.

SDE intern (product startup)

Roughly 150–250 solved problems with clean explanations, one strong project with a non-trivial backend or algorithm, and comfort with one language's standard library. Startups weight the project more than the problem count.

SDE intern (service company — TCS, Infosys, Wipro)

Aptitude plus basic coding. 50–80 solved problems is usually enough if your aptitude is sharp. Service companies often list 60% or 6.0 CGPA cutoffs — check the current cycle's eligibility page, because these shift year to year.

Data / analyst intern

SQL joins and window functions, one dashboard or analysis project with a real dataset, and basic Python (pandas). DSA matters less here; the ability to explain a finding matters more.

QA / support / startup generalist intern

One deployed project, clear written communication, and willingness to do unglamorous work. These roles convert to full-time offers more often than students expect, and they're the easiest entry point in 2nd year.

The 3-project rule for internship applications

Three projects, three different jobs. One with a real user or real usage (even 20 classmates counts). One with a non-trivial backend or algorithm — a CRUD app doesn't qualify. One that maps directly to the job description you're targeting, so you can say "I built this because your team does X."

If you're choosing what to build next, the projects that get you shortlisted breakdown shows which project types actually move a recruiter from skim to shortlist.

Resume and GitHub signals that pass the first scan

A recruiter spends roughly 7.4 seconds on the first resume scan, according to the Ladders 2018 eye-tracking study. In that window, they're looking for role fit, not reading your bullet points. So the top third of your resume has to carry the signal: your strongest project, your stack, and one number.

On GitHub, three things matter more than repo count: a pinned repo with a README that explains what the project does and how to run it, a deployed link, and commit activity in the last 90 days. A repo with 40 commits last year and nothing since reads as abandoned. If your resume needs a structural pass, the resume checklist for freshers covers the one-page format and bullet structure.

Does CGPA block internship applications?

For most off-campus internships, CGPA is a soft filter. Many startups don't ask at all. Service companies often list 60% or 6.0 CGPA cutoffs — check the current cycle's eligibility page, since these change. A low CGPA hurts more in on-campus shortlisting than off-campus, where projects, GitHub activity, and referrals can compensate.

If your CGPA is below 6.0, don't hide it — but don't lead with it either. Put your strongest project above your education section, and apply off-campus where the filter is weaker.

The 2-week readiness sprint

If you failed two or more self-test items, spend 14 days closing the biggest gap before mass-applying. The sprint is deliberately narrow — one gap, not five.

• Days 1–3: Pick the single weakest item. If it's DSA, do 10 medium problems on one pattern (say, two pointers) until you can explain each without notes.
• Days 4–7: Fix the resume and GitHub. Rewrite two bullets per project with a number or outcome. Pin one repo, write a real README, deploy it.
• Days 8–11: Rehearse the project walkthrough and behavioral answers out loud, recorded. Aim for 10 minutes and 90 seconds respectively.
• Days 12–14: Apply to 3–5 practice companies you don't care about. Treat the interviews as calibration, not auditions.

Interviews test compression, not knowledge. You can reverse a linked list on paper but freeze when asked to narrate the pointer moves out loud — that gap only closes by rehearsing aloud, not by solving more problems silently.

When to apply even if you fail the self-test

Apply to 3–5 practice companies regardless of your score. Real interview feedback is worth more than another week of solo prep, and the cost of a practice rejection is zero. But hold off on mass-applying to dream companies until you pass at least 4 of 5 items — burning a referral or a cool-off period at a top company is expensive and irreversible in the same cycle.

If you want a structured read on where you actually stand before you start applying, the internship readiness self-assessment benchmarks your background against current market and hiring data, with a human expert reviewing the output before it reaches you.