3 ms·
I’m building JobOps because I got tired of the "black box" nature of job hunting. I’m currently a final-year CS student, and I wanted a tool that didn't just sc
by dakheera47 8mo ago
I’m building JobOps because I got tired of the "black box" nature of job hunting. I’m currently a final-year CS student, and I wanted a tool that didn't just scrape jobs but actually closed the loop on whether recruiters are even looking at my resume.
The Two Big Changes:
1. Hiring Cafe Integration: I added an extractor for Hiring Cafe roles. They now flow into the same scoring/tailoring pipeline as all other roles. So it's the same UI with more job sources. Immediate win.
2. Tracer Links: This is the part I’m most excited (and nervous) about. I added tracked redirects for outbound links in the generated resumes.
How it works: When enabled, JobOps rewrites links to your host (/cv/...), logs the click, and redirects to your destination link.
The Goal: Moving from "fire and forget" to "this specific company actually clicked my portfolio link."
The Trade-off: I know this is a double-edged sword. Some email scanners might flag these redirects as suspicious, which is why it's an explicit opt-in feature. I’ve added rough human-vs-bot filtering, but I’d love to hear from anyone who has dealt with PDF-based link deliverability before.
I’d love your feedback on:
The Redirect Logic: Is there a more "stealthy" way to track clicks that won't annoy IT security?
Source Expansion: Which niche job boards are actually worth the effort of writing an extractor for next?
Repo (star if you find it interesting!): https://github.com/DaKheera47/job-ops https://github.com/DaKheera47/job-ops (247 stars and counting—thank you to the community for the feedback so far!)