# The Target Employer List, 60 to 80 Seeds Cut to 30 by Live Hiring Counts

*Build a ranked list of about 30 employers posting your role family now, each with live counts, a fit sentence, and a contact path, refreshed in 15 minutes a week.*

- Canonical URL: https://www.refolk.ai/candidates/guides/target-employer-list-live-hiring
- Pillar: Reading the market
- Format: Playbook
- Published: 2026-11-05
- Last reviewed: 2026-11-05
- Reading time: 20 min
- Keywords: how to build a target company list for job search, how many companies should be on a target list, find companies hiring for my role, track company careers page new job postings, target employer list spreadsheet template, which companies are actually hiring for my job title

## Key takeaways

- No published target-list method ties list size to measured outcomes: recommendations run from 15 to 20 up to 50 or more, and every one is based on manageability or resilience.
- In Refolk's index, no employer appeared twice in a 25-profile sample of Data Analysts in either the US or the UK, so a company-first list for a role like this needs 60 to 80 seeds, not 15.
- In one monthly BLS JOLTS release, establishments under 250 employees held about 77% of private job openings and 81% of hires, so a seed list built from household names misses most of the market.
- Large establishments are a weaker signal per opening: 5,000+ establishments showed 2.89 openings per hire against 0.92 at 50 to 249 employees.
- An employer makes the cut only after its own careers board shows a role-family open count, a new-in-30-days count, and saved posting IDs, with roles open 90+ days discounted as evergreen.
- A weekly ID diff is the only free way to see closures, because Lever drops closed postings from its feed and Workday reports age only as relative text like 30+ Days Ago.

This playbook turns one target role into a ranked list of about 30 employers that are posting that role family right now, and keeps the list current with a 15 minute refresh each week. It is for job seekers who know the job they want but not which employers to aim at. You end with a spreadsheet in which every row has a live posting count, a new-in-30-days count, a fit sentence, one contact path, and a tier with written rules for moving up or dropping off.

## What is a target employer list, and how is it different from a wish list?

A target employer list is a short, ranked set of companies you will actively go after, and a working one shows evidence that each company is posting your role family right now. A wish list only records companies you admire. What separates them is one filter, applied before an employer makes the cut.

Most published methods give you places to brainstorm company names and stop there. None of them makes you confirm that a company is hiring for your kind of work before it goes on the list. This playbook adds that check, plus a tiering rule and a weekly refresh.

Terms used throughout:

- **Role family**: the 3 to 6 job titles that cover the same work at different employers. A Data Analyst search might include Reporting Analyst and Product Analyst.
- **ATS (applicant tracking system)**: the software that hosts an employer's careers board and its apply links.
- **Live-hiring check**: counting role-family postings on the employer's own careers board, not on a job aggregator.
- **Open count**: role-family postings live on the board today.
- **New-in-30 count**: open role-family postings first published in the last 30 days.
- **Closed since last check**: posting IDs that were on the board last week and are gone now.
- **Evergreen requisition**: a posting left open permanently, usually to collect applicants. I treat anything open 90+ days as evergreen.
- **Tiers**: Pursue (apply and reach out now), Pipeline (ready, waiting for a signal), Watch (strong fit, no live signal).

Scope. This guide decides which employers to aim at. It does not judge single postings for ghost-job risk, rank cities, or build a sponsor-only list. Other documents in the library cover those. It also assumes your target titles are already settled. If they are not, start with the Adjacent-Title Map.

> **Rule:** No count, no cut
>
> An employer cannot make the ranked list until its own careers board shows a recorded open count, a recorded new-in-30 count, and saved posting IDs. A company you cannot count stays in the seed sheet, marked manual, until you count it by hand.

## How many companies should be on a target list?

Seed 60 to 80 employers and cut to about 30. No published method ties list size to measured outcomes, so every number, mine included, is a judgement about what you can manage. The published range is wide, and every source justifies its number the same way.

