Pipeline run
2dea7d3f-e7bb-4c54-953b-0d8296299cad
Pipeline LLM cost (USD)
API 1: $0.0000
API 2: $0.0000
API 3: $0.0000
Total: $0.0000
Client output enrichment
v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA description
SPARSE JD
Nature of work
—
Tech stack maturity
Mainstream Modern
AI index (0 = no AI use, 5 = totally AI-dependent · v2.1)
0.00 / 5
· Title match
· Has AI skill
· AI skill (primary)
· AI skill (secondary)
· On AI team
· Builds AI products
vocab breakdown (legacy)
Assistants (×1):
—
Frameworks (×2):
—
Models / concepts (×3):
—
Evidence — skills matched in JD (0)
Skill cluster (0 dimension groups, role-scoped)
Status:
extract_from_jd_done
Created: 2026-05-23T23:14:13.141195Z
Updated: 2026-05-23T23:14:13.141195Z
Flow
Current 3-step pipeline
1 POST /skills/extract-from-jd
2 POST /skills/extract-details
3 POST /skills/final-role-output
Role
Chosen role & resolution
No chosen role stored for this run.
Job description
Senior Engineer We are looking for a senior engineer to support our core insurance platform. The successful candidate will maintain and enhance legacy systems written in COBOL on z/OS, work with JCL batch jobs, CICS transactions, and DB2 databases. Experience with VSAM, IMS, or Assembler is a plus. You will collaborate with business analysts to translate insurance product requirements into enhancements. 8+ years in mainframe environments required.
Library artifacts (this run)
No artifact rows for this run.
API 1 — extract-from-jd click to toggle
{
"final_skills": [],
"jd_role": {
"display_name": "Senior Engineer",
"rationale": "JD body too sparse: 65 words, 0 tech-marker hits \u2014 needs more detail (\u003e=80 words or \u003e=2 tech markers) for confident classification",
"role_aliases": [],
"role_archetype": "Other",
"slug": ""
},
"nano_parsed": null,
"rejected": true,
"rejection_reason": "Sparse JD: JD body too sparse: 65 words, 0 tech-marker hits \u2014 needs more detail (\u003e=80 words or \u003e=2 tech markers) for confident classification",
"run_id": null,
"stage3_signals": null,
"stage4_decision": null,
"stage5_updates": null
}
API 2 — extract-details
{}
API 3 — final-role-output
{}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.
Loading…