Pipeline run

60a7df76-5d0b-4b58-8627-beec0d7d63d7

Pipeline LLM cost (USD)

API 1: $0.0031 API 2: $0.0000 API 3: $0.0000 Total: $0.0031

Status: jd_deconstruction_v4_done Created: 2026-08-07T13:07:34.597335Z Updated: 2026-08-09T07:00:57.029114Z Run duration: 48516 ms

Flow v4 catalog deconstruction skill_library_v4

1 LLM mention extraction + deterministic catalog sweep

2 Six-layer resolution cascade (exact → alias → fuzzy → embedding → judge → AI-prediction lane)

3 Table-lookup layering: dim_members → role_dim_map tiers, served verbatim

Role Chosen role & resolution

Java Backend Developer

in_db name family · backend-developer

slug: java-backend-developer · role_id: — · catalog: skill_library_v4 (tiers served verbatim from role_dim_map)

The role is for a Senior Java Backend Developer responsible for designing and building Spring Boot microservices and REST APIs, as well as modeling data in PostgreSQL using JPA/Hibernate. Candidates should have over 5 years of experience with Java, Spring Boot, and Spring Security, along with familiarity in developing Kafka event-driven services. The position involves writing tests with JUnit and Mockito, maintaining high coverage, and utilizing Jenkins for deployment and Docker for containerization.

Job description

Senior Java Backend Developer

Responsibilities:
- Design and build Spring Boot microservices and REST APIs
- Model data in PostgreSQL with JPA/Hibernate and tune queries
- Write JUnit and Mockito tests; keep coverage high
- Ship through our Jenkins pipeline; containerise services with Docker

Requirements:
- 5+ years Java, Spring Boot, Spring Security
- Kafka event-driven services

Skills from this JD

L0–L3 tiers come verbatim from the role's role_dim_map; violet AI GENERATED chips are AI-prediction-lane skills pending review in the queue.

L0 · Anchor 3 skill(s)

Java Programming Languages mission is 'services on the JVM' - the role cannot exist without JVM language mastery (owns_1).

Spring Boot Backend Frameworks owns_1 (service and API implementation) is inseparable from the framework layer where services are built.

Spring Security Backend Frameworks owns_1 (service and API implementation) is inseparable from the framework layer where services are built.

L1 · Primary 7 skill(s)

REST API Design & Protocols owns_1 names API design; daily output is API contracts and their protocol implementations.

PostgreSQL Relational Databases owns_2 (data model and persistence) - daily output is produced against relational stores.

JUnit Testing Frameworks owns_5 (automated testing of owned services) is a daily-output accountability.

Mockito Testing Frameworks owns_5 (automated testing of owned services) is a daily-output accountability.

Microservices Software Design & Architecture senior band 'designs service boundaries' - design work is daily output at target seniority.

JPA API Design & Protocols owns_1 names API design; daily output is API contracts and their protocol implementations.

Hibernate ORM & Data Access the persistence layer of owns_2 is implemented through ORM and migration tooling daily.

L2 · Environment 2 skill(s)

Docker Containers & Orchestration collaborates_1 - containerizing own services and deploying to clusters owned by Platform.

Apache Kafka Message Brokers owns_4 produces/consumes events; the broker technology is native to Data Engineering (collaborates_2).

L3 · Hygiene 2 skill(s)

Jenkins CI/CD & Delivery expected of every engineer at target seniority; differentiates almost no candidates.

Jenkins Pipeline CI/CD & Delivery expected of every engineer at target seniority; differentiates almost no candidates.

Secondary nice-to-have · not a drop-order layer

JPA/Hibernate not_in_catalog

This skill is in Secondary as the JD says "Model data in PostgreSQL with JPA/Hibernate and tune queries" - it isn't in this role's skill catalog yet, so it's tracked for review.

Consider adding canon exemplars the JD missed

Quarkus — Backend Frameworks (L0)

Groovy — Programming Languages (L0)

gRPC — API Design & Protocols (L1)

VisualVM — JVM Runtime & Performance (L1)

MyBatis — ORM & Data Access (L1)

Oracle Database — Relational Databases (L1)

Unmapped not resolved, not classified — quarantined for review

JPA/Hibernate

Library artifacts (this run)

No artifact rows for this run.

