Problem Statement

Your Task: Create a project that aligns with the theme of Connection. You may choose to leverage DevSoc’s Flagship Projects as a point of inspiration. Our projects are available here: https://devsoc.app/our-projects. 

 

DevSoc has created an API that contains UNSW data that our current projects use including room bookings, classes and courses. The documentation is available here: https://github.com/devsoc-unsw/graphql-api?tab=readme-ov-file.

Requirements

WHAT TO BUILD

Whatever you'd like, as long as it addresses the problem statement! There is no restriction on what form your project should be like and what technologies are used to build it. See the rules for a more detailed breakdown. 

 

WHAT TO SUBMIT

 

  • Your code on a public repository, screenshots of your project and a brief description of what it does on the DevPost.

  • A short pitch video (~1 min) is recommended for People's Choice

  • A max 5 min in-person pitch describing your project is REQUIRED for your team to be eligible for prizing

Hackathon Sponsors

Prizes

$500 in prizes
First Place Prize
$200 in cash
1 winner

Sponsor Merch

Runner Up Prize
$100 in cash
1 winner

Sponsor Merch

People's Choice
$100 in cash
1 winner

First Steps Prize
$100 in cash
1 winner

Devpost Achievements

Submitting to this hackathon could earn you:

Judges

Lucas Harvey

Lucas Harvey
DevSoc Co-President

Adrian Si

Adrian Si
Software Engineer @ Atlassian

Aiden Rawles

Aiden Rawles
Software Engineer @ Atlassian

Ashley Lamont

Ashley Lamont
Software Engineer @ Atlassian

Judging Criteria

  • Innovation and Creativity (25%)
    Originality: Is the idea novel and unique? Has it been done before? Creativity: Does the solution approach the problem in an innovative way? Impact: Does the project have the potential to make a significant impact or change?
  • Technical Complexity and Completeness (20%)
    Error Handling: Are there bugs? Are edge cases considered? Implementation: How well is the technology implemented? Are there any advanced technical elements? Functionality: Does the project function as intended? Are all features implemented properly?
  • User Experience and Design (20%)
    Usability: Is the project easy to use and navigate? Is the user interface intuitive? Aesthetics: How visually appealing is the design? Is the design cohesive and professional? Accessibility: Is the project accessible to users of varying abilities?
  • Practicality and Feasibility (15%)
    Feasibility: Can the project be realistically implemented? Scalability: Can the solution be scaled up? Does it handle increasing amounts of work well? Market Fit: Is there a clear market need for this solution? Target audience?
  • Presentation and Pitch (10%)
    Clarity: Is the presentation clear, concise and effectively communicate the project? Engagement: Does the team engage the audience and judges during their pitch? Q&A: How well does the team respond to questions?
  • Team Collaboration (10%)
    Teamwork: How well did the team work together? Did they utilise each member's strengths? Contribution: Did all team members contribute significantly to the project? Communication: How effectively did the team communicate during the hackathon?

Questions? Email the hackathon manager

Invite others to compete

Hackathon sponsors

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.