Case study, 2026
School Voting System
Student elections run online, from candidate list to final count.
The stack
- Frontend
- Next.js, React, TypeScript, Tailwind CSS
- Backend
- Node.js
- Database
- PostgreSQL, Supabase, Drizzle
- Auth
- Auth.js, role-based access
- Hosting
- Vercel
The problem
Paper ballots are slow to count and easy to dispute. Here each verified student votes once from a browser, and officers publish a count they can stand behind. Built and tested; not yet used in a real election.
My role
Designed and built it on my own, as the only developer.
How it works
- Student and admin portals, course-scoped elections
- Party lists with a coordinator invite and approval
- Scheduled elections that open and close themselves
- One ballot per verified student, server-enforced
- Results with tie-breakers, and an audit log
- Filtered voter reports with CSV export
The hard part
Keeping one vote per student: 750+ automated tests and database tests with ten simultaneous submissions.