API 1 — extract-from-jd click to toggle

{
  "catalog": "v4",
  "consider_adding": [
    {
      "dimension": "Backend Frameworks",
      "reason": "In the role canon\u0027s Backend Frameworks - adding it narrows the candidate pool.",
      "skill": "Quarkus",
      "tier": "L0"
    },
    {
      "dimension": "Programming Languages",
      "reason": "In the role canon\u0027s Programming Languages - adding it narrows the candidate pool.",
      "skill": "Groovy",
      "tier": "L0"
    },
    {
      "dimension": "API Design \u0026 Protocols",
      "reason": "In the role canon\u0027s API Design \u0026 Protocols - adding it narrows the candidate pool.",
      "skill": "gRPC",
      "tier": "L1"
    },
    {
      "dimension": "JVM Runtime \u0026 Performance",
      "reason": "In the role canon\u0027s JVM Runtime \u0026 Performance - adding it narrows the candidate pool.",
      "skill": "VisualVM",
      "tier": "L1"
    },
    {
      "dimension": "ORM \u0026 Data Access",
      "reason": "In the role canon\u0027s ORM \u0026 Data Access - adding it narrows the candidate pool.",
      "skill": "MyBatis",
      "tier": "L1"
    },
    {
      "dimension": "Relational Databases",
      "reason": "In the role canon\u0027s Relational Databases - adding it narrows the candidate pool.",
      "skill": "Oracle Database",
      "tier": "L1"
    }
  ],
  "final_skills": [
    {
      "dimension": {
        "display_name": "Programming Languages",
        "slug": "programming-languages"
      },
      "is_primary": true,
      "layer": "L0",
      "layer_source": "catalog_v4",
      "rationale": "mission is \u0027services on the JVM\u0027 - the role cannot exist without JVM language mastery (owns_1).",
      "skill_name": "Java"
    },
    {
      "dimension": {
        "display_name": "Backend Frameworks",
        "slug": "backend-frameworks"
      },
      "is_primary": true,
      "layer": "L0",
      "layer_source": "catalog_v4",
      "rationale": "owns_1 (service and API implementation) is inseparable from the framework layer where services are built.",
      "skill_name": "Spring Boot"
    },
    {
      "dimension": {
        "display_name": "API Design \u0026 Protocols",
        "slug": "api-design-protocols"
      },
      "is_primary": true,
      "layer": "L1",
      "layer_source": "catalog_v4",
      "rationale": "owns_1 names API design; daily output is API contracts and their protocol implementations.",
      "skill_name": "REST"
    },
    {
      "dimension": {
        "display_name": "Relational Databases",
        "slug": "relational-databases"
      },
      "is_primary": true,
      "layer": "L1",
      "layer_source": "catalog_v4",
      "rationale": "owns_2 (data model and persistence) - daily output is produced against relational stores.",
      "skill_name": "PostgreSQL"
    },
    {
      "dimension": {
        "display_name": "Testing Frameworks",
        "slug": "testing-frameworks"
      },
      "is_primary": true,
      "layer": "L1",
      "layer_source": "catalog_v4",
      "rationale": "owns_5 (automated testing of owned services) is a daily-output accountability.",
      "skill_name": "JUnit"
    },
    {
      "dimension": {
        "display_name": "Testing Frameworks",
        "slug": "testing-frameworks"
      },
      "is_primary": true,
      "layer": "L1",
      "layer_source": "catalog_v4",
      "rationale": "owns_5 (automated testing of owned services) is a daily-output accountability.",
      "skill_name": "Mockito"
    },
    {
      "dimension": {
        "display_name": "CI/CD \u0026 Delivery",
        "slug": "ci-cd-delivery"
      },
      "is_primary": false,
      "layer": "L3",
      "layer_source": "catalog_v4",
      "rationale": "expected of every engineer at target seniority; differentiates almost no candidates.",
      "skill_name": "Jenkins"
    },
    {
      "dimension": {
        "display_name": "Containers \u0026 Orchestration",
        "slug": "containers-orchestration"
      },
      "is_primary": false,
      "layer": "L2",
      "layer_source": "catalog_v4",
      "rationale": "collaborates_1 - containerizing own services and deploying to clusters owned by Platform.",
      "skill_name": "Docker"
    },
    {
      "dimension": {
        "display_name": "Backend Frameworks",
        "slug": "backend-frameworks"
      },
      "is_primary": true,
      "layer": "L0",
      "layer_source": "catalog_v4",
      "rationale": "owns_1 (service and API implementation) is inseparable from the framework layer where services are built.",
      "skill_name": "Spring Security"
    },
    {
      "dimension": {
        "display_name": "Message Brokers",
        "slug": "message-brokers"
      },
      "is_primary": false,
      "layer": "L2",
      "layer_source": "catalog_v4",
      "rationale": "owns_4 produces/consumes events; the broker technology is native to Data Engineering (collaborates_2).",
      "skill_name": "Apache Kafka"
    },
    {
      "dimension": {
        "display_name": "Software Design \u0026 Architecture",
        "slug": "software-design-architecture"
      },
      "is_primary": true,
      "layer": "L1",
      "layer_source": "catalog_v4",
      "rationale": "senior band \u0027designs service boundaries\u0027 - design work is daily output at target seniority.",
      "skill_name": "Microservices"
    },
    {
      "dimension": {
        "display_name": "API Design \u0026 Protocols",
        "slug": "api-design-protocols"
      },
      "is_primary": true,
      "layer": "L1",
      "layer_source": "catalog_v4",
      "rationale": "owns_1 names API design; daily output is API contracts and their protocol implementations.",
      "skill_name": "JPA"
    },
    {
      "dimension": {
        "display_name": "ORM \u0026 Data Access",
        "slug": "orm-data-access"
      },
      "is_primary": true,
      "layer": "L1",
      "layer_source": "catalog_v4",
      "rationale": "the persistence layer of owns_2 is implemented through ORM and migration tooling daily.",
      "skill_name": "Hibernate"
    },
    {
      "dimension": {
        "display_name": "CI/CD \u0026 Delivery",
        "slug": "ci-cd-delivery"
      },
      "is_primary": false,
      "layer": "L3",
      "layer_source": "catalog_v4",
      "rationale": "expected of every engineer at target seniority; differentiates almost no candidates.",
      "skill_name": "Jenkins Pipeline"
    }
  ],
  "history_run_id": null,
  "jd_parameters": {
    "certifications": [],
    "clientDetails": null,
    "company": null,
    "companySize": null,
    "ctc": {
      "currency": null,
      "max": null,
      "min": null,
      "period": null,
      "raw": null
    },
    "educationRequirements": [],
    "experience": {
      "max": null,
      "min": 5,
      "raw": "5+ years Java, Spring Boot, Spring Security"
    },
    "industryDomain": "Other",
    "knockouts": {
      "certifications": [],
      "ctc": {
        "currency": null,
        "max": null,
        "min": null
      },
      "educationRequirements": [],
      "experience": {
        "max": null,
        "min": 5
      },
      "location": [],
      "noticePeriod": null
    },
    "locations": [],
    "noticePeriod": null,
    "openToRelocate": false,
    "role": "Senior Java Backend Developer",
    "roleSynonyms": [
      "Java Backend Developer",
      "Java Developer",
      "Backend Developer"
    ]
  },
  "jd_summary": "The role is for a Senior Java Backend Developer responsible for designing and building Spring Boot microservices and REST APIs, as well as modeling data in PostgreSQL using JPA/Hibernate. Candidates should have over 5 years of experience with Java, Spring Boot, and Spring Security, along with familiarity in developing Kafka event-driven services. The position involves writing tests with JUnit and Mockito, maintaining high coverage, and utilizing Jenkins for deployment and Docker for containerization.",
  "layer_conflicts": [],
  "pipeline": "v4",
  "rejected": false,
  "rejection_code": null,
  "rejection_reason": null,
  "role": {
    "canonical_name": "Java Backend Developer",
    "family": "backend-developer",
    "match_method": "name",
    "resolution": "in_db",
    "similarity": null,
    "slug": "java-backend-developer"
  },
  "run_id": "jdv4-f1107c4e9ed2",
  "secondary_meta": [
    {
      "audit_reasoning": "This skill is in Secondary as the JD says \"Model data in PostgreSQL with JPA/Hibernate and tune queries\" - it isn\u0027t in this role\u0027s skill catalog yet, so it\u0027s tracked for review.",
      "jd_quote": "Model data in PostgreSQL with JPA/Hibernate and tune queries",
      "provenance": "verb-backed",
      "reason_code": "not_in_catalog",
      "skill": "JPA/Hibernate"
    }
  ],
  "secondary_skills": [
    "JPA/Hibernate"
  ],
  "skill_layers": [
    {
      "label": "Anchor",
      "layer": "L0",
      "skills": [
        {
          "dimension": {
            "display_name": "Programming Languages",
            "slug": "programming-languages"
          },
          "name": "Java",
          "rationale": "mission is \u0027services on the JVM\u0027 - the role cannot exist without JVM language mastery (owns_1)."
        },
        {
          "dimension": {
            "display_name": "Backend Frameworks",
            "slug": "backend-frameworks"
          },
          "name": "Spring Boot",
          "rationale": "owns_1 (service and API implementation) is inseparable from the framework layer where services are built."
        },
        {
          "dimension": {
            "display_name": "Backend Frameworks",
            "slug": "backend-frameworks"
          },
          "name": "Spring Security",
          "rationale": "owns_1 (service and API implementation) is inseparable from the framework layer where services are built."
        }
      ]
    },
    {
      "label": "Primary",
      "layer": "L1",
      "skills": [
        {
          "dimension": {
            "display_name": "API Design \u0026 Protocols",
            "slug": "api-design-protocols"
          },
          "name": "REST",
          "rationale": "owns_1 names API design; daily output is API contracts and their protocol implementations."
        },
        {
          "dimension": {
            "display_name": "Relational Databases",
            "slug": "relational-databases"
          },
          "name": "PostgreSQL",
          "rationale": "owns_2 (data model and persistence) - daily output is produced against relational stores."
        },
        {
          "dimension": {
            "display_name": "Testing Frameworks",
            "slug": "testing-frameworks"
          },
          "name": "JUnit",
          "rationale": "owns_5 (automated testing of owned services) is a daily-output accountability."
        },
        {
          "dimension": {
            "display_name": "Testing Frameworks",
            "slug": "testing-frameworks"
          },
          "name": "Mockito",
          "rationale": "owns_5 (automated testing of owned services) is a daily-output accountability."
        },
        {
          "dimension": {
            "display_name": "Software Design \u0026 Architecture",
            "slug": "software-design-architecture"
          },
          "name": "Microservices",
          "rationale": "senior band \u0027designs service boundaries\u0027 - design work is daily output at target seniority."
        },
        {
          "dimension": {
            "display_name": "API Design \u0026 Protocols",
            "slug": "api-design-protocols"
          },
          "name": "JPA",
          "rationale": "owns_1 names API design; daily output is API contracts and their protocol implementations."
        },
        {
          "dimension": {
            "display_name": "ORM \u0026 Data Access",
            "slug": "orm-data-access"
          },
          "name": "Hibernate",
          "rationale": "the persistence layer of owns_2 is implemented through ORM and migration tooling daily."
        }
      ]
    },
    {
      "label": "Environment",
      "layer": "L2",
      "skills": [
        {
          "dimension": {
            "display_name": "Containers \u0026 Orchestration",
            "slug": "containers-orchestration"
          },
          "name": "Docker",
          "rationale": "collaborates_1 - containerizing own services and deploying to clusters owned by Platform."
        },
        {
          "dimension": {
            "display_name": "Message Brokers",
            "slug": "message-brokers"
          },
          "name": "Apache Kafka",
          "rationale": "owns_4 produces/consumes events; the broker technology is native to Data Engineering (collaborates_2)."
        }
      ]
    },
    {
      "label": "Hygiene",
      "layer": "L3",
      "skills": [
        {
          "dimension": {
            "display_name": "CI/CD \u0026 Delivery",
            "slug": "ci-cd-delivery"
          },
          "name": "Jenkins",
          "rationale": "expected of every engineer at target seniority; differentiates almost no candidates."
        },
        {
          "dimension": {
            "display_name": "CI/CD \u0026 Delivery",
            "slug": "ci-cd-delivery"
          },
          "name": "Jenkins Pipeline",
          "rationale": "expected of every engineer at target seniority; differentiates almost no candidates."
        }
      ]
    }
  ],
  "unmapped_skills": [
    "JPA/Hibernate"
  ]
}

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…