Pipeline run
6c3ff8eb-9caf-42ad-8f09-fc97cac0a907
Client output enrichment
v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA descriptionvocab breakdown (legacy)
Signals
Post-classification
1 POST /skills/extract-from-jd
2 POST /skills/extract-details
3 POST /skills/final-role-output
Backend Developer
CASE Dslug: backend-engineer · id: 1 · source: db
LLM2 picked backend-engineer (confidence 0.79)
Resolution:
in_db
— role exists in library; skill↔dim and role↔dim links saved when applicable.
Job description
Client- Episoden Website : https://episoden.com/ Responsibilities:• Configuring Episoden Servers and Building a Development Environments • Manage substitute data and develop various service APIs[Introduction of the company]• Episoden (Episoden.com) is a video English conversation service used in more than 137 countries around the world. If you access Episoden, you can actually talk to people all over the world in two minutes, face-to-face, and talk in English. • In June 2021, the 1.0 beta version was opened, and in June 2022, the Episoden 2.0 service was opened, recording rapid growth of more than 1700% in the last 10 months. • Since the release of Episoden 2.0, users have been growing very rapidly around the world at the same time, so we need a great back-end developer. • The existing Episoden team is a talented team composed of key members from Seoul National University and Yonsei University who have experienced two M&As by creating good opportunities through serial startups over the past six years. • In July 2022, Primer Sazze Partners, an American venture capital, attracted investment and prepared to build a good development team based on this. • In response, we have hired a new Chief Technology Officer (CTO) who was the head of Samsung Electronics’ development team. • We look forward to backend developers who will work together to create a great service. Experience- 3+ years(excluding internship) Role- full time permanent Skills - Janus+Nodejs/Janus+java/Janus+kotlin Budget : 30 LPA
Skills from this JD
Each row merges API 1 extraction, API 2 library match / v3 orchestration (dimensions + locked dims), and API 3 persistence tags.
Aliases — catalog
- API (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Application Programming Interface
- Confidence
- 0.93
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: APIs are a core requirement in most software engineering JDs and underpin common integrations across cloud, mobile, and web stacks; major vendors like AWS, Stripe, and Google Cloud center products on API-first usage.
Skill profile (library / DB)
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 2
- Sub-category id
- 1174
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
API Integration and Data Fetching Catalog dimension db id 127
Library dimension (catalog)
Roles linked in library: Angular Frontend Developer, Frontend Developer, Fullstack Developer, Fullstack Developer, React Frontend Developer, Svelte Frontend Developer, Vue Frontend Developer, Web Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
API Integration and Data Fetching
api-integration-and-data-fetching
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
All API 3 persistence rows
Same grid as the skill-extractor “Persistence items” table: one row per (skill × dimension) work item.
| Skill | Tag | Dimension | Skill↔dim | Role↔dim | Outcome | Notes |
|---|---|---|---|---|---|---|
| API | in_db |
API Integration and Data Fetching
api-integration-and-data-fetching
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Library artifacts (this run)
nano JD Parser — gpt-4.1-nano click to toggle
Show raw JSON
{
"JD_type": "pass",
"about_company": {
"source_marker": {
"first_5_words": "Episoden (Episoden.com) is a",
"last_5_words": "together to create a great service."
},
"text": "Episoden (Episoden.com) is a video English conversation service used in more than 137 countries around the world. If you access Episoden, you can actually talk to people all over the world in two minutes, face-to-face, and talk in English.\n\nIn June 2021, the 1.0 beta version was opened, and in June 2022, the Episoden 2.0 service was opened, recording rapid growth of more than 1700% in the last 10 months.\n\nSince the release of Episoden 2.0, users have been growing very rapidly around the world at the same time, so we need a great back-end developer.\n\nThe existing Episoden team is a talented team composed of key members from Seoul National University and Yonsei University who have experienced two M\u0026As by creating good opportunities through serial startups over the past six years.\n\nIn July 2022, Primer Sazze Partners, an American venture capital, attracted investment and prepared to build a good development team based on this.\n\nIn response, we have hired a new Chief Technology Officer (CTO) who was the head of Samsung Electronics\u2019 development team.\n\nWe look forward to backend developers who will work together to create a great service.",
"word_count": 264
},
"certifications": [],
"company_name": "Episoden",
"ctc": {
"currency": "INR",
"max": 30,
"min": 30,
"period": "annual",
"raw": "30 LPA"
},
"domain": {
"primary": {
"aliases": [],
"domain": "Other"
},
"secondary": null
},
"education": [],
"experience": {
"max": null,
"min": 3,
"raw": "3+ years(excluding internship)"
},
"job_locations": [],
"role": "back-end developer",
"role_aliases": [
"Backend Developer",
"Software Engineer",
"Full Stack Developer"
],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 2,
"heading": "Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Configuring Episoden Servers and",
"last_5_words": "various service APIs"
},
"text": "\u2022 Configuring Episoden Servers and Building a Development Environments\n\n\u2022 Manage substitute data and develop various service APIs",
"word_count": 18
}
],
"urls": [
{
"type": "website",
"url": "https://episoden.com/"
}
]
}
API 1 — extract-from-jd click to toggle
{
"final_skills": [
{
"is_primary": true,
"skill_name": "API"
}
],
"jd_role": {
"display_name": "back-end developer",
"rationale": null,
"role_aliases": [
"Backend Developer",
"Software Engineer",
"Full Stack Developer"
],
"role_archetype": "Engineering",
"slug": ""
},
"nano_parsed": {
"JD_type": "pass",
"about_company": {
"source_marker": {
"first_5_words": "Episoden (Episoden.com) is a",
"last_5_words": "together to create a great service."
},
"text": "Episoden (Episoden.com) is a video English conversation service used in more than 137 countries around the world. If you access Episoden, you can actually talk to people all over the world in two minutes, face-to-face, and talk in English.\n\nIn June 2021, the 1.0 beta version was opened, and in June 2022, the Episoden 2.0 service was opened, recording rapid growth of more than 1700% in the last 10 months.\n\nSince the release of Episoden 2.0, users have been growing very rapidly around the world at the same time, so we need a great back-end developer.\n\nThe existing Episoden team is a talented team composed of key members from Seoul National University and Yonsei University who have experienced two M\u0026As by creating good opportunities through serial startups over the past six years.\n\nIn July 2022, Primer Sazze Partners, an American venture capital, attracted investment and prepared to build a good development team based on this.\n\nIn response, we have hired a new Chief Technology Officer (CTO) who was the head of Samsung Electronics\u2019 development team.\n\nWe look forward to backend developers who will work together to create a great service.",
"word_count": 264
},
"certifications": [],
"company_name": "Episoden",
"ctc": {
"currency": "INR",
"max": 30,
"min": 30,
"period": "annual",
"raw": "30 LPA"
},
"domain": {
"primary": {
"aliases": [],
"domain": "Other"
},
"secondary": null
},
"education": [],
"experience": {
"max": null,
"min": 3,
"raw": "3+ years(excluding internship)"
},
"job_locations": [],
"role": "back-end developer",
"role_aliases": [
"Backend Developer",
"Software Engineer",
"Full Stack Developer"
],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 2,
"heading": "Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Configuring Episoden Servers and",
"last_5_words": "various service APIs"
},
"text": "\u2022 Configuring Episoden Servers and Building a Development Environments\n\n\u2022 Manage substitute data and develop various service APIs",
"word_count": 18
}
],
"urls": [
{
"type": "website",
"url": "https://episoden.com/"
}
]
},
"rejected": false,
"rejection_reason": null,
"run_id": "6c3ff8eb-9caf-42ad-8f09-fc97cac0a907",
"stage3_signals": {
"alias_found": true,
"alias_match_roles": [
{
"display_name": "Fullstack Developer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 15,
"score": 1.0,
"slug": "full-stack-engineer",
"total_count": null
},
{
"display_name": "Backend Developer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 1,
"score": 1.0,
"slug": "backend-engineer",
"total_count": null
},
{
"display_name": "Backend Developer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 446,
"score": 1.0,
"slug": "backend-developer",
"total_count": null
}
],
"kra_match_roles": [
{
"display_name": "Backend Developer",
"kra_matches": [
{
"kra_text": "Designs and maintains RESTful and GraphQL API interfaces with proper authentication, versioning, rate limiting, and documentation for frontend and third-party consumers.",
"sentence": "Manage substitute data and develop various service APIs",
"similarity": 0.4693
},
{
"kra_text": "Configures Docker containers, deployment descriptors, environment variables, and CI/CD pipeline stages for backend service releases.",
"sentence": "Configuring Episoden Servers and Building a Development Environments",
"similarity": 0.4105
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 1,
"score": 0.4399,
"slug": "backend-engineer",
"total_count": null
},
{
"display_name": "Python Backend Developer",
"kra_matches": [
{
"kra_text": "Maintain data access and persistence",
"sentence": "Manage substitute data and develop various service APIs",
"similarity": 0.452
},
{
"kra_text": "Troubleshoot server-side defects",
"sentence": "Configuring Episoden Servers and Building a Development Environments",
"similarity": 0.416
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 80,
"score": 0.434,
"slug": "python-backend-developer",
"total_count": null
},
{
"display_name": "Svelte Frontend Developer",
"kra_matches": [
{
"kra_text": "backend data integration",
"sentence": "Manage substitute data and develop various service APIs",
"similarity": 0.4804
},
{
"kra_text": "frontend debugging and fixes",
"sentence": "Configuring Episoden Servers and Building a Development Environments",
"similarity": 0.3571
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 92,
"score": 0.4188,
"slug": "svelte-frontend-developer",
"total_count": null
},
{
"display_name": "Java Backend Developer",
"kra_matches": [
{
"kra_text": "service endpoint development",
"sentence": "Manage substitute data and develop various service APIs",
"similarity": 0.4285
},
{
"kra_text": "service endpoint development",
"sentence": "Configuring Episoden Servers and Building a Development Environments",
"similarity": 0.4013
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 79,
"score": 0.4149,
"slug": "java-backend-developer",
"total_count": null
},
{
"display_name": "Scala Backend Developer",
"kra_matches": [
{
"kra_text": "service endpoint development",
"sentence": "Manage substitute data and develop various service APIs",
"similarity": 0.4285
},
{
"kra_text": "service endpoint development",
"sentence": "Configuring Episoden Servers and Building a Development Environments",
"similarity": 0.4013
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 87,
"score": 0.4149,
"slug": "scala-backend-developer",
"total_count": null
}
],
"skill_match_roles": [
{
"display_name": "Fullstack Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"API"
],
"role_id": 15,
"score": 1.0,
"slug": "full-stack-engineer",
"total_count": 1
},
{
"display_name": "Frontend Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"API"
],
"role_id": 7,
"score": 1.0,
"slug": "frontend-engineer",
"total_count": 1
},
{
"display_name": "Web Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"API"
],
"role_id": 25,
"score": 1.0,
"slug": "web-developer",
"total_count": 1
},
{
"display_name": "React Frontend Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"API"
],
"role_id": 89,
"score": 1.0,
"slug": "react-frontend-developer",
"total_count": 1
},
{
"display_name": "Angular Frontend Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"API"
],
"role_id": 90,
"score": 1.0,
"slug": "angular-frontend-developer",
"total_count": 1
}
]
},
"stage4_decision": {
"alias_collision_detected": true,
"case": "D",
"chosen_role": {
"display_name": "Backend Developer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 1,
"score": 1.0,
"slug": "backend-engineer",
"total_count": null
},
"confidence": 0.79,
"is_new_role": false,
"llm2_fired": true,
"llm2_reasoning": "The JD\u2019s focus on server configuration, development environments, data management, and service APIs closely aligns with backend-engineer\u2019s core KRAs in server-side request flow and API implementation.",
"matched_dimensions": [],
"matched_kras": [],
"matched_skills": [],
"new_role_display_name": null,
"new_role_slug": null,
"queued": false,
"reasoning": "LLM2 picked backend-engineer (confidence 0.79)",
"sub_role": null
},
"stage5_updates": {
"centroid_n_after": 1483,
"centroid_updated": true,
"collision_log_id": 1130,
"new_kra_attached": null,
"new_skills_attached": [],
"queue_entry_id": null,
"v3_pipeline_triggered": false,
"v3_role_slug": null,
"v3_run_id": null
}
}
API 2 — extract-details
{
"alias_matches": [
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 2514,
"existing_alias_text": "API",
"input_term": "API",
"matched_canonical": {
"category_id": 2,
"display_name": "API",
"id": 1568,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "api",
"sub_category_id": 1174,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
}
],
"candidate_roles": [
{
"display_name": "Angular Frontend Developer",
"id": 90,
"rationale": null,
"role_archetype": "Engineering",
"slug": "angular-frontend-developer",
"source": "db"
},
{
"display_name": "Frontend Developer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "React Frontend Developer",
"id": 89,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-frontend-developer",
"source": "db"
},
{
"display_name": "Svelte Frontend Developer",
"id": 92,
"rationale": null,
"role_archetype": "Engineering",
"slug": "svelte-frontend-developer",
"source": "db"
},
{
"display_name": "Vue Frontend Developer",
"id": 91,
"rationale": null,
"role_archetype": "Engineering",
"slug": "vue-frontend-developer",
"source": "db"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
}
],
"chosen_role": {
"display_name": "Backend Developer",
"id": 1,
"rationale": "LLM2 picked backend-engineer (confidence 0.79)",
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Data Fetching",
"id": 127,
"rationale": "Client-side integration with backend endpoints and third-party services, including request shaping, response handling, and synchronization with UI state. This is central to frontend work because most screens depend on remote data.",
"slug": "api-integration-and-data-fetching",
"source": "db"
},
"input_skill": "API",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Angular Frontend Developer",
"id": 90,
"rationale": null,
"role_archetype": "Engineering",
"slug": "angular-frontend-developer",
"source": "db"
},
{
"display_name": "Frontend Developer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "React Frontend Developer",
"id": 89,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-frontend-developer",
"source": "db"
},
{
"display_name": "Svelte Frontend Developer",
"id": 92,
"rationale": null,
"role_archetype": "Engineering",
"slug": "svelte-frontend-developer",
"source": "db"
},
{
"display_name": "Vue Frontend Developer",
"id": 91,
"rationale": null,
"role_archetype": "Engineering",
"slug": "vue-frontend-developer",
"source": "db"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
}
]
}
],
"input_final_skills": [
"API"
],
"input_llm_skills": [
"API"
],
"new_aliases_persisted": 0,
"run_id": "6c3ff8eb-9caf-42ad-8f09-fc97cac0a907",
"skills_detail": [
{
"aliases_in_db": [
{
"alias_text": "API",
"alias_type": "CANONICAL",
"id": 2514,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 2,
"display_name": "API",
"id": 1568,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "api",
"sub_category_id": 1174,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Data Fetching",
"id": 127,
"rationale": "Client-side integration with backend endpoints and third-party services, including request shaping, response handling, and synchronization with UI state. This is central to frontend work because most screens depend on remote data.",
"slug": "api-integration-and-data-fetching",
"source": "db"
},
"input_skill": "API",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Angular Frontend Developer",
"id": 90,
"rationale": null,
"role_archetype": "Engineering",
"slug": "angular-frontend-developer",
"source": "db"
},
{
"display_name": "Frontend Developer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "React Frontend Developer",
"id": 89,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-frontend-developer",
"source": "db"
},
{
"display_name": "Svelte Frontend Developer",
"id": 92,
"rationale": null,
"role_archetype": "Engineering",
"slug": "svelte-frontend-developer",
"source": "db"
},
{
"display_name": "Vue Frontend Developer",
"id": 91,
"rationale": null,
"role_archetype": "Engineering",
"slug": "vue-frontend-developer",
"source": "db"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
}
]
}
],
"input_skill": "API",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
}
],
"unmatched_skills": []
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "Backend Developer",
"id": 1,
"rationale": "LLM2 picked backend-engineer (confidence 0.79)",
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
"chosen_role_resolution": "in_db",
"final_input_skills": [
{
"skill": "API",
"tag": "in_db"
}
],
"llm_cost_api1_usd": null,
"llm_cost_api2_usd": null,
"llm_cost_api3_usd": null,
"llm_cost_total_usd": null,
"persistence": {
"items": [
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Data Fetching",
"id": 127,
"rationale": "Client-side integration with backend endpoints and third-party services, including request shaping, response handling, and synchronization with UI state. This is central to frontend work because most screens depend on remote data.",
"slug": "api-integration-and-data-fetching",
"source": "db"
},
"dimension_id": 127,
"input_skill": "API",
"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": [
{
"display_name": "Angular Frontend Developer",
"id": 90,
"rationale": null,
"role_archetype": "Engineering",
"slug": "angular-frontend-developer",
"source": "db"
},
{
"display_name": "Frontend Developer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "React Frontend Developer",
"id": 89,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-frontend-developer",
"source": "db"
},
{
"display_name": "Svelte Frontend Developer",
"id": 92,
"rationale": null,
"role_archetype": "Engineering",
"slug": "svelte-frontend-developer",
"source": "db"
},
{
"display_name": "Vue Frontend Developer",
"id": 91,
"rationale": null,
"role_archetype": "Engineering",
"slug": "vue-frontend-developer",
"source": "db"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 1568,
"skill_tag": "in_db",
"skipped_reason": null
}
],
"new_skills_created": 0,
"role_dimension_saved": 0,
"skill_dimension_saved": 0,
"skipped": 0
},
"planner_output": null,
"run_id": "6c3ff8eb-9caf-42ad-8f09-fc97cac0a907"
}