Project Clinics
A project shows something real. It does not show everything.
A final-year project proves that you can start something, work in a team and finish. It does not prove that you wrote every line unaided, and employers do not expect it to. This session helps students say what the project shows, and speak honestly about the help they had.

Explore this page6 sections
Everyone had help. The question is whether you can say so.
Student projects rest on libraries, tutorials, open-source code, a guide's suggestions, a senior's advice and, now, online tools and assistants that can write code. Employers know this. They work the same way.
What they cannot accept is a candidate who claims work they cannot explain. A project that is half borrowed and fully understood is a better answer than a project claimed as original and not understood.
This session is not about rules or detection. It is about how to speak about your own work in a way that holds up when the interviewer asks a second question.
Reading your own project honestly
21 topics across 5 areas. Five questions each student answers about their project.
What Does It Prove?The real strengths.4
- You can take an idea to something that runs
- You can work with other people over months
- You can learn tools you were not taught
- You can finish, or at least reach a stopping point
What Does It Not Prove?What an interviewer will not assume.4
- That you can build it again from scratch
- That it works outside the demo
- That it is secure, fast or maintainable
- That every part is your own work
Saying this yourself, before you are asked, usually makes the interviewer trust the rest.
Help You HadSay it, and say what you did with it.5
A plain sentence works: 'I started from a tutorial for this part, then changed it to handle our data.' The interviewer's next question is then about your changes, which is where you want the conversation to go.
- A guide or senior who suggested the approach
- Tutorials, documentation and open-source examples
- Code you adapted, and what you changed
- Online tools or assistants that suggested or wrote code
- A teammate who solved something you could not
What You Must Be Able to ExplainWhoever wrote it first.4
- Any code you submit and list on your resume
- Every library you name, and what it does
- The central logic of the project
- Why the project is built the way it is
Checking Your Own UnderstandingA test you can run before the interview.4
- Close the code and explain one module aloud
- Change one small behaviour without help
- Explain a bug and how you would find it
- Mark what you could not do, and learn it first
Phrases that help, and phrases that hurt
- 'I adapted this from a tutorial and changed these parts' helps
- 'I built everything myself' hurts when it is not true
- 'The tool suggested it, and I checked it by doing this' helps
- 'I do not remember why we did that' is better than a guess
What participants leave with
- A fair two-line description of what their project shows
- A list of help they had, and how they will describe it
- A short list of parts to study before interviews
How the session runs
The professional talks through what projects usually show and do not show, then asks each team the honest questions: where did this part come from, and can you explain it. Teams then rewrite how they will describe their own work. The college chooses the date and the teams.
What your students leave with
- A realistic view of what the project proves to an employer
- A truthful way to describe help from tutorials, seniors, guides and tools
- Knowing which parts you must be able to explain yourself
- An answer to 'did you write this code?' that does not cost you the interview
- Confidence that honesty is the stronger position
Scheduled sessions
Nothing scheduled yet
Sessions are arranged with a college once a date is agreed. Ask us and we will find the right person for it.
A student rather than a college? See what is coming up, or ask your placement team to host this.
Honest about the help, clear about the work.
Tell us who your students are and what stage they are at. Sessions are free for participants.