A multi-role combat sports platform for fighters, managers, promoters, service providers, fans and admins, taken from the first commit to production.
Fightbook centralizes fighter profiles, fight opportunities, events, managers, promoters, service providers and fans. The backend had to support multiple combat sports, flexible rules, multi-role users and a large imported fighter dataset without turning routine queries into bottlenecks.
Start with a schema that could grow with the product, support different sports, weight classes and fight formats, let one user operate across multiple roles, and still keep list/search workflows predictable as real data arrived.
Designed the backend schema from the first commit, including flexible sports, weight classes, fight formats and many-to-many fighter/manager relationships.
Imported roughly 26,000 purchased real fighter profiles and built a one-click profile-claim flow backed by Veriff identity verification.
Implemented role-based authorization and in-session role switching for fans, fighters, managers, promoters, service providers and admins.
Built fight posting, challenge workflows and recommendation logic using sport, weight class, gender, record, location and availability.
Built one-to-one and group chat with Pusher presence, used Knock for product/chat notifications, Firebase for authentication and Loops for email.
Used BullMQ with Redis for asynchronous email and notification work so request paths stayed focused on user-facing work.
Reviewed PRs, helped shape technical tasks and API contracts, and coordinated backend decisions with the frontend team.
The product reached its first production launch in roughly six to seven months, supported launch activity and continued to handle recurring fight postings and live product usage after launch.