| Source | Size | Stated basis |
|---|---|---|
| CareerSherpa | 50+ | More is better |
| Duke / Dalton LAMP | ~40 | Manageable start |
| Career Vision | 30 to 50 (cut from 80) | Survive bad luck |
| WayUp | 20 to 30 | Under 10 narrow, over 50 unmanageable |
| Cruit | 15 to 20 | Depth of research |

Duke's version follows Steve Dalton's LAMP method from *The 2-Hour Job Search*. Career Vision is the only source that writes down its cut: four filters that take 80 companies to 40. That is the same shape I use (a wide seed, then filters), but I add the one filter it leaves out, which is whether the employer is hiring for your work right now.

### Why the seed has to be wide

For many roles, demand is spread across a huge number of employers, and you cannot see that from inside a brainstorm. Refolk's index of professional profiles shows how far it spreads for one common role.

**25 of 25 - Distinct employers in a 25-profile sample of Data Analysts, in both the US and the UK**

In Refolk's index, no employer appeared twice in either sample, so a small hand-picked set of companies covers very little of where this work happens.

| Metric | US | UK |
|---|---|---|
| Data Analyst profiles | 65,056 | 16,414 |
| Ratio | 3.96x | 1x |
| Literal title match in sample | 60% | 84% |
| Max employer repeats in 25 | 1 | 1 |

Source: Refolk's index. The ratio and percentages are derived.

Three things follow from this table:

- **Breadth.** When 25 people with one title work at 25 different employers, a list of 15 to 20 companies is a sample, not a market. That is why the seed is 60 to 80.
- **Title leakage.** In the US sample, 10 of 25 profiles found by searching "Data Analyst" did not hold that exact title. Careers-board keyword filters leak in the same way, which is why the live check filters on department as well as title.
- **Market size differs by country.** The US pool is almost four times the UK pool, but UK titles were more precise. A UK search can rely more on exact titles. A US search needs the full role family.

Limits. A 25-profile sample is enough to show that employers rarely repeat. It is not enough to estimate any one employer's share. I also ran a seniority-filtered version of the US query, and it returned nothing usable, so nothing in this guide makes claims about level.

### Why about 30 after the cut

Thirty sits where the WayUp and Career Vision ranges overlap, and it is the size at which a weekly refresh still fits in about 15 minutes. If your live check leaves fewer than 20 employers above threshold, the answer is to widen the seed, not to lower the bar.

## Where seed employers come from, and why brainstormed lists skew large

Seed from four places: your dream companies, competitors of each one, job-search engine results for your title variants, and a deliberate batch of small and mid-size employers, because that is where most openings and hires are. Lists built from best-of rankings lean heavily toward the largest employers, which hold a small share of openings.

One monthly release of the BLS Job Openings and Labor Turnover Survey (JOLTS) shows the distribution. These are preliminary estimates, in thousands:

| Establishment size | Openings | Hires | Openings per hire |
|---|---|---|---|
| 1 to 49 | 3,562 | 2,360 | 1.51 |
| 50 to 249 | 1,590 | 1,726 | 0.92 |
| 250 to 999 | 842 | 662 | 1.27 |
| 1,000 to 4,999 | 481 | 242 | 1.99 |
| 5,000+ | 211 | 73 | 2.89 |

The openings-per-hire column is derived. In that release, establishments under 250 employees held 77.1% of private openings and 80.7% of hires. Indeed's Hiring Lab notes that the largest establishments account for less than 5% of all openings in JOLTS. To re-check, open the latest JOLTS news release and its size-class table and recompute the shares. The pattern matters more than the exact figures.

Two cautions on reading the table:

- **Establishment is not firm.** BLS measures size by establishment (one location), not by company. A 40-person branch of a national bank counts as small. Small establishments are not the same thing as small companies.
- **Openings per hire measures signal strength.** At 5,000+ establishments there are 2.89 openings for every hire, compared with 0.92 at 50 to 249. Large employers carry more open requisitions that never become hires, so treat each of their postings as weaker evidence.

Sources for the small and mid-size batch:

- Local business journals
- Industry associations and their member directories
- Job board filters for company size
- Investor portfolio pages, for venture-backed employers
- SEC EDGAR Form D filings, which record private fundraises
- USAspending.gov, for federal contractors in your region

