Apply on the Company's Own Site, Not the Job Board
The usual argument for this is about applicant tracking systems and recruiter preference, and we have no data on either. Here is an argument we can prove: the listing you read on a job board is a copy, copies lose things, and the thing they lose most often is the number you most want.
Key Takeaways
- • Apple publishes a base pay range on its California postings. Our aggregated copy showed pay on 1 of 6,313.
- • We know because we published that 1-in-6,313 figure as a fact about Apple, and had to retract it.
- • Pay is commonly lost two ways: it sits in a separate section, or past a length limit.
- • 9.5% of live postings carry under 500 characters of description.
- • A missing salary or requirement on an aggregated listing is missing data, not employer behaviour.
The evidence, including our own mistake
We run a corpus of about 250,000 live job postings. We published a page saying Apple disclosed pay on 1 of 4,948 postings, and presented it as evidence that salary transparency is a property of the job board rather than the employer.
A reader told us they had seen salaries on Apple's own careers site with their own eyes. We checked. We took 14 Apple postings with a California location from our own corpus, opened each URL on jobs.apple.com, and 10 of them published an explicit base pay range, including a Cupertino role advertising $144,600 to $263,800. Two of eight sampled non-California US roles also had one, both in Seattle. Apple was disclosing the whole time. The pay sits in a Pay and Benefits block that our connector never read, so we stored the opening marketing paragraph and recorded an absence we had manufactured.
Apple California roles publishing pay
10 of 14
Sampled live from jobs.apple.com
What our aggregated copy recorded
1 of 6,313
The figure we retracted
Apple description we actually stored
871 chars
Median. The pay block sits below it
The full retraction, including why our original control failed to catch it, is on the corrected insight page.
Two ways pay gets lost in transit
Both of these produce an identical-looking blank where a salary should be, and neither is the employer choosing to hide anything.
It lives in a different section of the page
Employer career sites often render pay in a separate block from the job description. Anything that reads only the description field gets a complete-looking posting with no pay in it. This is what happened to us with Apple.
It is at the end of a long description, past a length limit
Amazon puts its pay range at the very bottom of a long posting. One record in our corpus ends mid-sentence on the words 'base salary range for this position is listed below' before a truncation limit cuts it off. The one posting in that sample that fit under the limit ends with the actual range.
What survives: pay delivered as structured data
Some feeds hand over pay as its own field rather than as prose. Those keep it regardless of length: one large source in our corpus carries a median description of just 453 characters and still reports pay on 80% of its postings. If you see pay on an aggregator, that is usually why.
Find the roles worth opening in the first place
Seeker ranks live postings by how well they actually fit your skills, so the ones you go and read in full are the ones worth your time.
New here? Learn how the resume match score works →
What to actually do
Use aggregators to discover, the employer's site to decide
Job boards are good at surfacing roles you would never have found. They are unreliable as the basis for a decision, because you cannot tell from the listing whether a field is absent or merely lost. Find it on the board, then open the original.
Never conclude 'they will not say the salary' from an aggregated listing
Especially for large employers in states with pay transparency laws, where the range is very likely published somewhere. Search the company's careers page for the exact title before you assume.
Treat a very short posting as a pointer, not a description
If a listing is a couple of hundred characters, it cannot contain a requirement, a level, or a salary. That is a listing telling you to go and read the real one, not an employer telling you the job has no requirements.
If the role is gone from the company's site, that is your strongest signal
It is better evidence than any posting-age heuristic. Aggregated copies routinely outlive the original.
What we are not claiming
We have no data on whether applying through a company site rather than an aggregator changes your odds of a response, and we are not going to invent any. Claims about applicant tracking systems preferring direct applications are not something our corpus can speak to. The argument here is narrower and, we think, more useful: the copy you are reading is lossy in ways you cannot detect from the copy itself, so the decision should be made against the original.
We are also not claiming aggregators are careless. We are one, we lost Apple's salaries in two different ways, and we only found out because a reader knew the source better than our data did.
Common questions
Should I apply on the company website or the job board?
The company's own site, when the role exists there, because the listing is more complete. We sampled 14 Apple California postings and 10 published a pay range; our aggregated copy of those same postings showed pay on 1 of 6,313.
Why do so many job postings not show a salary?
A large share of the time the pay was published and lost in transit, either because it sits in a separate section of the employer's page or because it falls past a length limit at the end of a long description. Absence on an aggregator is weak evidence about the employer.
Is the description on a job board the whole job description?
Often not. 9.5% of live postings carry under 500 characters, and the same employer can show a median of 120 characters through one feed and over 5,000 through another.
Does applying through a job board reduce my chances?
We do not know and will not guess. What we can demonstrate is that the information you are deciding on is frequently incomplete, which is a reason to read the original rather than a claim about how applications are processed.
See how this applies to your resume
Upload your resume and see which roles match your skills, where the gaps are, and what to target next. Free, about 60 seconds.
Analyze my resumeData & insights
Career transitions