Metrics - sameernagar-hub/regen-engine GitHub Wiki

Metrics

Every published number, where it comes from and how to reproduce it. Numbers that can't be reproduced aren't published.

Metric Value Reproduce
Verified applications 69 to date (2026-10-09) python -m engine report: counts SUBMITTED + proof screenshot on disk
Best day 28 (2026-10-09) python -m engine report 2026-10-09
Boards polled ~2,370 workspace/boards.json; a full scan prints the count
Fresh postings per full scan ~3,400 before filtering python -m engine scan 1 output
ATS read-back 77โ€“100% of matched JD terms resume events โ†’ coverage.ats.score
Scheduler throughput ร—2.05 (3 tabs), ร—2.5 (4 tabs) vs sequential python scripts/bench_scheduler.py 20 3 (seeded)
Tailoring speed ร—3 vs v0.7 python scripts/bench_tailor.py
Tests 95 passing python -m pytest -q
Lead resolution alerts 45 relevant โ†’ 6 at source; newgrad 215 โ†’ 34 engine alerts, engine newgrad output
Big-tech roles ready 43 on first run python -m engine bigtech 3

What a "verified application" means

The company's confirmation page was reached and saved as a full-page screenshot, and the event log's latest status for that URL is SUBMITTED. Form-filled-but-unsubmitted, CAPTCHA-blocked or unconfirmed attempts are not counted.

Funnel on a strong day (2026-10-09)

Unique jobs touched: 113 โ†’ skipped by the fit gate 39 โ†’ needs you (legal, CAPTCHA, self-certification) 24 โ†’ failed or errored on site 21 โ†’ flagged by airbags 1 โ†’ submitted 28.

Related: Testing and evidence ยท Outcomes and learning