Athlete Discovery & Scouting Platform

Problem context

Athlete discovery often depends on fragmented profiles, informal communication, and limited visibility between athletes and the scouts who might be relevant to them. The project aimed to translate this real-world process into a structured digital platform where athletes could build profiles, present their abilities, and become discoverable to scouts.

Team and responsibility

The platform was built by a two-person development team over September–November 2025. I worked collaboratively with one other team member across the build. This was a shared build, not independent or sole ownership — my own contribution centered on the database architecture, parts of the full-stack application, and specific interaction design, described below.

Role-specific workflows

The platform is structured around three distinct user roles — athletes, scouts, and platform administrators — each with its own workflow and view into the system. I helped structure how these role-specific workflows related to one another.

Database architecture contribution

I designed the database architecture underlying the platform — the structure that lets athlete profiles, scout activity, and administrative oversight function as distinct but related workflows rather than one undifferentiated data model.

Product interaction contribution

Beyond the database layer, I developed parts of the full-stack application and implemented the drag-and-drop interactions used within the product.

Technology

Built with React.js and Node.js. No other technologies, hosting providers, or infrastructure are claimed here.

Production status

The platform reached production and is used by real athletes and scouts. No user counts, revenue, or performance figures are published here.

Confidentiality boundary

Client identity, product name, domain, and proprietary implementation details are withheld. This case study describes contribution and architecture at a level that doesn’t expose confidential specifics.

Lessons

• Real-world discovery processes need clear digital boundaries between participant roles.
• Database structure affects how reliably profiles and relationships can evolve.
• Interaction design such as drag-and-drop must remain understandable and reliable.
• Working in a two-person team requires clear technical ownership and coordination.

These are read as lessons from this project specifically, not universal architectural rules.