No source has measured how many good targets each of these produces, so I cannot rank them. Use whichever ones produce names in your industry and location, and keep the size band on every row so you can see the mix.

## Which careers boards can you count without opening every page?

Employers on Greenhouse, Lever, and Ashby publish public job feeds that anyone can read without logging in, and Workday careers pages load from an endpoint that exists but is not documented. In tech-heavy samples these four cover most postings, but not every employer, and none of them reliably tells a repost apart from a new requisition.

To identify the ATS, look at the host of any apply link.

| ATS | Apply-link host | Public feed | Newness data |
|---|---|---|---|
| Greenhouse | boards.greenhouse.io | `/v1/boards/{token}/jobs`, no auth for reads | `first_published`, on most boards |
| Lever | jobs.lever.co | `/v0/postings/{site}?mode=json` | Closed roles vanish; diff IDs |
| Ashby | jobs.ashbyhq.com | `/posting-api/job-board/{name}` | Published date not confirmed in docs |
| Workday | myworkdayjobs.com | Undocumented `/wday/cxs/{tenant}/{site}/jobs` | Relative text only, e.g. 30+ Days Ago |

Details that change your counts:

- **Greenhouse.** The board token is the slug in the careers URL. The only call that needs authentication is submitting an application.
- **Lever.** Employers on Lever's EU data center use the hosts jobs.eu.lever.co and api.eu.lever.co. If the US host comes back empty, try the EU one before concluding anything.
- **Workday.** The list endpoint returns 20 jobs per page with a cap of 2,000. For a stable key, use `jobReqId`. Some tenants leave it out, and then `jobPostingId` is the fallback.
- **Others.** Workable, Recruitee, Personio, SmartRecruiters, Pinpoint, and Teamtailor also publish feeds. Personio's XML feed only exists if the employer has switched it on.

How much of your list this covers depends on your industry. In one job tracker's posting sample, Greenhouse, Ashby, and Lever together held 47.5% of postings, and adding Workday brings it to about 67.1% (derived). A separate company dataset from a resume tool puts Greenhouse at 19.0%, Workday at 17.5%, Lever at 15.6%, and iCIMS at 14.4%. Both measure postings, not employers, and both lean toward tech. Workday leads the Fortune 500 with over 40% of installs, and a quarter of the Fortune 500 uses iCIMS, which has no public feed listed here. In healthcare and retail, expect more rows marked manual.

You do not need to write code. Every feed above backs a careers page you can read in a browser. The feed only speeds up counting and makes the weekly ID diff easier.

## The build session, step by step

The build takes one session of 90 to 120 minutes and seven steps, ending with about 30 tiered employers. The stage times are proposed allocations, not measurements. The only published timing I found is Duke's exercise of 10 minutes or 10 organizations, whichever comes second, so adjust the times once you have done it once.

#### Build session, about 110 minutes

1. **Define the role family and filters** - Write 3 to 6 title variants plus location, size band, and level, before naming any company. About 10 minutes.
2. **Seed 60 to 80 employers** - Add dream companies, competitors of each, search-engine results for your titles, and a small and mid-size batch. Do not look at openings yet. About 30 minutes.
3. **Tag each employer's ATS and board slug** - Read the host of one apply link per employer and record the ATS and slug, or mark the row manual. About 15 minutes.
4. **Run the live-hiring check** - Record open role-family count, new-in-30 count, open 90+ days count, and posting IDs from each employer's own board. About 25 minutes.
5. **Cut to about 30 and tier** - Apply the size-scaled thresholds and sort survivors into Pursue, Pipeline, and Watch; archive the rest. About 10 minutes.
6. **Write a fit sentence and one contact path** - One sentence on why your history matches what they post, and one named route in, for every surviving row. About 20 minutes.
7. **Refresh weekly and apply the rules** - Re-pull boards, diff IDs for new and closed roles, update counts, and move rows by the written rules. About 15 minutes.

### Notes on the steps that go wrong most

**Step 1.** Start with criteria, not company names. Once you have named companies, you will tend to write titles that fit them.

