Jev cloud provider mention

Identify cloud platforms required by a job posting

Paste the posting's platform requirements. Distinguish AWS, Azure and Google Cloud from multiple required clouds or a posting that specifies none.

Which cloud platform does the posting require?Live API
Try an example

Original input for the AWS outcome. Edit the evidence to send a new request.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This is an original synthetic demonstration adapted from the cited workflow discussion. It does not reproduce the source application or verify its performance, adoption or security claims.

Read the platform explicitly required by the posting.

Decision rules and labels
AWSAzureGoogle CloudMultiple cloudsNo cloud specifiedNeed evidence
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

Classify the advertised stack, not the candidate.

The label describes what a fictional posting explicitly requires. It does not rate an applicant, infer experience or make a hiring decision. A posting that names no cloud belongs under No cloud specified.

Multiple clouds preserves an explicit AWS-and-Azure requirement. The classifier should not select one because it appears first. An incidental platform mention would need wording that distinguishes it from the actual requirement.

The latest API-collected source names cloud classification in job postings. These authored excerpts expose that text task without reproducing its dataset or claiming coverage of a real labor market.

This is an original synthetic demonstration adapted from the cited workflow discussion. It does not reproduce the source application or verify its performance, adoption or security claims.

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-posting cloud requirements.

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

    Add the information to check

    Paste the posting's platform requirements.

  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 AWS, Azure, Google Cloud, Multiple clouds, No cloud specified. 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 Need evidence 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
AWS requirementAWS100%
Azure requirementAzure100%
Google Cloud requirementGoogle Cloud100%
Multi-cloud requirementMultiple clouds100%
No named requirementNo cloud specified100%
Posting absentNeed evidence100%

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. 6 of 6 results matched the authored fixture expectations.Verified

Understand the results

Source and example scope

Compare each saved result with its authored expectation. A disagreement remains in the fixture review; the call is not repeated to obtain a preferred label.

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.

Runnable offline example

Run one sample, then inspect the local packet

View the code example
Single-request replay
npm install @typesafe-ai/sdk@0.6.0
# Set TYPESAFE_API_KEY privately in your shell.
node run-choice-sample.mjs samples.json case-1
python preview_choice_workflow.py samples.json saved-api-results.json
Scope of this demo

Where this decision fits

Useful scope

  • Cataloging explicit platform requirements in public technical text
  • Preserving multi-cloud mentions
  • Replaying original stack-classification fixtures

Outside this demonstration

  • Evaluating or ranking a job applicant
  • Inferring an organization’s actual infrastructure from an ad
  • Estimating market share from six fictional postings
Example FAQ

Questions about cloud provider mention.

The rubric explains the decision; the application owns the next step.

Does AWS mean the organization actually runs on AWS?

No. It means the supplied posting explicitly requires AWS under this rubric. Actual infrastructure would need separate evidence.

Is this a hiring recommendation?

No. No applicant is supplied or evaluated. The task classifies the text’s technical-platform requirement.

Does the leading probability measure production accuracy?

No. It is the model distribution for this one request. The six examples are functional checks with authored expectations, not a representative benchmark. Inspect disagreements and evaluate your own examples before using the label.

What happens when the API fails?

The window shows an error and supplies no fresh judgment. The downloadable runner sends one request without retries. Need evidence is a valid outcome about incomplete input; it does not stand in for a network or provider failure.

Try your own cloud provider mention input

Edit the evidence above or use the Playground to test another bounded question.