Data coverage
Coverage is shown as a measured signal, not a promise of completeness. LensCareer publishes salary ranges only when the underlying sample can support a useful comparison.
Dataset
Community submitted
Salary entries come from candidate and employee contributions.
Reliability floor
5+ records
Small samples stay hidden or marked as insufficient.
Freshness
Approval based
Public signals update after review and moderation.
Coverage depends on what the community has contributed and what passed moderation.
Reliable cohorts are counted at the role and city level because those filters materially change compensation.
Company salary pages may show less detail when a company does not yet have enough approved reports.
Coverage is strongest where contributors are active. Missing roles or cities mean no public claim is made.
The interface favors suppression over false precision.
Percentiles require at least five accepted records for the comparable set.
When the threshold is not met, LensCareer explains the gap instead of showing a thin range.
Coverage and sample counts are shown near salary ranges so the context travels with the number.
Freshness reflects the newest accepted salary report in the relevant set.
New submissions affect public surfaces after moderation, not at raw intake time.
Older or sparse segments are treated cautiously and may be omitted from public ranges.
Salary bands can move as more recent reports enter the sample.
Public data is designed to be useful without exposing individuals.
Individual salary reports are not published with personal identity.
Public salary intelligence is presented as grouped statistics and range summaries.
Submissions can be rejected or held back when they look unsafe, inconsistent, or identifying.