But the process is a complete black box.
You never know:
• if the recruiter opened your resume • which repositories they checked • what projects caught their attention
So I built recruiter analytics for developer portfolios.
It tracks:
• profile views • repository clicks • resume open rate • viewer location insights • company type viewing the profile
The goal is to give developers a feedback loop similar to product analytics.
Instead of guessing what recruiters value, you can see which projects or skills actually get attention.
I wrote a technical breakdown of how the tracking works and the reasoning behind the design here:
Curious to hear what the HN community thinks about adding analytics to developer portfolios.