Skip to content

Claude Opus 5.5 (effort default (no --effort flag) · thinking on) on Cut a batch of job postings down to the real roles that fit your resume and flag the ones that offer work-permit sponsorship

AClaude Opus 5.5default · thinking on · Claude Code 2.1.299 (headless -p) · cloud · 2026-10-26 · by @bobsiopener

Trust 80%Fully autonomoussuccess · first try
Estimated cost
$0.13
Wall time
25s
Human step-ins
0
Outcome
Pass

Compare with other models on this task →

Summary

Exact prompt

# Cut a batch of job postings down to the real roles that fit your resume and flag the ones that offer work-permit sponsorship All postings and employers are synthetic (employers are neutral codes). Inputs: `resume.json` (role_families, seniority_min, seniority_max, locations), `period.json` (as_of date) and `postings.csv` (posting_id, employer, title, role_family, seniority, location, posted_on, description). Seniority runs junior < mid < senior < staff. `recruiter-notes.txt` is a recruiter's checklist; where it disagrees with the rules below, the rules win. Rules: - Duplicates: postings with the same employer, the same title after lower-casing and collapsing runs of spaces, and the same location are one role. Keep the copy with the earliest `posted_on` (ties: the lowest posting_id); every other copy is a duplicate. Same title at a different location is a different role. - Stale: a kept posting is stale when `as_of` minus `posted_on` is more than 30 days. Exactly 30 days is not stale. - Fit: a kept, non-stale posting fits when its role_family is in the resume's role_families, its seniority is between seniority_min and seniority_max inclusive, and its location is one of the resume's locations. These are the real roles. - Sponsorship: a real role offers work-permit sponsorship only when its description has a line that is exactly `Sponsorship: available` (letter case aside). `Sponsorship: not available` and `Sponsorship: none` mean no. - Write `out/shortlist.json`: `{"real_roles": [<sorted posting_ids>], "duplicates_dropped": [<sorted posting_ids>], "stale_dropped": [<sorted posting_ids of kept postings that are stale>], "sponsor_roles": [<sorted posting_ids>], "roles_by_employer": {"<employer>": <number of real roles>, ...}}`. - Roll-ups: Employers in postings.csv with no real roles are left out. ## How this run works - Work on your own: nobody will answer questions in this task, and writing to `ask/` counts against the run. - Write only under `out/`. Create `out/` if it is missing. Inputs are synthetic; don't fetch anything from the network. - Scoring is partial credit: each listed check is pass/fail, and the score is the share passed. Numbers are compared to within 0.005 unless the task says otherwise.

Take a synthetic batch of job postings from employers with neutral codes and cut it down to the real roles that fit a given resume. First merge reposts, which can differ in letter case and spacing, keeping the earliest copy. Then drop postings older than 30 days, and keep roles that match the resume's role families, seniority range and locations. Flag the roles whose description has a buried 'Sponsorship: available' line. Report the real roles, the dropped duplicates and stale postings, the sponsoring roles and real roles per employer; employers with no real roles are left out. A posting exactly 30 days old, the same title at another location and 'Sponsorship: not available' lines are decoys. The recruiter's checklist gets the repost, staleness and sponsorship rules wrong. Inspired by https://x.com/AbhijayArora/status/2114344232244883509 Headless, offline run on a reproducible fixture. Each run's notes say how its cost was measured (estimates are marked).

Success criteria: real_roles duplicates_dropped stale_dropped sponsor_roles roles_by_employer

Setup notes: Batch 43 case tv04-job-postings-shortlist-and-sponsorship-flags (offline, synthetic inputs, seed 192932884). Autonomous case: no stand-in user and no step-ins expected; any file the solver wrote to ask/ is counted as a measured intervention (0) and blocks a pass. Prompt = TASK.md verbatim. Hidden key kept outside the solver's work dir. Scored with the case's scorer (python3 score.py WORKDIR KEYDIR, absolute paths); pass = every check true and no ask/ files. Tools: Read/Write/Edit/Glob/Grep/Bash, web disabled. Single run, no retries. 1-min load average at scoring 8.43 (8 cores). Time-zone results depend on the system time-zone database: tzdata 2026c-0+deb13u1 (Python zoneinfo). Claude Code's own reported cost for claude-opus-5.5: $0.134362. Score: 5/5. Cost is an ESTIMATE: measured tokens x pricing.json list price (Claude Pro subscription, nothing billed); input_tokens include cache reads and writes. Single run.

Estimated cost List-price estimate; not actually billed.

Metrics

Estimated cost
$0.13
Wall time
25s
Human step-ins
0
Turns
4
Model usage
ModelInput tokOutput tokCost
AClaude Opus 5.5anthropic/claude-opus-5.5effort default (no --effort flag) · thinking on80,7282,060$0.13

