Explaining your own projects, a one-page resume with no work experience, and group or hackathon work you can defend.
5 questions in Early Careers, Internships & Graduate Hiring.
Take one tutorial project somewhere the tutorial did not go, so you face a real decision on your own. Credit the tutorial in a README that says what you changed and why, add tests around your own code, and let the commits show the work. That gives your GitHub portfolio something to question.
Name the team size and your role, then the specific part of the hackathon project you built and one decision you made under the time limit. Say what in the demo was real and what was mocked or hard-coded. Your individual contribution, honestly scoped, is what the interviewer is scoring, not the prize.
A graduate resume with no work experience leads with education and projects written as decisions and outcomes, adds part-time work, and keeps a short skills list you can defend. Conventions differ by country: US resumes and UK CVs usually omit photos and personal details; some other markets more often include them.
Walk through your final-year project as problem, your part, two or three decisions with their trade-offs, what failed and what you would redo. The interviewer digs into whichever decision or result you cannot explain, so prepare the why behind every choice and the method behind every number.
Say plainly what your part was, why it was smaller, and what you would do differently, without inflating it or blaming teammates. A small, owned contribution described precisely beats a large one that collapses under two follow-up questions, and the lesson you drew is what gets scored.