Data from 40+ member internship cycles: which companies recruit from universities, what they actually test, and how building society projects gives you an edge in interviews.
What the Data Actually Shows
Over three years we've tracked internship outcomes for DevSoc members who went through our career prep program. The headline number: 73% of members who completed at least one society project and attended two or more career events landed a technical internship within six months of applying. The number for members who didn't engage with projects: 31%.
The gap isn't explained by intelligence or degree grade — it's almost entirely explained by having concrete work to talk about. Interviewers at every company we surveyed said the same thing: they want to hear about something you built, not what you learned in lectures.
The Preparation Timeline
Applications for summer internships at large tech companies open in August and September — seven to nine months before the internship starts. Most students don't realise this and apply in February when half the spots are gone. Set a calendar reminder right now.
Our recommended timeline: start a society project or personal project 3 months before applications open. Spend the month before applications doing LeetCode medium questions (aim for 40–60 solved). Apply to 15–20 companies, not 3. Referrals matter — ask your DevSoc network.
Why Projects Give You an Edge
Every technical interview has a behavioural component. 'Tell me about a time you had to debug a complex issue.' 'Describe a project you're proud of.' 'How did you handle a technical disagreement with a teammate?' If your only experience is coursework, your answers will be generic. If you've shipped something in a team under pressure, your answers will be specific and credible.
DevSoc project teams deliberately simulate real engineering environments: code review, pull requests, planning sprints, managing scope. When you interview and say 'in my last team we used a feature flag to roll out gradually and caught an edge case before it hit all users', that lands differently than 'in my algorithms assignment I...'.
Nailing the Behavioural Round
Use the STAR format but keep it tight: Situation (one sentence), Task (one sentence), Action (two to three sentences on what YOU specifically did), Result (one sentence with a number if possible). Practice out loud, not just in your head. Record yourself once — the gap between how you think you sound and how you actually sound is always humbling.
Prepare five strong STAR stories and you can answer 80% of behavioural questions. The stories that work best: shipped something under a deadline, debugged something that stumped the team, disagreed with a technical decision and handled it well, helped an onboarding teammate, and a project you're genuinely proud of.
3rd year software engineering student, incoming SWE intern at a top-tier tech company. Leads DevSoc's career mentorship program.
