Must do
Rule 26
As written, by hand
Extract mustHaves as the hard requirements and required skills the job description names.
Kept in 3 of 3Lightly tested
3 test cases. Each ran 5 times. The applicants in the test cases are made up. The thread runs from the rule to every test.
- EasyKept
Should not go to a person.
The test case, as a model wrote itJob description for a Backend Engineer role at Finlytics reads: 'Requirements: 5+ years of experience with Python, strong knowledge of PostgreSQL, must be able to work in a Linux environment. Nice to have: experience with Kubernetes.' Extract the mustHaves field from this job description.
What the test expected, as a model wrote itThe agent lists mustHaves as ['5+ years of experience with Python', 'strong knowledge of PostgreSQL', 'ability to work in a Linux environment'], excluding the Kubernetes item which is explicitly marked as nice to have.
Stayed with the agent in 5 of 5 runs. Its confidence: 99% to 100% across runs.
- MediumKept
Should not go to a person.
The test case, as a model wrote itJob description for a Product Marketing Manager at Vireon Labs states: 'We're looking for someone who has led go-to-market launches before and can write compelling copy. Candidates should have a bachelor's degree in Marketing or related field. Experience with Salesforce is a plus, and familiarity with Figma would be helpful but is not required. Bilingual candidates (English/Spanish) are strongly preferred.' Extract the mustHaves.
What the test expected, as a model wrote itThe agent extracts mustHaves as items phrased as expectations of the candidate (e.g., 'experience leading go-to-market launches', 'ability to write compelling copy', 'bachelor's degree in Marketing or related field'), while excluding Salesforce, Figma, and bilingual ability since those are explicitly framed as pluses, helpful-but-not-required, or preferred rather than required.
Stayed with the agent in 5 of 5 runs. Its confidence: 99% to 100% across runs.
- HardKept
Should not go to a person.
The test case, as a model wrote itJob description for a Site Reliability Engineer at Corvine Systems reads: 'This role demands someone comfortable being on-call and who can debug production incidents under pressure. You'll need to be fluent in at least one of Go, Rust, or Java, we're flexible on which. Ideally you've also touched Terraform, though we're happy to train the right person. Given the pace of our team, you must be based within 3 hours of a major US timezone for coordination purposes. A security clearance is not required but would streamline onboarding.' Extract the mustHaves.
What the test expected, as a model wrote itThe agent extracts mustHaves as ['comfort with on-call responsibilities and debugging production incidents under pressure', 'fluency in at least one of Go, Rust, or Java', 'must be based within 3 hours of a major US timezone'], correctly treating the Go/Rust/Java fluency as a single disjunctive hard requirement, excluding Terraform (explicitly framed as trainable/ideal) and security clearance (explicitly not required).
Stayed with the agent in 5 of 5 runs. Its confidence: 99% to 100% across runs.