Pipeline run
c6cf559d-8548-4524-b803-d16b84402271
Client output enrichment
v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA descriptionNature 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:
completed
Created: 2026-05-08T11:01:29.881910Z
Updated: 2026-05-08T11:03:29.509839Z
API 3 duration: 343 ms
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.
0
New skills
0
Skill↔dim saved
0
Role↔dim saved
0
Skipped
Job description
Company Description Guildstars is a comprehensive platform designed to accelerate professional growth through its unique three-pillar ecosystem: Campus, Academy, and Launchpad. Our offerings include rigorous career upskilling, personalized education consulting, and targeted career acceleration to prepare individuals for success in top-tier roles. We focus on helping ambitious individuals navigate their journeys by providing world-class mentorship, practical skills training, and exclusive opportunities. Guildstars is dedicated to empowering exceptional talent, ensuring they achieve their full potential with strategic support at every stage of their path. Role Description This is a full-time, remote role for a Software Engineer. The Software Engineer will be responsible for designing, developing, and maintaining software solutions, with a particular focus on back-end web development and programming. Day-to-day tasks include writing efficient and scalable code, collaborating with cross-functional teams, implementing object-oriented programming principles, and troubleshooting software issues. Additionally, the role involves contributing to the continuous improvement of software engineering best practices. Qualifications Solid knowledge of Computer Science principles and methodologies Experience in Back-End Web Development and Software Development Strong skills in Programming and Object-Oriented Programming (OOP) Familiarity with team collaboration tools and version control systems like Git Strong problem-solving abilities and attention to detail Bachelor’s degree in Computer Science, Engineering, or related field, or equivalent experience Preferred: Experience with cloud-based platforms, CI/CD pipelines, or familiarity with Agile methodology
history_view bundle (older API). Showing raw API payloads below.
Library artifacts (this run)
No artifact rows for this run.
API 1 — extract-from-jd click to toggle
{
"filtered_unknown_words": [
"Academy",
"Bachelor",
"CD",
"CI",
"Campus",
"Company",
"Computer",
"Day",
"Description",
"Development",
"End",
"Engineer",
"Engineering",
"Experience",
"Familiarity",
"Guildstars",
"Launchpad",
"Object",
"Preferred",
"Programming",
"Qualifications",
"Role",
"Science",
"Software",
"Web",
"abilities",
"acceleration",
"attention",
"career",
"class",
"cloud",
"code",
"collaboration",
"control",
"day",
"degree",
"designing",
"detail",
"developing",
"development",
"ecosystem",
"education",
"end",
"engineering",
"experience",
"familiarity",
"field",
"focus",
"growth",
"improvement",
"individuals",
"issues",
"journeys",
"knowledge",
"methodologies",
"methodology",
"object",
"offerings",
"opportunities",
"path",
"pillar",
"pipelines",
"platform",
"platforms",
"potential",
"practices",
"principles",
"problem",
"programming",
"role",
"skills",
"software",
"solutions",
"stage",
"success",
"support",
"systems",
"talent",
"tasks",
"team",
"teams",
"tier",
"time",
"tools",
"training",
"version",
"web",
"world"
],
"final_non_skills": [
"Academy",
"Bachelor",
"Campus",
"Company",
"Computer",
"Day",
"Description",
"Development",
"End",
"Engineer",
"Engineering",
"Experience",
"Familiarity",
"Guildstars",
"Launchpad",
"Object",
"Preferred",
"Programming",
"Qualifications",
"Role",
"Science",
"Software",
"Web",
"abilities",
"acceleration",
"attention",
"career",
"class",
"code",
"collaboration",
"control",
"degree",
"designing",
"detail",
"developing",
"ecosystem",
"education",
"field",
"focus",
"growth",
"improvement",
"individuals",
"issues",
"journeys",
"knowledge",
"methodologies",
"methodology",
"offerings",
"opportunities",
"path",
"pillar",
"potential",
"practices",
"principles",
"problem",
"skills",
"solutions",
"stage",
"success",
"support",
"systems",
"talent",
"tasks",
"team",
"teams",
"tier",
"time",
"tools",
"training",
"world"
],
"final_skills": [
"CD",
"CI",
"cloud",
"pipelines",
"platform",
"platforms",
"version"
],
"initial_skills": [],
"jd_role_hint": {
"display_name": "Software Engineer",
"rationale": "The excerpt repeatedly describes a Software Engineer responsible for designing, developing, and maintaining software solutions.",
"role_archetype": "Software engineering role focused on back-end web development and programming.",
"slug": "software-engineer"
},
"llm_non_skills": [
"Academy",
"Bachelor",
"Campus",
"Company",
"Computer",
"Day",
"Description",
"Development",
"End",
"Engineer",
"Engineering",
"Experience",
"Familiarity",
"Guildstars",
"Launchpad",
"Object",
"Preferred",
"Programming",
"Qualifications",
"Role",
"Science",
"Software",
"Web",
"abilities",
"acceleration",
"attention",
"career",
"class",
"code",
"collaboration",
"control",
"degree",
"designing",
"detail",
"developing",
"ecosystem",
"education",
"field",
"focus",
"growth",
"improvement",
"individuals",
"issues",
"journeys",
"knowledge",
"methodologies",
"methodology",
"offerings",
"opportunities",
"path",
"pillar",
"potential",
"practices",
"principles",
"problem",
"skills",
"solutions",
"stage",
"success",
"support",
"systems",
"talent",
"tasks",
"team",
"teams",
"tier",
"time",
"tools",
"training",
"world"
],
"llm_skills": [
"CD",
"CI",
"cloud",
"pipelines",
"platform",
"platforms",
"version"
],
"run_id": null,
"unknown_words": [
"Academy",
"Bachelor",
"CD",
"CI",
"Campus",
"Company",
"Computer",
"Day",
"Description",
"Development",
"End",
"Engineer",
"Engineering",
"Experience",
"Familiarity",
"Guildstars",
"Launchpad",
"Object",
"Preferred",
"Programming",
"Qualifications",
"Role",
"Science",
"Software",
"Web",
"abilities",
"acceleration",
"attention",
"career",
"class",
"cloud",
"code",
"collaboration",
"control",
"day",
"degree",
"designing",
"detail",
"developing",
"development",
"ecosystem",
"education",
"end",
"engineering",
"experience",
"familiarity",
"field",
"focus",
"growth",
"improvement",
"individuals",
"issues",
"journeys",
"knowledge",
"methodologies",
"methodology",
"object",
"offerings",
"opportunities",
"path",
"pillar",
"pipelines",
"platform",
"platforms",
"potential",
"practices",
"principles",
"problem",
"programming",
"role",
"skills",
"software",
"solutions",
"stage",
"success",
"support",
"systems",
"talent",
"tasks",
"team",
"teams",
"tier",
"time",
"tools",
"training",
"version",
"web",
"world"
]
}
API 2 — extract-details
{
"alias_matches": [],
"candidate_roles": [],
"chosen_role": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Continuous Delivery Practices",
"id": null,
"rationale": "Covers the practices and tooling used to automatically build, test, and promote software changes toward release. CD belongs here because it commonly refers to continuous delivery, the delivery pipeline discipline that moves code from commit to deployable artifacts.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CD",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Continuous Integration",
"id": null,
"rationale": "Practices for automatically building, testing, and validating code changes whenever they are merged or proposed. CI belongs here because it is the core automation layer that catches integration issues early and keeps the main branch healthy.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CI",
"llm_role": null,
"roles_from_db": []
}
],
"input_final_skills": [
"CD",
"CI",
"cloud",
"pipelines",
"platform",
"platforms",
"version"
],
"input_llm_skills": [
"CD",
"CI",
"cloud",
"pipelines",
"platform",
"platforms",
"version"
],
"new_aliases_persisted": 0,
"run_id": "c6cf559d-8548-4524-b803-d16b84402271",
"skills_detail": [
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Continuous Delivery Practices",
"id": null,
"rationale": "Covers the practices and tooling used to automatically build, test, and promote software changes toward release. CD belongs here because it commonly refers to continuous delivery, the delivery pipeline discipline that moves code from commit to deployable artifacts.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CD",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "CD",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Methodology",
"skill_nature": "METHODOLOGY",
"sub_category": "continuous_delivery",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"continuous_deployment",
"circular_dependency"
],
"reasoning": "\"CD\" is a common acronym for both continuous delivery and continuous deployment, and can also be read as circular dependency in technical contexts, so a JD mention could be misclassified."
},
"context_keywords": {
"context_keywords": [
"CI/CD",
"deployment pipeline",
"release automation",
"blue-green deployment",
"canary release",
"feature flags",
"rollback",
"staging environment",
"production deployment",
"build pipeline",
"artifact repository",
"versioning",
"infrastructure as code",
"GitOps",
"automated testing"
]
},
"maturity": {
"confidence": 0.93,
"maturity": "well_known",
"reasoning": "Continuous Delivery is a standard DevOps practice and appears in many job descriptions alongside CI/CD and cloud platforms; major vendors like AWS, Azure, and GitHub document it as a mainstream delivery pattern."
},
"skill_id": "cd",
"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 practices and tooling used to automatically build, test, and promote software changes toward release. CD belongs here because it commonly refers to continuous delivery, the delivery pipeline discipline that moves code from commit to deployable artifacts.",
"exemplar_skills": [
"CD",
"continuous delivery",
"delivery pipelines",
"release promotion",
"deployment automation"
],
"in_scope": "CD, continuous delivery, delivery pipelines, automated build and test, release promotion, deployment automation, release gates",
"name": "Continuous Delivery Practices",
"out_of_scope": "continuous integration test design, source control branching models, runtime service orchestration, infrastructure provisioning, manual QA execution",
"overlap_flags": [
{
"reason": "Delivery pipelines often include environment promotion steps, but that catalog dimension owns the environment lifecycle specifics.",
"with_dim_id": "environment-provisioning-and-promotion",
"with_dim_name": null,
"with_role": "DevOps Engineer"
},
{
"reason": "CD relies on build tools and executors, but this dimension focuses on the end-to-end delivery practice rather than the tooling itself.",
"with_dim_id": "build-and-execution-tooling",
"with_dim_name": null,
"with_role": "Automation Tester"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "CD",
"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": "cd"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"contract-tests",
"scorecards",
"defect-retest"
],
"requires": [],
"skill_id": "cd",
"suppress_on_match": []
},
"skill_id": "cd",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.93,
"name": "CD",
"reasoning": "CD here most naturally means Continuous Delivery, which is a way of working for releasing software, so by the Concept vs Methodology rule it is a Methodology.",
"skill_id": "cd",
"subtype": "continuous_delivery",
"type": "Methodology"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Continuous Integration",
"id": null,
"rationale": "Practices for automatically building, testing, and validating code changes whenever they are merged or proposed. CI belongs here because it is the core automation layer that catches integration issues early and keeps the main branch healthy.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CI",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "CI",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Methodology",
"skill_nature": "METHODOLOGY",
"sub_category": "continuous_integration_methodology",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"continuous_delivery",
"continuous_deployment"
],
"reasoning": "\"CI\" is a common abbreviation for continuous integration, but in JDs it can be conflated with nearby DevOps terms like continuous delivery or continuous deployment, especially when shorthand is used loosely."
},
"context_keywords": {
"context_keywords": [
"Jenkins",
"GitHub Actions",
"GitLab CI",
"CircleCI",
"Travis CI",
"build pipeline",
"automated testing",
"unit tests",
"integration tests",
"pipeline as code",
"build artifacts",
"merge request",
"pull request",
"deployment pipeline",
"artifact repository"
]
},
"maturity": {
"confidence": 0.96,
"maturity": "well_known",
"reasoning": "CI is a standard hiring-pipeline requirement in many software JDs, and major platforms like GitHub Actions, GitLab CI, and Jenkins show broad ecosystem adoption."
},
"skill_id": "ci",
"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 automatically building, testing, and validating code changes whenever they are merged or proposed. CI belongs here because it is the core automation layer that catches integration issues early and keeps the main branch healthy.",
"exemplar_skills": [
"CI",
"continuous integration",
"build validation",
"pull request checks",
"automated build pipelines",
"merge gating",
"GitHub Actions",
"Jenkins",
"GitLab CI"
],
"in_scope": "CI, continuous integration pipelines, automated build triggers, pull request validation, unit test runs, linting, static checks, merge gating, build status checks, GitHub Actions, Jenkins, GitLab CI, Azure Pipelines",
"name": "Continuous Integration",
"out_of_scope": "Continuous delivery and release promotion, deployment orchestration, test framework authoring, application runtime monitoring, source control branching strategy, infrastructure provisioning",
"overlap_flags": [
{
"reason": "CI often uses build tools and runners, but this dimension is about the integration workflow rather than the tooling itself.",
"with_dim_id": "build-and-execution-tooling",
"with_dim_name": null,
"with_role": "Automation Tester"
},
{
"reason": "CI commonly executes automated tests, but the test framework design belongs to the testing dimension.",
"with_dim_id": "testing-and-automation-frameworks",
"with_dim_name": null,
"with_role": "iOS Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "CI",
"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": "ci"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [],
"requires": [],
"skill_id": "ci",
"suppress_on_match": []
},
"skill_id": "ci",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.9,
"name": "CI",
"reasoning": "CI is fundamentally a way of working for integrating code frequently and validating it continuously, so it fits the Concept vs Methodology rule as a Methodology rather than a Tool or Framework.",
"skill_id": "ci",
"subtype": "continuous_integration_methodology",
"type": "Methodology"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "cloud",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "pipelines",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "platform",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "platforms",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "version",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"CD",
"CI"
]
}
API 3 — final-role-output
{
"chosen_role": null,
"final_input_skills": [
{
"skill": "CD",
"tag": "new"
},
{
"skill": "CI",
"tag": "new"
},
{
"skill": "cloud",
"tag": "new"
},
{
"skill": "pipelines",
"tag": "new"
},
{
"skill": "platform",
"tag": "new"
},
{
"skill": "platforms",
"tag": "new"
},
{
"skill": "version",
"tag": "new"
}
],
"persistence": {
"items": [],
"new_skills_created": 0,
"role_dimension_saved": 0,
"skill_dimension_saved": 0,
"skipped": 0
},
"planner_output": null,
"run_id": "c6cf559d-8548-4524-b803-d16b84402271"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.
Loading…