Why a map is the right interface for a job search

A job is a place. Not a pin on a listing feed — a real commute, a real neighborhood, a real set of tradeoffs about rent, daycare, and which coffee shop you'll actually be sitting in at 9am. List-first job boards hide that. You scroll past 400 titles before you notice that half of them are in suburbs you'd never live in.

PiNC flips the orientation. Instead of a feed of titles you filter down, you see a map of open roles you navigate. The filter sidebar is still there — salary, remote, posted age, company, keyword — but the primary affordance is geographic. Zoom into a neighborhood and you see who's hiring there. Drop a pin on where you want to live and the distances update live.

What changes when place is the primary axis

• You stop applying to roles you'd never accept. A 90-minute commute reads as 90 minutes on the map, not as a line of address text that doesn't register.
• You discover cities. The map surfaces adjacent metros you'd never search by name — not because an algorithm recommended them, but because they were already visible.
• You negotiate better. When you know what roles exist nearby and what they pay, you negotiate from data, not from a gut feeling.

Why this is hard to do well

Most geo-aware job tools treat the map as a decoration on top of a list. The list is still the source of truth; the pins are just an output. That produces a map that's always a little wrong — the bounds drift, the filters don't apply, the zoom is off. We're building PiNC map-first: filters and camera are the same state, pins are derived from visible bounds, and the list is a flattened view of what the map is already showing.