I implemented the Vue/Nuxt frontend, Node.js backend, APIs, and PostgreSQL database architecture. The application spans provider and organization discovery, detailed profiles, reviews, and responsive interfaces.

That scope required thinking beyond individual screens. A provider can appear in a search result, on a map, and on a profile page; those surfaces need a consistent representation of the provider and their locations. Working across the stack let me connect the interface requirements directly to the API and database work.

I built geospatial search with PostgreSQL and PostGIS so discovery could account for location alongside the other search criteria. Location is part of finding a relevant provider, rather than a separate map added after the results.

The interface combines location input, provider results, and a map. The engineering problem is to preserve the relationship between a provider, their practice locations, and the geographic area the user is searching.

I implemented fuzzy name matching, advanced filtering, and provider ranking. These address different parts of discovery: approximate names help users find a record, filters narrow the eligible results, and ranking determines their order.

A useful search experience has to balance those concerns. An approximate name match is not the same thing as a relevant provider, so the product also exposes structured criteria and profile information that help users evaluate the result.

The frontend covers provider search, provider profiles, a universal search modal, organization pages, a provider feed, and mobile layouts. I worked on the application as a connected set of workflows, including the transition from discovering a provider to inspecting their details.

The project demonstrates full-stack ownership through concrete features: database-backed discovery, API integration, location-aware results, and an interface that makes those capabilities usable.