**Step 2.** Seeding before you look at openings is deliberate. Career Vision builds the list before looking at any openings, and WayUp says to check that a company is hiring before you invest time in it. Both are right, at different stages. Seed blind so you get breadth, then check before the cut so you have evidence.

**Step 4.** For each row, filter the board by your role-family titles and by the department that does the work. Count three numbers:

- Open role-family postings
- Of those, postings new in the last 30 days
- Of those, postings open 90+ days (evergreen)

Save every posting ID. Next week's diff depends on them.

**Step 6.** A fit sentence names what the employer keeps posting for and the matching line in your history. If you cannot write one, the row does not belong in Pursue. [Refolk](/candidates) scores how well your actual history fits a specific posting, which is a fast way to test whether a fit sentence holds up against the employer's real requirements. The contact path is one specific route in: the recruiter named on a posting, the lead of the team that does the work, or a former colleague who works there now.

**Target employer sheet, column headers**

```
Employer | Size band | ATS | Board slug or "manual" | Role-family titles matched | Department filtered | Open (role family) | New in 30 days | Open 90+ days | Closed since last check | Posting IDs (comma-separated) | Last checked (date) | Tier | Fit sentence | Contact path | Notes
```

*Paste into row 1 of a spreadsheet; one row per employer, archive cut rows to a second tab rather than deleting them.*

## How to tier the list: Pursue, Pipeline, Watch

Sort by two questions: is the employer hiring for your role family now, at a level that clears its size threshold, and can you write a credible fit sentence? Both yes is Pursue. Fit without hiring is Watch. Hiring that clears the bar but needs more work on fit is Pipeline. Neither is cut.

#### Live hiring against fit

Horizontal axis runs from Below hiring threshold to Above hiring threshold. Vertical axis runs from Weak fit to Strong fit.

| Quadrant | What it means |
| --- | --- |
| Watch | Keep on the list, check weekly, promote on the first new role-family posting |
| Pursue | Apply to live postings and use the contact path this week |
| Cut | Archive to the second tab; revisit only if your role family changes |
| Pipeline | Hold while you sharpen the fit sentence; promote once it holds against a live posting |

*An employer earns Pursue only when it clears the size-scaled hiring threshold and you can write a fit sentence that holds up against its postings.*

### The hiring threshold, scaled by size

Thresholds for hiring signals come from sales prospecting, where one public guide uses 3+ related roles within 30 days and another proposes 2 or more postings in the same function within 30 days for companies under 200 people. For one job seeker, the size-scaled version carries over:

- **Under 200 people:** 2+ role-family postings new in the last 30 days.
- **200 people and up:** 3+ role-family postings new in the last 30 days.
- **Very large employers:** 3 roles at a 50,000-person firm is not a spike. No public source gives a number for this size, so set your own higher bar and rely more on new-in-30 and closures than on the open count, given the 2.89 openings per hire at 5,000+ establishments.
- **In every case:** do not count roles open 90+ days toward the threshold.

What the threshold shows: the employer has approved and published several requisitions for your kind of work within one month. How it misleads: one opening reposted several times looks like several. A cluster of new roles can also be a single team backfilling after departures, which is still real hiring but less of it than it looks. The ID diff and the failure-modes section deal with both.

**Written tier rules, paste above the sheet**

```
PURSUE: new-in-30 meets size threshold (2+ under 200 people, 3+ at 200 and up), excluding roles open 90+ days, AND fit sentence written, AND contact path named.
PIPELINE: at least 1 open non-evergreen role-family posting, OR threshold met but fit sentence not yet holding up.
WATCH: strong fit sentence, but 0 open non-evergreen role-family postings; or row marked unverifiable/manual and not yet counted by hand.
PROMOTE Watch -> Pipeline: any new role-family posting ID appears.
PROMOTE Pipeline -> Pursue: new-in-30 reaches the size threshold and the fit sentence holds against a live posting.
DEMOTE Pursue -> Pipeline: new-in-30 falls below the threshold.
DROP Watch -> archive: no role-family posting for 90 days.
REFILL: when the list falls below about 30, pull the next seeds from the archive tab and run the live check on them.
```

