There is a field on Wellfound that this Actor does not return, and the reason is a number worth stating plainly.
The measurement
Across 2,229 unique jobs measured over 25 roles and all 13 categories, the maximum years-of-experience value was present on 2 rows. That is a fill rate of 0.1%.
Why 0.1% is worse than absent
A column that is null on 999 rows in 1,000 is not a sparse field, it is a field that does not exist wearing the costume of one. It appears in a schema. It appears in a field list. Somebody writes a query against it, gets nulls, and spends an afternoon deciding whether their pipeline is broken.
The incentive this resists
Field count is a marketing metric in this category — “58 fields” is a selling line, and 59 would be a slightly better one. That is precisely the incentive that produces schemas padded with columns nobody can use, and the only defence against it is a rule applied before the count is advertised rather than after.
What ships instead
years_experience_min, at 31.6% overall and between 12.8% and 75% by role category, with the range published rather than the mean — the same treatment as ats_source.
The same decision elsewhere
The Telegram Actor in this catalogue removed six attachment fields after 893 posts across 29 channels produced zero positive cases for any of them — that measurement. Different target, same rule: a column that would always carry the same value is not a measurement.



