Education search and comparison platform
Edumatch
A product concept for helping families compare schools through structured information, search behavior, and fit signals.
- Next.js
- TypeScript
- Python
- PostgreSQL
- Search UX
Problem
School discovery often becomes a flat directory problem, even though families are comparing context, constraints, and tradeoffs.
Goal
Design a clearer decision flow that turns school data into useful comparison and matching behavior.
My role
Product engineer across UX structure, data modeling, interface direction, and implementation planning.
What this proves
Product thinking, search UX, structured data modeling, and family-facing decision design.
Architecture
- Public discovery interface
- Structured content/data model
- Search and filtering layer
- Admin-friendly content workflow
Features
- Structured school profiles
- Comparison-oriented browsing
- Filter and matching logic
- Decision-friendly detail pages
Technical decisions
Challenge
Avoiding a generic school directory experience
Decision
Framed project pages around decision tasks instead of raw listings
Challenge
Presenting complex comparison data without overwhelming users
Decision
Grouped attributes by family needs and fit signals
Challenge
Keeping data structure flexible for future matching signals
Decision
Separated discovery, comparison, and detail reading into clear paths
Results and learning
Shows product discovery thinking, information architecture, and the ability to turn a broad search problem into a decision workflow.
Good search products need opinionated information architecture as much as they need filters.