This is a submission for the Hacktoberfest Open-Source AI Challenge Week 3: Slow and Steady

A job posting said it offered “a blend of remote flexibility and in-person collaboration.” My tool called it remote.

For someone applying from Nigeria, that isn't a small mistake. It can mean spending time on a role that isn't actually remote.

That wasn't the only problem I found while building JobKit. Some of the bugs were in my Rust rules. Others were in my reference labels—the answers I had prepared to judge whether the tool was correct.

I built JobKit to make the first read of a job posting faster. What I didn't expect was how much time I'd spend checking my own assumptions.

The model proposes, Rust verifies.

What I Built

Reading a job posting properly takes me about 17 minutes. Most of that goes on three boring questions: is it actually remote, what hours does it want, and how many years of experience does it ask for.…