Pipeline run
32f0bb4d-8c26-4dd9-b13c-901b251a9bb3
Client output enrichment
v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA description
SPARSE JD
Nature of work
—
Tech stack maturity
Mainstream Modern
AI index (0 = no AI use, 5 = totally AI-dependent · v2.1)
0.00 / 5
· Title match
· Has AI skill
· AI skill (primary)
· AI skill (secondary)
· On AI team
· Builds AI products
vocab breakdown (legacy)
Assistants (×1):
—
Frameworks (×2):
—
Models / concepts (×3):
—
Evidence — skills matched in JD (0)
Skill cluster (0 dimension groups, role-scoped)
Status:
completed
Created: 2026-05-08T10:51:40.670113Z
Updated: 2026-05-08T10:53:27.203356Z
API 3 duration: 296 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",
"offerings",
"opportunities",
"path",
"pillar",
"pipelines",
"platform",
"platforms",
"potential",
"practices",
"principles",
"problem",
"skills",
"solutions",
"stage",
"success",
"support",
"systems",
"talent",
"tasks",
"team",
"teams",
"tier",
"time",
"tools",
"training",
"version",
"world"
],
"final_skills": [
"CD",
"CI",
"cloud",
"methodology"
],
"initial_skills": [],
"jd_role_hint": {
"display_name": "Software Engineer",
"rationale": "The excerpt centers on software engineering responsibilities, web development, programming, and collaboration, indicating a software engineer role.",
"role_archetype": "Software engineer focused on building and maintaining web-based software solutions.",
"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",
"offerings",
"opportunities",
"path",
"pillar",
"pipelines",
"platform",
"platforms",
"potential",
"practices",
"principles",
"problem",
"skills",
"solutions",
"stage",
"success",
"support",
"systems",
"talent",
"tasks",
"team",
"teams",
"tier",
"time",
"tools",
"training",
"version",
"world"
],
"llm_skills": [
"CD",
"CI",
"cloud",
"methodology"
],
"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 Pipelines",
"id": null,
"rationale": "Covers automated build, test, and release pipelines that move software from source control into environments and production. The skill CD fits here when it means continuous delivery in software engineering rather than blockchain contract deployment.",
"slug": "d_init_02",
"source": "llm"
},
"input_skill": "CD",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Continuous Integration Practices",
"id": null,
"rationale": "Covers the automation and workflow practices that run builds and tests whenever code changes are introduced. This skill belongs here because CI is the standard shorthand for integrating code frequently and validating it early through automated pipelines.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CI",
"llm_role": null,
"roles_from_db": []
}
],
"input_final_skills": [
"CD",
"CI",
"cloud",
"methodology"
],
"input_llm_skills": [
"CD",
"CI",
"cloud",
"methodology"
],
"new_aliases_persisted": 0,
"run_id": "32f0bb4d-8c26-4dd9-b13c-901b251a9bb3",
"skills_detail": [
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Continuous Delivery Pipelines",
"id": null,
"rationale": "Covers automated build, test, and release pipelines that move software from source control into environments and production. The skill CD fits here when it means continuous delivery in software engineering rather than blockchain contract deployment.",
"slug": "d_init_02",
"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_integration",
"cicd"
],
"reasoning": "\"CD\" is a common abbreviation for continuous delivery, but in JDs it can also be read as part of CI/CD or confused with continuous integration in release-engineering contexts."
},
"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 model."
},
"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 automated build, test, and release pipelines that move software from source control into environments and production. The skill CD fits here when it means continuous delivery in software engineering rather than blockchain contract deployment.",
"exemplar_skills": [
"CD",
"continuous delivery",
"release pipeline",
"deployment automation",
"rollback automation"
],
"in_scope": "CD, continuous delivery, release pipelines, deployment automation, build promotion, gated releases, rollback automation, environment promotion",
"name": "Continuous Delivery Pipelines",
"out_of_scope": "Smart contract deployment and upgrade mechanics, source code compilation details, infrastructure provisioning, runtime observability, manual QA test execution",
"overlap_flags": [
{
"reason": "Delivery pipelines frequently coordinate environment promotion, but this dimension focuses on the pipeline mechanics rather than environment setup.",
"with_dim_id": "environment-provisioning-and-promotion",
"with_dim_name": null,
"with_role": "DevOps Engineer"
}
],
"tentative_id": "d_init_02"
}
],
"merge_log": [
{
"a_dim_id": "d_init_01",
"a_name": "Contract Deployment and Upgrades",
"a_role": "__skill_focal__",
"b_dim_id": "contract-deployment-and-upgrades",
"b_name": "Contract Deployment and Upgrades",
"b_role": "Blockchain Developer",
"into": "d_merge_01",
"into_name": "Smart Contract Deployment, Migration, and Upgrade Management",
"merged_from": [
"d_init_01",
"contract-deployment-and-upgrades"
],
"pair_kind": "cross_role",
"reasoning": "Both dims describe the same blockchain contract lifecycle cluster. A covers deploying smart contracts, migration steps, upgrade paths, and safe rollout practices; its exemplars include smart contract deployment, contract migration, upgradeable contracts, and proxy patterns. B says deployment strategies, migration planning, and upgrade mechanisms for on-chain code, which is the same skill set. No distinct subcluster appears, so MERGE.",
"similarity": 0.7648561413853886
}
],
"placed": {
"name": "CD",
"placement_confidence": 0.92,
"primary_dimension": "d_init_02",
"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": [],
"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 continuously, 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 Practices",
"id": null,
"rationale": "Covers the automation and workflow practices that run builds and tests whenever code changes are introduced. This skill belongs here because CI is the standard shorthand for integrating code frequently and validating it early through automated pipelines.",
"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",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"continuous_improvement",
"ci_cd"
],
"reasoning": "\"CI\" is a common acronym for continuous integration, but in JDs it can also mean continuous improvement or be used as shorthand within CI/CD. A parser could reasonably misread the intended skill."
},
"context_keywords": {
"context_keywords": [
"Jenkins",
"GitHub Actions",
"GitLab CI",
"CircleCI",
"Travis CI",
"build pipeline",
"automated testing",
"unit tests",
"integration tests",
"artifact",
"pipeline as code",
"YAML",
"merge request",
"pull request",
"build status"
]
},
"maturity": {
"confidence": 0.97,
"maturity": "well_known",
"reasoning": "CI is a hiring-pipeline staple: job descriptions for software engineers commonly list Jenkins, GitHub Actions, GitLab CI, or Azure DevOps pipelines, and major vendors actively support it as standard practice."
},
"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": "Covers the automation and workflow practices that run builds and tests whenever code changes are introduced. This skill belongs here because CI is the standard shorthand for integrating code frequently and validating it early through automated pipelines.",
"exemplar_skills": [
"CI",
"continuous integration",
"automated build pipelines",
"commit-triggered validation",
"pipeline status checks"
],
"in_scope": "CI, continuous integration, automated builds, commit-triggered pipelines, merge request validation, unit test execution in pipeline, linting in pipeline, build status checks",
"name": "Continuous Integration Practices",
"out_of_scope": "Continuous delivery/release promotion, deployment orchestration, runtime operations, manual test case design, source control branching strategy",
"overlap_flags": [
{
"reason": "CI commonly uses build tools and runners, but this dimension is about the integration workflow rather than the tools themselves.",
"with_dim_id": "build-and-execution-tooling",
"with_dim_name": null,
"with_role": "Automation Tester"
},
{
"reason": "CI often executes automated tests, but the test framework dimension owns the test design and framework mechanics.",
"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": [
"junit"
],
"requires": [],
"skill_id": "ci",
"suppress_on_match": []
},
"skill_id": "ci",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.93,
"name": "CI",
"reasoning": "CI is fundamentally a way of working for integrating code frequently and validating changes continuously, so by the Concept vs Methodology rule it is a Methodology rather than a tool or platform.",
"skill_id": "ci",
"subtype": "continuous_integration",
"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": "methodology",
"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": "methodology",
"tag": "new"
}
],
"persistence": {
"items": [],
"new_skills_created": 0,
"role_dimension_saved": 0,
"skill_dimension_saved": 0,
"skipped": 0
},
"planner_output": null,
"run_id": "32f0bb4d-8c26-4dd9-b13c-901b251a9bb3"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.
Loading…