University Competitions Worth Your Time: Awards, Challenges and Hackathons

The Short Answer

For university students in creative and technical fields, competitions sort into three useful families: established art and design awards, technical challenges, and hackathons. Each builds something different — a public record, a tested skill, a finished thing made under pressure — and the honest way to choose is by what your CV is missing, not by which name sounds grandest. One entered properly beats five entered thinly.

Family One: Art and Design Awards

These are the juried student awards run by design bodies and long-running competitions — the kind with archives you can browse and past winners you can study. Long-established examples include student programs from major design associations and international illustration and photography awards; most publish briefs months ahead.

• What they build: a public, dated record read by employers and postgraduate reviewers alike
• The rhythm: annual briefs, fixed deadlines — which quietly teaches deadline-shaped making
• The honest odds: selective by design; the portfolio piece you make for the brief keeps its value either way

Family Two: Technical Challenges

Data competitions, algorithmic contests and engineering challenges test a specific skill against a defined problem. They suit students whose evidence needs a score or a working artefact behind it — and the write-up matters as much as the rank.

• What they build: proof a skill works outside the classroom
• The trap: chasing leaderboards instead of understanding — a mid-table finish you can explain beats a high one you can't
• The multiplier: publish the write-up; the reasoning is the portfolio piece

Family Three: Hackathons

Hackathons compress the whole making cycle — team, idea, build, pitch — into a weekend. For art-and-tech students they are the fastest way to practise working in a mixed team, which is exactly what studios and product teams do daily.

• What they build: teamwork evidence, a demo, and pitch practice under real fatigue
• Who thrives: students who bring one clear skill — design, code or story — and trade it generously
• The follow-through: the 48-hour prototype only becomes CV material if someone finishes it afterwards

How to Choose, Honestly

• Pick by gap: no public record → an award; untested skills → a challenge; no team experience → a hackathon
• Budget one or two per year, entered seriously — with preparation time protected like a course
• Document everything: brief, process, result and reflection, dated in the archive
• Losing is normal and useful; an honest post-mortem is worth more than a small win badly understood

Competitions are evidence machines, not lottery tickets. Enter the ones whose making process you would value even if no result ever arrived — that way every entry pays, whatever the judges decide.