Overview & result
I rebuilt my job crawler with Jev. The task: start at a company's official homepage, find Careers, and identify jobs that match my profile. Before, with an LLM: ~5 minutes. After, with Jev: just over 20 seconds in my test. Every company organizes its website differently. Jev identifies the Careers entry point, chooses which links to follow, recognizes job pages, and scores each role against my profile. This is where Jev makes sense to me: automation that needs lots of small decisions, with faster responses and lower costs than calling an LLM at each step. Packaged it as a skill: jev-job-hunter. Demo below.
How Jev fits in the loop
- Ingest real-time application state and relevant contextual parameters
- Format the decision problem as a bounded Choice or Noul schema
- Query Jev to receive a typed probability distribution over the options
- Execute downstream actions or route tasks according to the winning choice
How to reproduce
- Inspect the original showcase and source material at https://x.com/hqmank/status/2100933183931900346
- Verify the bounded prompt and input candidate schema configured for Jev
- Benchmark decision latency and classification accuracy against baseline models
Why this build matters
Demonstrates a real-world, cost-effective implementation of Jev in a browser automation agent scenario, replacing expensive generative calls with fast typed decisions.
Limitations
- Task accuracy is bounded by the precision of the defined candidate choices
- Third-party external dependencies and network latency may affect total workflow duration