| Most "AI Job Matchers" have a major hallucination problem: they are way too optimistic. They see two matching keywords and give you a 95% score, ignoring the fact that a Web Dev probably shouldn't be applying for a Senior Embedded Engineer role. I’m building Job Bro to act more like a cynical hiring manager. I just pushed v0.1.8, focusing on Domain-Aware Scoring and Risk Detection. ### What’s new in the logic:
The Technical Goal:I’m aiming for sub-50ms feedback loops for the agentic interface because nobody wants to wait for a spinning wheel while job hunting. The goal is to move past "keyword matching" and into "contextual reasoning." I'd love to get this community's thoughts: What are the "hidden" signals you look for in a JD that most AI tools currently miss? I'm looking to add more risk categories in v0.1.9. Github: aeroxy/job-bro [link] [comments] |