Jev job preference fit

Compare a job posting with your stated work preferences

Give your work-condition preferences and the posting. Separate an explicit match or conflict from a condition the posting leaves unstated; the comparison does not rank applicants.

job preference fitLive API
Try an example

Both stated work conditions are met.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Compare only the seeker's stated work preferences with the posting.

Decision rules and labels
MatchConflictUnstatedReview
A real response from the Jev API

Edit any input to explore a different decision. No request is sent until you run it.

Your next decision

Not run yet

Choose an example or write your own input, then run it to see the ranked choices.

Results are not stored by this site. Your submitted text is processed by the API provider.

The decision

What the decision checks

A preference mismatch is not an ability judgment. A person may be capable of a role and still choose not to work its schedule or location. This page only uses preferences they explicitly provide.

An omitted condition also differs from a conflict. If a posting says nothing about remote work, the next step is to clarify it rather than infer that remote work is forbidden.

The linked LinkScout workflow separates interests and working conditions from skill fit. This independent exercise keeps only the seeker-controlled preference comparison; it does not screen people for an employer.

This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Illustration of one spreadsheet row producing two separate classification results
Illustration of the decision flow.
How it works

Try the example in four steps

Use the sample to understand the rule, then test your own input for job preference matching.

  1. Illustration of adding the text or evidence for a decision

    Add the information to check

    Give your work-condition preferences and the posting.

  2. Illustration of defining a question and its allowed choices

    Confirm the question and labels

    Open the decision rules and keep the intended distinction between Match, Conflict, Unstated, Review. Edit the choices only when testing your own rule.

  3. Illustration of sending one input and comparing the returned choices

    Run the decision

    Use a sample first, then try your own input. Compare the selected label with the other returned probabilities.

  4. Illustration of reviewing a result and an uncertain item before using it

    Review the next step

    Review Review before using a result. The label is a decision about the supplied information, not an executed action.

Our API test

Recorded API observations

Recorded API observations
Original inputObserved labelLeading probability
Remote daytime workMatch100%
Explicit onsite night shiftConflict100%
Remote status omittedUnstated84.0%
Conflict plus another unknownConflict99.0%
No preferences statedUnstated53.0%
Contradictory postingReview84.0%

These are six original synthetic inputs, tested once per request revision. The percentage is the leading option probability, not measured accuracy. Authored expectations and any disagreements remain in the downloadable evidence. 5 of 6 results matched the authored fixture expectations. For No preferences stated, the expectation was Review; the observed choice was Unstated.Verified

Understand the results

Job preference matching: six recorded examples

The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.

Using the result in your application

The single-request SDK runner uses your private TYPESAFE_API_KEY. The offline consumer reads saved observations, checks request hashes and prints a pending output. It does not call the model or change any external system.

Replay options

Inspect saved outputs or request a new decision

View the code example
Two independent commands
# Offline: inspect the downloaded saved observations. No API key is needed.
python preview_choice_workflow.py samples.json saved-api-results.json

# Optional live request: install the SDK and set TYPESAFE_API_KEY privately.
npm install @typesafe-ai/sdk@0.6.0
node run-choice-sample.mjs samples.json case-1
# The live response prints to the terminal; it does not update saved-api-results.json.
Scope of this demo

Where this decision fits

Useful scope

  • Checking a posting against your stated remote-work preference.
  • Finding an explicit schedule conflict before applying.
  • Identifying missing working-condition information to ask about.

Outside this demonstration

  • Ranking applicants, assessing ability or deciding who should be hired.
  • Inferring age, health, family circumstances or preferences that the user did not state.
Example FAQ

Using this example

The input contract and these limits define what the result means.

Does Conflict mean I am unqualified?

No. It describes a mismatch with your stated working preferences. The example does not evaluate skills or qualifications.

What if the posting leaves out a condition?

Unstated records that gap when no explicit conflict exists. Ask for clarification rather than treating missing information as a refusal.

Does the leading probability measure accuracy?

It describes the distribution over the supplied choices for this request. These six synthetic examples are functional tests with authored expectations, not a production accuracy benchmark.

Will a result change an external system?

No. The demo displays a label and distribution. The downloadable consumer produces a pending preview packet. Application code and a separate authorization policy would control any real action.

Test a different input

Edit the example above to see how a changed fact affects the decision, or open the Playground for another task.