Pipeline run

{
  "final_skills": [
    {
      "is_primary": true,
      "skill_name": "Large Language Models"
    },
    {
      "is_primary": true,
      "skill_name": "Cloud Native"
    },
    {
      "is_primary": true,
      "skill_name": "AI"
    },
    {
      "is_primary": true,
      "skill_name": "Security"
    },
    {
      "is_primary": true,
      "skill_name": "Reliability"
    },
    {
      "is_primary": true,
      "skill_name": "Efficiency"
    }
  ],
  "jd_role": {
    "display_name": "LLM Operations Engineer",
    "rationale": null,
    "role_archetype": "Other",
    "slug": ""
  },
  "nano_parsed": {
    "JD_type": "pass",
    "about_company": null,
    "certifications": [],
    "company_name": null,
    "ctc": null,
    "domain": {
      "primary": {
        "aliases": [],
        "domain": "Other"
      },
      "secondary": null
    },
    "education": [
      {
        "level": "null",
        "qualification": "null - null",
        "raw": "15 years full time education",
        "requirement": "required"
      }
    ],
    "experience": {
      "max": null,
      "min": 3,
      "raw": "Minimum 3 Year(s) Of Experience Is Required"
    },
    "job_locations": [
      {
        "aliases": [
          "Gurgaon"
        ],
        "city": "Gurugram",
        "country": "India",
        "state": null,
        "work_mode": "null"
      }
    ],
    "role": "LLM Operations Engineer",
    "role_archetype": "Other",
    "roles_and_responsibilities": [
      {
        "bullet_count": 6,
        "heading": "Roles \u0026 Responsibilities",
        "heading_was_present": true,
        "source_marker": {
          "first_5_words": "Expected to perform independently and",
          "last_5_words": "guidance and sharing expertise to"
        },
        "text": "Expected to perform independently and become an SME.\nRequired active participation/contribution in team discussions.\nContribute in providing solutions to work related problems.\nCollaborate with cross-functional teams to optimize deployment workflows and operational processes.\nAssist in documenting operational procedures and best practices to support knowledge sharing.\nSupport junior team members by providing guidance and sharing expertise to foster professional growth.",
        "word_count": 56
      },
      {
        "bullet_count": 5,
        "heading": "Professional \u0026 Technical Skills",
        "heading_was_present": true,
        "source_marker": {
          "first_5_words": "Must To Have Skills: Proficiency",
          "last_5_words": "for reliability and efficiency."
        },
        "text": "Must To Have Skills: Proficiency in Large Language Models (LLMs).\nExperience with cloud-native services and tools for deployment and monitoring of AI models.\nStrong understanding of operational challenges related to AI systems and strategies to address them.\nFamiliarity with compliance and security standards applicable to AI and data operations.\nAbility to analyze system performance metrics and implement improvements for reliability and efficiency.",
        "word_count": 66
      }
    ],
    "urls": []
  },
  "run_id": null
}

