Pipeline run
3c93ea27-c08f-40bb-b029-8bec0c05ceab
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 Engineer
CASE Eslug: backend-engineer · id: 1 · source: db
The primary skills of Java, Spring Boot, and Microservices align closely with the responsibilities of a Backend Engineer.
Resolution:
in_db
— role exists in library; skill↔dim and role↔dim links saved when applicable.
Job description
About the job The Applications Development Programmer Analyst is an intermediate level position responsible for participation in the establishment and implementation of new or revised application systems and programs in coordination with the Technology team. The overall objective of this role is to contribute to applications systems analysis and programming activities. Responsibilities: Utilize knowledge of applications development procedures and concepts, and basic knowledge of other technical areas to identify and define necessary system enhancements Identify and analyze issues, make recommendations, and implement solutions Utilize knowledge of business processes, system processes, and industry standards to solve complex issues Analyze information and make evaluative judgements to recommend solutions and improvements Conduct testing and debugging, utilize script tools, and write basic code for design specifications Assess applicability of similar experiences and evaluate options under circumstances not covered by procedures Develop working knowledge of Citi’s information systems, procedures, standards, client server application development, network operations, database administration, systems administration, data center operations, and PC-based applications Appropriately assess risk when business decisions are made, demonstrating particular consideration for the firm's reputation and safeguarding Citigroup, its clients and assets, by driving compliance with applicable laws, rules and regulations, adhering to Policy, applying sound ethical judgment regarding personal behavior, conduct and business practices, and escalating, managing and reporting control issues with transparency. Qualifications: 2+ years of relevant experience Experience in programming/debugging used in business applications Working knowledge of industry practice and standards Comprehensive knowledge of specific business area for application development Working knowledge of Java Springboot Microservices. Knowledge of Angular/ UI development will be advantage but not mandatory. Consistently demonstrates clear and concise written and verbal communication Education: Bachelor’s degree/University degree or equivalent experience This job description provides a high-level review of the types of work performed. Other job-related duties may be assigned as required. ------------------------------------------------------ Job Family Group: Technology ------------------------------------------------------ Job Family: Applications Development ------------------------------------------------------ Time Type: Full time ------------------------------------------------------ Most Relevant Skills Please see the requirements listed above. ------------------------------------------------------ Other Relevant Skills For complementary skills, please see above and/or contact the recruiter.
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
- Java (CANONICAL) primary
- JDK (VERSION)
- JDK 10 (VERSION)
- JDK 11 (VERSION)
- JDK 12 (VERSION)
- JDK 13 (VERSION)
- JDK 14 (VERSION)
- JDK 15 (VERSION)
- JDK 16 (VERSION)
- JDK 17 (VERSION)
- JDK 18 (VERSION)
- JDK 19 (VERSION)
- JDK 20 (VERSION)
- JDK 21 (VERSION)
- JDK 5 (VERSION)
- JDK 6 (VERSION)
- JDK 7 (VERSION)
- JDK 8 (VERSION)
- JDK 9 (VERSION)
- Java 1.0 (VERSION)
- Java 1.1 (VERSION)
- Java 1.2 (VERSION)
- Java 1.3 (VERSION)
- Java 1.4 (VERSION)
- Java 1.5 (VERSION)
- Java 1.6 (VERSION)
- Java 1.7 (VERSION)
- Java 1.8 (VERSION)
- Java 10 (VERSION)
- Java 11 (VERSION)
- Java 12 (VERSION)
- Java 13 (VERSION)
- Java 14 (VERSION)
- Java 15 (VERSION)
- Java 16 (VERSION)
- Java 17 (VERSION)
- Java 18 (VERSION)
- Java 19 (VERSION)
- Java 20 (VERSION)
- Java 21 (VERSION)
- Java 5 (VERSION)
- Java 6 (VERSION)
- Java 7 (VERSION)
- Java 8 (VERSION)
- Java 9 (VERSION)
- Java11 (VERSION)
- Java17 (VERSION)
- Java21 (VERSION)
- Java8 (VERSION)
- OpenJDK 11 (VERSION)
- OpenJDK 17 (VERSION)
- OpenJDK 21 (VERSION)
- OpenJDK 8 (VERSION)
- java 11 (VERSION)
- java 17 (VERSION)
- java 21 (VERSION)
- java 4 (VERSION)
- java 5 (VERSION)
- java 6 (VERSION)
- java 7 (VERSION)
- java 8 (VERSION)
- java lts (VERSION)
- java-11 (VERSION)
- java-17 (VERSION)
- java-21 (VERSION)
- java-4 (VERSION)
- java-5 (VERSION)
- java-6 (VERSION)
- java-7 (VERSION)
- java-8 (VERSION)
- java11 (VERSION)
- java17 (VERSION)
- java21 (VERSION)
- java4 (VERSION)
- java5 (VERSION)
- java6 (VERSION)
- java7 (VERSION)
- java8 (VERSION)
- jdk 11 (VERSION)
- jdk 17 (VERSION)
- jdk 21 (VERSION)
- jdk 4 (VERSION)
- jdk 5 (VERSION)
- jdk 6 (VERSION)
- jdk 7 (VERSION)
- jdk 8 (VERSION)
- jdk11 (VERSION)
- jdk17 (VERSION)
- jdk21 (VERSION)
- jdk4 (VERSION)
- jdk5 (VERSION)
- jdk6 (VERSION)
- jdk7 (VERSION)
- jdk8 (VERSION)
- jvm21 (VERSION)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Language
- Sub-category
- Programming Language
- Vendor
- Oracle
- License
- other_open
- Year introduced
- 1995
- Confidence
- 0.99
- Version strategy
- SEPARATE_ENTITY
- Version tag
- 21
Maturity reasoning: Java is a hiring-pipeline staple with very high JD volume across enterprise backend, Android, and cloud roles; it remains widely supported by major vendors and frameworks like Spring.
Skill profile (library / DB)
- Skill nature
- LANGUAGE
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 6
- Sub-category id
- 96
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Kotlin and Java Catalog dimension db id 161
Library dimension (catalog)
Roles linked in library: Android Engineer
-
Programming Languages Catalog dimension db id 1
Library dimension (catalog)
Roles linked in library: Backend Engineer
-
Programming Languages for Data Work Catalog dimension db id 21
Library dimension (catalog)
Roles linked in library: Data Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Kotlin and Java
kotlin-and-java
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Programming Languages
programming-languages
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
|
Programming Languages for Data Work
programming-languages-for-data-work
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- Spring Boot (CANONICAL) primary
- SB2 (VERSION)
- SB3 (VERSION)
- Spring Boot 2 (VERSION)
- Spring Boot 2.x (VERSION)
- Spring Boot 3 (VERSION)
- Spring Boot 3.x (VERSION)
- boot2 (VERSION)
- boot3 (VERSION)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Framework
- Sub-category
- Backend Framework
- Vendor
- Pivotal Software
- License
- apache_2
- Year introduced
- 2014
- Confidence
- 0.99
- Version strategy
- SEPARATE_ENTITY
- Version tag
- 3.x
Maturity reasoning: Spring Boot appears in a large volume of backend Java job descriptions and is the default Spring stack for new services; Spring’s own docs and ecosystem center on Boot for production apps.
Skill profile (library / DB)
- Skill nature
- FRAMEWORK
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 5
- Sub-category id
- 34
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Web Application Frameworks Catalog dimension db id 2
Library dimension (catalog)
Roles linked in library: Backend Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Web Application Frameworks
web-application-frameworks
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Aliases — catalog
- microservices (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Architecture
- Sub-category
- Distributed System Architecture
- Confidence
- 0.99
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Microservices is a common architecture in job descriptions across backend/cloud roles, and major vendors like AWS, Google Cloud, and Kubernetes ecosystems provide first-class support and reference patterns.
Skill profile (library / DB)
- Skill nature
- PATTERN
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 1
- Sub-category id
- 1
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Microservices and Distributed Systems Catalog dimension db id 9
Library dimension (catalog)
Roles linked in library: Backend Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Microservices and Distributed Systems
microservices-and-distributed-systems
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Aliases — catalog
- Angular (CANONICAL) primary
- Angular 1 (VERSION)
- Angular 1.x (VERSION)
- Angular 10 (VERSION)
- Angular 11 (VERSION)
- Angular 12 (VERSION)
- Angular 13 (VERSION)
- Angular 14 (VERSION)
- Angular 15 (VERSION)
- Angular 16 (VERSION)
- Angular 17 (VERSION)
- Angular 2 (VERSION)
- Angular 2+ (VERSION)
- Angular 4 (VERSION)
- Angular 5 (VERSION)
- Angular 6 (VERSION)
- Angular 7 (VERSION)
- Angular 8 (VERSION)
- Angular 9 (VERSION)
- AngularJS (VERSION)
- angular 1 (VERSION)
- angular 1.x (VERSION)
- angular 10 (VERSION)
- angular 11 (VERSION)
- angular 12 (VERSION)
- angular 13 (VERSION)
- angular 14 (VERSION)
- angular 15 (VERSION)
- angular 16 (VERSION)
- angular 17 (VERSION)
- angular 18 (VERSION)
- angular 19 (VERSION)
- angular 2 (VERSION)
- angular 2+ (VERSION)
- angular 2.x (VERSION)
- angular 3 (VERSION)
- angular 4 (VERSION)
- angular 5 (VERSION)
- angular 6 (VERSION)
- angular 7 (VERSION)
- angular 8 (VERSION)
- angular 9 (VERSION)
- angular17 (VERSION)
- angular2 (VERSION)
- angularjs (VERSION)
- angularjs 1.x (VERSION)
- ng (VERSION)
- ng1 (VERSION)
- ng2 (VERSION)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Framework
- Sub-category
- Frontend Framework
- Vendor
- License
- mit
- Year introduced
- 2010
- Confidence
- 0.98
- Version strategy
- SEPARATE_ENTITY
- Version tag
- 2+
Maturity reasoning: Angular remains widely listed in frontend job descriptions and enterprise stacks; Google continues maintaining Angular, and it is a common hiring-pipeline skill alongside React/Vue rather than a sunset technology.
Skill profile (library / DB)
- Skill nature
- FRAMEWORK
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 5
- Sub-category id
- 341
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
UI Frameworks and Rendering Catalog dimension db id 115
Library dimension (catalog)
Roles linked in library: Frontend Engineer, Hybrid Mobile Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
UI Frameworks and Rendering
ui-frameworks-and-rendering
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Skill enrichment (orchestrator / LLM)
UI development is a core hiring-pipeline staple across frontend and product roles; job postings routinely list React, Angular, or Vue UI work, showing broad market demand rather than a niche toolset.
(0.90)
“UI Development” is a broad, distinct domain term and is unlikely to be confused with another specific catalog skill.
Not versioned
Domain ·user_interface_development confidence 0.90
UI Development is best treated as a domain of practice focused on building user interfaces, not a specific language, framework, or methodology.
- Category
- Domain
- Sub-category
- user_interface_development
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Version strategy
- NOT_APPLICABLE
Dimensions (API 2 worklist)
-
React Frontend Development Catalog dimension db id 96
Library dimension (catalog)
-
Frontend Architecture and Code Organization Catalog dimension db id 128
Library dimension (catalog)
Roles linked in library: Frontend Engineer
-
Frontend Architecture and Code Organization Catalog dimension db id 128
Library dimension (catalog)
Roles linked in library: Frontend Engineer
Locked dimensions (v3 placement)
-
User Interface Development
Pipeline tentative id
Building interactive application screens, layouts, and component behavior for end users. This fits UI Development because it covers the implementation of visual structure, interaction patterns, and reusable interface elements across client apps.
-
Frontend Architecture and Code Organization
Reuses catalog slug
Structural patterns for organizing large client applications into maintainable modules, layers, and feature boundaries. UI Development can touch this area when building screens within a broader frontend architecture, but the core focus is on code structure rather than the UI itself.
-
Frontend Architecture and Code Organization
Reuses catalog slug
Structural patterns for organizing large client applications into maintainable modules, layers, and feature boundaries. Senior frontend engineers often own these decisions to keep UI code scalable over time.
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
React Frontend Development
d_init_01
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Frontend Architecture and Code Organization
frontend-architecture-and-code-organization
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Skill enrichment (orchestrator / LLM)
Core architecture pattern in most software JDs and system design interviews; widely used across web, mobile, and enterprise apps, with no successor replacing it.
(0.95)
“Client-Server Architecture” is a specific architecture pattern; unlikely to be confused with other distinct architecture skills in typical JDs.
Not versioned
Architecture ·client_server_architecture confidence 0.98
This is an Architecture because Client-Server describes a system-shape pattern for how components are organized and interact, not a concept or methodology.
- Category
- Architecture
- Sub-category
- client_server_architecture
- Skill nature
- PATTERN
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Version strategy
- NOT_APPLICABLE
Dimensions (API 2 worklist)
-
React Frontend Development Catalog dimension db id 96
Library dimension (catalog)
Locked dimensions (v3 placement)
-
Client-Server Architecture
Pipeline tentative id
Design patterns and structural decisions for splitting responsibilities between client applications and backend servers. This skill fits here because it covers request/response boundaries, API contracts, session flow, and how distributed application tiers interact.
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
React Frontend Development
d_init_01
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Skill enrichment (orchestrator / LLM)
Network Operations is a common hiring requirement in NOC/SRE/IT ops job descriptions, with many postings asking for monitoring, incident response, and troubleshooting of enterprise networks.
(0.90)
“Network Operations” is a clear domain term focused on operating and maintaining networks; it’s unlikely to be confused with another distinct catalog skill.
Not versioned
Domain ·network_operations confidence 0.95
Network Operations is a vertical/problem-space body of knowledge rather than a tool, framework, or methodology, so it fits the Domain type.
- Category
- Domain
- Sub-category
- network_operations
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Version strategy
- NOT_APPLICABLE
Dimensions (API 2 worklist)
-
React Frontend Development Catalog dimension db id 96
Library dimension (catalog)
Locked dimensions (v3 placement)
-
Network Operations
Pipeline tentative id
Operational practices for monitoring, maintaining, and troubleshooting networked systems and connectivity. This fits the target skill because it covers day-to-day network health, incident handling, and service availability work rather than application-level API coding.
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
React Frontend Development
d_init_01
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Skill enrichment (orchestrator / LLM)
Database administration is a common hiring requirement across DBAs, SREs, and platform roles; job postings routinely list backup/recovery, replication, and performance tuning for PostgreSQL, MySQL, and SQL Server.
(0.90)
“Database Administration” is a clear domain term and unlikely to be confused with other distinct catalog skills.
Not versioned
Domain ·database_administration confidence 0.95
Database Administration is a vertical body of knowledge and practice around managing databases, so by the Domain rule it is not a tool or methodology.
- Category
- Domain
- Sub-category
- database_administration
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Version strategy
- NOT_APPLICABLE
Dimensions (API 2 worklist)
-
React Frontend Development Catalog dimension db id 96
Library dimension (catalog)
Locked dimensions (v3 placement)
-
Database Administration
Pipeline tentative id
Operational management of database systems, including installation, configuration, backups, recovery, patching, and routine maintenance. This skill belongs here because it focuses on keeping databases available, secure, and performant for application workloads.
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
React Frontend Development
d_init_01
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Skill enrichment (orchestrator / LLM)
Systems administration is a common hiring requirement across IT ops and infrastructure JDs, often listed alongside Linux, Windows Server, and cloud admin duties; it remains a standard baseline skill rather than a niche specialty.
(0.90)
“Systems Administration” is a broad, distinct domain term; typical JDs won’t confuse it with other specific catalog skills.
Not versioned
Domain ·systems_administration confidence 0.93
Systems Administration is a vertical body of operational knowledge and responsibilities rather than a specific tool, framework, or methodology, so it fits the Domain type.
- Category
- Domain
- Sub-category
- systems_administration
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Version strategy
- NOT_APPLICABLE
Dimensions (API 2 worklist)
-
React Frontend Development Catalog dimension db id 96
Library dimension (catalog)
-
Cloud Platforms Catalog dimension db id 20
Library dimension (catalog)
Roles linked in library: Backend Engineer, Cybersecurity Engineer, Data Engineer, DevOps Engineer, ML Engineer
-
Cloud Platforms Catalog dimension db id 20
Library dimension (catalog)
Roles linked in library: Backend Engineer, Cybersecurity Engineer, Data Engineer, DevOps Engineer, ML Engineer
Locked dimensions (v3 placement)
-
Systems Administration
Pipeline tentative id
Administration of servers, operating systems, and core runtime environments to keep business systems available, patched, and correctly configured. This fits the target skill because it covers day-to-day management of infrastructure hosts rather than application code.
-
Cloud Platforms
Reuses catalog slug
Proficiency in major cloud service provider platforms and their core services. Systems administration can overlap here when admins manage cloud-hosted servers, but the core skill is broader platform operation rather than host-level administration.
-
Cloud Platforms
Reuses catalog slug
Proficiency in major cloud service provider platforms and their core services.
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
React Frontend Development
d_init_01
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Cloud Platforms
cloud-platforms
|
✓ | ✓ | New skill saved · Existing dimension (library) · Role↔dimension saved |
Skill enrichment (orchestrator / LLM)
Common in infrastructure and facilities JDs for hyperscalers, colocation, and enterprise IT; roles routinely list data center operations, monitoring, and incident response as core requirements.
(0.90)
“Data Center Operations” is a specific domain term (facility/infra ops) and is unlikely to be confused with other distinct catalog skills.
Not versioned
Domain ·data_center_operations confidence 0.97
Data Center Operations is a vertical/problem-space body of knowledge rather than a tool, framework, or methodology, so it fits the Domain type.
- Category
- Domain
- Sub-category
- data_center_operations
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Version strategy
- NOT_APPLICABLE
Dimensions (API 2 worklist)
-
React Frontend Development Catalog dimension db id 96
Library dimension (catalog)
Locked dimensions (v3 placement)
-
Data Center Operations
Pipeline tentative id
Operational practices for running physical data center facilities and the IT equipment housed in them. This covers day-to-day availability, maintenance, access, and incident handling for servers, racks, power, cooling, and related infrastructure.
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
React Frontend Development
d_init_01
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Skill enrichment (orchestrator / LLM)
PC-based applications remain a common requirement in job postings for desktop software, enterprise tools, and internal business apps; the category is broadly adopted rather than a niche stack.
(0.50)
“PC-based Applications” is a broad, specific desktop/PC application context and doesn’t closely overlap with another distinct catalog skill name.
Not versioned
Tool ·desktop_application confidence 0.90
PC-based Applications are software you run locally as a user rather than a hosted environment or codebase you build inside, so they fit the Tool definition.
- Category
- Tool
- Sub-category
- desktop_application
- Skill nature
- TOOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Version strategy
- NOT_APPLICABLE
Dimensions (API 2 worklist)
-
React Frontend Development Catalog dimension db id 96
Library dimension (catalog)
Locked dimensions (v3 placement)
-
Desktop Application Development
Pipeline tentative id
Builds software that runs as installed or locally executed applications on personal computers. This covers desktop UI, windowing, local workflows, and platform-specific client behavior, which is the natural home for PC-based Applications.
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
React Frontend Development
d_init_01
|
✓ | — | New skill saved · 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 |
|---|---|---|---|---|---|---|
| Java | in_db |
Kotlin and Java
kotlin-and-java
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Java | in_db |
Programming Languages
programming-languages
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| Java | in_db |
Programming Languages for Data Work
programming-languages-for-data-work
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Spring Boot | in_db |
Web Application Frameworks
web-application-frameworks
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| Microservices | in_db |
Microservices and Distributed Systems
microservices-and-distributed-systems
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| Angular | in_db |
UI Frameworks and Rendering
ui-frameworks-and-rendering
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| UI Development | in_db |
React Frontend Development
d_init_01
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| UI Development | in_db |
Frontend Architecture and Code Organization
frontend-architecture-and-code-organization
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Client-Server Architecture | in_db |
React Frontend Development
d_init_01
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Network Operations | in_db |
React Frontend Development
d_init_01
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Database Administration | in_db |
React Frontend Development
d_init_01
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Systems Administration | in_db |
React Frontend Development
d_init_01
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Systems Administration | in_db |
Cloud Platforms
cloud-platforms
|
✓ | ✓ | New skill saved · Existing dimension (library) · Role↔dimension saved | |
| Data Center Operations | in_db |
React Frontend Development
d_init_01
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| PC-based Applications | in_db |
React Frontend Development
d_init_01
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Library artifacts (this run)
| Kind | Detail | DB id |
|---|---|---|
| canonical_skill_added | UI Development | 1371 |
| canonical_skill_added | Client-Server Architecture | 1372 |
| canonical_skill_added | Network Operations | 1373 |
| canonical_skill_added | Database Administration | 1374 |
| canonical_skill_added | Systems Administration | 1375 |
| canonical_skill_added | Data Center Operations | 1376 |
| canonical_skill_added | PC-based Applications | 1377 |
| dimension_skill_link | UI Development ↔ React Frontend Development | 96 |
| dimension_skill_link | UI Development ↔ Frontend Architecture and Code Organization | 128 |
| dimension_skill_link | Client-Server Architecture ↔ React Frontend Development | 96 |
| dimension_skill_link | Network Operations ↔ React Frontend Development | 96 |
| dimension_skill_link | Database Administration ↔ React Frontend Development | 96 |
| dimension_skill_link | Systems Administration ↔ React Frontend Development | 96 |
| dimension_skill_link | Systems Administration ↔ Cloud Platforms | 20 |
| dimension_skill_link | Data Center Operations ↔ React Frontend Development | 96 |
| dimension_skill_link | PC-based Applications ↔ React Frontend Development | 96 |
nano JD Parser — gpt-4.1-nano click to toggle
Show raw JSON
{
"JD_type": "pass",
"about_company": null,
"certifications": [],
"company_name": "Citi",
"ctc": null,
"domain": {
"primary": {
"aliases": [
"ITES",
"BPO"
],
"domain": "IT Services \u0026 Consulting"
},
"secondary": null
},
"education": [
{
"level": "Bachelor\u0027s",
"qualification": "Bachelor\u0027s - Any Discipline",
"raw": "Bachelor\u2019s degree/University degree or equivalent experience",
"requirement": "required"
}
],
"experience": {
"max": null,
"min": 2,
"raw": "2+ years of relevant experience"
},
"job_locations": [],
"role": "Applications Development Programmer Analyst",
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 0,
"heading": "Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "Utilize knowledge of applications development",
"last_5_words": "with transparency."
},
"text": "Utilize knowledge of applications development procedures and concepts, and basic knowledge of other technical areas to identify and define necessary system enhancements\nIdentify and analyze issues, make recommendations, and implement solutions\nUtilize knowledge of business processes, system processes, and industry standards to solve complex issues\nAnalyze information and make evaluative judgements to recommend solutions and improvements\nConduct testing and debugging, utilize script tools, and write basic code for design specifications\nAssess applicability of similar experiences and evaluate options under circumstances not covered by procedures\nDevelop working knowledge of Citi\u2019s information systems, procedures, standards, client server application development, network operations, database administration, systems administration, data center operations, and PC-based applications\nAppropriately assess risk when business decisions are made, demonstrating particular consideration for the firm\u0027s reputation and safeguarding Citigroup, its clients and assets, by driving compliance with applicable laws, rules and regulations, adhering to Policy, applying sound ethical judgment regarding personal behavior, conduct and business practices, and escalating, managing and reporting control issues with transparency.",
"word_count": 198
},
{
"bullet_count": 6,
"heading": "Qualifications",
"heading_was_present": true,
"source_marker": {
"first_5_words": "2+ years of relevant experience",
"last_5_words": "and verbal communication"
},
"text": "2+ years of relevant experience\nExperience in programming/debugging used in business applications\nWorking knowledge of industry practice and standards\nComprehensive knowledge of specific business area for application development\nWorking knowledge of Java Springboot Microservices. Knowledge of Angular/ UI development will be advantage but not mandatory.\nConsistently demonstrates clear and concise written and verbal communication",
"word_count": 56
},
{
"bullet_count": 0,
"heading": "Education",
"heading_was_present": true,
"source_marker": {
"first_5_words": "Bachelor\u2019s degree/University degree or",
"last_5_words": "or equivalent experience"
},
"text": "Bachelor\u2019s degree/University degree or equivalent experience",
"word_count": 10
}
],
"urls": []
}
API 1 — extract-from-jd click to toggle
{
"final_skills": [
{
"is_primary": true,
"skill_name": "Java"
},
{
"is_primary": true,
"skill_name": "Spring Boot"
},
{
"is_primary": true,
"skill_name": "Microservices"
},
{
"is_primary": false,
"skill_name": "Angular"
},
{
"is_primary": false,
"skill_name": "UI Development"
},
{
"is_primary": false,
"skill_name": "Client-Server Architecture"
},
{
"is_primary": false,
"skill_name": "Network Operations"
},
{
"is_primary": false,
"skill_name": "Database Administration"
},
{
"is_primary": false,
"skill_name": "Systems Administration"
},
{
"is_primary": false,
"skill_name": "Data Center Operations"
},
{
"is_primary": false,
"skill_name": "PC-based Applications"
}
],
"jd_role": {
"display_name": "Applications Development Programmer Analyst",
"rationale": null,
"role_archetype": "Engineering",
"slug": ""
},
"nano_parsed": {
"JD_type": "pass",
"about_company": null,
"certifications": [],
"company_name": "Citi",
"ctc": null,
"domain": {
"primary": {
"aliases": [
"ITES",
"BPO"
],
"domain": "IT Services \u0026 Consulting"
},
"secondary": null
},
"education": [
{
"level": "Bachelor\u0027s",
"qualification": "Bachelor\u0027s - Any Discipline",
"raw": "Bachelor\u2019s degree/University degree or equivalent experience",
"requirement": "required"
}
],
"experience": {
"max": null,
"min": 2,
"raw": "2+ years of relevant experience"
},
"job_locations": [],
"role": "Applications Development Programmer Analyst",
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 0,
"heading": "Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "Utilize knowledge of applications development",
"last_5_words": "with transparency."
},
"text": "Utilize knowledge of applications development procedures and concepts, and basic knowledge of other technical areas to identify and define necessary system enhancements\nIdentify and analyze issues, make recommendations, and implement solutions\nUtilize knowledge of business processes, system processes, and industry standards to solve complex issues\nAnalyze information and make evaluative judgements to recommend solutions and improvements\nConduct testing and debugging, utilize script tools, and write basic code for design specifications\nAssess applicability of similar experiences and evaluate options under circumstances not covered by procedures\nDevelop working knowledge of Citi\u2019s information systems, procedures, standards, client server application development, network operations, database administration, systems administration, data center operations, and PC-based applications\nAppropriately assess risk when business decisions are made, demonstrating particular consideration for the firm\u0027s reputation and safeguarding Citigroup, its clients and assets, by driving compliance with applicable laws, rules and regulations, adhering to Policy, applying sound ethical judgment regarding personal behavior, conduct and business practices, and escalating, managing and reporting control issues with transparency.",
"word_count": 198
},
{
"bullet_count": 6,
"heading": "Qualifications",
"heading_was_present": true,
"source_marker": {
"first_5_words": "2+ years of relevant experience",
"last_5_words": "and verbal communication"
},
"text": "2+ years of relevant experience\nExperience in programming/debugging used in business applications\nWorking knowledge of industry practice and standards\nComprehensive knowledge of specific business area for application development\nWorking knowledge of Java Springboot Microservices. Knowledge of Angular/ UI development will be advantage but not mandatory.\nConsistently demonstrates clear and concise written and verbal communication",
"word_count": 56
},
{
"bullet_count": 0,
"heading": "Education",
"heading_was_present": true,
"source_marker": {
"first_5_words": "Bachelor\u2019s degree/University degree or",
"last_5_words": "or equivalent experience"
},
"text": "Bachelor\u2019s degree/University degree or equivalent experience",
"word_count": 10
}
],
"urls": []
},
"rejected": false,
"rejection_reason": null,
"run_id": "3c93ea27-c08f-40bb-b029-8bec0c05ceab",
"stage3_signals": {
"alias_match_roles": [],
"kra_match_roles": [
{
"display_name": "Android Engineer",
"matched_count": null,
"role_id": 4,
"score": 0.3886,
"slug": "android-engineer",
"total_count": null
},
{
"display_name": "Data Engineer",
"matched_count": null,
"role_id": 2,
"score": 0.3849,
"slug": "data-engineer",
"total_count": null
},
{
"display_name": "Cloud Architect",
"matched_count": null,
"role_id": 9,
"score": 0.3675,
"slug": "cloud-architect",
"total_count": null
},
{
"display_name": "Cybersecurity Engineer",
"matched_count": null,
"role_id": 5,
"score": 0.3674,
"slug": "cybersecurity-engineer",
"total_count": null
},
{
"display_name": "Frontend Engineer",
"matched_count": null,
"role_id": 7,
"score": 0.3651,
"slug": "frontend-engineer",
"total_count": null
}
],
"skill_match_roles": [
{
"display_name": "Backend Engineer",
"matched_count": 3,
"role_id": 1,
"score": 0.2727,
"slug": "backend-engineer",
"total_count": 11
},
{
"display_name": "Data Engineer",
"matched_count": 1,
"role_id": 2,
"score": 0.0909,
"slug": "data-engineer",
"total_count": 11
},
{
"display_name": "Android Engineer",
"matched_count": 1,
"role_id": 4,
"score": 0.0909,
"slug": "android-engineer",
"total_count": 11
},
{
"display_name": "Frontend Engineer",
"matched_count": 1,
"role_id": 7,
"score": 0.0909,
"slug": "frontend-engineer",
"total_count": 11
},
{
"display_name": "Hybrid Mobile Developer",
"matched_count": 1,
"role_id": 11,
"score": 0.0909,
"slug": "hybrid-mobile-developer",
"total_count": 11
}
],
"stage35_ran": false
},
"stage4_decision": {
"alias_collision_detected": false,
"case": "E",
"chosen_role": null,
"confidence": 0.0,
"llm2_fired": false,
"llm2_reasoning": null,
"queued": true,
"reasoning": "low_kra: top KRA 0.39 \u003c 0.4"
},
"stage5_updates": {
"centroid_n_after": null,
"centroid_updated": false,
"collision_log_id": null,
"new_kra_attached": null,
"new_skills_attached": [],
"queue_entry_id": 39,
"v3_pipeline_triggered": true,
"v3_role_slug": "applications-development-programmer-analyst",
"v3_run_id": "317768df-76f2-40d6-82eb-4990e9243942"
}
}
API 2 — extract-details
{
"alias_matches": [
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 1,
"existing_alias_text": "Java",
"input_term": "Java",
"matched_canonical": {
"category_id": 6,
"display_name": "Java",
"id": 1,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "LANGUAGE",
"slug": "java",
"sub_category_id": 96,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 79,
"existing_alias_text": "Spring Boot",
"input_term": "Spring Boot",
"matched_canonical": {
"category_id": 5,
"display_name": "Spring Boot",
"id": 6,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "FRAMEWORK",
"slug": "spring-boot",
"sub_category_id": 34,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 178,
"existing_alias_text": "microservices",
"input_term": "Microservices",
"matched_canonical": {
"category_id": 1,
"display_name": "microservices",
"id": 41,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PATTERN",
"slug": "microservices",
"sub_category_id": 1,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 1067,
"existing_alias_text": "Angular",
"input_term": "Angular",
"matched_canonical": {
"category_id": 5,
"display_name": "Angular",
"id": 612,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "FRAMEWORK",
"slug": "angular",
"sub_category_id": 341,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
}
],
"candidate_roles": [
{
"display_name": "Android Engineer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"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"
},
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "Frontend Engineer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "Cybersecurity Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
},
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
}
],
"chosen_role": {
"display_name": "Backend Engineer",
"id": 1,
"rationale": "The primary skills of Java, Spring Boot, and Microservices align closely with the responsibilities of a Backend Engineer.",
"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": "Kotlin and Java",
"id": 161,
"rationale": "Primary implementation languages for Android app features, platform integration, and client-side business logic. Android engineers use these languages to build screens, state flows, service adapters, and device-aware behavior.",
"slug": "kotlin-and-java",
"source": "db"
},
"input_skill": "Java",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Android Engineer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages",
"id": 1,
"rationale": "Core server-side languages used to implement backend business logic, integrations, and service internals. This is the primary coding surface for the role across application layers.",
"slug": "programming-languages",
"source": "db"
},
"input_skill": "Java",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"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"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Data Work",
"id": 21,
"rationale": "Languages used to implement data pipelines, transformations, and operational glue. This is the primary coding surface for building ingestion, enrichment, and automation logic in data engineering.",
"slug": "programming-languages-for-data-work",
"source": "db"
},
"input_skill": "Java",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Web Application Frameworks",
"id": 2,
"rationale": "Server frameworks and runtimes used to build HTTP services, controllers, middleware, and request pipelines. These frameworks shape how backend endpoints are structured and delivered.",
"slug": "web-application-frameworks",
"source": "db"
},
"input_skill": "Spring Boot",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"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"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Microservices and Distributed Systems",
"id": 9,
"rationale": "Architectural patterns for decomposed backend systems and the operational concerns they introduce. Covers service boundaries, consistency tradeoffs, retries, circuit breakers, and distributed coordination.",
"slug": "microservices-and-distributed-systems",
"source": "db"
},
"input_skill": "Microservices",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"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"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "UI Frameworks and Rendering",
"id": 115,
"rationale": "Component frameworks and rendering models used to build browser screens, reusable UI, and interactive client flows. This is a core cluster because frontend engineers spend much of their time composing and updating view hierarchies.",
"slug": "ui-frameworks-and-rendering",
"source": "db"
},
"input_skill": "Angular",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "UI Development",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Frontend Architecture and Code Organization",
"id": 128,
"rationale": "Structural patterns for organizing large client applications into maintainable modules, layers, and feature boundaries. Senior frontend engineers often own these decisions to keep UI code scalable over time.",
"slug": "frontend-architecture-and-code-organization",
"source": "db"
},
"input_skill": "UI Development",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Frontend Architecture and Code Organization",
"id": 128,
"rationale": "Structural patterns for organizing large client applications into maintainable modules, layers, and feature boundaries. Senior frontend engineers often own these decisions to keep UI code scalable over time.",
"slug": "frontend-architecture-and-code-organization",
"source": "db"
},
"input_skill": "UI Development",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Client-Server Architecture",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Network Operations",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Database Administration",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Systems Administration",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platforms",
"id": 20,
"rationale": "Proficiency in major cloud service provider platforms and their core services.",
"slug": "cloud-platforms",
"source": "db"
},
"input_skill": "Systems Administration",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"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"
},
{
"display_name": "Cybersecurity Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
},
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
},
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platforms",
"id": 20,
"rationale": "Proficiency in major cloud service provider platforms and their core services.",
"slug": "cloud-platforms",
"source": "db"
},
"input_skill": "Systems Administration",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"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"
},
{
"display_name": "Cybersecurity Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
},
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
},
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Data Center Operations",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "PC-based Applications",
"llm_role": null,
"roles_from_db": []
}
],
"input_final_skills": [
"Java",
"Spring Boot",
"Microservices",
"Angular",
"UI Development",
"Client-Server Architecture",
"Network Operations",
"Database Administration",
"Systems Administration",
"Data Center Operations",
"PC-based Applications"
],
"input_llm_skills": [
"Java",
"Spring Boot",
"Microservices",
"Angular",
"UI Development",
"Client-Server Architecture",
"Network Operations",
"Database Administration",
"Systems Administration",
"Data Center Operations",
"PC-based Applications"
],
"new_aliases_persisted": 0,
"run_id": "3c93ea27-c08f-40bb-b029-8bec0c05ceab",
"skills_detail": [
{
"aliases_in_db": [
{
"alias_text": "Java",
"alias_type": "CANONICAL",
"id": 1,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JDK 11",
"alias_type": "VERSION",
"id": 4,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JDK 17",
"alias_type": "VERSION",
"id": 5,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JDK 21",
"alias_type": "VERSION",
"id": 6,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JDK 8",
"alias_type": "VERSION",
"id": 3,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 1.0",
"alias_type": "VERSION",
"id": 11,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 1.1",
"alias_type": "VERSION",
"id": 12,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 1.2",
"alias_type": "VERSION",
"id": 13,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 1.3",
"alias_type": "VERSION",
"id": 14,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 1.4",
"alias_type": "VERSION",
"id": 15,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 1.5",
"alias_type": "VERSION",
"id": 16,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 1.6",
"alias_type": "VERSION",
"id": 17,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 1.7",
"alias_type": "VERSION",
"id": 18,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 1.8",
"alias_type": "VERSION",
"id": 19,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 11",
"alias_type": "VERSION",
"id": 8,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 17",
"alias_type": "VERSION",
"id": 9,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 21",
"alias_type": "VERSION",
"id": 10,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 5",
"alias_type": "VERSION",
"id": 288,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 6",
"alias_type": "VERSION",
"id": 289,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 7",
"alias_type": "VERSION",
"id": 290,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 8",
"alias_type": "VERSION",
"id": 7,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "OpenJDK 11",
"alias_type": "VERSION",
"id": 21,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "OpenJDK 17",
"alias_type": "VERSION",
"id": 22,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "OpenJDK 21",
"alias_type": "VERSION",
"id": 23,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "OpenJDK 8",
"alias_type": "VERSION",
"id": 20,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java 11",
"alias_type": "VERSION",
"id": 1512,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java 17",
"alias_type": "VERSION",
"id": 1513,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java 21",
"alias_type": "VERSION",
"id": 1514,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java 4",
"alias_type": "VERSION",
"id": 1496,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java 5",
"alias_type": "VERSION",
"id": 1497,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java 6",
"alias_type": "VERSION",
"id": 1498,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java 7",
"alias_type": "VERSION",
"id": 1499,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java 8",
"alias_type": "VERSION",
"id": 1500,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java-11",
"alias_type": "VERSION",
"id": 1515,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java-17",
"alias_type": "VERSION",
"id": 1516,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java-21",
"alias_type": "VERSION",
"id": 1517,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java-4",
"alias_type": "VERSION",
"id": 1501,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java-5",
"alias_type": "VERSION",
"id": 1502,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java-6",
"alias_type": "VERSION",
"id": 1503,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java-7",
"alias_type": "VERSION",
"id": 1504,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java-8",
"alias_type": "VERSION",
"id": 1505,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java11",
"alias_type": "VERSION",
"id": 1506,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java17",
"alias_type": "VERSION",
"id": 1507,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java21",
"alias_type": "VERSION",
"id": 1508,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java4",
"alias_type": "VERSION",
"id": 1482,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java5",
"alias_type": "VERSION",
"id": 1483,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java6",
"alias_type": "VERSION",
"id": 1484,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java7",
"alias_type": "VERSION",
"id": 1485,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java8",
"alias_type": "VERSION",
"id": 1486,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "jdk 11",
"alias_type": "VERSION",
"id": 1509,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "jdk 17",
"alias_type": "VERSION",
"id": 1510,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "jdk 21",
"alias_type": "VERSION",
"id": 1511,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "jdk 4",
"alias_type": "VERSION",
"id": 1487,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "jdk 5",
"alias_type": "VERSION",
"id": 1488,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "jdk 6",
"alias_type": "VERSION",
"id": 1489,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "jdk 7",
"alias_type": "VERSION",
"id": 1490,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "jdk 8",
"alias_type": "VERSION",
"id": 1491,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "jdk11",
"alias_type": "VERSION",
"id": 1492,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "jdk17",
"alias_type": "VERSION",
"id": 1493,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "jdk21",
"alias_type": "VERSION",
"id": 1494,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "jdk4",
"alias_type": "VERSION",
"id": 1477,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "jdk5",
"alias_type": "VERSION",
"id": 1478,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "jdk6",
"alias_type": "VERSION",
"id": 1479,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "jdk7",
"alias_type": "VERSION",
"id": 1480,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "jdk8",
"alias_type": "VERSION",
"id": 1481,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "jvm21",
"alias_type": "VERSION",
"id": 1495,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 6,
"display_name": "Java",
"id": 1,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "LANGUAGE",
"slug": "java",
"sub_category_id": 96,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Kotlin and Java",
"id": 161,
"rationale": "Primary implementation languages for Android app features, platform integration, and client-side business logic. Android engineers use these languages to build screens, state flows, service adapters, and device-aware behavior.",
"slug": "kotlin-and-java",
"source": "db"
},
"input_skill": "Java",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Android Engineer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages",
"id": 1,
"rationale": "Core server-side languages used to implement backend business logic, integrations, and service internals. This is the primary coding surface for the role across application layers.",
"slug": "programming-languages",
"source": "db"
},
"input_skill": "Java",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"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"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Data Work",
"id": 21,
"rationale": "Languages used to implement data pipelines, transformations, and operational glue. This is the primary coding surface for building ingestion, enrichment, and automation logic in data engineering.",
"slug": "programming-languages-for-data-work",
"source": "db"
},
"input_skill": "Java",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
]
}
],
"input_skill": "Java",
"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": [
{
"alias_text": "Spring Boot",
"alias_type": "CANONICAL",
"id": 79,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 5,
"display_name": "Spring Boot",
"id": 6,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "FRAMEWORK",
"slug": "spring-boot",
"sub_category_id": 34,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Web Application Frameworks",
"id": 2,
"rationale": "Server frameworks and runtimes used to build HTTP services, controllers, middleware, and request pipelines. These frameworks shape how backend endpoints are structured and delivered.",
"slug": "web-application-frameworks",
"source": "db"
},
"input_skill": "Spring Boot",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"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"
}
]
}
],
"input_skill": "Spring Boot",
"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": [
{
"alias_text": "microservices",
"alias_type": "CANONICAL",
"id": 178,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 1,
"display_name": "microservices",
"id": 41,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PATTERN",
"slug": "microservices",
"sub_category_id": 1,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Microservices and Distributed Systems",
"id": 9,
"rationale": "Architectural patterns for decomposed backend systems and the operational concerns they introduce. Covers service boundaries, consistency tradeoffs, retries, circuit breakers, and distributed coordination.",
"slug": "microservices-and-distributed-systems",
"source": "db"
},
"input_skill": "Microservices",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"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"
}
]
}
],
"input_skill": "Microservices",
"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": [
{
"alias_text": "Angular",
"alias_type": "CANONICAL",
"id": 1067,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Angular 1",
"alias_type": "VERSION",
"id": 1068,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Angular 1.x",
"alias_type": "VERSION",
"id": 1086,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Angular 10",
"alias_type": "VERSION",
"id": 1077,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Angular 11",
"alias_type": "VERSION",
"id": 1078,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Angular 12",
"alias_type": "VERSION",
"id": 1079,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Angular 13",
"alias_type": "VERSION",
"id": 1080,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Angular 14",
"alias_type": "VERSION",
"id": 1081,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Angular 15",
"alias_type": "VERSION",
"id": 1082,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Angular 16",
"alias_type": "VERSION",
"id": 1083,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Angular 17",
"alias_type": "VERSION",
"id": 1084,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Angular 2",
"alias_type": "VERSION",
"id": 1069,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Angular 2+",
"alias_type": "VERSION",
"id": 1085,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Angular 4",
"alias_type": "VERSION",
"id": 1070,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Angular 5",
"alias_type": "VERSION",
"id": 1071,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Angular 6",
"alias_type": "VERSION",
"id": 1072,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Angular 7",
"alias_type": "VERSION",
"id": 1073,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Angular 8",
"alias_type": "VERSION",
"id": 1074,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Angular 9",
"alias_type": "VERSION",
"id": 1075,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "AngularJS",
"alias_type": "VERSION",
"id": 1076,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 5,
"display_name": "Angular",
"id": 612,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "FRAMEWORK",
"slug": "angular",
"sub_category_id": 341,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "UI Frameworks and Rendering",
"id": 115,
"rationale": "Component frameworks and rendering models used to build browser screens, reusable UI, and interactive client flows. This is a core cluster because frontend engineers spend much of their time composing and updating view hierarchies.",
"slug": "ui-frameworks-and-rendering",
"source": "db"
},
"input_skill": "Angular",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
}
]
}
],
"input_skill": "Angular",
"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": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "UI Development",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Frontend Architecture and Code Organization",
"id": 128,
"rationale": "Structural patterns for organizing large client applications into maintainable modules, layers, and feature boundaries. Senior frontend engineers often own these decisions to keep UI code scalable over time.",
"slug": "frontend-architecture-and-code-organization",
"source": "db"
},
"input_skill": "UI Development",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Frontend Architecture and Code Organization",
"id": 128,
"rationale": "Structural patterns for organizing large client applications into maintainable modules, layers, and feature boundaries. Senior frontend engineers often own these decisions to keep UI code scalable over time.",
"slug": "frontend-architecture-and-code-organization",
"source": "db"
},
"input_skill": "UI Development",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
}
]
}
],
"input_skill": "UI Development",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Domain",
"skill_nature": "CONCEPT",
"sub_category": "user_interface_development",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "\u201cUI Development\u201d is a broad, distinct domain term and is unlikely to be confused with another specific catalog skill."
},
"context_keywords": {
"context_keywords": [
"React",
"Angular",
"Vue.js",
"Bootstrap",
"CSS Grid",
"Flexbox",
"Material Design",
"UI/UX",
"Wireframing",
"Prototyping",
"Responsive Design",
"Accessibility",
"Component Libraries",
"Design Systems",
"JavaScript Frameworks"
]
},
"maturity": {
"confidence": 0.95,
"maturity": "well_known",
"reasoning": "UI development is a core hiring-pipeline staple across frontend and product roles; job postings routinely list React, Angular, or Vue UI work, showing broad market demand rather than a niche toolset."
},
"skill_id": "ui-development",
"vendor_license": {
"confidence": 0.9,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [
{
"a_dim_id": "d_init_01",
"a_name": "User Interface Development",
"a_role": "__skill_focal__",
"b_dim_id": "frontend-architecture-and-code-organization",
"b_name": "Frontend Architecture and Code Organization",
"b_role": "__skill_focal__",
"pair_kind": "intra_role",
"reasoning": "Dim A covers UI implementation: screen layout, component composition, responsive design, forms, navigation flows, reusable widgets, and client-side interaction handling. Dim B covers frontend architecture: organizing large client apps into maintainable modules, layers, and feature boundaries. A senior UI developer is not automatically a senior frontend architect; the skills and daily work differ. career-track: no, because building interfaces and designing code organization are distinct frontend specialties.",
"similarity": 0.6001062769167697
},
{
"a_dim_id": "frontend-architecture-and-code-organization",
"a_name": "Frontend Architecture and Code Organization",
"a_role": "__skill_focal__",
"b_dim_id": "frontend-architecture-and-code-organization",
"b_name": "Frontend Architecture and Code Organization",
"b_role": "Frontend Engineer",
"pair_kind": "cross_role",
"reasoning": "Cross-role pair with same label but different scope. Dim A is a skill_focal cluster about structuring large client apps: feature modules, component boundaries, folder structure, layering, shared UI libraries, and design system integration; its exemplars include UI Development and frontend modularization. Dim B is the Frontend Engineer version, centered on senior ownership of architecture decisions to keep UI code scalable. career-track: no, because a senior practitioner in A\u2019s UI/code-organization cluster is not automatically a senior practitioner in B\u2019s broader frontend-engineer ownership cluster.",
"similarity": 0.9357753703854504
}
],
"locked_dimensions": [
{
"description": "Building interactive application screens, layouts, and component behavior for end users. This fits UI Development because it covers the implementation of visual structure, interaction patterns, and reusable interface elements across client apps.",
"exemplar_skills": [
"UI Development",
"screen layout implementation",
"component-based UI",
"responsive UI design",
"interactive form development",
"navigation UI",
"reusable widgets"
],
"in_scope": "UI Development, screen layout, component composition, responsive design, forms, navigation flows, reusable UI widgets, theming, client-side interaction handling",
"name": "User Interface Development",
"out_of_scope": "frontend-testing-and-e2e-automation, state-management-patterns, accessibility-and-internationalization, backend API design, server rendering, visual design/branding",
"overlap_flags": [
{
"reason": "UI Development often depends on how screens and components are structured, but this dimension is about implementation rather than codebase organization.",
"with_dim_id": "frontend-architecture-and-code-organization",
"with_dim_name": null,
"with_role": "Frontend Engineer"
},
{
"reason": "UI Development frequently consumes and updates client state, but state modeling is a separate concern.",
"with_dim_id": "state-management-patterns",
"with_dim_name": null,
"with_role": "Frontend Engineer"
},
{
"reason": "Accessible and localized UI is closely related, but this dimension focuses on general interface construction.",
"with_dim_id": "accessibility-and-internationalization",
"with_dim_name": null,
"with_role": "Android Engineer, Hybrid Mobile Developer, Ios engineer"
}
],
"tentative_id": "d_init_01"
},
{
"description": "Structural patterns for organizing large client applications into maintainable modules, layers, and feature boundaries. UI Development can touch this area when building screens within a broader frontend architecture, but the core focus is on code structure rather than the UI itself.",
"exemplar_skills": [
"UI Development",
"frontend modularization",
"component architecture",
"feature-based organization",
"design system integration",
"shared component libraries"
],
"in_scope": "feature modules, component boundaries, folder structure, layering, shared UI libraries, design system integration, UI Development in large frontend codebases",
"name": "Frontend Architecture and Code Organization",
"out_of_scope": "visual layout implementation, interaction wiring, styling details, state management, accessibility, testing",
"overlap_flags": [
{
"reason": "Frontend architecture often determines where state lives, but state handling is a distinct skill cluster.",
"with_dim_id": "state-management-patterns",
"with_dim_name": null,
"with_role": "Frontend Engineer"
}
],
"tentative_id": "frontend-architecture-and-code-organization"
},
{
"description": "Structural patterns for organizing large client applications into maintainable modules, layers, and feature boundaries. Senior frontend engineers often own these decisions to keep UI code scalable over time.",
"exemplar_skills": [
"Frontend Architecture and Code Organization"
],
"in_scope": "Skills, tools, and practices that belong under Frontend Architecture and Code Organization for the target role, including items implied by the dimension rationale.",
"name": "Frontend Architecture and Code Organization",
"out_of_scope": "Adjacent clusters explicitly not owned by Frontend Architecture and Code Organization, including unrelated platforms, roles, and skill families per library policy.",
"overlap_flags": [],
"tentative_id": "frontend-architecture-and-code-organization"
}
],
"merge_log": [],
"placed": {
"name": "UI Development",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"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": [
"frontend-architecture-and-code-organization"
],
"skill_id": "ui-development"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"mvvm",
"react-native",
"react-navigation",
"ui-automator",
"xctest",
"testflight",
"dynamic-type",
"voiceover"
],
"requires": [],
"skill_id": "ui-development",
"suppress_on_match": []
},
"skill_id": "ui-development",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.9,
"name": "UI Development",
"reasoning": "UI Development is best treated as a domain of practice focused on building user interfaces, not a specific language, framework, or methodology.",
"skill_id": "ui-development",
"subtype": "user_interface_development",
"type": "Domain"
},
"warnings": [
"stage3_post_filter_dropped_catalog_only_locked_dims:42-\u003e3"
]
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Client-Server Architecture",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Client-Server Architecture",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Architecture",
"skill_nature": "PATTERN",
"sub_category": "client_server_architecture",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "\u201cClient-Server Architecture\u201d is a specific architecture pattern; unlikely to be confused with other distinct architecture skills in typical JDs."
},
"context_keywords": {
"context_keywords": [
"RESTful services",
"API design",
"load balancing",
"microservices",
"database connectivity",
"session management",
"scalability",
"stateful vs stateless",
"service-oriented architecture",
"network protocols",
"client-side rendering",
"server-side processing",
"middleware",
"data serialization",
"web sockets"
]
},
"maturity": {
"confidence": 0.98,
"maturity": "well_known",
"reasoning": "Core architecture pattern in most software JDs and system design interviews; widely used across web, mobile, and enterprise apps, with no successor replacing it."
},
"skill_id": "client-server-architecture",
"vendor_license": {
"confidence": 0.95,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Design patterns and structural decisions for splitting responsibilities between client applications and backend servers. This skill fits here because it covers request/response boundaries, API contracts, session flow, and how distributed application tiers interact.",
"exemplar_skills": [
"Client-Server Architecture",
"three-tier architecture",
"n-tier architecture",
"frontend-backend separation",
"API contract design",
"distributed application design"
],
"in_scope": "Client-Server Architecture, client/server separation of concerns, request-response flow, tiered application design, frontend-backend boundaries, API contract alignment, session handoff between tiers, thin-client vs thick-client tradeoffs",
"name": "Client-Server Architecture",
"out_of_scope": "HTTP request construction and response parsing, retries and transport details owned by networking-and-api-integration, database schema design and persistence owned by data architecture, service-to-service routing and mesh policy owned by service-mesh-and-traffic-management",
"overlap_flags": [
{
"reason": "Client-server systems rely on API calls, but that dimension focuses on the client-side mechanics of making those calls rather than the overall tiered architecture.",
"with_dim_id": "networking-and-api-integration",
"with_dim_name": null,
"with_role": "Android Engineer, Hybrid Mobile Developer, Ios engineer"
},
{
"reason": "Both touch client application structure, but this dimension is about system boundaries between client and server, not organizing frontend code.",
"with_dim_id": "frontend-architecture-and-code-organization",
"with_dim_name": null,
"with_role": "Frontend Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Client-Server Architecture",
"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": "client-server-architecture"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"distributed-systems",
"event-driven-architecture",
"load-balancing",
"apis",
"repository-pattern",
"mvvm",
"node-js",
"relational-databases"
],
"requires": [],
"skill_id": "client-server-architecture",
"suppress_on_match": []
},
"skill_id": "client-server-architecture",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "Client-Server Architecture",
"reasoning": "This is an Architecture because Client-Server describes a system-shape pattern for how components are organized and interact, not a concept or methodology.",
"skill_id": "client-server-architecture",
"subtype": "client_server_architecture",
"type": "Architecture"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Network Operations",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Network Operations",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Domain",
"skill_nature": "CONCEPT",
"sub_category": "network_operations",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "\u201cNetwork Operations\u201d is a clear domain term focused on operating and maintaining networks; it\u2019s unlikely to be confused with another distinct catalog skill."
},
"context_keywords": {
"context_keywords": [
"network monitoring",
"troubleshooting",
"packet analysis",
"SNMP",
"TCP/IP",
"firewall management",
"VPN",
"network topology",
"routing protocols",
"switch configuration",
"load balancing",
"network security",
"QoS",
"WAN optimization",
"DNS management"
]
},
"maturity": {
"confidence": 0.88,
"maturity": "well_known",
"reasoning": "Network Operations is a common hiring requirement in NOC/SRE/IT ops job descriptions, with many postings asking for monitoring, incident response, and troubleshooting of enterprise networks."
},
"skill_id": "network-operations",
"vendor_license": {
"confidence": 0.9,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Operational practices for monitoring, maintaining, and troubleshooting networked systems and connectivity. This fits the target skill because it covers day-to-day network health, incident handling, and service availability work rather than application-level API coding.",
"exemplar_skills": [
"Network Operations",
"network monitoring",
"DNS troubleshooting",
"VPN support",
"firewall troubleshooting",
"latency analysis",
"packet capture analysis"
],
"in_scope": "Network Operations, network monitoring, link and route troubleshooting, DNS and DHCP checks, packet loss analysis, latency investigation, VPN connectivity, firewall rule validation, load balancer health checks, network incident triage",
"name": "Network Operations",
"out_of_scope": "Application HTTP client code, request/response parsing, and retry logic belong to networking-and-api-integration; cloud routing policy and service-to-service traffic shaping belong to service-mesh-and-traffic-management; identity policy administration belongs to identity-and-access-management-products",
"overlap_flags": [
{
"reason": "Both involve networked communication, but this dimension is about operational troubleshooting while that one is about application-side integration.",
"with_dim_id": "networking-and-api-integration",
"with_dim_name": null,
"with_role": "Android Engineer, Hybrid Mobile Developer, Ios engineer"
},
{
"reason": "Traffic routing and reliability controls can overlap with operations, but service mesh focuses on platform-level service-to-service policy.",
"with_dim_id": "service-mesh-and-traffic-management",
"with_dim_name": null,
"with_role": "Cloud Architect, DevOps Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Network Operations",
"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": "network-operations"
},
"relationships": {
"child_skills": [],
"parent_skills": [
"devops",
"distributed-systems",
"monitoring",
"load-balancing"
],
"related_to": [
"rdbms",
"ecs",
"node-js",
"apns",
"location-services"
],
"requires": [],
"skill_id": "network-operations",
"suppress_on_match": []
},
"skill_id": "network-operations",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.95,
"name": "Network Operations",
"reasoning": "Network Operations is a vertical/problem-space body of knowledge rather than a tool, framework, or methodology, so it fits the Domain type.",
"skill_id": "network-operations",
"subtype": "network_operations",
"type": "Domain"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Database Administration",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Database Administration",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Domain",
"skill_nature": "CONCEPT",
"sub_category": "database_administration",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "\u201cDatabase Administration\u201d is a clear domain term and unlikely to be confused with other distinct catalog skills."
},
"context_keywords": {
"context_keywords": [
"SQL",
"NoSQL",
"backup",
"replication",
"performance tuning",
"indexing",
"database migration",
"data modeling",
"transaction management",
"stored procedures",
"query optimization",
"database security",
"ETL",
"high availability",
"database design"
]
},
"maturity": {
"confidence": 0.94,
"maturity": "well_known",
"reasoning": "Database administration is a common hiring requirement across DBAs, SREs, and platform roles; job postings routinely list backup/recovery, replication, and performance tuning for PostgreSQL, MySQL, and SQL Server."
},
"skill_id": "database-administration",
"vendor_license": {
"confidence": 0.9,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Operational management of database systems, including installation, configuration, backups, recovery, patching, and routine maintenance. This skill belongs here because it focuses on keeping databases available, secure, and performant for application workloads.",
"exemplar_skills": [
"Database Administration",
"SQL Server Administration",
"Oracle DBA",
"PostgreSQL Administration",
"MySQL Administration",
"Backup and Recovery",
"Database Patching",
"Replication Management"
],
"in_scope": "Database Administration, database installation and configuration, backup and restore, replication setup, patching and upgrades, user and role management, capacity planning, monitoring and alerting, maintenance windows, SQL Server administration, Oracle DBA tasks, PostgreSQL administration, MySQL administration",
"name": "Database Administration",
"out_of_scope": "Schema design and query tuning, which belong to data modeling or performance tuning, application-side ORM usage, which belongs to application development, cloud account governance and network controls, which belong to cloud security governance",
"overlap_flags": [
{
"reason": "Managed database services and storage choices can overlap with operational database administration in cloud environments.",
"with_dim_id": "cloud-storage-and-data-services",
"with_dim_name": null,
"with_role": "Cloud Architect"
},
{
"reason": "DBA work often includes indexing and query performance troubleshooting, which can overlap with broader performance tuning.",
"with_dim_id": "performance-and-scalability-tuning",
"with_dim_name": null,
"with_role": "Backend Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Database Administration",
"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": "database-administration"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"rdbms",
"relational-databases",
"nosql",
"monitoring",
"rollback-procedures",
"distributed-systems",
"vector-db",
"data-lakes"
],
"requires": [],
"skill_id": "database-administration",
"suppress_on_match": []
},
"skill_id": "database-administration",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.95,
"name": "Database Administration",
"reasoning": "Database Administration is a vertical body of knowledge and practice around managing databases, so by the Domain rule it is not a tool or methodology.",
"skill_id": "database-administration",
"subtype": "database_administration",
"type": "Domain"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Systems Administration",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platforms",
"id": 20,
"rationale": "Proficiency in major cloud service provider platforms and their core services.",
"slug": "cloud-platforms",
"source": "db"
},
"input_skill": "Systems Administration",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"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"
},
{
"display_name": "Cybersecurity Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
},
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
},
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platforms",
"id": 20,
"rationale": "Proficiency in major cloud service provider platforms and their core services.",
"slug": "cloud-platforms",
"source": "db"
},
"input_skill": "Systems Administration",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"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"
},
{
"display_name": "Cybersecurity Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
},
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
},
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
}
]
}
],
"input_skill": "Systems Administration",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Domain",
"skill_nature": "CONCEPT",
"sub_category": "systems_administration",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "\u201cSystems Administration\u201d is a broad, distinct domain term; typical JDs won\u2019t confuse it with other specific catalog skills."
},
"context_keywords": {
"context_keywords": [
"Linux",
"Windows Server",
"Active Directory",
"VMware",
"Shell Scripting",
"Network Configuration",
"Backup Solutions",
"Monitoring Tools",
"Configuration Management",
"Cloud Services",
"Security Patches",
"User Management",
"Troubleshooting",
"Automation",
"System Performance"
]
},
"maturity": {
"confidence": 0.93,
"maturity": "well_known",
"reasoning": "Systems administration is a common hiring requirement across IT ops and infrastructure JDs, often listed alongside Linux, Windows Server, and cloud admin duties; it remains a standard baseline skill rather than a niche specialty."
},
"skill_id": "systems-administration",
"vendor_license": {
"confidence": 0.9,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [
{
"a_dim_id": "d_init_01",
"a_name": "Systems Administration",
"a_role": "__skill_focal__",
"b_dim_id": "cloud-platforms",
"b_name": "Cloud Platforms",
"b_role": "__skill_focal__",
"pair_kind": "intra_role",
"reasoning": "Dim A is host/OS operations: Linux/Windows administration, patching, service management, backups, host monitoring, and shell work. Dim B is cloud-provider platform proficiency across major CSPs and their core services. These overlap only superficially; the exemplar skills point to different layers of the stack. career-track: no, because a senior systems administrator is not automatically a senior cloud-platforms practitioner; the daily work and expertise differ.",
"similarity": 0.6167879886441846
},
{
"a_dim_id": "cloud-platforms",
"a_name": "Cloud Platforms",
"a_role": "__skill_focal__",
"b_dim_id": "cloud-platforms",
"b_name": "Cloud Platforms",
"b_role": "DevOps Engineer",
"pair_kind": "cross_role",
"reasoning": "Same name, but A is broader and explicitly includes cloud-console ops, compute instances, managed networking/storage, plus a systems-administration boundary (OS patching, local services, filesystem tuning, user accounts). Its exemplars include Systems Administration, AWS, Azure, GCP. B only says major cloud platforms/core services and is tied to DevOps Engineer with no scope detail or exemplars. career-track: no, because A\u2019s cloud-platform/admin-adjacent cluster is not guaranteed to be the same as a DevOps cloud-platform cluster focused on platform operations/automation.",
"similarity": 0.8363219473325317
}
],
"locked_dimensions": [
{
"description": "Administration of servers, operating systems, and core runtime environments to keep business systems available, patched, and correctly configured. This fits the target skill because it covers day-to-day management of infrastructure hosts rather than application code.",
"exemplar_skills": [
"Systems Administration",
"Linux Administration",
"Windows Server Administration",
"Server Patching",
"Service Management",
"Backup and Restore Operations",
"Host Monitoring"
],
"in_scope": "Systems Administration, Linux and Windows server administration, user and group management, patching and updates, service management, filesystem and storage configuration, backups and restores, host monitoring, log review, basic shell administration",
"name": "Systems Administration",
"out_of_scope": "Cloud resource provisioning and templates, which belong to infrastructure-as-code or cloud-platforms, identity product configuration, which belongs to identity-and-access-management-products, incident triage and forensic investigation, which belong to incident-response-digital-forensics",
"overlap_flags": [
{
"reason": "Systems administration often runs on cloud-hosted servers, but this dimension is about the host OS and runtime upkeep rather than provider services.",
"with_dim_id": "cloud-platforms",
"with_dim_name": null,
"with_role": "Backend Engineer, Cybersecurity Engineer, Data Engineer, DevOps Engineer, ML Engineer"
},
{
"reason": "Automating server setup can overlap with IaC, but this dimension focuses on manual operational administration of systems.",
"with_dim_id": "infrastructure-as-code",
"with_dim_name": null,
"with_role": "Cloud Architect, DevOps Engineer"
}
],
"tentative_id": "d_init_01"
},
{
"description": "Proficiency in major cloud service provider platforms and their core services. Systems administration can overlap here when admins manage cloud-hosted servers, but the core skill is broader platform operation rather than host-level administration.",
"exemplar_skills": [
"Systems Administration",
"AWS",
"Microsoft Azure",
"Google Cloud Platform",
"Cloud Console Administration",
"Compute Instance Management"
],
"in_scope": "AWS, Azure, Google Cloud Platform, compute instances, managed networking, storage services, cloud console operations, basic cloud administration, Systems Administration in cloud environments",
"name": "Cloud Platforms",
"out_of_scope": "Operating system patching, local service management, filesystem tuning, and user account administration on individual hosts, which belong to Systems Administration",
"overlap_flags": [
{
"reason": "Many systems administrators work on cloud-hosted servers, but the catalog already has a host-operations dimension for OS-level administration.",
"with_dim_id": "d_init_01",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Cloud platform work often uses declarative provisioning, but that is a separate automation discipline from platform operations.",
"with_dim_id": "infrastructure-as-code",
"with_dim_name": null,
"with_role": "Cloud Architect, DevOps Engineer"
}
],
"tentative_id": "cloud-platforms"
},
{
"description": "Proficiency in major cloud service provider platforms and their core services.",
"exemplar_skills": [
"Cloud Platforms"
],
"in_scope": "Skills, tools, and practices that belong under Cloud Platforms for the target role, including items implied by the dimension rationale.",
"name": "Cloud Platforms",
"out_of_scope": "Adjacent clusters explicitly not owned by Cloud Platforms, including unrelated platforms, roles, and skill families per library policy.",
"overlap_flags": [],
"tentative_id": "cloud-platforms"
}
],
"merge_log": [],
"placed": {
"name": "Systems Administration",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"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": [
"cloud-platforms"
],
"skill_id": "systems-administration"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"devops",
"monitoring",
"distributed-systems",
"ci-cd",
"load-balancing",
"autoscaling",
"rdbms",
"ecs"
],
"requires": [],
"skill_id": "systems-administration",
"suppress_on_match": []
},
"skill_id": "systems-administration",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.93,
"name": "Systems Administration",
"reasoning": "Systems Administration is a vertical body of operational knowledge and responsibilities rather than a specific tool, framework, or methodology, so it fits the Domain type.",
"skill_id": "systems-administration",
"subtype": "systems_administration",
"type": "Domain"
},
"warnings": [
"stage3_post_filter_dropped_catalog_only_locked_dims:42-\u003e3"
]
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Data Center Operations",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Data Center Operations",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Domain",
"skill_nature": "CONCEPT",
"sub_category": "data_center_operations",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "\u201cData Center Operations\u201d is a specific domain term (facility/infra ops) and is unlikely to be confused with other distinct catalog skills."
},
"context_keywords": {
"context_keywords": [
"server management",
"virtualization",
"network infrastructure",
"disaster recovery",
"load balancing",
"data backup",
"monitoring tools",
"rack optimization",
"power management",
"cooling systems",
"cloud integration",
"capacity planning",
"incident response",
"SLA management",
"asset tracking"
]
},
"maturity": {
"confidence": 0.86,
"maturity": "well_known",
"reasoning": "Common in infrastructure and facilities JDs for hyperscalers, colocation, and enterprise IT; roles routinely list data center operations, monitoring, and incident response as core requirements."
},
"skill_id": "data-center-operations",
"vendor_license": {
"confidence": 0.9,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Operational practices for running physical data center facilities and the IT equipment housed in them. This covers day-to-day availability, maintenance, access, and incident handling for servers, racks, power, cooling, and related infrastructure.",
"exemplar_skills": [
"Data Center Operations",
"rack and stack",
"server installation",
"hardware replacement",
"cabling management",
"facility access control",
"inventory tracking"
],
"in_scope": "Data Center Operations, rack and stack, server installation and decommissioning, power and cooling checks, cabling and labeling, hardware swaps, remote hands coordination, facility access procedures, inventory tracking, uptime monitoring",
"name": "Data Center Operations",
"out_of_scope": "Cloud platform administration, virtual machine provisioning, and managed service configuration, which belong to cloud-platforms; network design and traffic routing, which belong to service-mesh-and-traffic-management or networking-and-api-integration; security policy and compliance controls, which belong to cloud-security-governance or data-security-and-dlp",
"overlap_flags": [
{
"reason": "Data center work often supports cloud infrastructure, but this dimension is about physical facility operations rather than provider services.",
"with_dim_id": "cloud-platforms",
"with_dim_name": null,
"with_role": "Backend Engineer, Cybersecurity Engineer, Data Engineer, DevOps Engineer, ML Engineer"
},
{
"reason": "Physical access and environmental controls intersect with security, but the core skill is operational facility management.",
"with_dim_id": "cloud-security-governance",
"with_dim_name": null,
"with_role": "Cloud Architect"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Data Center Operations",
"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": "data-center-operations"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"devops",
"monitoring",
"load-balancing",
"distributed-systems",
"rdbms",
"rds",
"data-lakes",
"datadog"
],
"requires": [],
"skill_id": "data-center-operations",
"suppress_on_match": []
},
"skill_id": "data-center-operations",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.97,
"name": "Data Center Operations",
"reasoning": "Data Center Operations is a vertical/problem-space body of knowledge rather than a tool, framework, or methodology, so it fits the Domain type.",
"skill_id": "data-center-operations",
"subtype": "data_center_operations",
"type": "Domain"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "PC-based Applications",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "PC-based Applications",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Tool",
"skill_nature": "TOOL",
"sub_category": "desktop_application",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "\u201cPC-based Applications\u201d is a broad, specific desktop/PC application context and doesn\u2019t closely overlap with another distinct catalog skill name."
},
"context_keywords": {
"context_keywords": [
"Windows",
"macOS",
"Linux",
"GUI",
"desktop software",
"application deployment",
"user interface",
"system compatibility",
"installation",
"software updates",
"performance optimization",
"local storage",
"file management",
"user experience",
"security protocols"
]
},
"maturity": {
"confidence": 0.84,
"maturity": "well_known",
"reasoning": "PC-based applications remain a common requirement in job postings for desktop software, enterprise tools, and internal business apps; the category is broadly adopted rather than a niche stack."
},
"skill_id": "pc-based-applications",
"vendor_license": {
"confidence": 0.5,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Builds software that runs as installed or locally executed applications on personal computers. This covers desktop UI, windowing, local workflows, and platform-specific client behavior, which is the natural home for PC-based Applications.",
"exemplar_skills": [
"PC-based Applications",
"desktop application development",
"native desktop UI",
"window management",
"local file integration"
],
"in_scope": "PC-based Applications, desktop application architecture, native desktop UI, windowing and dialogs, local file handling, desktop menus and shortcuts, installer-aware client behavior, Windows/macOS/Linux desktop apps",
"name": "Desktop Application Development",
"out_of_scope": "mobile apps, web applications in browsers, backend services, cloud infrastructure, embedded firmware",
"overlap_flags": [
{
"reason": "Desktop apps still need modular UI structure and feature organization, but this dimension is about the desktop application runtime itself.",
"with_dim_id": "frontend-architecture-and-code-organization",
"with_dim_name": null,
"with_role": "Frontend Engineer"
},
{
"reason": "Implementation languages may overlap, but this dimension focuses on the application type rather than the language used.",
"with_dim_id": "programming-languages-and-scripting",
"with_dim_name": null,
"with_role": "Cybersecurity Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "PC-based Applications",
"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": "pc-based-applications"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"xcode",
"c",
"java",
"perl",
"git",
"apis",
"rdbms",
"distributed-systems"
],
"requires": [],
"skill_id": "pc-based-applications",
"suppress_on_match": []
},
"skill_id": "pc-based-applications",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.9,
"name": "PC-based Applications",
"reasoning": "PC-based Applications are software you run locally as a user rather than a hosted environment or codebase you build inside, so they fit the Tool definition.",
"skill_id": "pc-based-applications",
"subtype": "desktop_application",
"type": "Tool"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"UI Development",
"Client-Server Architecture",
"Network Operations",
"Database Administration",
"Systems Administration",
"Data Center Operations",
"PC-based Applications"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "Backend Engineer",
"id": 1,
"rationale": "The primary skills of Java, Spring Boot, and Microservices align closely with the responsibilities of a Backend Engineer.",
"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": "Java",
"tag": "in_db"
},
{
"skill": "Spring Boot",
"tag": "in_db"
},
{
"skill": "Microservices",
"tag": "in_db"
},
{
"skill": "Angular",
"tag": "in_db"
},
{
"skill": "UI Development",
"tag": "new"
},
{
"skill": "Client-Server Architecture",
"tag": "new"
},
{
"skill": "Network Operations",
"tag": "new"
},
{
"skill": "Database Administration",
"tag": "new"
},
{
"skill": "Systems Administration",
"tag": "new"
},
{
"skill": "Data Center Operations",
"tag": "new"
},
{
"skill": "PC-based Applications",
"tag": "new"
}
],
"persistence": {
"items": [
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Kotlin and Java",
"id": 161,
"rationale": "Primary implementation languages for Android app features, platform integration, and client-side business logic. Android engineers use these languages to build screens, state flows, service adapters, and device-aware behavior.",
"slug": "kotlin-and-java",
"source": "db"
},
"dimension_id": 161,
"input_skill": "Java",
"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": "Android Engineer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 1,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages",
"id": 1,
"rationale": "Core server-side languages used to implement backend business logic, integrations, and service internals. This is the primary coding surface for the role across application layers.",
"slug": "programming-languages",
"source": "db"
},
"dimension_id": 1,
"input_skill": "Java",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"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"
}
],
"skill_dimension_saved": true,
"skill_id": 1,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Data Work",
"id": 21,
"rationale": "Languages used to implement data pipelines, transformations, and operational glue. This is the primary coding surface for building ingestion, enrichment, and automation logic in data engineering.",
"slug": "programming-languages-for-data-work",
"source": "db"
},
"dimension_id": 21,
"input_skill": "Java",
"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": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 1,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Web Application Frameworks",
"id": 2,
"rationale": "Server frameworks and runtimes used to build HTTP services, controllers, middleware, and request pipelines. These frameworks shape how backend endpoints are structured and delivered.",
"slug": "web-application-frameworks",
"source": "db"
},
"dimension_id": 2,
"input_skill": "Spring Boot",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"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"
}
],
"skill_dimension_saved": true,
"skill_id": 6,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Microservices and Distributed Systems",
"id": 9,
"rationale": "Architectural patterns for decomposed backend systems and the operational concerns they introduce. Covers service boundaries, consistency tradeoffs, retries, circuit breakers, and distributed coordination.",
"slug": "microservices-and-distributed-systems",
"source": "db"
},
"dimension_id": 9,
"input_skill": "Microservices",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"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"
}
],
"skill_dimension_saved": true,
"skill_id": 41,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "UI Frameworks and Rendering",
"id": 115,
"rationale": "Component frameworks and rendering models used to build browser screens, reusable UI, and interactive client flows. This is a core cluster because frontend engineers spend much of their time composing and updating view hierarchies.",
"slug": "ui-frameworks-and-rendering",
"source": "db"
},
"dimension_id": 115,
"input_skill": "Angular",
"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": "Frontend Engineer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 612,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"dimension_id": 96,
"input_skill": "UI Development",
"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": 1371,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Frontend Architecture and Code Organization",
"id": 128,
"rationale": "Structural patterns for organizing large client applications into maintainable modules, layers, and feature boundaries. Senior frontend engineers often own these decisions to keep UI code scalable over time.",
"slug": "frontend-architecture-and-code-organization",
"source": "db"
},
"dimension_id": 128,
"input_skill": "UI Development",
"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": "Frontend Engineer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 1371,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"dimension_id": 96,
"input_skill": "Client-Server Architecture",
"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": 1372,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"dimension_id": 96,
"input_skill": "Network Operations",
"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": 1373,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"dimension_id": 96,
"input_skill": "Database Administration",
"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": 1374,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"dimension_id": 96,
"input_skill": "Systems Administration",
"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": 1375,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platforms",
"id": 20,
"rationale": "Proficiency in major cloud service provider platforms and their core services.",
"slug": "cloud-platforms",
"source": "db"
},
"dimension_id": 20,
"input_skill": "Systems Administration",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "New skill saved \u00b7 Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"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"
},
{
"display_name": "Cybersecurity Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
},
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
},
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 1375,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"dimension_id": 96,
"input_skill": "Data Center Operations",
"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": 1376,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"dimension_id": 96,
"input_skill": "PC-based Applications",
"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": 1377,
"skill_tag": "in_db",
"skipped_reason": null
}
],
"new_skills_created": 7,
"role_dimension_saved": 0,
"skill_dimension_saved": 9,
"skipped": 0
},
"planner_output": null,
"run_id": "3c93ea27-c08f-40bb-b029-8bec0c05ceab"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.