A Correction: We Measured Our Connectors and Called It a Metro
Based on 257,534+ analyzed job listings · Updated 2026-08-16
This page led with a number that felt like a real discovery: Columbus shows 396 job postings and 363 of them, 91.7%, are JPMorgan Chase, across just 11 distinct employers. The intended lesson was that a metro's posting count hides how few employers are behind it. Re-checked as part of a deliberate sweep for a mistake we had already made twice today, it does not hold. 90.5% of our Columbus postings arrive through one feed, and that feed is JPMorgan's own careers portal. We see 11 employers in Columbus because we ingest one bank's careers site plus a handful of broad boards, not because Columbus has 11 employers. The concentration ranking is a readout of our ingestion portfolio.
See where you actually stand in this market
Upload your resume and Seeker compares you against current openings — which roles fit your experience, and which are screening you out.
Columbus is 91.7% one bank
What this page claimed
Retained as the figure being corrected, not as a current claim
90.5%
Our Columbus postings from one feed
421 of 465, and that feed is JPMorgan's own careers portal
418 are JPMorgan
Of those 421
The concentration and the connector are the same fact
4 of 4
Largest employers in the original table
JPMorgan, Amazon, Apple and Citi. We run a direct connector for every one
our coverage
What the metro figures do measure
Which employers we ingest directly, and where those employers have hubs
3
Corrections from this root cause today
Apple's salary, posting length, and this
The original table, re-read as what it actually shows
| Metro | Largest employer as published | Do we ingest them directly? | What the row actually says |
|---|---|---|---|
| Columbus | JPMorgan Chase, 91.7% | Yes, via their own careers portal | We read one bank's portal and Columbus is a JPMorgan hub |
| Philadelphia | JPMorgan Chase, 71.3% | Yes, same portal | Same connector, second hub |
| Seattle | Amazon, 62.5% | Yes, dedicated Amazon feed | We read Amazon directly and Amazon is in Seattle |
| San Diego | Apple, 47.6% | Yes, dedicated Apple feed | Same shape |
| Pune | Citi, 47.0% | Yes, dedicated Citi feed | Same shape |
| Boston | 10.5% across 131 employers | No hub employer we connect to | What a metro looks like through broad boards only |
Boston is the row that gives the game away. It was published as the diversified counter-example, and the reason it looks diversified is that we do not run a direct connector for any employer with a Boston hub. The spread between Columbus and Boston is not a spread between concentrated and diversified labour markets. It is the difference between a metro where we read an employer's own portal and one where we do not.
Source: Seeker job corpus, 257,534 active job postings, snapshot 2026-08-16. seekerscore.com/insights/one-employer-metro-job-markets-2026
Correction, 2026-08-16
What this page claimed: 'Columbus is 396 postings of which 363 (91.7%) are JPMorgan Chase, across 11 distinct employers,' with Philadelphia at 71.3%, Seattle 62.5% Amazon and San Diego 47.6% Apple, presented as evidence that a metro's posting count hides how few employers stand behind it. What is true: of the 465 active postings we hold with a Columbus metro tag, 421 (90.5%) come from a single source, and that source is `jpmc.fa.oraclecloud.com`, JPMorgan's own careers portal. 418 of those 421 are JPMorgan Chase. The concentration figure and the connector are the same fact stated twice. Every largest-employer in the published table, JPMorgan, Amazon, Apple and Citi, is an employer we ingest directly rather than one that emerged from a survey of the metro.
Why this took three tries to see
This page was itself a correction. An earlier version ranked metros from a 30,000-row sample and got the ordering badly wrong, and this page was written to fix it by moving to the full corpus. Moving to the full corpus fixed the sampling error and left the deeper one untouched, because the full corpus has the same shape as the sample in the way that mattered: it contains whichever employers we built connectors for. A bigger denominator does not fix a biased numerator. The number that should have stopped us was printed on the page in its own column: 11 distinct employers in a metro of 465 postings is a statement about coverage, not about concentration, and we published it as a finding rather than reading it as a warning.
What stands
Two things. First, the arithmetic: the counts, the per-metro shares and the 55,867 metro-tagged denominator were all computed correctly over the corpus. Nothing here is a calculation error. Second, and more usefully, the general warning the page was trying to make is still true and is now better supported: a metro's posting count on any job board is not a census of that metro, and the employer mix behind it is worth checking before you read anything into the volume. We are simply the demonstration rather than the observer. If a job board tells you a city has a certain number of openings, that number is a function of which employers that board reads.
What is withdrawn
Every per-metro concentration figure, the ranking of metros by concentration, the Columbus and Philadelphia headline claims, and the Boston-as-diversified counter-example. We are not replacing them with corrected concentration figures, because we cannot compute an honest one: measuring how many employers are behind a metro requires knowing that we see a representative set of that metro's employers, and we demonstrably do not. Fixing this needs different data, not better arithmetic on the same data.
How we measured it (and what we did not claim)
The correction is a source decomposition of the same corpus rows the original page used: all active postings carrying a Columbus metro tag, grouped by source and by company, on 2026-08-16. That is one query, and it is the query that should have run before publication. We are NOT claiming Columbus is not a JPMorgan town, which it may well be, nor that Seattle is not Amazon-heavy, which it plainly is. We are claiming that our data cannot establish either, because the employers we see most are the employers we chose to read. We are also NOT claiming the metro tagging is wrong; 22.6% of the corpus carries a metro and that scoping was stated correctly throughout. This is the third correction today with the same root cause, which is a claim built by comparing our own copy of the world against itself. The others are on the salary page and the posting-length page.
Frequently asked questions
Is Columbus really 91.7% one employer?
We cannot say. What we can say is that 90.5% of our Columbus postings come from a single feed, which is JPMorgan's own careers portal, and 418 of those 421 are JPMorgan. The concentration we measured is our connector, not the city.
How many employers are behind a metro's job postings?
More than any single job board can see, including ours. Every largest-employer in our original ranking was a company we ingest directly. That is a fact about our coverage rather than about the metro, and we withdrew the ranking rather than publish a corrected version we cannot support.
Does this mean metro job counts are useless?
It means they are a function of which employers the board reads. That is worth knowing before you compare two cities on any job site. The useful habit is to ask which employers are behind the count, which is exactly the question this page asked and then answered with our own ingestion list.
Why did this page change twice?
The first version ranked metros from a 30,000-row sample and got the order wrong. This version moved to the full corpus, which fixed the sampling error but not the deeper one: the corpus contains whichever employers we built connectors for. A bigger denominator does not fix a biased numerator.
See where you stand
Upload your resume to see your skill gaps, match scores, and which roles fit your background.
Analyze my resumeRelated Data
We Analyzed 1,835 “Entry-Level” Job Postings. Most Still Demand Experience.
“Entry-level” / junior postings analyzed: 1,835
The Highest-Paid Skills in 2026, From 73,374 Job Postings That Disclosed Pay
Job postings we analyzed: 73,374
Backend Engineer Market: What 200,000 Job Listings Tell Us
Active backend roles: 24,600+
The 25 Fastest-Growing Skills in 2026 Job Postings
Jobs analyzed: 133,000+
Guides
Dataset & citation
- Dataset
- 257,534+ active job postings
- Collected
- Full active corpus, source decomposition run 2026-08-16; corrects figures published 2026-08-13
- Last verified
- 2026-08-16
- Methodology
- How we measure
Suggested citation
SeekerScore. "Correction: Our 'One-Employer Metros' Were a Map of Our Own Connectors (2026 Data)." Analysis of 257,534+ job postings, 2026-08-16. https://www.seekerscore.com/insights/one-employer-metro-job-markets-2026
Data derived from Seeker's job corpus of 257,534+ listings across multiple sources. Updated 2026-08-16. Individual results vary based on resume content, target market, and role specifics.