Pipeline run
6c5696ec-e2f8-4796-8e11-851c3676621e
Client output enrichment
v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA descriptionvocab breakdown (legacy)
Signals
Post-classification
Captured for admin review
The Pega/LowCode Tech PM is responsible for technically managing projects/programs and implementation of PRPC/Rules-based/Configuration based solutions, including leadership roles in design to develop…
1 POST /skills/extract-from-jd
2 POST /skills/extract-details
3 POST /skills/final-role-output
Technical Program Manager (TPM)
CASE Aslug: technical-program-manager-tpm · id: 119 · source: db
Exact alias hit on technical-program-manager-tpm (1.0) — no other alias at this confidence; skill_top full-stack-engineer 0.07 does not contradict
Resolution:
in_db
— role exists in library; skill↔dim and role↔dim links saved when applicable.
Job description
A Low-code Technical Program Manager (TPM), having 20+ years of experience in Architecting, Designing and developing scalable and high volume Pega/LowCode/software applications. 5+ years experience in solutioning, design and implementation of Pega/LowCode new age modern cloud based SaaS software solutions, including leadership role in managing large scale technical projects and programs. 5+ years experience driving the execution of product/programs from carving out the vision, KRAs , setting up development teams and delivering to those KRAs/vision. Duties include contributing technical expertise to product/program development, coordinating the development and providing services around new technologies- such as Automation, cloud/modernization, Low Code etc - with IT engineers, LOBs, clients and systems teams and ensuring timely product / project delivery. Prior experience as a tech PM, solution architect on multiple large-scale products, applications or enterprise designs and solutions on Pega PRPC V8.x/Unqork/ other Low-Code products or similar modern cloud technology stack platforms. Experience in technically managing projects/programs and implementation of PRPC/Rules-based/Configuration based solutions, including leadership roles in design to develop shared/reusable/framework based apps enterprise rules and workflow components within Pega or other Low-Code/automation platforms/products. Strong experience scoping, planning and delivering projects using iterative/Agile/Agile @Scale software development lifecycles over multiple release cycles, within the purview of a Center of Excellence , in Low-Code Responsibilities The Pega/LowCode Tech PM is responsible for technically managing projects/programs and implementation of PRPC/Rules-based/Configuration based solutions, including leadership roles in design to develop shared/reusable/framework based apps enterprise rules and workflow components within Pega or other Low-Code/automation platforms/products. Also responsible for Collaborating with business users, Citizen developers, product managers, end users, developers, and other stakeholders to Suggest, Analyse architect Pega/LowCode Solutions. Solve problems, build frameworks, guardrails, platform solutions within the purview of a Low-Code COE. Provide thought-leadership to end users/Biz Users across Line of Businesses and technical project dimensions solving complex business requirements Works in conjunction with Program Managers, Biz Users & Citizen developers to analyze ,size, manage scope and risk and deliver Pega/Low-code platform Level Solutions & apps Accountable for ensuring the business and technical architecture of the delivered solution and the tech design is in accordance with the tech standards, risk and control and compliance standards laid out by the JPMC Participates in the development of additional consulting opportunities within the User bases. Rapid Application Development and the ability to quickly create proof of concepts on different latest Pega/Low-code products, Solutions and frameworks, and marketplace based tech stacks Understanding of architecture and design across various JPMC internal and external systems and applications Performing reviews, implementation reviews, design and architecture reviews, API design reviews, preparing and monitoring, development & QA standards for Pega/low-code platforms. Capable of technically guiding high performing agile teams. Project/Program management, tracking, reporting, monitoring and control. Communications and Stakeholder management, removing impediments, so that tech teams can focus on technical deliverables. Follow industry best practice, Recommend improvements to existing software programs and processes as necessary, Quickly and thoroughly learn new technologies required to perform duties Skills And/or Work Experience Requirements Bachelor's degree in a related field and/or relevant work experience (computer science engineering or relevant experience) Experience in technical projects/program management , Lead the Delivery , developing , releasing and maintaining applications developed on Pega V8.X/Low code platforms or Cloud/modernization platforms. Experience in new Pega/low-code/Modern Cloud native SaaS platforms capabilities, functionality, frameworks, products platforms and solutions. Experience integrating enterprise applications with Pega/Low-code solutions Experience in delivery and implementation of low-code/SaaS cloud hosted platform solutions, including leadership role in technical program management of multiple initiates that happen within a COE. Experience in Java, JavaScript, ReactJS, React Native, HTML5, CSS3, Python, Angular / Java / node.js, Java Spring / Spring Boot experiences, Experience with cloud platforms and technologies - AWS / Azure Experience on Relational Database management systems MS SQL, MySQL and with No-SQL DB systems is an added plus Experience with latest versions of GitHub, bit bucket and/0r Jira Working knowledge of Enterprise Interface Development, REST and JSON Able to combine business knowledge with technological expertise to promote innovation, growth in the COE - from technical and business dimensions. Experience handling high performing Agile teams, Agile Scrum Master, Agile@Scale Strong communication , inter-personal skills, handling matrix organization structures, complex stakeholder management. JPMorgan Chase & Co., one of the oldest financial institutions, offers innovative financial solutions to millions of consumers, small businesses and many of the world's most prominent corporate, institutional and government clients under the J.P. Morgan and Chase brands. Our history spans over 200 years and today we are a leader in investment banking, consumer and small business banking, commercial banking, financial transaction processing and asset management. We recognize that our people are our strength and the diverse talents they bring to our global workforce are directly linked to our success. We are an equal opportunity employer and place a high value on diversity and inclusion at our company. We do not discriminate on the basis of any protected attribute, including race, religion, color, national origin, gender, sexual orientation, gender identity, gender expression, age, marital or veteran status, pregnancy or disability, or any other basis protected under applicable law. In accordance with applicable law, we make reasonable accommodations for applicants' and employees' religious practices and beliefs, as well as any mental health or physical disability needs.
Skills from this JD
Each row merges API 1 extraction, API 2 library match / v3 orchestration (dimensions + locked dims), and API 3 persistence tags.
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Low-Code Platforms
- Sub-category
- general
- Skill nature
- PLATFORM
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Development Methodologies
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Low-Code Platforms
- Sub-category
- general
- Skill nature
- TOOL
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Development Methodologies
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Development Methodologies
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Development Methodologies
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Development Methodologies
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Development Methodologies
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Aliases — catalog
- API (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Application Programming Interface
- Confidence
- 0.93
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: APIs are a core requirement in most software engineering JDs and underpin common integrations across cloud, mobile, and web stacks; major vendors like AWS, Stripe, and Google Cloud center products on API-first usage.
Skill profile (library / DB)
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 2
- Sub-category id
- 1174
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
API Integration and Data Fetching Catalog dimension db id 127
Library dimension (catalog)
Roles linked in library: Angular Frontend Developer, Frontend Developer, Fullstack Developer, React Frontend Developer, Svelte Frontend Developer, Vue Frontend Developer, Web Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
API Integration and Data Fetching
api-integration-and-data-fetching
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- Agile (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Methodology
- Sub-category
- Agile
- Confidence
- 0.99
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Agile appears in a large share of software job descriptions and is a standard hiring-pipeline requirement; Scrum/Kanban are commonly listed alongside it, showing broad market adoption.
Skill profile (library / DB)
- Skill nature
- METHODOLOGY
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 8
- Sub-category id
- 367
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
React Frontend Development Catalog dimension db id 96
Library dimension (catalog)
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Development Methodologies
- Sub-category
- general
- Skill nature
- PRACTICE
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Development Practices
- Sub-category
- general
- Skill nature
- PRACTICE
- Volatility
- FAST
- Typical lifespan
- SHORT_LIVED
- Version strategy
- VERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Compliance and Governance
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Software Testing
- Sub-category
- general
- Skill nature
- PRACTICE
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Compliance and Governance
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Compliance and Governance
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
All API 3 persistence rows
Same grid as the skill-extractor “Persistence items” table: one row per (skill × dimension) work item.
| Skill | Tag | Dimension | Skill↔dim | Role↔dim | Outcome | Notes |
|---|---|---|---|---|---|---|
| API | in_db |
API Integration and Data Fetching
api-integration-and-data-fetching
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Agile | in_db |
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Library artifacts (this run)
| Kind | Detail | DB id |
|---|---|---|
| canonical_skill_proposed | Pega | type=Low-Code Platforms subtype=general nature=PLATFORM lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Low-Code | type=Development Methodologies subtype=general nature=CONCEPT lifespan=MULTI_YEAR | |
| canonical_skill_proposed | PRPC | type=Low-Code Platforms subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Rules-based | type=Development Methodologies subtype=general nature=CONCEPT lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Configuration-based | type=Development Methodologies subtype=general nature=CONCEPT lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Workflow | type=Development Methodologies subtype=general nature=CONCEPT lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Automation | type=Development Methodologies subtype=general nature=CONCEPT lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Framework | type=Development Methodologies subtype=general nature=CONCEPT lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Rapid Application Development | type=Development Methodologies subtype=general nature=PRACTICE lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Proof of Concept | type=Development Practices subtype=general nature=PRACTICE lifespan=SHORT_LIVED | |
| canonical_skill_proposed | Tech Standards | type=Compliance and Governance subtype=general nature=CONCEPT lifespan=MULTI_YEAR | |
| canonical_skill_proposed | QA | type=Software Testing subtype=general nature=PRACTICE lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Risk and Control | type=Compliance and Governance subtype=general nature=CONCEPT lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Compliance Standards | type=Compliance and Governance subtype=general nature=CONCEPT lifespan=MULTI_YEAR |
nano JD Parser — gpt-4.1-nano click to toggle
Show raw JSON
{
"JD_type": "pass",
"about_company": {
"source_marker": {
"first_5_words": "JPMorgan Chase \u0026 Co., one",
"last_5_words": "transaction processing and asset management."
},
"text": "JPMorgan Chase \u0026 Co., one of the oldest financial institutions, offers innovative financial solutions to millions of consumers, small businesses and many of the world\u0027s most prominent corporate, institutional and government clients under the J.P. Morgan and Chase brands. Our history spans over 200 years and today we are a leader in investment banking, consumer and small business banking, commercial banking, financial transaction processing and asset management.",
"word_count": 64
},
"archetype_override_applied": true,
"archetype_override_reason": "tech-adjacent title + tech-context body",
"certifications": [],
"company_name": "JPMorgan Chase \u0026 Co.",
"ctc": null,
"domain": {
"primary": {
"aliases": [
"FinTech",
"Banking"
],
"domain": "Financial Services"
},
"secondary": null
},
"education": [
{
"level": "Bachelor\u0027s",
"qualification": "Bachelor\u0027s - Related Field",
"raw": "Bachelor\u0027s degree in a related field and/or relevant work experience (computer science engineering or relevant experience)",
"requirement": "required"
}
],
"experience": {
"max": null,
"min": 20,
"raw": "20+ years of experience"
},
"job_locations": [],
"role": "Low-code Technical Program Manager (TPM)",
"role_aliases": [
"Technical Program Manager",
"TPM",
"Program Manager"
],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 0,
"heading": "Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "The Pega/LowCode Tech PM is",
"last_5_words": "new technologies required to perform duties."
},
"text": "The Pega/LowCode Tech PM is responsible for technically managing projects/programs and implementation of PRPC/Rules-based/Configuration based solutions, including leadership roles in design to develop shared/reusable/framework based apps enterprise rules and workflow components within Pega or other Low-Code/automation platforms/products.\n\nAlso responsible for Collaborating with business users, Citizen developers, product managers, end users, developers, and other stakeholders to Suggest, Analyse architect Pega/LowCode Solutions. Solve problems, build frameworks, guardrails, platform solutions within the purview of a Low-Code COE.\nProvide thought-leadership to end users/Biz Users across Line of Businesses and technical project dimensions solving complex business requirements.\nWorks in conjunction with Program Managers, Biz Users \u0026 Citizen developers to analyze, size, manage scope and risk and deliver Pega/Low-code platform Level Solutions \u0026 apps.\nAccountable for ensuring the business and technical architecture of the delivered solution and the tech design is in accordance with the tech standards, risk and control and compliance standards laid out by the JPMC.\nParticipates in the development of additional consulting opportunities within the User bases.\nRapid Application Development and the ability to quickly create proof of concepts on different latest Pega/Low-code products, Solutions and frameworks, and marketplace based tech stacks.\nUnderstanding of architecture and design across various JPMC internal and external systems and applications.\nPerforming reviews, implementation reviews, design and architecture reviews, API design reviews, preparing and monitoring, development \u0026 QA standards for Pega/low-code platforms.\nCapable of technically guiding high performing agile teams.\nProject/Program management, tracking, reporting, monitoring and control.\nCommunications and Stakeholder management, removing impediments, so that tech teams can focus on technical deliverables.\nFollow industry best practice, Recommend improvements to existing software programs and processes as necessary, Quickly and thoroughly learn new technologies required to perform duties.",
"word_count": 366
}
],
"urls": []
}
API 1 — extract-from-jd click to toggle
{
"final_skills": [
{
"is_primary": true,
"skill_name": "Pega"
},
{
"is_primary": true,
"skill_name": "Low-Code"
},
{
"is_primary": true,
"skill_name": "PRPC"
},
{
"is_primary": true,
"skill_name": "Rules-based"
},
{
"is_primary": true,
"skill_name": "Configuration-based"
},
{
"is_primary": true,
"skill_name": "Workflow"
},
{
"is_primary": true,
"skill_name": "Automation"
},
{
"is_primary": true,
"skill_name": "Framework"
},
{
"is_primary": true,
"skill_name": "API"
},
{
"is_primary": true,
"skill_name": "Agile"
},
{
"is_primary": true,
"skill_name": "Rapid Application Development"
},
{
"is_primary": false,
"skill_name": "Proof of Concept"
},
{
"is_primary": true,
"skill_name": "Tech Standards"
},
{
"is_primary": true,
"skill_name": "QA"
},
{
"is_primary": true,
"skill_name": "Risk and Control"
},
{
"is_primary": true,
"skill_name": "Compliance Standards"
}
],
"jd_role": {
"display_name": "Low-code Technical Program Manager (TPM)",
"rationale": null,
"role_aliases": [
"Technical Program Manager",
"TPM",
"Program Manager"
],
"role_archetype": "Engineering",
"slug": ""
},
"nano_parsed": {
"JD_type": "pass",
"about_company": {
"source_marker": {
"first_5_words": "JPMorgan Chase \u0026 Co., one",
"last_5_words": "transaction processing and asset management."
},
"text": "JPMorgan Chase \u0026 Co., one of the oldest financial institutions, offers innovative financial solutions to millions of consumers, small businesses and many of the world\u0027s most prominent corporate, institutional and government clients under the J.P. Morgan and Chase brands. Our history spans over 200 years and today we are a leader in investment banking, consumer and small business banking, commercial banking, financial transaction processing and asset management.",
"word_count": 64
},
"archetype_override_applied": true,
"archetype_override_reason": "tech-adjacent title + tech-context body",
"certifications": [],
"company_name": "JPMorgan Chase \u0026 Co.",
"ctc": null,
"domain": {
"primary": {
"aliases": [
"FinTech",
"Banking"
],
"domain": "Financial Services"
},
"secondary": null
},
"education": [
{
"level": "Bachelor\u0027s",
"qualification": "Bachelor\u0027s - Related Field",
"raw": "Bachelor\u0027s degree in a related field and/or relevant work experience (computer science engineering or relevant experience)",
"requirement": "required"
}
],
"experience": {
"max": null,
"min": 20,
"raw": "20+ years of experience"
},
"job_locations": [],
"role": "Low-code Technical Program Manager (TPM)",
"role_aliases": [
"Technical Program Manager",
"TPM",
"Program Manager"
],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 0,
"heading": "Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "The Pega/LowCode Tech PM is",
"last_5_words": "new technologies required to perform duties."
},
"text": "The Pega/LowCode Tech PM is responsible for technically managing projects/programs and implementation of PRPC/Rules-based/Configuration based solutions, including leadership roles in design to develop shared/reusable/framework based apps enterprise rules and workflow components within Pega or other Low-Code/automation platforms/products.\n\nAlso responsible for Collaborating with business users, Citizen developers, product managers, end users, developers, and other stakeholders to Suggest, Analyse architect Pega/LowCode Solutions. Solve problems, build frameworks, guardrails, platform solutions within the purview of a Low-Code COE.\nProvide thought-leadership to end users/Biz Users across Line of Businesses and technical project dimensions solving complex business requirements.\nWorks in conjunction with Program Managers, Biz Users \u0026 Citizen developers to analyze, size, manage scope and risk and deliver Pega/Low-code platform Level Solutions \u0026 apps.\nAccountable for ensuring the business and technical architecture of the delivered solution and the tech design is in accordance with the tech standards, risk and control and compliance standards laid out by the JPMC.\nParticipates in the development of additional consulting opportunities within the User bases.\nRapid Application Development and the ability to quickly create proof of concepts on different latest Pega/Low-code products, Solutions and frameworks, and marketplace based tech stacks.\nUnderstanding of architecture and design across various JPMC internal and external systems and applications.\nPerforming reviews, implementation reviews, design and architecture reviews, API design reviews, preparing and monitoring, development \u0026 QA standards for Pega/low-code platforms.\nCapable of technically guiding high performing agile teams.\nProject/Program management, tracking, reporting, monitoring and control.\nCommunications and Stakeholder management, removing impediments, so that tech teams can focus on technical deliverables.\nFollow industry best practice, Recommend improvements to existing software programs and processes as necessary, Quickly and thoroughly learn new technologies required to perform duties.",
"word_count": 366
}
],
"urls": []
},
"rejected": false,
"rejection_reason": null,
"run_id": "6c5696ec-e2f8-4796-8e11-851c3676621e",
"stage3_signals": {
"alias_found": true,
"alias_match_roles": [
{
"display_name": "Technical Program Manager (TPM)",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 119,
"score": 1.0,
"slug": "technical-program-manager-tpm",
"total_count": null
}
],
"kra_match_roles": [
{
"display_name": "Cloud Architect",
"kra_matches": [
{
"kra_text": "Conducts architecture reviews, approves technical design documents, and guides engineering teams through cloud migration and modernization projects.",
"sentence": "Performing reviews, implementation reviews, design and architecture reviews, API design reviews, preparing and monitoring, development \u0026 QA standards for Pega/low-code platforms.",
"similarity": 0.6042
},
{
"kra_text": "Conducts architecture reviews, approves technical design documents, and guides engineering teams through cloud migration and modernization projects.",
"sentence": "Accountable for ensuring the business and technical architecture of the delivered solution and the tech design is in accordance with the tech standards, risk and control and compliance standards laid out by the JPMC.",
"similarity": 0.5551
},
{
"kra_text": "Conducts architecture reviews, approves technical design documents, and guides engineering teams through cloud migration and modernization projects.",
"sentence": "Understanding of architecture and design across various JPMC internal and external systems and applications.",
"similarity": 0.5272
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 9,
"score": 0.5622,
"slug": "cloud-architect",
"total_count": null
},
{
"display_name": "Fullstack Developer",
"kra_matches": [
{
"kra_text": "Works closely with product managers and UX designers to translate requirements and wireframes into working software features through iterative development.",
"sentence": "Works in conjunction with Program Managers, Biz Users \u0026 Citizen developers to analyze, size, manage scope and risk and deliver Pega/Low-code platform Level Solutions \u0026 apps.",
"similarity": 0.5299
},
{
"kra_text": "Works closely with product managers and UX designers to translate requirements and wireframes into working software features through iterative development.",
"sentence": "Also responsible for Collaborating with business users, Citizen developers, product managers, end users, developers, and other stakeholders to Suggest, Analyse architect Pega/LowCode Solutions.",
"similarity": 0.5258
},
{
"kra_text": "Works closely with product managers and UX designers to translate requirements and wireframes into working software features through iterative development.",
"sentence": "Performing reviews, implementation reviews, design and architecture reviews, API design reviews, preparing and monitoring, development \u0026 QA standards for Pega/low-code platforms.",
"similarity": 0.4688
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 15,
"score": 0.5081,
"slug": "full-stack-engineer",
"total_count": null
},
{
"display_name": "Data Engineer",
"kra_matches": [
{
"kra_text": "Works with data analysts, data scientists, and business stakeholders to define data models, ingestion schedules, and data delivery requirements.",
"sentence": "Works in conjunction with Program Managers, Biz Users \u0026 Citizen developers to analyze, size, manage scope and risk and deliver Pega/Low-code platform Level Solutions \u0026 apps.",
"similarity": 0.5079
},
{
"kra_text": "Works with data analysts, data scientists, and business stakeholders to define data models, ingestion schedules, and data delivery requirements.",
"sentence": "Also responsible for Collaborating with business users, Citizen developers, product managers, end users, developers, and other stakeholders to Suggest, Analyse architect Pega/LowCode Solutions.",
"similarity": 0.5
},
{
"kra_text": "Works with data analysts, data scientists, and business stakeholders to define data models, ingestion schedules, and data delivery requirements.",
"sentence": "Provide thought-leadership to end users/Biz Users across Line of Businesses and technical project dimensions solving complex business requirements.",
"similarity": 0.471
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 2,
"score": 0.493,
"slug": "data-engineer",
"total_count": null
},
{
"display_name": "DevOps Engineer",
"kra_matches": [
{
"kra_text": "Collaborates with development teams to improve build processes, reduce deployment friction, containerize applications, and adopt DevOps best practices.",
"sentence": "Solve problems, build frameworks, guardrails, platform solutions within the purview of a Low-Code COE.",
"similarity": 0.4953
},
{
"kra_text": "Collaborates with development teams to improve build processes, reduce deployment friction, containerize applications, and adopt DevOps best practices.",
"sentence": "Also responsible for Collaborating with business users, Citizen developers, product managers, end users, developers, and other stakeholders to Suggest, Analyse architect Pega/LowCode Solutions.",
"similarity": 0.4925
},
{
"kra_text": "Collaborates with development teams to improve build processes, reduce deployment friction, containerize applications, and adopt DevOps best practices.",
"sentence": "Communications and Stakeholder management, removing impediments, so that tech teams can focus on technical deliverables.",
"similarity": 0.4902
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 10,
"score": 0.4927,
"slug": "devops-engineer",
"total_count": null
},
{
"display_name": "Cyber Security Engineer",
"kra_matches": [
{
"kra_text": "Reviews and enforces access control policies, privilege escalation procedures, role-based access control, and identity governance workflows.",
"sentence": "Performing reviews, implementation reviews, design and architecture reviews, API design reviews, preparing and monitoring, development \u0026 QA standards for Pega/low-code platforms.",
"similarity": 0.5195
},
{
"kra_text": "Defines secure engineering standards, secure coding guidelines, threat intelligence feeds, and compliance requirements for the organization.",
"sentence": "Accountable for ensuring the business and technical architecture of the delivered solution and the tech design is in accordance with the tech standards, risk and control and compliance standards laid out by the JPMC.",
"similarity": 0.4954
},
{
"kra_text": "Performs threat modeling, security architecture reviews, and quantitative risk analysis for new product features and infrastructure changes.",
"sentence": "Works in conjunction with Program Managers, Biz Users \u0026 Citizen developers to analyze, size, manage scope and risk and deliver Pega/Low-code platform Level Solutions \u0026 apps.",
"similarity": 0.4555
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 5,
"score": 0.4901,
"slug": "cybersecurity-engineer",
"total_count": null
}
],
"skill_match_roles": [
{
"display_name": "Fullstack Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"API"
],
"role_id": 15,
"score": 0.0667,
"slug": "full-stack-engineer",
"total_count": 15
},
{
"display_name": "Frontend Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"API"
],
"role_id": 7,
"score": 0.0667,
"slug": "frontend-engineer",
"total_count": 15
},
{
"display_name": "Web Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"API"
],
"role_id": 25,
"score": 0.0667,
"slug": "web-developer",
"total_count": 15
},
{
"display_name": "React Frontend Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"API"
],
"role_id": 89,
"score": 0.0667,
"slug": "react-frontend-developer",
"total_count": 15
},
{
"display_name": "Angular Frontend Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"API"
],
"role_id": 90,
"score": 0.0667,
"slug": "angular-frontend-developer",
"total_count": 15
}
]
},
"stage4_decision": {
"alias_collision_detected": false,
"case": "A",
"chosen_role": {
"display_name": "Technical Program Manager (TPM)",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 119,
"score": 1.0,
"slug": "technical-program-manager-tpm",
"total_count": null
},
"confidence": 1.0,
"is_new_role": false,
"llm2_fired": false,
"llm2_reasoning": null,
"matched_dimensions": [],
"matched_kras": [],
"matched_skills": [],
"new_role_display_name": null,
"new_role_slug": null,
"queued": false,
"reasoning": "Exact alias hit on technical-program-manager-tpm (1.0) \u2014 no other alias at this confidence; skill_top full-stack-engineer 0.07 does not contradict",
"sub_role": null
},
"stage5_updates": {
"centroid_n_after": 1,
"centroid_updated": true,
"collision_log_id": null,
"new_kra_attached": {
"best_kra_similarity": 0.0,
"queue_id": 423,
"r_and_r_preview": "The Pega/LowCode Tech PM is responsible for technically managing projects/programs and implementation of PRPC/Rules-based/Configuration based solutions, including leadership roles in design to develop",
"role_display_name": "Technical Program Manager (TPM)",
"role_slug": "technical-program-manager-tpm",
"status": "pending"
},
"new_skills_attached": [
{
"is_primary": true,
"queue_id": 7637,
"role_display_name": "Technical Program Manager (TPM)",
"role_slug": "technical-program-manager-tpm",
"skill_name": "Pega",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 7638,
"role_display_name": "Technical Program Manager (TPM)",
"role_slug": "technical-program-manager-tpm",
"skill_name": "Low-Code",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 7639,
"role_display_name": "Technical Program Manager (TPM)",
"role_slug": "technical-program-manager-tpm",
"skill_name": "PRPC",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 7640,
"role_display_name": "Technical Program Manager (TPM)",
"role_slug": "technical-program-manager-tpm",
"skill_name": "Rules-based",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 7641,
"role_display_name": "Technical Program Manager (TPM)",
"role_slug": "technical-program-manager-tpm",
"skill_name": "Configuration-based",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 7642,
"role_display_name": "Technical Program Manager (TPM)",
"role_slug": "technical-program-manager-tpm",
"skill_name": "Workflow",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 7643,
"role_display_name": "Technical Program Manager (TPM)",
"role_slug": "technical-program-manager-tpm",
"skill_name": "Automation",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 7644,
"role_display_name": "Technical Program Manager (TPM)",
"role_slug": "technical-program-manager-tpm",
"skill_name": "Framework",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 7645,
"role_display_name": "Technical Program Manager (TPM)",
"role_slug": "technical-program-manager-tpm",
"skill_name": "Rapid Application Development",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 7646,
"role_display_name": "Technical Program Manager (TPM)",
"role_slug": "technical-program-manager-tpm",
"skill_name": "Proof of Concept",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 7647,
"role_display_name": "Technical Program Manager (TPM)",
"role_slug": "technical-program-manager-tpm",
"skill_name": "Tech Standards",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 7648,
"role_display_name": "Technical Program Manager (TPM)",
"role_slug": "technical-program-manager-tpm",
"skill_name": "QA",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 7649,
"role_display_name": "Technical Program Manager (TPM)",
"role_slug": "technical-program-manager-tpm",
"skill_name": "Risk and Control",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 7650,
"role_display_name": "Technical Program Manager (TPM)",
"role_slug": "technical-program-manager-tpm",
"skill_name": "Compliance Standards",
"status": "pending"
}
],
"queue_entry_id": null,
"v3_pipeline_triggered": false,
"v3_role_slug": null,
"v3_run_id": null
}
}
API 2 — extract-details
{
"alias_matches": [
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 2514,
"existing_alias_text": "API",
"input_term": "API",
"matched_canonical": {
"category_id": 2,
"display_name": "API",
"id": 1568,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "api",
"sub_category_id": 1174,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 868,
"existing_alias_text": "Agile",
"input_term": "Agile",
"matched_canonical": {
"category_id": 8,
"display_name": "Agile",
"id": 520,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "agile",
"sub_category_id": 367,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
}
],
"candidate_roles": [
{
"display_name": "Angular Frontend Developer",
"id": 90,
"rationale": null,
"role_archetype": "Engineering",
"slug": "angular-frontend-developer",
"source": "db"
},
{
"display_name": "Frontend Developer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "React Frontend Developer",
"id": 89,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-frontend-developer",
"source": "db"
},
{
"display_name": "Svelte Frontend Developer",
"id": 92,
"rationale": null,
"role_archetype": "Engineering",
"slug": "svelte-frontend-developer",
"source": "db"
},
{
"display_name": "Vue Frontend Developer",
"id": 91,
"rationale": null,
"role_archetype": "Engineering",
"slug": "vue-frontend-developer",
"source": "db"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
}
],
"chosen_role": {
"display_name": "Technical Program Manager (TPM)",
"id": 119,
"rationale": "Exact alias hit on technical-program-manager-tpm (1.0) \u2014 no other alias at this confidence; skill_top full-stack-engineer 0.07 does not contradict",
"role_archetype": null,
"slug": "technical-program-manager-tpm",
"source": "db"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Data Fetching",
"id": 127,
"rationale": "Client-side integration with backend endpoints and third-party services, including request shaping, response handling, and synchronization with UI state. This is central to frontend work because most screens depend on remote data.",
"slug": "api-integration-and-data-fetching",
"source": "db"
},
"input_skill": "API",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Angular Frontend Developer",
"id": 90,
"rationale": null,
"role_archetype": "Engineering",
"slug": "angular-frontend-developer",
"source": "db"
},
{
"display_name": "Frontend Developer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "React Frontend Developer",
"id": 89,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-frontend-developer",
"source": "db"
},
{
"display_name": "Svelte Frontend Developer",
"id": 92,
"rationale": null,
"role_archetype": "Engineering",
"slug": "svelte-frontend-developer",
"source": "db"
},
{
"display_name": "Vue Frontend Developer",
"id": 91,
"rationale": null,
"role_archetype": "Engineering",
"slug": "vue-frontend-developer",
"source": "db"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
}
]
},
{
"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": "Agile",
"llm_role": null,
"roles_from_db": []
}
],
"input_final_skills": [
"Pega",
"Low-Code",
"PRPC",
"Rules-based",
"Configuration-based",
"Workflow",
"Automation",
"Framework",
"API",
"Agile",
"Rapid Application Development",
"Proof of Concept",
"Tech Standards",
"QA",
"Risk and Control",
"Compliance Standards"
],
"input_llm_skills": [
"Pega",
"Low-Code",
"PRPC",
"Rules-based",
"Configuration-based",
"Workflow",
"Automation",
"Framework",
"API",
"Agile",
"Rapid Application Development",
"Proof of Concept",
"Tech Standards",
"QA",
"Risk and Control",
"Compliance Standards"
],
"new_aliases_persisted": 0,
"run_id": "6c5696ec-e2f8-4796-8e11-851c3676621e",
"skills_detail": [
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Pega",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Low-Code Platforms",
"skill_nature": "PLATFORM",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "pega",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Low-Code",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Development Methodologies",
"skill_nature": "CONCEPT",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "low-code",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "PRPC",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Low-Code Platforms",
"skill_nature": "TOOL",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "prpc",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Rules-based",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Development Methodologies",
"skill_nature": "CONCEPT",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "rules-based",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Configuration-based",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Development Methodologies",
"skill_nature": "CONCEPT",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "configuration-based",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Workflow",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Development Methodologies",
"skill_nature": "CONCEPT",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "workflow",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Automation",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Development Methodologies",
"skill_nature": "CONCEPT",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "automation",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Framework",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Development Methodologies",
"skill_nature": "CONCEPT",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "framework",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "API",
"alias_type": "CANONICAL",
"id": 2514,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 2,
"display_name": "API",
"id": 1568,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "api",
"sub_category_id": 1174,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Data Fetching",
"id": 127,
"rationale": "Client-side integration with backend endpoints and third-party services, including request shaping, response handling, and synchronization with UI state. This is central to frontend work because most screens depend on remote data.",
"slug": "api-integration-and-data-fetching",
"source": "db"
},
"input_skill": "API",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Angular Frontend Developer",
"id": 90,
"rationale": null,
"role_archetype": "Engineering",
"slug": "angular-frontend-developer",
"source": "db"
},
{
"display_name": "Frontend Developer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "React Frontend Developer",
"id": 89,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-frontend-developer",
"source": "db"
},
{
"display_name": "Svelte Frontend Developer",
"id": 92,
"rationale": null,
"role_archetype": "Engineering",
"slug": "svelte-frontend-developer",
"source": "db"
},
{
"display_name": "Vue Frontend Developer",
"id": 91,
"rationale": null,
"role_archetype": "Engineering",
"slug": "vue-frontend-developer",
"source": "db"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
}
]
}
],
"input_skill": "API",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Agile",
"alias_type": "CANONICAL",
"id": 868,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 8,
"display_name": "Agile",
"id": 520,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "agile",
"sub_category_id": 367,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"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": "Agile",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Agile",
"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": [],
"input_skill": "Rapid Application Development",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Development Methodologies",
"skill_nature": "PRACTICE",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "rapid-application-development",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Proof of Concept",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Development Practices",
"skill_nature": "PRACTICE",
"sub_category": "general",
"typical_lifespan": "SHORT_LIVED",
"version_strategy": "VERSIONED",
"volatility": "FAST"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "proof-of-concept",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Tech Standards",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Compliance and Governance",
"skill_nature": "CONCEPT",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "tech-standards",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "QA",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Software Testing",
"skill_nature": "PRACTICE",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "qa",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Risk and Control",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Compliance and Governance",
"skill_nature": "CONCEPT",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "risk-and-control",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Compliance Standards",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Compliance and Governance",
"skill_nature": "CONCEPT",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "compliance-standards",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"Pega",
"Low-Code",
"PRPC",
"Rules-based",
"Configuration-based",
"Workflow",
"Automation",
"Framework",
"Rapid Application Development",
"Proof of Concept",
"Tech Standards",
"QA",
"Risk and Control",
"Compliance Standards"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "Technical Program Manager (TPM)",
"id": 119,
"rationale": "Exact alias hit on technical-program-manager-tpm (1.0) \u2014 no other alias at this confidence; skill_top full-stack-engineer 0.07 does not contradict",
"role_archetype": null,
"slug": "technical-program-manager-tpm",
"source": "db"
},
"chosen_role_resolution": "in_db",
"final_input_skills": [
{
"skill": "Pega",
"tag": "new"
},
{
"skill": "Low-Code",
"tag": "new"
},
{
"skill": "PRPC",
"tag": "new"
},
{
"skill": "Rules-based",
"tag": "new"
},
{
"skill": "Configuration-based",
"tag": "new"
},
{
"skill": "Workflow",
"tag": "new"
},
{
"skill": "Automation",
"tag": "new"
},
{
"skill": "Framework",
"tag": "new"
},
{
"skill": "API",
"tag": "in_db"
},
{
"skill": "Agile",
"tag": "in_db"
},
{
"skill": "Rapid Application Development",
"tag": "new"
},
{
"skill": "Proof of Concept",
"tag": "new"
},
{
"skill": "Tech Standards",
"tag": "new"
},
{
"skill": "QA",
"tag": "new"
},
{
"skill": "Risk and Control",
"tag": "new"
},
{
"skill": "Compliance Standards",
"tag": "new"
}
],
"llm_cost_api1_usd": null,
"llm_cost_api2_usd": null,
"llm_cost_api3_usd": null,
"llm_cost_total_usd": null,
"persistence": {
"items": [
{
"chosen_role_id": 119,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Data Fetching",
"id": 127,
"rationale": "Client-side integration with backend endpoints and third-party services, including request shaping, response handling, and synchronization with UI state. This is central to frontend work because most screens depend on remote data.",
"slug": "api-integration-and-data-fetching",
"source": "db"
},
"dimension_id": 127,
"input_skill": "API",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Angular Frontend Developer",
"id": 90,
"rationale": null,
"role_archetype": "Engineering",
"slug": "angular-frontend-developer",
"source": "db"
},
{
"display_name": "Frontend Developer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "React Frontend Developer",
"id": 89,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-frontend-developer",
"source": "db"
},
{
"display_name": "Svelte Frontend Developer",
"id": 92,
"rationale": null,
"role_archetype": "Engineering",
"slug": "svelte-frontend-developer",
"source": "db"
},
{
"display_name": "Vue Frontend Developer",
"id": 91,
"rationale": null,
"role_archetype": "Engineering",
"slug": "vue-frontend-developer",
"source": "db"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 1568,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 119,
"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": "Agile",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": true,
"skill_id": 520,
"skill_tag": "in_db",
"skipped_reason": null
}
],
"new_skills_created": 0,
"role_dimension_saved": 0,
"skill_dimension_saved": 0,
"skipped": 0
},
"planner_output": null,
"run_id": "6c5696ec-e2f8-4796-8e11-851c3676621e"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.