GET THE
INTERNSHIP
YOU DESERVE.

Your CV and cover letter are your first impression - the gateway to securing an interview. For engineering internships, focus on showcasing relevant technical projects, societies, and any work experience. Keep your CV to one page and ensure it's ATS-friendly (Applicant Tracking System) by using standard fonts and avoiding graphics, tables, or text boxes that confuse automated scanners.

When writing bullet points, use the STAR-ish format - describe what you did, how you did it, and the outcome. Quantify wherever possible: "increased efficiency by 30%" lands harder than "improved the process". Prioritise projects where you can show genuine technical depth - a well-explained university project beats a vague internship description any day.

Your cover letter should open with why you specifically want this company - not a generic line, but something that shows you've done your research. Reference a recent project, product, or piece of news that genuinely interests you. Then tie your skills to the role requirements and close with confident enthusiasm. Always customise; a generic cover letter is obvious and instantly forgettable.

Online assessments typically include numerical reasoning, verbal reasoning, logical reasoning, and sometimes coding challenges. Most engineering companies use standardised tests from SHL, Kenexa, Cappfinity, or Pymetrics. Knowing which one your target company uses lets you practice the right format.

For numerical reasoning, practice questions involving percentages, ratios, graphs, and data interpretation - JobTestPrep and AssessmentDay are excellent. For verbal reasoning, work on reading comprehension and critical reasoning, focusing on speed. For logical/diagrammatic reasoning, identify the pattern before you look at the answer choices - this saves significant time.

Game-based assessments (Pymetrics, Arctic Shores) are increasingly common and fundamentally different - they measure behavioural traits, not raw ability. There's no single "right" answer; they analyse consistency, decision-making style, and how you respond under pressure. The biggest mistake is trying to "game" them - play naturally, stay calm, and be consistent.

For coding assessments (HackerRank, CodeSignal), focus on easy-to-medium LeetCode problems first. Write clean, commented code - interviewers value clarity. If stuck, describe your approach before coding; partial credit is real.

Finally: stable internet, quiet room, read all instructions before the timer starts, and check the scoring rules (some penalise wrong answers). It's normal not to finish every section - calm, accurate work beats rushed guessing.

HireVue is a pre-recorded video interview platform where you answer questions under timed conditions - typically 30–60 seconds to prepare and 2–3 minutes to respond. There's no interviewer on the other end in real time, which feels strange at first but becomes manageable with practice.

Treat it like a real interview: dress professionally, ensure good lighting (face a window if possible), clear audio, and a tidy background. Look directly at your camera lens, not your own face on screen - this creates the impression of eye contact. Practice recording yourself beforehand; most people are surprised by how they come across.

Questions focus on competency and motivation: "Tell me about a time you worked in a team", "Why this company?", "Describe a challenge you've overcome." Prepare 5–6 versatile examples from projects, societies, or jobs that demonstrate leadership, problem-solving, teamwork, and resilience. Structure each answer using STAR (Situation, Task, Action, Result) - be specific, be concrete, and quantify your results where you can.

A tactical tip: weave in technical detail even in seemingly soft questions. Mentioning an engineering principle or tool naturally in a teamwork answer signals genuine expertise and sets you apart from candidates who only offer generic examples.

Finally - authenticity beats polish. Recruiters watch hundreds of these. A genuine, warm, focused answer with a clear result lands far better than a rehearsed monologue. Smile, be direct, and don't be afraid to take a breath before diving in.

Live video interviews are typically on Teams, Zoom or Google Meet with one or more interviewers and last 30–60 minutes. Unlike HireVue, there's real dialogue - follow-up questions, clarifications, and genuine conversation. This is your biggest chance to build rapport and show personality alongside ability.

Research is non-negotiable. Know the company's main products, recent projects, competitors, and stated values. Look up the interviewers on LinkedIn if you can - knowing their background helps you tailor responses. Prepare 3–4 thoughtful questions to ask at the end: "What does a typical project look like for interns?", "What's been the biggest technical challenge your team has faced recently?", "What separates the interns who thrive here from those who struggle?" - questions that show genuine curiosity, not just box-ticking.

For technical questions, thinking aloud is crucial. Interviewers care more about how you reason than whether you get the right answer immediately. If you're stuck, say so and explain your approach: "I'm not sure of the exact value but I'd start by considering X because Y..." This shows analytical thinking and intellectual honesty - both highly valued in engineering.

For behavioural questions, keep using STAR and always quantify: "I led a team of four" beats "I was in a team"; "reduced build time by 40%" beats "improved the process". Keep answers focused - 2–3 minutes per STAR answer is plenty. Rambling loses marks.

Body language matters even on camera: sit upright, gesture naturally, and look at the lens. Have your CV and the job description open in a second window for reference. Dress from head to toe - you never know when you might need to stand up. And send a brief thank-you email within 24 hours; it's a small touch that many candidates skip.

Assessment Centres are usually the final stage and can last half a day to a full day. They typically include a group exercise, individual presentation, technical or case study task, and one or more interviews. You're being evaluated continuously - not just during formal activities.

In group exercises, the golden rule is: don't dominate, don't disappear. Contribute meaningful ideas that move the discussion forward. Show leadership by keeping the group on track, managing time, or synthesising different viewpoints: "We've heard X, Y, and Z - could we align on the most feasible option?" Actively invite quieter members in; assessors notice this immediately.

For presentations, structure is everything: clear introduction, 2–3 well-supported arguments, and a confident conclusion. Don't memorise word-for-word - know your material well enough to speak naturally. Vary your pace, make eye contact across the room, and keep slides minimal. How you deliver is as important as what you say.

In technical tasks and case studies, narrate your thinking. State your assumptions upfront, be methodical, and don't panic if you don't know an answer - explain how you'd find it. A thoughtful, structured approach with an imperfect answer often scores higher than a correct answer delivered without explanation.

The AC is also your chance to evaluate them. Talk to current employees and interns during breaks. Ask about real projects, team culture, and what distinguishes people who thrive there. These conversations often reveal more than any job description.

One final thing: everyone else is nervous too. The candidates who stand out aren't necessarily the most technically impressive - they're the ones who stay composed, stay curious, and treat every person they meet (staff, assessors, other candidates) with genuine warmth and respect.