What We Measure

Ghosting Leaderboard is a measurement platform for hiring responsiveness. We track reports of no response during the hiring process, structured as data about user-reported timelines, not platform editorial claims.

All report data is submitted by users. Verification checks use Gmail metadata only.

What Counts as a Report

• A report must be submitted by an authenticated user
• Reporter must attest the report is based on personal hiring experience
• Last contact date is derived from metadata verification, not free-text narrative input
• One report per user per company per role (defined by normalized role title plus optional job URL or req ID)

Weighting System

Reports are weighted to reflect credibility:

• Base weight: 1.0
• +1.0: If job URL or req ID is provided
• +2.0: If email used to apply is provided (stored only as a hash)
• +3.0: If metadata verification confirms domain-matched exchange
• Total range: 1.0 to 7.0

Silence Meter

A higher number means more risk of no response. Calculated as:

1. For each waiting report (status='waiting' AND days_since_last_contact >= 14):
2. days_capped = min(days_since_last_contact, 90)
3. stage_multiplier = applied: 1.0, screening: 1.2, technical: 1.4, final: 1.8
4. weighted_days = days_capped × stage_multiplier × weight
5. Silence Meter = weighted_average(weighted_days) across all waiting reports

Responsiveness Score

A higher number means more responsive. Calculated as:

1. resolved_weighted = sum(weight) where status IN ('rejected', 'offer', 'withdrawn')
2. waiting_weighted = sum(weight) where status IN ('waiting', 'ghosted') AND days >= 14
3. resolved dispute outcomes use reduced impact weight (35% of normal unresolved impact)
4. resolved_ratio = resolved_weighted / (resolved_weighted + waiting_weighted + 1)
5. silence_penalty = min(50, SilenceMeter / 2)
6. score = (resolved_ratio × 100) - silence_penalty
7. Responsiveness Score = clamp(score, 0, 100)

Disputes

If you believe a report is inaccurate or malicious, please contact us. We review disputes through our admin moderation system.

Companies can claim their profile to respond to reports and provide context. We verify affiliation via work email (e.g. @company.com) before approving claims.

See Badge Criteria and How Verification Works for public formulas and verification details.

Privacy

Reporter identities are never shown publicly. We only store what is necessary for scoring and duplicate prevention. See our Privacy Policy for details.