
A university project can be excellent interview evidence.
The key is to explain it as work you did, not as a module description.
Start with the problem
Give enough context:
“Our team had six weeks to design a service for students finding part-time work.”
Then move quickly to your role.
Separate your contribution
Interviewers need to know what you did.
Use “we” for team context and “I” for your decisions and work.
Use a simple structure
The STAR method works well:
Situation: context.
Task: what you were responsible for.
Action: what you actually did.
Result: outcome and what you learned.
Do not force every answer into a dramatic metric.
A result can be:
- a tested prototype
- a decision changed by research
- a technical problem solved
- an event delivered
- feedback incorporated
- a mistake recognised and corrected
Talk about constraints
Startup work has constraints too.
Useful project constraints include:
- deadline
- team conflict
- limited data
- unfamiliar technology
- budget
- user access
- changing brief
Explain the trade-off you made.
Prepare follow-up questions
Expect:
Why did you choose that approach?
What did you personally own?
What failed?
What would you change?
How did you know the result was good?
If you can answer those, the project becomes credible professional evidence rather than “just university work”.