Reproduce this run

  1. Use the use case prompt on the use case page.
  2. Same setup: Claude Opus 5.5 (anthropic/claude-opus-5.5, effort default (no --effort flag) · thinking on) via Claude Code 2.1.299 (headless -p), cloud.
  3. It counts as a success only if it meets every success criterion: real_roles duplicates_dropped stale_dropped sponsor_roles roles_by_employer
  4. Log model, tokens, wall time, human step-ins and the evidence log, then submit it as a reproduction. A different model? Submit a head-to-head rerun.

How runs are scored: Methodology.

Was this useful?

⇄ Rerun on another model

Automated checks

Trust 80% comes from these checks (how Trust % works).

Evidence log
[
 {
  "duration_api_ms": 23879,
  "stop_reason": "end_turn",
  "session_id": "[REDACTED]",
  "total_cost_usd": 0.134362,
  "usage": {
   "input_tokens": 8,
   "cache_creation_input_tokens": 9870,
   "cache_read_input_tokens": 70850,
   "output_tokens": 2060,
   "output_tokens_details": {
    "thinking_tokens": 205
   },
   "server_tool_use": {
    "web_search_requests": 0,
    "web_fetch_requests": 0
   },
   "service_tier": "standard",
   "cache_creation": {
    "ephemeral_1h_input_tokens": 9870,
    "ephemeral_5m_input_tokens": 0
   },
   "inference_geo": "global",
   "iterations": [
    {
     "input_tokens": 2,
     "output_tokens": 602,
     "cache_read_input_tokens": 20617,
     "cache_creation_input_tokens": 1399,
     "cache_creation": {
      "ephemeral_5m_input_tokens": 0,
      "ephemeral_1h_input_tokens": 1399
     },
     "type": "message"
    }
   ],
   "speed": "standard",
   "fallback_credit": null
  },
  "modelUsage": {
   "claude-opus-5-5": {
    "inputTokens": 8,
    "outputTokens": 2060,
    "cacheReadInputTokens": 70850,
    "cacheCreationInputTokens": 9870,
    "webSearchRequests": 0,
    "costUSD": 0.134362,
    "contextWindow": 1000000,
    "maxOutputTokens": 128000,
    "thinkingTokens": 205,
    "canonicalModel": "claude-opus-5-5",
    "provider": "firstParty",
    "costBasis": "list"
   }
  },
  "permission_denials": [],
  "terminal_reason": "completed",
  "fast_mode_state": "off",
  "fast_mode_disabled_reason": "sdk_opt_in_required",
  "subagent_stats": {
   "spawned": 0,
   "requested": {
    "background": 0,
    "foreground": 0,
    "unset": 0
   },
   "started_in_background": 0,
   "max_depth": 0,
   "spawned_by_subagents": 0,
   "completed": 0,
   "failed": 0,
   "killed": {
    "parent": 0,
    "user": 0,
    "system": 0
   },
   "refused": {
    "depth_limit": 0,
    "concurrency_limit": 0,
    "budget": 0
   },
   "by_type": {}
  },
  "safety_stops": 0,
  "is_error": false,
  "num_turns": 4,
  "subtype": "success",
  "api_error_status": null,
  "result": "I wrote the shortlist to `out/shortlist.json`. Out of 19 postings, 13 are real roles that fit your resume, and 4 of those offer work-permit sponsorship.\n\n- **Real roles (13):** JP-1074, 1077, 1081, 1085, 1088, 1090, 1094, 1097, 1103, 1113, 1123, 1130, 1138.\n- **Sponsorship (4):** JP-1077, JP-1085, JP-1090 and JP-1113.\n- **Duplicates dropped (2):** JP-1117 and JP-1118 are reposts of Employer E-83's Backend Engineer role in Lisbon. JP-1113 is the earliest copy, so it's the one kept. One of the reposts has its title written as \"  BACKEND  ENGINEER \" with extra spaces. I trimmed the spaces at both ends as well as collapsing the runs inside, so it still counts as the same title.\n- **Stale dropped (1):** JP-1136 was posted 48 days before the as-of date of 2026-05-18. JP-1130 is exactly 30 days old, so under your rules it stays in.\n- **Real roles by employer:** E-17 has 3, E-39 has 2, E-42 has 3, E-83 has 3 and E-88 has 2. E-44 has none, so it's left out.\n\nWhere the recruiter's checklist disagreed with your rules, I followed your rules. That means:\n- I kept the earliest copy of a duplicate, not the newest.\n- I used a 30-day window, not 60.\n- A posting counts as sponsoring only if it has the exact line `Sponsorship: available`.\n- Employers with no real roles are left out rather than listed at 0.",
  "ttft_ms": 3183,
  "type": "result",
  "duration_ms": 24360,
  "uuid": "[REDACTED]",
  "ttft_stream_ms": 2499,
  "time_to_request_ms": 194,
  "first_content_frame_ms": 2500,
  "queued_turn_count": 0,
  "result_index": 0
 }
]

Get new runs and ranking changes weekly