job-ops

k." 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 (247 stars and counting—thank you to the community for the feedback so far!)

tent ./data volume. The LLM integration is provider-agnostic—swap between OpenAI, Gemini, OpenRouter, or local models without code changes. Built an adapter pattern that made adding Ollama support trivial. Job extraction uses a pluggable system: JobSpy (Python wrapper), Gradcracker, UKVisaJobs, manual imports, Glassdoor. Everything normalizes to a unified schema with deduplication. Why local-first: Your job hunt data is sensitive. This runs entirely on your machine. No SaaS, no tracking, no data leaving your infrastructure unless you explicitly configure webhooks. Current state: Been shipping daily for 3 weeks. 200+ stars, 570+ Docker pulls, 5 contributors I've never met, users answering each other's questions in issues. It's gone from "tool for myself" to something people are actually using. Demo (read-only): https://jobops.dakheera47.com Repo: https://github.com/DaKheera47/job-ops Open to feedback, questions, and PRs.

cts for a job i actually care about, it generates an ATS-friendly CV pdf for that role, by changing the top level summary, the keywords and the projects shown. when i get an interview, i can look back to see the job description (to see what the company wants), and my tailored resume (to see what i sent the company). - step 3; track + automate the boring bits the UI has the obvious stuff (stages, extraction, sources), but the fun part is when you mark “applied” it emits a webhook. i use that to push the job into my notion db via n8n, so i’m not copy pasting titles/companies/locations like a caveman. i treat notion as my "source of truth", not because it's good, just because it's what i've been using since the start. it’s open source, local-first, and self-hosted (docker). i’m not selling anything and i’m not trying to turn this into a SaaS, i just wanted something i could run myself and figured it might help someone else too. write-up (hashnode): https://dakheera47.hashnode.dev/jobops repo + quickstart: https://github.com/DaKheera47/job-ops read-only demo: https://jobops.dakheera47.com/ if you hit anything weird, please open an issue (even if it’s just “this step in the README confused me”)