Engineering Internship Guide

• Build 2 technical projects that demonstrate the skills relevant to your target role (web dev, ML, embedded systems)
• Deploy projects online — GitHub + a live demo URL is exponentially more credible than "implemented locally"
• Solve 100 LeetCode problems (minimum: Easy 40 + Medium 50 + Hard 10) before applying to product companies
• Learn one technology deeply rather than six things shallowly — full-stack (React + Node), ML (PyTorch + sklearn), or embedded (STM32/Arduino + C)
• Contribute to 1–2 open source projects — even small documentation fixes or bug reports show initiative

• Write a 1-page resume: name + contact + education + 2–3 projects + 2–3 experiences (including college clubs) + skills
• Tailor your resume for each role: if the JD says React, your resume should prominently feature React projects
• Apply to 30–50 companies — not 5. Internship conversion rates are 10–20% per application at the shortlisting stage
• Use LinkedIn, Unstop, Internshala, AngelList, and direct company career pages simultaneously
• Send cold emails to engineers at target companies — a referral from an employee multiplies shortlisting odds by 3–5x

• Practice mock technical interviews — not just LeetCode, but timed whiteboard-style explanation of your thinking
• Prepare 3–5 behavioral stories using STAR format: a challenge you solved, a team conflict, your biggest technical mistake
• Research each company you interview with: what they build, their tech stack, recent product launches
• Complete at least 2 mock interviews with peers or a mentor before the real interview
• Review your own projects deeply — you must be able to explain every technical decision in your project

• Ship something in your first 2 weeks — a small feature, a bug fix, a test suite. Visible output builds credibility fast
• Ask your manager explicitly about return offer criteria in week 2 — not at the end of the internship
• Volunteer for cross-team work — the intern who only does their assigned tasks is memorable for the wrong reasons
• Write a 1-page intern project summary at the end — share it with your team, your manager, and your LinkedIn
• Connect with every engineer you work with on LinkedIn before the internship ends

Set up job alerts for "Software Engineer Intern" + your target city. Apply within 24 hours of posting — early applicants have higher review rates. Connect with recruiters and hiring managers before applying.

Participate in hackathons — winners often receive fast-track interviews at sponsoring companies. Competitions on Unstop are a shortcut past resume screening.

Good for 1st-year students or students without prior projects — companies here are more open to freshers with limited experience.

Google SWE intern, Microsoft Engage, Flipkart GRiD, Goldman Sachs analyst programs — all have specific intern programs with their own portals. Apply directly, not through aggregators.

Startups on Wellfound often have shorter interview processes (2–3 rounds) and allow you to ship real product features. Good for students who want hands-on experience quickly.

Find the engineering manager or recruiter for your target team on LinkedIn. Send a 3-sentence email: who you are, what you are interested in, one specific thing about their work you find compelling. Link your GitHub. Response rate: 5–15% — still better than most job boards.

Active GitHub profile with regular commits, readable commit messages, and proper branching on your projects

LeetCode profile with 100+ problems solved, or a competitive programming handle with rating

A deployed app (Vercel, Render, Railway) with working features — not just a local project

Clear README files on every GitHub project — setup instructions, architecture diagram, known limitations

At least one project with unit tests and a CI pipeline — shows production mindset

✕ Starting the internship search in February for a May internship

Fix: Top companies close intern applications in October–November for the following summer. By February, the only available opportunities are from small companies or startups. Start building your profile in January of your 2nd year and begin applying in August.

✕ Applying to 5 companies and expecting conversion

Fix: Intern application to offer conversion rates are typically 5–15% at the application stage. Apply to 30–50 companies across tiers: 5 reach companies, 15 match companies, and 20 safety companies. Breadth is part of the strategy.

✕ Not preparing for the coding assessment

Fix: Online assessments (HackerRank, Codility) are the first filter. Failing them means no interview regardless of your profile. Solve 100+ LeetCode problems (weighted toward Medium) before applications open. This takes 3–4 months of consistent practice.

✕ Lying or exaggerating on the resume

Fix: Any claim on your resume is fair game for interview questions. If your resume says "Proficient in React" and you cannot explain React hooks and state management in an interview, you will be rejected — and often flagged. Only list technologies you can discuss comfortably for 10+ minutes.

✕ Asking for a return offer or salary in the first week of the internship

Fix: Ask about return offer criteria in week 2, framed as: "What would a successful intern look like by the end of the internship?" Ask about compensation only after receiving a return offer or at the last week — not during the internship.