{
  "alias_matches": [
    {
      "alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
      "alias_persisted": false,
      "existing_alias_id": 3431,
      "existing_alias_text": "AI",
      "input_term": "AI",
      "matched_canonical": {
        "category_id": 2,
        "display_name": "AI",
        "id": 2634,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "CONCEPT",
        "slug": "ai",
        "sub_category_id": 2147,
        "typical_lifespan": "EVERGREEN",
        "volatility": "STABLE"
      },
      "matched_via": "alias"
    }
  ],
  "candidate_roles": [
    {
      "display_name": "Network Engineer",
      "id": 21,
      "rationale": null,
      "role_archetype": null,
      "slug": "network-engineer",
      "source": "db"
    },
    {
      "display_name": "Virtualization Engineer",
      "id": 26,
      "rationale": null,
      "role_archetype": null,
      "slug": "virtualization-engineer",
      "source": "db"
    }
  ],
  "chosen_role": {
    "display_name": "LLM Operations Engineer",
    "id": null,
    "rationale": "The primary skills focus on AI and cloud technologies, which align with the LLM operations role.",
    "role_archetype": "Other",
    "slug": "llm-operations-engineer",
    "source": "llm"
  },
  "dimensions": [
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "Version Control Systems",
        "id": 365,
        "rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
        "slug": "d_init_01",
        "source": "db"
      },
      "input_skill": "AI",
      "llm_role": null,
      "roles_from_db": []
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "Version Control Systems",
        "id": 365,
        "rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
        "slug": "d_init_01",
        "source": "db"
      },
      "input_skill": "Large Language Models",
      "llm_role": null,
      "roles_from_db": []
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "Version Control Systems",
        "id": 365,
        "rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
        "slug": "d_init_01",
        "source": "db"
      },
      "input_skill": "Cloud Native",
      "llm_role": null,
      "roles_from_db": []
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "Version Control Systems",
        "id": 365,
        "rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
        "slug": "d_init_01",
        "source": "db"
      },
      "input_skill": "Security",
      "llm_role": null,
      "roles_from_db": []
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "Version Control Systems",
        "id": 365,
        "rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
        "slug": "d_init_01",
        "source": "db"
      },
      "input_skill": "Reliability",
      "llm_role": null,
      "roles_from_db": []
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "Capacity Planning and Performance Tuning",
        "id": 284,
        "rationale": "Forecasting and tuning the virtualization estate to maintain headroom and acceptable performance. This includes analyzing contention, balancing density, and responding to growth trends.",
        "slug": "capacity-planning-and-performance-tuning",
        "source": "db"
      },
      "input_skill": "Efficiency",
      "llm_role": null,
      "roles_from_db": [
        {
          "display_name": "Network Engineer",
          "id": 21,
          "rationale": null,
          "role_archetype": null,
          "slug": "network-engineer",
          "source": "db"
        },
        {
          "display_name": "Virtualization Engineer",
          "id": 26,
          "rationale": null,
          "role_archetype": null,
          "slug": "virtualization-engineer",
          "source": "db"
        }
      ]
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "Version Control Systems",
        "id": 365,
        "rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
        "slug": "d_init_01",
        "source": "db"
      },
      "input_skill": "Efficiency",
      "llm_role": null,
      "roles_from_db": []
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "Capacity Planning and Performance Tuning",
        "id": 284,
        "rationale": "Forecasting and tuning the virtualization estate to maintain headroom and acceptable performance. This includes analyzing contention, balancing density, and responding to growth trends.",
        "slug": "capacity-planning-and-performance-tuning",
        "source": "db"
      },
      "input_skill": "Efficiency",
      "llm_role": null,
      "roles_from_db": [
        {
          "display_name": "Network Engineer",
          "id": 21,
          "rationale": null,
          "role_archetype": null,
          "slug": "network-engineer",
          "source": "db"
        },
        {
          "display_name": "Virtualization Engineer",
          "id": 26,
          "rationale": null,
          "role_archetype": null,
          "slug": "virtualization-engineer",
          "source": "db"
        }
      ]
    }
  ],
  "input_final_skills": [
    "Large Language Models",
    "Cloud Native",
    "AI",
    "Security",
    "Reliability",
    "Efficiency"
  ],
  "input_llm_skills": [
    "Large Language Models",
    "Cloud Native",
    "AI",
    "Security",
    "Reliability",
    "Efficiency"
  ],
  "new_aliases_persisted": 0,
  "run_id": "afe8eb6e-990a-4496-8b36-09eea3b1a6d1",
  "skills_detail": [
    {
      "aliases_in_db": [],
      "canonical": null,
      "dimensions": [
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "Version Control Systems",
            "id": 365,
            "rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
            "slug": "d_init_01",
            "source": "db"
          },
          "input_skill": "Large Language Models",
          "llm_role": null,
          "roles_from_db": []
        }
      ],
      "input_skill": "Large Language Models",
      "matched_via": null,
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": {
        "derived": {
          "category": "Concept",
          "skill_nature": "CONCEPT",
          "sub_category": "machine_learning_model_concept",
          "typical_lifespan": "EVERGREEN",
          "version_strategy": "NOT_APPLICABLE",
          "volatility": "STABLE"
        },
        "enrichment": {
          "ambiguity": {
            "ambiguity_flag": false,
            "confused_with": [],
            "reasoning": "The term is specific and commonly used in JDs to mean LLMs. It is unlikely to be confused with a different catalog skill in typical hiring context."
          },
          "context_keywords": {
            "context_keywords": [
              "transformer",
              "attention",
              "tokenization",
              "prompt engineering",
              "fine-tuning",
              "inference",
              "embedding",
              "context window",
              "RAG",
              "instruction tuning",
              "RLHF",
              "few-shot",
              "zero-shot",
              "hallucination",
              "vector database"
            ]
          },
          "maturity": {
            "confidence": 0.93,
            "maturity": "well_known",
            "reasoning": "LLMs are now a hiring-pipeline staple: job postings commonly ask for prompt engineering, RAG, and OpenAI/Anthropic integration, and major cloud vendors ship managed LLM services."
          },
          "skill_id": "large-language-models",
          "vendor_license": {
            "confidence": 0.99,
            "license": null,
            "vendor": null,
            "year_introduced": null
          },
          "versioning": {
            "current_version": null,
            "version_aliases": {},
            "versioned": false
          }
        },
        "keep_log": [],
        "locked_dimensions": [
          {
            "description": "Covers the core concepts, capabilities, and operational concerns of LLMs as model artifacts and inference systems. This skill belongs here because it refers to the model class itself, including how LLMs are selected, evaluated, and used in production AI workflows.",
            "exemplar_skills": [
              "Large Language Models",
              "LLM fundamentals",
              "foundation models",
              "transformer models",
              "instruction-tuned models",
              "prompt engineering basics",
              "tokenization",
              "context windows"
            ],
            "in_scope": "Large Language Models, transformer-based foundation models, prompt behavior, tokenization basics, context windows, instruction tuning, model capabilities and limitations, model selection for generative tasks, LLM evaluation concepts",
            "name": "Large Language Models",
            "out_of_scope": "Context packaging and retrieval for prompts, vector search and RAG pipelines, serving infrastructure and deployment packaging, general machine learning training workflows, classic NLP models not based on LLMs",
            "overlap_flags": [
              {
                "reason": "LLM usage often depends on retrieval and prompt context assembly, but that dimension owns the mechanics of grounding and packaging context.",
                "with_dim_id": "context-management-and-retrieval",
                "with_dim_name": null,
                "with_role": "AI Engineer"
              },
              {
                "reason": "Operationalizing LLMs frequently involves deployment and runtime packaging, but that dimension owns serving infrastructure rather than the model concept itself.",
                "with_dim_id": "model-serving-deployment-and-runtime-packaging",
                "with_dim_name": null,
                "with_role": "MLOps Engineer, Machine Learning Engineer"
              },
              {
                "reason": "LLM applications are often embedded in serving architectures, but this dimension focuses on hosting and routing patterns rather than the model class.",
                "with_dim_id": "model-serving-architecture",
                "with_dim_name": null,
                "with_role": "Machine Learning Engineer"
              }
            ],
            "tentative_id": "d_init_01"
          }
        ],
        "merge_log": [],
        "placed": {
          "name": "Large Language Models",
          "placement_confidence": 0.92,
          "primary_dimension": "d_init_01",
          "reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
          "secondary_dimensions": [],
          "skill_id": "large-language-models"
        },
        "relationships": {
          "child_skills": [],
          "parent_skills": [
            "machine-learning"
          ],
          "related_to": [
            "vision-language-models",
            "ml",
            "ai-ml",
            "vlms",
            "multimodal-document-understanding",
            "mlops",
            "mlflow",
            "hybrid-retrieval",
            "layout-parsing",
            "big-data"
          ],
          "requires": [],
          "skill_id": "large-language-models",
          "suppress_on_match": []
        },
        "skill_id": "large-language-models",
        "split_log": [],
        "typed": {
          "alternatives_considered": [],
          "confidence": 0.94,
          "name": "Large Language Models",
          "reasoning": "Large Language Models are a named knowledge unit about a class of machine learning models, so by the Concept vs Methodology rule they are a Concept rather than a tool or framework.",
          "skill_id": "large-language-models",
          "subtype": "machine_learning_model_concept",
          "type": "Concept"
        },
        "warnings": []
      },
      "source_tag": "llm",
      "was_in_llm_skills": true
    },
    {
      "aliases_in_db": [],
      "canonical": null,
      "dimensions": [
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "Version Control Systems",
            "id": 365,
            "rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
            "slug": "d_init_01",
            "source": "db"
          },
          "input_skill": "Cloud Native",
          "llm_role": null,
          "roles_from_db": []
        }
      ],
      "input_skill": "Cloud Native",
      "matched_via": null,
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": {
        "derived": {
          "category": "Architecture",
          "skill_nature": "PATTERN",
          "sub_category": "cloud_native_architecture",
          "typical_lifespan": "EVERGREEN",
          "version_strategy": "NOT_APPLICABLE",
          "volatility": "STABLE"
        },
        "enrichment": {
          "ambiguity": {
            "ambiguity_flag": false,
            "confused_with": [],
            "reasoning": "\u201cCloud Native\u201d is a fairly specific architecture term in JDs and is usually distinguishable from generic cloud skills or vendor products; typical extractors are unlikely to confuse it with another catalog skill."
          },
          "context_keywords": {
            "context_keywords": [
              "Kubernetes",
              "containers",
              "microservices",
              "service mesh",
              "Docker",
              "Helm",
              "Istio",
              "CI/CD",
              "DevOps",
              "observability",
              "autoscaling",
              "immutable infrastructure",
              "12-factor app",
              "serverless",
              "GitOps"
            ]
          },
          "maturity": {
            "confidence": 0.93,
            "maturity": "well_known",
            "reasoning": "Cloud-native is broadly adopted: it appears in many job descriptions and is a standard focus in CNCF/Kubernetes ecosystems, with major vendors marketing cloud-native platforms and tooling."
          },
          "skill_id": "cloud-native",
          "vendor_license": {
            "confidence": 0.98,
            "license": null,
            "vendor": null,
            "year_introduced": null
          },
          "versioning": {
            "current_version": null,
            "version_aliases": {},
            "versioned": false
          }
        },
        "keep_log": [],
        "locked_dimensions": [
          {
            "description": "Designing applications and services to run effectively in cloud-managed environments using elastic, distributed, and container-friendly patterns. Cloud Native fits here because it describes the architectural style and operational assumptions behind modern cloud-first systems.",
            "exemplar_skills": [
              "Cloud Native",
              "microservices architecture",
              "containerized application design",
              "stateless service design",
              "horizontal autoscaling",
              "immutable infrastructure"
            ],
            "in_scope": "Cloud Native, microservices, containers, stateless services, twelve-factor app principles, service discovery, horizontal scaling, immutable infrastructure, Kubernetes-aware design",
            "name": "Cloud Native Architecture",
            "out_of_scope": "Specific cloud provider configuration, CI/CD pipelines, observability tooling, and service-to-service API wiring, which belong to other platform or integration dimensions",
            "overlap_flags": [
              {
                "reason": "Cloud native systems often rely on APIs and events, but that dimension focuses on how services connect rather than the deployment style itself.",
                "with_dim_id": "cloud-service-integration-patterns",
                "with_dim_name": null,
                "with_role": "Cloud Architect"
              },
              {
                "reason": "For LLM operations, cloud native deployment patterns can overlap with model serving, but model-serving architecture is specifically about inference hosting and routing.",
                "with_dim_id": "model-serving-architecture",
                "with_dim_name": null,
                "with_role": "Machine Learning Engineer"
              }
            ],
            "tentative_id": "d_init_01"
          }
        ],
        "merge_log": [],
        "placed": {
          "name": "Cloud Native",
          "placement_confidence": 0.92,
          "primary_dimension": "d_init_01",
          "reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
          "secondary_dimensions": [],
          "skill_id": "cloud-native"
        },
        "relationships": {
          "child_skills": [],
          "parent_skills": [],
          "related_to": [
            "devops",
            "ci-cd",
            "mlops",
            "nosql",
            "big-data",
            "lxc-lxd",
            "microsoft-azure",
            "aws-lambda",
            "ec2",
            "minio"
          ],
          "requires": [],
          "skill_id": "cloud-native",
          "suppress_on_match": []
        },
        "skill_id": "cloud-native",
        "split_log": [],
        "typed": {
          "alternatives_considered": [
            "Concept: ruled out \u2014 it is broader than a single knowledge unit and primarily describes an architectural approach."
          ],
          "confidence": 0.9,
          "name": "Cloud Native",
          "reasoning": "By the Architecture vs Concept rule, Cloud Native is a system-shape pattern for building and operating software in cloud environments, not a knowledge unit or methodology.",
          "skill_id": "cloud-native",
          "subtype": "cloud_native_architecture",
          "type": "Architecture"
        },
        "warnings": []
      },
      "source_tag": "llm",
      "was_in_llm_skills": true
    },
    {
      "aliases_in_db": [
        {
          "alias_text": "AI",
          "alias_type": "CANONICAL",
          "id": 3431,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        }
      ],
      "canonical": {
        "category_id": 2,
        "display_name": "AI",
        "id": 2634,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "CONCEPT",
        "slug": "ai",
        "sub_category_id": 2147,
        "typical_lifespan": "EVERGREEN",
        "volatility": "STABLE"
      },
      "dimensions": [
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "Version Control Systems",
            "id": 365,
            "rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
            "slug": "d_init_01",
            "source": "db"
          },
          "input_skill": "AI",
          "llm_role": null,
          "roles_from_db": []
        }
      ],
      "input_skill": "AI",
      "matched_via": "alias",
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": null,
      "source_tag": "db",
      "was_in_llm_skills": true
    },
    {
      "aliases_in_db": [],
      "canonical": null,
      "dimensions": [
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "Version Control Systems",
            "id": 365,
            "rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
            "slug": "d_init_01",
            "source": "db"
          },
          "input_skill": "Security",
          "llm_role": null,
          "roles_from_db": []
        }
      ],
      "input_skill": "Security",
      "matched_via": null,
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": {
        "derived": {
          "category": "Domain",
          "skill_nature": "CONCEPT",
          "sub_category": "security",
          "typical_lifespan": "EVERGREEN",
          "version_strategy": "NOT_APPLICABLE",
          "volatility": "STABLE"
        },
        "enrichment": {
          "ambiguity": {
            "ambiguity_flag": false,
            "confused_with": [],
            "reasoning": "\u201cSecurity\u201d is a broad domain term, but in JDs it usually denotes the cybersecurity/security function itself rather than a different catalog skill. It\u2019s not a short acronym or overloaded product name."
          },
          "context_keywords": {
            "context_keywords": [
              "threat modeling",
              "vulnerability assessment",
              "penetration testing",
              "SIEM",
              "IDS/IPS",
              "zero trust",
              "IAM",
              "least privilege",
              "incident response",
              "SOC",
              "CVE",
              "CWE",
              "OWASP",
              "encryption",
              "risk assessment"
            ]
          },
          "maturity": {
            "confidence": 0.96,
            "maturity": "well_known",
            "reasoning": "Security is a standard requirement in most engineering JDs (AppSec, cloud security, IAM, SOC2), and major vendors like AWS/Azure/GCP all market security services as core platform capabilities."
          },
          "skill_id": "security",
          "vendor_license": {
            "confidence": 0.99,
            "license": null,
            "vendor": null,
            "year_introduced": null
          },
          "versioning": {
            "current_version": null,
            "version_aliases": {},
            "versioned": false
          }
        },
        "keep_log": [],
        "locked_dimensions": [
          {
            "description": "Core security concepts and controls that apply across systems, services, and operations. This skill is broad and not specific enough to fit a narrower catalog dimension, so it belongs in a foundational security cluster.",
            "exemplar_skills": [
              "Security",
              "Threat Modeling",
              "Least Privilege",
              "Defense in Depth",
              "Vulnerability Management",
              "Secure Configuration",
              "Encryption Basics",
              "Secrets Management"
            ],
            "in_scope": "Security, threat modeling, least privilege, defense in depth, vulnerability awareness, risk reduction, secure configuration, encryption basics, secrets handling, audit logging",
            "name": "Security Fundamentals",
            "out_of_scope": "Authentication flows and identity protocols, which belong to authentication-and-session-security; incident handling and breach response, which belong to incident-response-and-containment; email-specific protections, which belong to email-security-and-anti-phishing",
            "overlap_flags": [
              {
                "reason": "Identity, login, and session protections are a common sub-area of security but are more specific than the broad target skill.",
                "with_dim_id": "authentication-and-session-security",
                "with_dim_name": null,
                "with_role": "Cybersecurity Engineer"
              },
              {
                "reason": "Operational security work often overlaps with detecting and responding to incidents, but that is a distinct response-focused dimension.",
                "with_dim_id": "incident-response-and-containment",
                "with_dim_name": null,
                "with_role": "Cybersecurity Engineer"
              }
            ],
            "tentative_id": "d_init_01"
          }
        ],
        "merge_log": [],
        "placed": {
          "name": "Security",
          "placement_confidence": 0.92,
          "primary_dimension": "d_init_01",
          "reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
          "secondary_dimensions": [],
          "skill_id": "security"
        },
        "relationships": {
          "child_skills": [],
          "parent_skills": [],
          "related_to": [
            "authentication",
            "tls-internals",
            "digital-signatures",
            "ecdsa",
            "observability",
            "testability",
            "sql",
            "git",
            "ocr",
            "governance-controlled-upgrades"
          ],
          "requires": [],
          "skill_id": "security",
          "suppress_on_match": []
        },
        "skill_id": "security",
        "split_log": [],
        "typed": {
          "alternatives_considered": [],
          "confidence": 0.98,
          "name": "Security",
          "reasoning": "Security is a vertical/problem-space body of knowledge rather than a tool, framework, or methodology, so it fits the Domain type.",
          "skill_id": "security",
          "subtype": "security",
          "type": "Domain"
        },
        "warnings": []
      },
      "source_tag": "llm",
      "was_in_llm_skills": true
    },
    {
      "aliases_in_db": [],
      "canonical": null,
      "dimensions": [
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "Version Control Systems",
            "id": 365,
            "rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
            "slug": "d_init_01",
            "source": "db"
          },
          "input_skill": "Reliability",
          "llm_role": null,
          "roles_from_db": []
        }
      ],
      "input_skill": "Reliability",
      "matched_via": null,
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": {
        "derived": {
          "category": "Concept",
          "skill_nature": "CONCEPT",
          "sub_category": "reliability",
          "typical_lifespan": "EVERGREEN",
          "version_strategy": "NOT_APPLICABLE",
          "volatility": "STABLE"
        },
        "enrichment": {
          "ambiguity": {
            "ambiguity_flag": false,
            "confused_with": [],
            "reasoning": "\u201cReliability\u201d is a broad concept but not a short acronym or overloaded product name; in JDs it usually clearly means system reliability/resilience, not a distinct catalog skill."
          },
          "context_keywords": {
            "context_keywords": [
              "fault tolerance",
              "redundancy",
              "high availability",
              "failover",
              "resilience",
              "MTBF",
              "MTTR",
              "SLA",
              "incident response",
              "disaster recovery",
              "observability",
              "monitoring",
              "capacity planning",
              "service uptime",
              "error budget"
            ]
          },
          "maturity": {
            "confidence": 0.93,
            "maturity": "well_known",
            "reasoning": "Reliability is a standard SRE/DevOps hiring requirement; job postings commonly ask for SLIs/SLOs, incident response, and high-availability design across cloud platforms."
          },
          "skill_id": "reliability",
          "vendor_license": {
            "confidence": 0.99,
            "license": null,
            "vendor": null,
            "year_introduced": null
          },
          "versioning": {
            "current_version": null,
            "version_aliases": {},
            "versioned": false
          }
        },
        "keep_log": [],
        "locked_dimensions": [
          {
            "description": "Practices for keeping systems available, resilient, and recoverable under failure or load. This fits the target skill because reliability is the umbrella concern for uptime, fault tolerance, incident readiness, and safe recovery.",
            "exemplar_skills": [
              "Reliability",
              "fault tolerance",
              "high availability",
              "failover design",
              "graceful degradation",
              "service level objectives",
              "resilience testing"
            ],
            "in_scope": "Reliability, uptime targets, fault tolerance, redundancy, failover, graceful degradation, recovery objectives, service health, resilience testing, error budgets, SLOs, SLIs",
            "name": "System Reliability Engineering",
            "out_of_scope": "Capacity planning and performance tuning, storage latency optimization, incident triage and containment, application feature correctness, security hardening",
            "overlap_flags": [
              {
                "reason": "Operational response to outages overlaps with reliability, but this dimension owns the reactive incident workflow.",
                "with_dim_id": "incident-response-and-containment",
                "with_dim_name": null,
                "with_role": "Cybersecurity Engineer"
              },
              {
                "reason": "Performance and headroom affect reliability, but that catalog dimension owns load and capacity optimization.",
                "with_dim_id": "capacity-planning-and-performance-tuning",
                "with_dim_name": null,
                "with_role": "Network Engineer, Virtualization Engineer"
              }
            ],
            "tentative_id": "d_init_01"
          }
        ],
        "merge_log": [],
        "placed": {
          "name": "Reliability",
          "placement_confidence": 0.92,
          "primary_dimension": "d_init_01",
          "reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
          "secondary_dimensions": [],
          "skill_id": "reliability"
        },
        "relationships": {
          "child_skills": [],
          "parent_skills": [],
          "related_to": [
            "testability",
            "observability",
            "failure-analysis",
            "evaluation",
            "evaluation-design",
            "restore-validation",
            "restore-testing",
            "ci-cd",
            "agile",
            "authentication"
          ],
          "requires": [],
          "skill_id": "reliability",
          "suppress_on_match": []
        },
        "skill_id": "reliability",
        "split_log": [],
        "typed": {
          "alternatives_considered": [],
          "confidence": 0.96,
          "name": "Reliability",
          "reasoning": "Reliability is a named knowledge unit about system behavior and quality, so by the Concept vs Methodology rule it is a Concept rather than a way of working or an architecture.",
          "skill_id": "reliability",
          "subtype": "reliability",
          "type": "Concept"
        },
        "warnings": []
      },
      "source_tag": "llm",
      "was_in_llm_skills": true
    },
    {
      "aliases_in_db": [],
      "canonical": null,
      "dimensions": [
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "Capacity Planning and Performance Tuning",
            "id": 284,
            "rationale": "Forecasting and tuning the virtualization estate to maintain headroom and acceptable performance. This includes analyzing contention, balancing density, and responding to growth trends.",
            "slug": "capacity-planning-and-performance-tuning",
            "source": "db"
          },
          "input_skill": "Efficiency",
          "llm_role": null,
          "roles_from_db": [
            {
              "display_name": "Network Engineer",
              "id": 21,
              "rationale": null,
              "role_archetype": null,
              "slug": "network-engineer",
              "source": "db"
            },
            {
              "display_name": "Virtualization Engineer",
              "id": 26,
              "rationale": null,
              "role_archetype": null,
              "slug": "virtualization-engineer",
              "source": "db"
            }
          ]
        },
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "Version Control Systems",
            "id": 365,
            "rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
            "slug": "d_init_01",
            "source": "db"
          },
          "input_skill": "Efficiency",
          "llm_role": null,
          "roles_from_db": []
        },
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "Capacity Planning and Performance Tuning",
            "id": 284,
            "rationale": "Forecasting and tuning the virtualization estate to maintain headroom and acceptable performance. This includes analyzing contention, balancing density, and responding to growth trends.",
            "slug": "capacity-planning-and-performance-tuning",
            "source": "db"
          },
          "input_skill": "Efficiency",
          "llm_role": null,
          "roles_from_db": [
            {
              "display_name": "Network Engineer",
              "id": 21,
              "rationale": null,
              "role_archetype": null,
              "slug": "network-engineer",
              "source": "db"
            },
            {
              "display_name": "Virtualization Engineer",
              "id": 26,
              "rationale": null,
              "role_archetype": null,
              "slug": "virtualization-engineer",
              "source": "db"
            }
          ]
        }
      ],
      "input_skill": "Efficiency",
      "matched_via": null,
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": {
        "derived": {
          "category": "Concept",
          "skill_nature": "CONCEPT",
          "sub_category": "efficiency_principle",
          "typical_lifespan": "EVERGREEN",
          "version_strategy": "NOT_APPLICABLE",
          "volatility": "STABLE"
        },
        "enrichment": {
          "ambiguity": {
            "ambiguity_flag": true,
            "confused_with": [
              "efficiency_ratio",
              "energy_efficiency"
            ],
            "reasoning": "\"Efficiency\" is a broad concept and in JDs could refer to efficiency ratio or energy efficiency rather than the general performance-tuning principle, so an extractor may conflate it with related catalog skills."
          },
          "context_keywords": {
            "context_keywords": [
              "throughput",
              "latency",
              "resource utilization",
              "bottleneck analysis",
              "profiling",
              "benchmarking",
              "capacity planning",
              "performance tuning",
              "scalability",
              "load testing",
              "optimization",
              "CPU utilization",
              "memory footprint",
              "response time"
            ]
          },
          "maturity": {
            "confidence": 0.93,
            "maturity": "well_known",
            "reasoning": "Efficiency is a core performance-tuning principle referenced across most engineering JDs and capacity-planning roles; it\u2019s a standard expectation in system design, SRE, and backend interviews rather than a niche tool or sunset practice."
          },
          "skill_id": "efficiency",
          "vendor_license": {
            "confidence": 0.99,
            "license": null,
            "vendor": null,
            "year_introduced": null
          },
          "versioning": {
            "current_version": null,
            "version_aliases": {},
            "versioned": false
          }
        },
        "keep_log": [
          {
            "a_dim_id": "capacity-planning-and-performance-tuning",
            "a_name": "Capacity Planning and Performance Tuning",
            "a_role": "__skill_focal__",
            "b_dim_id": "capacity-planning-and-performance-tuning",
            "b_name": "Capacity Planning and Performance Tuning",
            "b_role": "Virtualization Engineer",
            "pair_kind": "cross_role",
            "reasoning": "Dim A is general system/application performance work: throughput, latency, resource utilization, workload right-sizing, bottleneck analysis, and tuning compute/memory/storage/network budgets. Dim B is virtualization-specific: forecasting and tuning the virtualization estate, maintaining headroom, analyzing contention, and balancing density. A\u2019s exemplars like throughput tuning and latency tuning fit broad runtime optimization; B\u2019s focus on estate density and headroom is a different layer of infrastructure management. Same label, different skill cluster.",
            "similarity": 0.7154335963486582
          },
          {
            "a_dim_id": "capacity-planning-and-performance-tuning",
            "a_name": "Capacity Planning and Performance Tuning",
            "a_role": "__skill_focal__",
            "b_dim_id": "performance-tuning-and-latency",
            "b_name": "Performance Tuning and Latency",
            "b_role": "Storage Engineer",
            "pair_kind": "cross_role",
            "reasoning": "Dim A is broad system-level capacity/performance work: it covers throughput, latency, resource utilization, workload right-sizing, headroom analysis, and density optimization across compute/memory/storage/network. Its exemplars include capacity forecasting, resource utilization, bottleneck analysis, and workload right-sizing. Dim B is storage-specific: it targets storage throughput, IOPS, and latency under workload pressure, with changes to media, protocol, and configuration. The overlap is only in generic performance wording; the underlying skill clusters differ.",
            "similarity": 0.7080801755296889
          }
        ],
        "locked_dimensions": [
          {
            "description": "Covers improving system throughput, latency, and resource utilization by sizing workloads, removing bottlenecks, and tuning configurations. Efficiency fits here when it means getting more useful work from the same compute, memory, storage, or network budget.",
            "exemplar_skills": [
              "Efficiency",
              "capacity forecasting",
              "resource utilization",
              "bottleneck analysis",
              "workload right-sizing",
              "throughput tuning",
              "latency tuning"
            ],
            "in_scope": "Efficiency, capacity forecasting, headroom analysis, contention reduction, workload right-sizing, throughput tuning, latency tuning, resource utilization, bottleneck analysis, performance baselining, density optimization",
            "name": "Capacity Planning and Performance Tuning",
            "out_of_scope": "Code readability, feature design, and product UX efficiency; those belong to application or frontend dimensions. Security hardening and incident handling are excluded because they optimize risk response rather than runtime efficiency.",
            "overlap_flags": [
              {
                "reason": "Both dimensions address runtime speed and bottlenecks; this one is broader and includes capacity/headroom concerns.",
                "with_dim_id": "performance-tuning-and-latency",
                "with_dim_name": null,
                "with_role": "Storage Engineer"
              },
              {
                "reason": "Query-level efficiency can be a subcase of overall performance tuning, especially for data-heavy systems.",
                "with_dim_id": "data-access-and-query-optimization",
                "with_dim_name": null,
                "with_role": "Data Engineer"
              }
            ],
            "tentative_id": "capacity-planning-and-performance-tuning"
          },
          {
            "description": "Covers choosing and analyzing approaches that reduce time or space complexity in code and data processing. Efficiency belongs here when it refers to making an implementation faster, smaller, or less computationally expensive.",
            "exemplar_skills": [
              "Efficiency",
              "time complexity",
              "space complexity",
              "algorithm optimization",
              "asymptotic analysis",
              "memoization",
              "data structure choice"
            ],
            "in_scope": "Efficiency, time complexity, space complexity, algorithm optimization, asymptotic analysis, memoization, batching, caching, computational cost reduction, data structure choice",
            "name": "Algorithmic Efficiency",
            "out_of_scope": "Infrastructure sizing, cluster utilization, and hardware tuning are excluded because they belong to capacity and performance operations. UI responsiveness and visual rendering efficiency are excluded because they belong to frontend performance dimensions.",
            "overlap_flags": [
              {
                "reason": "Efficiency may appear in scripting and notebook work, but this dimension is about the computational properties of the solution rather than the language itself.",
                "with_dim_id": "analytical-programming-languages",
                "with_dim_name": null,
                "with_role": "Data Analyst, Data Scientist"
              }
            ],
            "tentative_id": "d_init_01"
          },
          {
            "description": "Forecasting and tuning the virtualization estate to maintain headroom and acceptable performance. This includes analyzing contention, balancing density, and responding to growth trends.",
            "exemplar_skills": [
              "Capacity Planning and Performance Tuning"
            ],
            "in_scope": "Skills, tools, and practices that belong under Capacity Planning and Performance Tuning for the target role, including items implied by the dimension rationale.",
            "name": "Capacity Planning and Performance Tuning",
            "out_of_scope": "Adjacent clusters explicitly not owned by Capacity Planning and Performance Tuning, including unrelated platforms, roles, and skill families per library policy.",
            "overlap_flags": [],
            "tentative_id": "capacity-planning-and-performance-tuning"
          }
        ],
        "merge_log": [],
        "placed": {
          "name": "Efficiency",
          "placement_confidence": 0.92,
          "primary_dimension": "capacity-planning-and-performance-tuning",
          "reasoning": "Deterministic JD placement: locked_dimensions has 3 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
          "secondary_dimensions": [
            "d_init_01"
          ],
          "skill_id": "efficiency"
        },
        "relationships": {
          "child_skills": [],
          "parent_skills": [],
          "related_to": [
            "evaluation",
            "prompt-engineering",
            "agile",
            "observability",
            "testability",
            "workflow-automation",
            "queueing",
            "devops",
            "lean",
            "algorithms"
          ],
          "requires": [],
          "skill_id": "efficiency",
          "suppress_on_match": []
        },
        "skill_id": "efficiency",
        "split_log": [],
        "typed": {
          "alternatives_considered": [],
          "confidence": 0.93,
          "name": "Efficiency",
          "reasoning": "Efficiency is a named knowledge unit about minimizing resource use or waste, so by the Concept vs Methodology rule it is a Concept rather than a way of working.",
          "skill_id": "efficiency",
          "subtype": "efficiency_principle",
          "type": "Concept"
        },
        "warnings": [
          "stage3_post_filter_dropped_catalog_only_locked_dims:42-\u003e3"
        ]
      },
      "source_tag": "llm",
      "was_in_llm_skills": true
    }
  ],
  "unmatched_skills": [
    "Large Language Models",
    "Cloud Native",
    "Security",
    "Reliability",
    "Efficiency"
  ]
}

