Career applications (12 months)
--
Nkosi Felix, Senior Data Platform Engineer
An interactive analytics view of a real, evidence-bounded job-search tracker -- built from the same twelve months of data used to run this search.
This page turns a rigorous, evidence-bounded job-search tracker -- fit scores, funnel stages, interview signal, source provenance, twelve months of data -- into a public analytics view: application volume over time, fit-score distributions, conversion funnel, source-type conversion, and interview signal, with drill-down and cross-filtering.
The rigor of the analytics is the proof of capability; the subject matter -- how hard a real search has been -- is the vulnerability, not a sob story layered on top. Every number here traces back to a private tracker, parsed, validated, and allowlisted before it ever reaches this page.
Loading career telemetry…
Career applications (12 months)
--
Average fit score
--
Median fit score
--
Primary-lane opportunities
--
Broader than "career applications" at left: also counts non-role entries (e.g. scholarships) that are Primary-lane but not a job application, so this number can be larger.
This month's applications
--
"Human-attached" mode (a distinct hand-submission signal) is not yet tracked as its own field in the underlying data and is not shown here rather than approximated.
Interactive charts load when you scroll to this section.
Interview-stage data is sparse -- shown as recorded, never backfilled.
Every attended interview is plotted. A missing numeric score never means a missing interview -- it means the score wasn't recorded, and appears as a distinct "attended, no score" marker instead.
A proxy view: cumulative career applications and cumulative average fit stand in for effort; cumulative applications that reached at least a recruiter screen stand in for traction. A fuller version would need a distinct capability/proof-growth series and an explicit employment-outcome series, neither of which exists in the underlying data yet.
Select a chart segment above to see the underlying records here.
The browser will never read the raw tracker or call the private job-search backend. Every number is generated at build time from an allowlisted set of fields -- counts, percentages, averages, and bucketed scores -- with recruiter and vendor names, compensation figures, and raw private notes never included, by construction, rather than redacted after the fact.