*Replace the threshold numbers only if your size bands differ; keep the rules in writing so the weekly refresh is mechanical.*

## The weekly 15-minute refresh

Once a week, re-pull every board, compare posting IDs with last week's, update the three counts, and apply the written rules. The diff gives you new roles and closures, and closures are the one signal you cannot get any other way.

#### Weekly refresh loop

1. **Re-pull** - Load each board or feed for the roughly 30 rows
2. **Diff IDs** - New IDs are new roles; missing IDs are closures
3. **Update counts** - Recompute open, new-in-30, and open 90+ days
4. **Apply rules** - Promote, demote, or drop by the written tier rules
5. **Refill** - Replace dropped rows from the archive tab after a live check

*A weekly ID diff turns a static list into a live one, because closed postings only show up as IDs that disappeared.*

Why weekly. Published advice ranges from every week or two up to every one to two months. I use weekly for three reasons:

- **The new-in-30 window goes stale.** A count recorded a month ago tells you about last month. One prospecting source notes that a 30-day window already includes roles that may have been filled.
- **Closures only show up as a diff.** Lever drops closed postings from its feed without a date field. If you check monthly, a role can open and close between checks and you never see it.
- **Postings may close quickly.** One source claims postings fill in 2 to 4 weeks. The figure is unbenchmarked, so do not plan around it. But if it is even roughly right, a monthly check misses whole openings.

Read closures carefully. A closure tells you the requisition was filled, cancelled, or paused. It does not tell you which. Several closures followed by new IDs with the same titles points to reposting, not hiring.

## How this goes wrong: false negatives, inflated counts, and skewed seeds

Most errors fall into three groups: deciding an employer is not hiring when you just failed to find its board, counting the same opening more than once, and starting from a seed list that leaves out most of the market. Each one below says what you will see and what to do.

> **Watch out:** A missing board does not mean no hiring
>
> Not finding a public feed is the most common false negative in this method. Many Greenhouse and Lever customers turn off the public endpoint, publish on a vanity domain, or embed jobs in a widget, so "no board found" means "not yet counted", never "not hiring".

1. **Board token not found, read as "not hiring."** You see an empty feed or a 404 while the careers page lists jobs. Check the page source for `boards.greenhouse.io/embed/job_board?for=` followed by a token, and try the EU Lever host. If both fail, mark the row manual and count on the page itself.
2. **Stale duplicate board.** One company can have an old, nearly empty board next to the live one, and the old one gives you near-zero counts. Keep the larger board and note the slug you used.
3. **Workday "30+ Days Ago" counted as 30.** Relative text puts a 31-day-old role and a 90-day-old role in the same bucket. On Mastercard's Workday site, 314 of 1,037 jobs, about 30%, showed "Posted 30+ Days Ago". Read the start date from each job's detail call before counting it as new.
4. **Repost counted as new.** The same opening reappears with a fresh date. Diff on the requisition ID, not on title plus date. Where the ID is missing, mark the row unverifiable and keep it out of Pursue. No public source confirms that any of these fields reliably separates a repost from a new requisition. Repeated reposts of one role often point to unrealistic expectations or budget limits, which is a reason to cool on the employer, not warm to it.
5. **Title-keyword noise.** In Refolk's index, 40% of the US Data Analyst sample did not hold the literal title. Board keyword filters miss real matches and catch unrelated roles in the same way. Filter by department as well as title, and read any posting whose title is ambiguous.
6. **Sales thresholds applied to big employers.** Three roles at a 50,000-person firm puts it in Pursue on noise. Scale the threshold by size and set a higher bar of your own for the largest employers.
7. **Evergreen requisitions.** A posting that never closes keeps the open count up indefinitely. Prospecting guides classify postings open 90+ days as noise. Leave them out of the threshold and record them in their own column.
8. **Brainstormed seeds skew large.** A seed list taken from best-of lists over-represents the size classes that hold under 5% of openings. Check the size band column against the JOLTS table. If most rows are household names, add small and mid-size employers before you cut.

> A company that cannot show you a role-family posting this month belongs on Watch, not on your calendar.

