TechRush is PISB's hackathon, and one of its best-known events. Teams pick problem statements across domains and build a working solution in about a week. This repo keeps every edition (rulebook, problem statements, website) so the next organising team can start from them.
| What you have | Put it in |
|---|---|
| Rulebook, problem statements, judging criteria | <year>/, e.g. 2026/ |
| TechRush website / registration portal code | <year>/website/ |
| Notes for next year's organisers | <year>/README.md |
| Winning teams' projects | Link to their repos from <year>/README.md (the code stays in the teams' own accounts) |
Never commit registration sheets, team lists, .env files or anyone's contact details.
| Edition | Material |
|---|---|
| TechRush 2024 | ✅ Rulebook · Problem statements |
| TechRush 2025 | 🔜 goes in 2025/ |
| TechRush 2026 | 🔜 goes in 2026/ |
- Teams: 2–4 members. The registration fee is waived if a team has at least one PISB member.
- Domains: Frontend Development (Web/App), AI/ML, Full Stack Development.
- Tech stacks (Web): Django/DRF, HTML/CSS (Bootstrap/Tailwind), JS, React, Node/Express, Next.js, MongoDB/SQL/Postgres. App: Flutter.
- Each team chooses two problem-statement preferences and is assigned one.
- A GitHub repo with a proper README is mandatory, as proof that the work was built from scratch.
- Problem statements released 12 July 2024, with evaluation on 21 July 2024.
techrush/
├── 2024/ rulebook.pdf, problem-statements.pdf
└── 2026/
├── README.md ← notes for organisers + links to winning projects
└── website/ ← TechRush website / portal code
Part of the PICT IEEE Student Branch · Looking for Credenz events? See the org page.