A student prepared guide on how to master interviews based on experience(from mock and past interviews)
- Have at least one good project to showcase.
- Be prepared to defend the significance of your project. Never say it was of no use.
- Differentiate between internships and short trainings/visits:
- Internship: At least 1 month long.
- Industry visits/trainings: Do not call them internships.
- If your project spans *multiple domains, emphasize the parts most *relevant to the interviewing company.
- If it's a team project, be clear about your specific contributions.
- Don't speak for too long on one point or beat around the bush.
- Involve the interviewer in the discussion — make it interactive.
- Speak convincingly to highlight the value of your knowledge.
- Your introduction sets the stage — interviewers often base their next questions on it.
- Maintain a confident tone; it can lead to simpler follow-ups.
- Wear a smile to create a positive impression.
- Posture and eye contact are important throughout the interview.
- Ensure you are well groomed and look presentable.
- Get a good night's sleep and eat properly before the interview.
- Do attend mock interviews.
- Don't cheat — they're meant to help you improve.
- If you don't know an answer:
- Say "I don't know".
- But add context (e.g., "I know XYZ works like this, but I'm not sure about X specifically").
- Explain in an understandable way — focus on clarity.
- Share your thought process when solving questions.
- It's okay to *take time, but form *proper statements.
- Do thorough research about the company:
- Align your resume with the company's domain.
- Example: If Oracle is coming, they stress more on Java and databases, so highlight these skills more in your resume.
- Use company research to ask meaningful questions.
- Don't ask about roles, work ethics, or generic company info.
- Maintain two resume formats:
- One for online submission.
- One for interview (highlighting key achievements clearly).
- It is not necessary to submit the same resume for online tests and interviews — update it if required.
- Note on resume tailoring:
- For 3rd year internships: Companies are usually flexible about domains
- For 4th year full-time roles: Companies often specify roles (e.g., Presidio emphasizes full-stack, Tiger Analytics focuses on ML) — tailor your projects and skills accordingly
- Aim to create a two-way conversation — don't let it be one-sided.
- First 20–30 minutes are crucial to leave a strong impression.
- Try to create an X-factor that makes you stand out.
- If you answer initial technical questions confidently, the interview may move faster to HR or end sooner.
- Prepare answers for:
- Why engineering?
- Why this branch?
- Why this college?
- Why not higher studies?
- Why do you want to join this company?
- Why should we hire you?
- Do you have plans for masters?
- Where do you see yourself in the next 5/10 years?
- How will you create an impact in this company for your given role?
- Be prepared for scenario-based questions (e.g., "You're a manager and one team member isn't focusing on work. What would you do?")
- Important: There are no right or wrong answers — focus on convincing them with your reasoning
- Avoid saying anything that demeans the company or your college.
-
Be very clear with DSA topics.
-
Revise tech stack used in your project.
-
When solving problems:
- Explain your DSA approach.
- Walk through your solution clearly.
If you came this far and felt like you got some new insights please star ⭐ this repository and if you have more insights feel free to submit a Pull Request.
- Ahmed Baari for organizing this event, taking efforts and initiative to start something like this for students
- Harish and Sai Ethihas for letting me listen to all the interviews and gain this knowledge
- Shriram for iterating on this guide for further clarity
- The other group of panels
- Hemapriya
- Jyotsna
- Madhesh
- Thanushree
- Tharani