Skip to content
IdeaScout.
← Back to archive

Map-based job search with radius and per-area alerts

AI-discovered

Problem

Job seekers open to relocating must run separate searches on multiple job boards for every city they'd consider, with no way to draw a radius on a map around several areas, set location-adjusted salary expectations, and get filtered alerts per location. The geography of a job search is fundamentally broken.

Opportunity

A job-search app with a map-first UX: define multiple radius areas, see aggregated openings from several boards inside each circle, set per-area salary and filters, and receive location-scoped alerts — 'house hunting sites, but for jobs'.

Market analysis

The UX insight is genuinely good and the comparison to house-hunting maps is apt, but map-first job search already exists (Goodwyrk) and map radius views ship as features of job-board software. The hard part is not the map, it is the multi-board aggregation underneath, which is a costly data problem with no clean shortcut.

Market · Relocation-minded job seekers and couples doing dual-city job searches; a niche of high-intent users, but no strong demand signal surfaced beyond the original thread.

Pricing · Job-seeker tools are expected free; realistic monetization is employer-side or affiliate, as with aggregators, not subscriptions from candidates.

score 4/10 by glm-5.1

Pros

  • + Clearly better interaction model for a real, underserved scenario (multi-city relocation).
  • + Per-area alerts create a natural retention and email touchpoint during an active search.
  • + Compelling, instantly understandable pitch: house hunting sites, but for jobs.

Cons

  • − Aggregating several boards means fragile scraping or restrictive APIs; data acquisition is the real cost center.
  • − Consumers expect job search to be free, and employer-side sales are out of reach for a solo builder.
  • − Partial substitutes are everywhere: board radius filters, remote-only boards like Himalayas, and AI search that answers multi-city queries conversationally.

Source

r/SomebodyMakeThis (Reddit)

Open original thread ↗

The uncomfortable truth for this idea is that conversational AI is absorbing exactly this query shape: “software engineer jobs within 90 minutes of either Raleigh or Austin, adjusted for local salary” is now a plausible single prompt in an AI search product, which erodes the standalone map tool’s reason to exist. If built, the defensible move is to pick one or two aggregators with legitimate open APIs (or official partner programs) rather than trying to unify all boards, and to own the relocation workflow end to end: cost-of-living deltas, salary normalization per radius, side-by-side area comparison. As a thin map skin over scraped listings it dies; as a relocation decision tool it has a story.