## Before you call the list done, and what to do next

The list is done when every surviving row has evidence, a reason, and a way in, and when the rules that move rows are written down rather than kept in your head. Run this check at the end of the build session and again after your first refresh.

#### Target employer list, done means

- [ ] The role family is written as 3 to 6 titles, with location, size band, and level filters.
- [ ] The seed tab held 60 to 80 employers before any were cut, each with a size band.
- [ ] Small and mid-size employers make up a real share of seeds, not just household names.
- [ ] Every row has an ATS and board slug, or is marked manual and counted by hand.
- [ ] Every ranked row shows an open role-family count, a new-in-30 count, and an open 90+ days count.
- [ ] Posting IDs are saved for every ranked row, so next week's diff can run.
- [ ] About 30 rows remain, each tiered Pursue, Pipeline, or Watch.
- [ ] Every Pursue row has a fit sentence and one named contact path.
- [ ] No row without a requisition ID sits in Pursue.
- [ ] The written tier rules are pasted above the sheet, with the date of the last refresh.

What to do next:

- **Pursue rows.** Apply to live role-family postings this week and use the contact path. Each application needs a resume tailored to that posting. Refolk builds the tailored version from your own history and drafts the cover letter, so a Pursue tier of a dozen employers does not mean a dozen evenings of rewriting.
- **Pipeline rows.** Work on the fit sentence. If it still does not hold up against a live posting after a couple of refreshes, move the row to Watch.
- **Watch rows.** Do nothing except the weekly diff. The first new role-family ID promotes the row.
- **Keep it current.** Spend 15 minutes on the refresh every week, refill from the archive when the list drops below about 30, and redo the build session from Step 1 only if your role family changes.

## Frequently asked questions

### How many companies should be on a target list for a job search?

Seed 60 to 80 and cut to about 30 that are posting your role family now. Published advice ranges from 15 to 20 up to 50 or more, and none of it ties the number to outcomes; every source bases its figure on manageability or resilience. The wide seed matters more than the final number, because in Refolk's index no employer repeated in a 25-profile Data Analyst sample, so a small hand-picked set covers very little of the demand.

### How do I find which companies are actually hiring for my job title?

Check each employer's own careers board, not an aggregator, and count postings in your role family rather than your exact title. Many employers run their boards on Greenhouse, Lever, or Ashby, which publish public job feeds that need no login. Record the open count, the count new in the last 30 days, and the posting IDs. Filter by department as well as title, because exact-title matching misses real matches and pulls in noise.

### How do I track new job postings on a company careers page?

Save the posting IDs each week and compare them with the previous week's list. IDs that appear are new roles, and IDs that vanish are closures. Lever simply drops closed postings, so the diff is the only way to see them. Use requisition IDs, not title plus date, because reposts can look new. On Workday, read the start date from the job detail page, since the list only says things like 30+ Days Ago.

### Should I build my target list before or after checking who is hiring?

Both, in that order. Seed the list before you look at openings, so current postings do not narrow what you consider, then run a live-hiring check on every seed before it can make the cut. Published methods disagree here: one says to build the list before looking at a single opening, another says to verify hiring before investing time. Splitting seeding from cutting gets you breadth and evidence together.

### What if I cannot find a company's careers board feed?

Treat it as unknown, not as not hiring. Many enterprises turn off the public board, use a vanity careers domain, or embed jobs in a widget. Look in the page source for a Greenhouse embed token, try the EU Lever host, and check whether an old, nearly empty board exists alongside a live one. If you still find nothing, mark the row manual and count postings on the careers page itself.

### How often should I refresh a target company list?

Weekly, in about 15 minutes. Published advice ranges from every week or two up to every one to two months. I use weekly because the new-in-30-days count goes stale in a month and closures only show up as an ID diff. One source claims postings fill in 2 to 4 weeks. That figure is unbenchmarked, but if it is anywhere near right, a monthly check would miss whole openings.

---

*From the Refolk guide library. I revise these guides rather than replacing them, so the current version is always at https://www.refolk.ai/candidates/guides/target-employer-list-live-hiring*