← Back to history

Pipeline run

ff415621-d7aa-4c1f-b32b-24c29141034d

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

—

no_db_connection

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)

No skills extracted

Skill cluster (0 dimension groups, role-scoped)

No dimension groups computed for this JD.

Status: extract_from_jd_done Created: 2026-05-25T22:21:59.635529Z Updated: 2026-05-25T22:21:59.635529Z

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

Site Reliability Engineer

Responsibilities:
- Own SLOs and error budgets for our production services.
- Build and maintain observability stack (Prometheus, Grafana, OpenTelemetry).
- Design incident response runbooks and lead postmortems.
- Capacity planning, performance tuning, on-call rotation.
- Collaborate with feature teams on production-readiness reviews.
- Reduce toil through automation; measure and report MTTR/MTTD.

Skills: Kubernetes, Prometheus, Grafana, on-call, observability, SLOs.

Library artifacts (this run)

No artifact rows for this run.

API 1 — extract-from-jd click to toggle

{
  "final_skills": [],
  "jd_role": {
    "display_name": "Site Reliability Engineer",
    "rationale": "JD body too sparse: 59 words, 1 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: 59 words, 1 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…