What I Worked On
Worked across the public ticketing flow, admin tooling, event creation workflows, and the internal dashboard used to manage the platform day to day.
Contributed to the Supabase PostgreSQL data layer and used cron jobs to support real-time checks around ticket activity, helping the product stay aware of changes without relying only on manual refreshes.
Helped shape the dashboard experience from both a design and engineering perspective, keeping the interface focused on the information organizers need when creating events, tracking tickets, and managing operations.
Engineering Focus
Built the ticket purchase flow with Stripe Payment Intents and Stripe Payment Elements, keeping checkout flexible while still fitting naturally into the Sound Planet experience.
The engineering work blended full-stack product development with careful UI decisions: clean forms, useful admin views, responsive layouts, and workflows that made event creation feel less like back-office software.
Platform Workflows
A valuable part of the work was connecting the pieces around an event lifecycle: creating an event, publishing it, selling tickets, monitoring activity, and giving admins enough visibility to manage the process.
That made the project more than a checkout screen. It required thinking through the dashboard, organizer tasks, ticket state, and how product workflows should feel when live-event operations are moving quickly.
Technologies
Outcome
Contributed to a more complete event and ticketing product: checkout, admin controls, event setup, dashboard visibility, and database-backed workflows working together as one platform.
It was a strong full-stack project because the frontend, payments, database, and operational tools all had to support the same real-world goal: helping teams run events with fewer rough edges.