{
  "chosen_role": {
    "display_name": "LLM Operations Engineer",
    "id": null,
    "rationale": "The primary skills focus on AI and cloud technologies, which align with the LLM operations role.",
    "role_archetype": "Other",
    "slug": "llm-operations-engineer",
    "source": "llm"
  },
  "chosen_role_resolution": "human_review_required",
  "final_input_skills": [
    {
      "skill": "Large Language Models",
      "tag": "new"
    },
    {
      "skill": "Cloud Native",
      "tag": "new"
    },
    {
      "skill": "AI",
      "tag": "in_db"
    },
    {
      "skill": "Security",
      "tag": "new"
    },
    {
      "skill": "Reliability",
      "tag": "new"
    },
    {
      "skill": "Efficiency",
      "tag": "new"
    }
  ],
  "persistence": {
    "items": [
      {
        "chosen_role_id": null,
        "dimension": {
          "difficulty_hint": "well_known",
          "display_name": "Version Control Systems",
          "id": 365,
          "rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
          "slug": "d_init_01",
          "source": "db"
        },
        "dimension_id": 365,
        "input_skill": "AI",
        "llm_role": null,
        "matched_chosen_role": false,
        "outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
        "role_dimension_saved": false,
        "roles_from_db": [],
        "skill_dimension_saved": true,
        "skill_id": 2634,
        "skill_tag": "in_db",
        "skipped_reason": null
      },
      {
        "chosen_role_id": null,
        "dimension": {
          "difficulty_hint": "well_known",
          "display_name": "Version Control Systems",
          "id": 365,
          "rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
          "slug": "d_init_01",
          "source": "db"
        },
        "dimension_id": 365,
        "input_skill": "Large Language Models",
        "llm_role": null,
        "matched_chosen_role": false,
        "outcome_line": "New skill saved \u00b7 Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
        "role_dimension_saved": false,
        "roles_from_db": [],
        "skill_dimension_saved": true,
        "skill_id": 2695,
        "skill_tag": "in_db",
        "skipped_reason": null
      },
      {
        "chosen_role_id": null,
        "dimension": {
          "difficulty_hint": "well_known",
          "display_name": "Version Control Systems",
          "id": 365,
          "rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
          "slug": "d_init_01",
          "source": "db"
        },
        "dimension_id": 365,
        "input_skill": "Cloud Native",
        "llm_role": null,
        "matched_chosen_role": false,
        "outcome_line": "New skill saved \u00b7 Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
        "role_dimension_saved": false,
        "roles_from_db": [],
        "skill_dimension_saved": true,
        "skill_id": 2696,
        "skill_tag": "in_db",
        "skipped_reason": null
      },
      {
        "chosen_role_id": null,
        "dimension": {
          "difficulty_hint": "well_known",
          "display_name": "Version Control Systems",
          "id": 365,
          "rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
          "slug": "d_init_01",
          "source": "db"
        },
        "dimension_id": 365,
        "input_skill": "Security",
        "llm_role": null,
        "matched_chosen_role": false,
        "outcome_line": "New skill saved \u00b7 Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
        "role_dimension_saved": false,
        "roles_from_db": [],
        "skill_dimension_saved": true,
        "skill_id": 2697,
        "skill_tag": "in_db",
        "skipped_reason": null
      },
      {
        "chosen_role_id": null,
        "dimension": {
          "difficulty_hint": "well_known",
          "display_name": "Version Control Systems",
          "id": 365,
          "rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
          "slug": "d_init_01",
          "source": "db"
        },
        "dimension_id": 365,
        "input_skill": "Reliability",
        "llm_role": null,
        "matched_chosen_role": false,
        "outcome_line": "New skill saved \u00b7 Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
        "role_dimension_saved": false,
        "roles_from_db": [],
        "skill_dimension_saved": true,
        "skill_id": 2698,
        "skill_tag": "in_db",
        "skipped_reason": null
      },
      {
        "chosen_role_id": null,
        "dimension": {
          "difficulty_hint": "well_known",
          "display_name": "Capacity Planning and Performance Tuning",
          "id": 284,
          "rationale": "Forecasting and tuning the virtualization estate to maintain headroom and acceptable performance. This includes analyzing contention, balancing density, and responding to growth trends.",
          "slug": "capacity-planning-and-performance-tuning",
          "source": "db"
        },
        "dimension_id": 284,
        "input_skill": "Efficiency",
        "llm_role": null,
        "matched_chosen_role": false,
        "outcome_line": "New skill saved \u00b7 Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
        "role_dimension_saved": false,
        "roles_from_db": [
          {
            "display_name": "Network Engineer",
            "id": 21,
            "rationale": null,
            "role_archetype": null,
            "slug": "network-engineer",
            "source": "db"
          },
          {
            "display_name": "Virtualization Engineer",
            "id": 26,
            "rationale": null,
            "role_archetype": null,
            "slug": "virtualization-engineer",
            "source": "db"
          }
        ],
        "skill_dimension_saved": true,
        "skill_id": 2699,
        "skill_tag": "in_db",
        "skipped_reason": null
      },
      {
        "chosen_role_id": null,
        "dimension": {
          "difficulty_hint": "well_known",
          "display_name": "Version Control Systems",
          "id": 365,
          "rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
          "slug": "d_init_01",
          "source": "db"
        },
        "dimension_id": 365,
        "input_skill": "Efficiency",
        "llm_role": null,
        "matched_chosen_role": false,
        "outcome_line": "New skill saved \u00b7 Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
        "role_dimension_saved": false,
        "roles_from_db": [],
        "skill_dimension_saved": true,
        "skill_id": 2699,
        "skill_tag": "in_db",
        "skipped_reason": null
      }
    ],
    "new_skills_created": 5,
    "role_dimension_saved": 0,
    "skill_dimension_saved": 6,
    "skipped": 0
  },
  "planner_output": null,
  "run_id": "afe8eb6e-990a-4496-8b36-09eea3b1a6d1"
}