Pipeline run
2f36746a-f68a-49c2-b646-3c524dd0b9ee
Client output enrichment
v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA description
role baseline loaded
sources · ai_index: jd · nature_of_work: no_kras · tech_stack_maturity: jd
Nature of work
no kras
Vague JD — no KRAs present to derive a specific nature of work.
Tech stack maturity
Mainstream Modern
AI index (0 = no AI use, 5 = totally AI-dependent · v2.1)
0.00 / 5
· Title match
· Has AI skill
· AI skill (primary)
· AI skill (secondary)
· On AI team
· Builds AI products
vocab breakdown (legacy)
Assistants (×1):
—
Frameworks (×2):
—
Models / concepts (×3):
—
Evidence — skills matched in JD (0)
Skill cluster (0 dimension groups, role-scoped)
Status:
completed
Created: 2026-05-08T12:52:20.377377Z
Updated: 2026-05-08T12:54:07.711157Z
API 3 duration: 719 ms
Flow
Current 3-step pipeline
1 POST /skills/extract-from-jd
2 POST /skills/extract-details
3 POST /skills/final-role-output
Role
Chosen role & resolution
Data Scientist
slug: data-scientist · id: 7 · source: db
0
New skills
0
Skill↔dim saved
0
Role↔dim saved
6
Skipped
Job description
About the job Description Are you passionate about transforming customer experiences through innovative technology? Amazon is seeking a skilled Salesforce Developer to design and deliver scalable CRM solutions that drive operational excellence and customer delight at a global scale. Key job responsibilities In this role, you will architect and implement sophisticated Salesforce solutions, lead technical sprint reviews, and collaborate with cross-functional teams to optimize business processes. You'll own the full release lifecycle for application development and proactively identify opportunities for system improvements and customizations that directly impact how we serve millions of customers worldwide. A day in the life A typical day blends deep technical work — Salesforce configurations, code reviews, and system design — with strategic collaboration across business and engineering stakeholders. You'll bring both hands-on development expertise and a forward-thinking mindset to a team that thrives on continuous innovation. About The Team We are a collaborative, forward-thinking group dedicated to pushing the boundaries of customer service technology. Our team thrives on innovation, continuous learning, and making meaningful impacts at a global scale. You'll join a dynamic environment where your technical expertise and creative thinking can transform how we serve millions of customers worldwide. Basic Qualifications Experience building complex software systems that have been successfully delivered to customers Experience working with technical and business stakeholders from global cross-functional teams Experience with VisualForce, Apex Classes/Controllers, Apex Triggers development Experience leading the design, automation, deployment, and support of large-scale infrastructure Preferred Qualifications Knowledge of the capabilities and constraints of the SFDC CRM application coupled with a good understanding of HR business processes Experience implementing at least two full life cycle SFDC implementations successfully Experience in a test-driven and formal QA development environment, including development, staging, production (or equivalent) deployment cycles Experience working in an Agile or Scrum environment Our inclusive culture empowers Amazonians to deliver the best results for our customers. If you have a disability and need a workplace accommodation or adjustment during the application and hiring process, including support for the interview or onboarding process, please visit https://amazon.jobs/content/en/how-we-hire/accommodations for more information. If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner.
history_view bundle (older API). Showing raw API payloads below.
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 |
|---|---|---|---|---|---|---|
| automation | in_db |
Programming for Data Automation
programming-for-data-automation
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| QA | new |
Quality Assurance Testing
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| SFDC | new |
Salesforce Platform Development
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Salesforce | new |
Salesforce Platform Development
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Triggers | new |
Database Triggers
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Triggers | new |
Salesforce Automation Triggers
d_init_02
|
— | — | — | skill_not_in_db_v3_proposed |
Library artifacts (this run)
| Kind | Detail | DB id |
|---|---|---|
| canonical_skill_proposed | QA | type=SoftSkill subtype=quality_assurance nature=PRACTICE lifespan=EVERGREEN | |
| canonical_skill_proposed | SFDC | type=Platform subtype=crm_platform nature=PLATFORM lifespan=EVERGREEN | |
| canonical_skill_proposed | Salesforce | type=Platform subtype=crm_platform nature=PLATFORM lifespan=EVERGREEN | |
| canonical_skill_proposed | Triggers | type=Concept subtype=database_trigger nature=CONCEPT lifespan=EVERGREEN | |
| dimension_proposed | Quality Assurance Testing | |
| dimension_skill_link_proposed | QA ↔ Quality Assurance Testing | |
| dimension_proposed | Salesforce Platform Development | |
| dimension_skill_link_proposed | SFDC ↔ Salesforce Platform Development | |
| dimension_proposed | Salesforce Platform Development | |
| dimension_skill_link_proposed | Salesforce ↔ Salesforce Platform Development | |
| dimension_proposed | Database Triggers | |
| dimension_skill_link_proposed | Triggers ↔ Database Triggers | |
| dimension_proposed | Salesforce Automation Triggers | |
| dimension_skill_link_proposed | Triggers ↔ Salesforce Automation Triggers |
API 1 — extract-from-jd click to toggle
{
"filtered_unknown_words": [
"Amazon",
"Amazonians",
"Basic",
"Classes",
"Controllers",
"Description",
"Developer",
"Experience",
"HR",
"Knowledge",
"Partner",
"Preferred",
"QA",
"Qualifications",
"Recruiting",
"SFDC",
"Salesforce",
"Team",
"Triggers",
"accommodation",
"adjustment",
"application",
"boundaries",
"building",
"business",
"capabilities",
"code",
"configurations",
"constraints",
"country",
"culture",
"customer",
"customers",
"customizations",
"cycle",
"cycles",
"day",
"delight",
"deployment",
"design",
"development",
"disability",
"engineering",
"environment",
"excellence",
"experiences",
"expertise",
"global",
"group",
"hands",
"hiring",
"https://amazon.jobs/content/en/how-we-hire/accommodations",
"impacts",
"implementations",
"improvements",
"information",
"interview",
"job",
"learning",
"life",
"lifecycle",
"millions",
"mindset",
"opportunities",
"process",
"processes",
"production",
"region",
"release",
"responsibilities",
"results",
"reviews",
"role",
"service",
"software",
"solutions",
"sprint",
"stakeholders",
"support",
"system",
"systems",
"team",
"teams",
"technology",
"test",
"thinking",
"understanding",
"work",
"workplace"
],
"final_non_skills": [
"Amazon",
"Amazonians",
"Basic",
"Classes",
"Controllers",
"Description",
"Developer",
"Experience",
"HR",
"Knowledge",
"Partner",
"Preferred",
"Qualifications",
"Recruiting",
"Team",
"accommodation",
"adjustment",
"boundaries",
"building",
"business",
"capabilities",
"constraints",
"country",
"culture",
"customer",
"customers",
"customizations",
"cycle",
"cycles",
"day",
"delight",
"disability",
"excellence",
"experiences",
"expertise",
"global",
"group",
"hands",
"hiring",
"https://amazon.jobs/content/en/how-we-hire/accommodations",
"impacts",
"improvements",
"information",
"interview",
"job",
"learning",
"life",
"millions",
"mindset",
"opportunities",
"process",
"processes",
"region",
"responsibilities",
"results",
"reviews",
"role",
"software",
"sprint",
"stakeholders",
"support",
"system",
"systems",
"teams",
"technology",
"thinking",
"understanding",
"work",
"workplace"
],
"final_skills": [
"automation",
"QA",
"SFDC",
"Salesforce",
"Triggers",
"application",
"code",
"deployment",
"design",
"development",
"engineering",
"implementations",
"lifecycle",
"production",
"release",
"service",
"solutions",
"test"
],
"initial_skills": [
"automation"
],
"jd_role_hint": {
"display_name": "Salesforce Developer",
"rationale": "The excerpt centers on Salesforce solution design, Apex/Visualforce development, release lifecycle ownership, and cross-functional process optimization.",
"role_archetype": "Builds and customizes Salesforce CRM solutions, integrations, and automation for business workflows.",
"slug": "salesforce-developer"
},
"llm_non_skills": [
"Amazon",
"Amazonians",
"Basic",
"Classes",
"Controllers",
"Description",
"Developer",
"Experience",
"HR",
"Knowledge",
"Partner",
"Preferred",
"Qualifications",
"Recruiting",
"Team",
"accommodation",
"adjustment",
"boundaries",
"building",
"business",
"capabilities",
"constraints",
"country",
"culture",
"customer",
"customers",
"customizations",
"cycle",
"cycles",
"day",
"delight",
"disability",
"excellence",
"experiences",
"expertise",
"global",
"group",
"hands",
"hiring",
"https://amazon.jobs/content/en/how-we-hire/accommodations",
"impacts",
"improvements",
"information",
"interview",
"job",
"learning",
"life",
"millions",
"mindset",
"opportunities",
"process",
"processes",
"region",
"responsibilities",
"results",
"reviews",
"role",
"software",
"sprint",
"stakeholders",
"support",
"system",
"systems",
"teams",
"technology",
"thinking",
"understanding",
"work",
"workplace"
],
"llm_skills": [
"QA",
"SFDC",
"Salesforce",
"Triggers",
"application",
"code",
"deployment",
"design",
"development",
"engineering",
"implementations",
"lifecycle",
"production",
"release",
"service",
"solutions",
"test"
],
"run_id": null,
"unknown_words": [
"Amazon",
"Amazonians",
"Basic",
"Classes",
"Controllers",
"Description",
"Developer",
"Experience",
"HR",
"Knowledge",
"Partner",
"Preferred",
"QA",
"Qualifications",
"Recruiting",
"SFDC",
"Salesforce",
"Team",
"Triggers",
"accommodation",
"adjustment",
"application",
"boundaries",
"building",
"business",
"capabilities",
"code",
"configurations",
"constraints",
"country",
"culture",
"customer",
"customers",
"customizations",
"cycle",
"cycles",
"day",
"delight",
"deployment",
"design",
"development",
"disability",
"engineering",
"environment",
"excellence",
"experiences",
"expertise",
"global",
"group",
"hands",
"hiring",
"https://amazon.jobs/content/en/how-we-hire/accommodations",
"impacts",
"implementations",
"improvements",
"information",
"interview",
"job",
"learning",
"life",
"lifecycle",
"millions",
"mindset",
"opportunities",
"process",
"processes",
"production",
"region",
"release",
"responsibilities",
"results",
"reviews",
"role",
"service",
"software",
"solutions",
"sprint",
"stakeholders",
"support",
"system",
"systems",
"team",
"teams",
"technology",
"test",
"thinking",
"understanding",
"work",
"workplace"
]
}
API 2 — extract-details
{
"alias_matches": [],
"candidate_roles": [
{
"display_name": "Data Scientist",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "data-scientist",
"source": "db"
}
],
"chosen_role": {
"display_name": "Data Scientist",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "data-scientist",
"source": "single_candidate"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming for Data Automation",
"id": 93,
"rationale": "Lightweight scripting used to automate repetitive analysis tasks, data preparation, and report generation. This is a useful split because data scientists often need practical automation without owning full pipelines.",
"slug": "programming-for-data-automation",
"source": "db"
},
"input_skill": "automation",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Scientist",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "data-scientist",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Quality Assurance Testing",
"id": null,
"rationale": "Validating software behavior against requirements through manual and exploratory testing. QA belongs here because it commonly refers to the role of checking functionality, finding defects, and confirming fixes before release.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "QA",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Salesforce Platform Development",
"id": null,
"rationale": "Covers building and customizing solutions on the Salesforce platform. SFDC belongs here because it commonly refers to Salesforce development work across objects, automation, UI, and Apex-based business logic.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SFDC",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Salesforce Platform Development",
"id": null,
"rationale": "Building and customizing business applications on the Salesforce platform. This covers declarative and programmatic development used by a Salesforce Developer to implement objects, automation, UI, and integrations.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Salesforce",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Database Triggers",
"id": null,
"rationale": "Database triggers are procedural actions that run automatically in response to data changes or other table events. This skill belongs here when it refers to trigger logic, timing, and side effects tied to inserts, updates, deletes, or schema events in a database platform such as Salesforce-backed data handling.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Triggers",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Salesforce Automation Triggers",
"id": null,
"rationale": "Salesforce automation triggers cover event-driven logic used to enforce business rules and automate record processing inside the Salesforce platform. This dimension fits the target skill because Salesforce developers commonly implement triggers to react to record changes and coordinate downstream actions.",
"slug": "d_init_02",
"source": "llm"
},
"input_skill": "Triggers",
"llm_role": null,
"roles_from_db": []
}
],
"input_final_skills": [
"automation",
"QA",
"SFDC",
"Salesforce",
"Triggers",
"application",
"code",
"deployment",
"design",
"development",
"engineering",
"implementations",
"lifecycle",
"production",
"release",
"service",
"solutions",
"test"
],
"input_llm_skills": [
"QA",
"SFDC",
"Salesforce",
"Triggers",
"application",
"code",
"deployment",
"design",
"development",
"engineering",
"implementations",
"lifecycle",
"production",
"release",
"service",
"solutions",
"test"
],
"new_aliases_persisted": 0,
"run_id": "2f36746a-f68a-49c2-b646-3c524dd0b9ee",
"skills_detail": [
{
"aliases_in_db": [
{
"alias_text": "automation",
"alias_type": "CANONICAL",
"id": 851,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 2,
"display_name": "automation",
"id": 553,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "automation",
"sub_category_id": 397,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming for Data Automation",
"id": 93,
"rationale": "Lightweight scripting used to automate repetitive analysis tasks, data preparation, and report generation. This is a useful split because data scientists often need practical automation without owning full pipelines.",
"slug": "programming-for-data-automation",
"source": "db"
},
"input_skill": "automation",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Scientist",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "data-scientist",
"source": "db"
}
]
}
],
"input_skill": "automation",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": false
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Quality Assurance Testing",
"id": null,
"rationale": "Validating software behavior against requirements through manual and exploratory testing. QA belongs here because it commonly refers to the role of checking functionality, finding defects, and confirming fixes before release.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "QA",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "QA",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "SoftSkill",
"skill_nature": "PRACTICE",
"sub_category": "quality_assurance",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"quality_assurance"
],
"reasoning": "\"QA\" is a common abbreviation for quality assurance, but in JDs it can also mean quality analyst or QA testing roles; the catalog likely contains the fuller quality_assurance skill, so an extractor could conflate them."
},
"context_keywords": {
"context_keywords": [
"test cases",
"test plans",
"defect tracking",
"bug triage",
"regression testing",
"UAT",
"test automation",
"manual testing",
"acceptance criteria",
"test scripts",
"JIRA",
"Selenium",
"test coverage",
"smoke testing",
"traceability matrix"
]
},
"maturity": {
"confidence": 0.93,
"maturity": "well_known",
"reasoning": "QA appears in a large share of software job descriptions and is a standard hiring requirement across manual and automation roles; market demand is broad rather than niche."
},
"skill_id": "qa",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Validating software behavior against requirements through manual and exploratory testing. QA belongs here because it commonly refers to the role of checking functionality, finding defects, and confirming fixes before release.",
"exemplar_skills": [
"QA",
"manual testing",
"test case design",
"test execution",
"regression testing",
"exploratory testing",
"smoke testing"
],
"in_scope": "QA, manual testing, test case design, test execution, regression testing, smoke testing, exploratory testing, acceptance testing, defect reproduction, test evidence",
"name": "Quality Assurance Testing",
"out_of_scope": "Automated API checks, unit test frameworks, and CI test pipelines, which belong to automation-focused testing dimensions; production monitoring and incident response, which belong to operational reliability dimensions.",
"overlap_flags": [
{
"reason": "QA may include API validation, but automated service-level verification is owned by the automation dimension.",
"with_dim_id": "api-and-service-test-automation",
"with_dim_name": null,
"with_role": "Automation Tester"
},
{
"reason": "QA can touch test tooling, but framework development and automation are a separate skill cluster.",
"with_dim_id": "testing-and-automation-frameworks",
"with_dim_name": null,
"with_role": "iOS Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "QA",
"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": "qa"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"acceptance-criteria-checks",
"acceptance-criteria-validation",
"test-case-authoring",
"defect-retest",
"risk-based-testing",
"cross-browser-testing",
"session-based-testing",
"charter-based-testing"
],
"requires": [],
"skill_id": "qa",
"suppress_on_match": []
},
"skill_id": "qa",
"split_log": [],
"typed": {
"alternatives_considered": [
"Methodology: ruled out \u2014 QA is broader than a specific process like TDD or Scrum, but it is still closer to a working practice than a technical tool.",
"Concept: ruled out \u2014 QA is not primarily a named theory or principle to know, but an operational discipline."
],
"confidence": 0.67,
"name": "QA",
"reasoning": "QA is best treated as a quality-assurance practice/role rather than a software artifact, and under the Concept vs Methodology rule it fits a way of working more than a knowledge unit.",
"skill_id": "qa",
"subtype": "quality_assurance",
"type": "SoftSkill"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Salesforce Platform Development",
"id": null,
"rationale": "Covers building and customizing solutions on the Salesforce platform. SFDC belongs here because it commonly refers to Salesforce development work across objects, automation, UI, and Apex-based business logic.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SFDC",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "SFDC",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Platform",
"skill_nature": "PLATFORM",
"sub_category": "crm_platform",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"salesforce"
],
"reasoning": "SFDC is a common abbreviation for Salesforce, so a JD mention could be extracted as the broader Salesforce skill in the catalog."
},
"context_keywords": {
"context_keywords": [
"Sales Cloud",
"Service Cloud",
"Apex",
"Visualforce",
"Lightning",
"LWC",
"SOQL",
"SOSL",
"Flow Builder",
"Process Builder",
"Salesforce CPQ",
"Salesforce API",
"Einstein Analytics",
"AppExchange",
"sandbox"
]
},
"maturity": {
"confidence": 0.93,
"maturity": "well_known",
"reasoning": "Salesforce (SFDC) is a common CRM platform in enterprise job postings and partner ecosystems, with broad hiring demand across admin, dev, and ops roles."
},
"skill_id": "sfdc",
"vendor_license": {
"confidence": 0.98,
"license": "proprietary",
"vendor": "Salesforce",
"year_introduced": 1999
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers building and customizing solutions on the Salesforce platform. SFDC belongs here because it commonly refers to Salesforce development work across objects, automation, UI, and Apex-based business logic.",
"exemplar_skills": [
"SFDC",
"Salesforce",
"Apex",
"Lightning Web Components",
"Visualforce",
"SOQL",
"SOSL",
"Salesforce Flows",
"Salesforce Triggers"
],
"in_scope": "SFDC, Salesforce, Apex, Lightning Web Components, Visualforce, SOQL, SOSL, triggers, flows, process automation, custom objects, validation rules, platform events",
"name": "Salesforce Platform Development",
"out_of_scope": "ServiceNow instance administration and workflows, generic CRM business analysis, non-Salesforce cloud architecture, mobile app development, backend services not built on Salesforce",
"overlap_flags": [
{
"reason": "Salesforce implementations often integrate with external services and APIs, but this dimension owns the platform-specific build work.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": "Backend Engineer"
},
{
"reason": "Salesforce role, profile, and permission setup can overlap with access administration, but platform development is the primary anchor here.",
"with_dim_id": "identity-and-access-configuration",
"with_dim_name": null,
"with_role": "ServiceNOW Developer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "SFDC",
"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": "sfdc"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [],
"requires": [],
"skill_id": "sfdc",
"suppress_on_match": []
},
"skill_id": "sfdc",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.93,
"name": "SFDC",
"reasoning": "SFDC refers to Salesforce, which is a hosted multi-tenant environment with APIs and managed services, so by the Platform vs Tool rule it is a Platform.",
"skill_id": "sfdc",
"subtype": "crm_platform",
"type": "Platform"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Salesforce Platform Development",
"id": null,
"rationale": "Building and customizing business applications on the Salesforce platform. This covers declarative and programmatic development used by a Salesforce Developer to implement objects, automation, UI, and integrations.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Salesforce",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Salesforce",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Platform",
"skill_nature": "PLATFORM",
"sub_category": "crm_platform",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "Salesforce is a well-known, specific CRM platform name. In typical JDs it is unlikely to be confused with a different catalog skill."
},
"context_keywords": {
"context_keywords": [
"Apex",
"Visualforce",
"Lightning Web Components",
"SOQL",
"SOSL",
"Sales Cloud",
"Service Cloud",
"Flow Builder",
"Process Builder",
"Salesforce CPQ",
"Salesforce Service Cloud",
"Einstein Analytics",
"AppExchange",
"Salesforce DX",
"MuleSoft"
]
},
"maturity": {
"confidence": 0.96,
"maturity": "well_known",
"reasoning": "Salesforce appears in high-volume job postings across sales ops, admin, and CRM engineering roles, and has a large ecosystem of certified roles and AppExchange partners."
},
"skill_id": "salesforce",
"vendor_license": {
"confidence": 0.99,
"license": "proprietary",
"vendor": "Salesforce, Inc.",
"year_introduced": 1999
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Building and customizing business applications on the Salesforce platform. This covers declarative and programmatic development used by a Salesforce Developer to implement objects, automation, UI, and integrations.",
"exemplar_skills": [
"Salesforce",
"Apex",
"Lightning Web Components",
"Visualforce",
"SOQL",
"SOSL",
"Salesforce DX",
"Salesforce Flows"
],
"in_scope": "Salesforce, Apex, Lightning Web Components, Visualforce, Salesforce objects and fields, Flows and Process Builder, triggers, SOQL and SOSL, custom metadata, platform events, Salesforce DX",
"name": "Salesforce Platform Development",
"out_of_scope": "ServiceNow instance configuration and workflows, generic frontend styling outside Salesforce UI frameworks, cloud infrastructure administration, non-Salesforce CRM administration",
"overlap_flags": [
{
"reason": "Salesforce implementations often integrate with external services and APIs, but the core skill here is platform-specific app development.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": "Backend Engineer"
},
{
"reason": "Salesforce roles, profiles, and permission sets can overlap with access configuration, but that dimension owns general access administration.",
"with_dim_id": "identity-and-access-configuration",
"with_dim_name": null,
"with_role": "ServiceNOW Developer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Salesforce",
"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": "salesforce"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [],
"requires": [],
"skill_id": "salesforce",
"suppress_on_match": []
},
"skill_id": "salesforce",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "Salesforce",
"reasoning": "By the Platform vs Tool rule, Salesforce is a hosted multi-tenant environment with APIs and managed services, not software you run locally.",
"skill_id": "salesforce",
"subtype": "crm_platform",
"type": "Platform"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Database Triggers",
"id": null,
"rationale": "Database triggers are procedural actions that run automatically in response to data changes or other table events. This skill belongs here when it refers to trigger logic, timing, and side effects tied to inserts, updates, deletes, or schema events in a database platform such as Salesforce-backed data handling.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Triggers",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Salesforce Automation Triggers",
"id": null,
"rationale": "Salesforce automation triggers cover event-driven logic used to enforce business rules and automate record processing inside the Salesforce platform. This dimension fits the target skill because Salesforce developers commonly implement triggers to react to record changes and coordinate downstream actions.",
"slug": "d_init_02",
"source": "llm"
},
"input_skill": "Triggers",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Triggers",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concept",
"skill_nature": "CONCEPT",
"sub_category": "database_trigger",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "In JDs, \"triggers\" usually clearly refers to database triggers; the term is specific enough and not commonly confused with another catalog skill."
},
"context_keywords": {
"context_keywords": [
"stored procedures",
"PL/SQL",
"T-SQL",
"BEFORE INSERT",
"AFTER UPDATE",
"row-level",
"statement-level",
"cascade",
"audit logging",
"change data capture",
"referential integrity",
"event-driven",
"trigger recursion",
"INSTEAD OF",
"database events"
]
},
"maturity": {
"confidence": 0.93,
"maturity": "well_known",
"reasoning": "Triggers are a standard SQL feature across major databases and appear routinely in DBA/backend job descriptions; they\u2019re widely supported by PostgreSQL, MySQL, SQL Server, and Oracle rather than being a niche add-on."
},
"skill_id": "triggers",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Database triggers are procedural actions that run automatically in response to data changes or other table events. This skill belongs here when it refers to trigger logic, timing, and side effects tied to inserts, updates, deletes, or schema events in a database platform such as Salesforce-backed data handling.",
"exemplar_skills": [
"Triggers",
"Apex triggers",
"before insert triggers",
"after update triggers",
"bulk-safe trigger design",
"trigger recursion control"
],
"in_scope": "Triggers, before insert triggers, before update triggers, after insert triggers, after update triggers, after delete triggers, Apex trigger logic, trigger contexts, recursion control, bulk-safe trigger design",
"name": "Database Triggers",
"out_of_scope": "Workflow automation, approval routing, screen flows, process builder, scheduled jobs, validation rules, these belong to business process automation or declarative platform configuration rather than database event handlers",
"overlap_flags": [
{
"reason": "Trigger-driven side effects can overlap with backend event handling, but this dimension is specifically about database event hooks.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": "Backend Engineer"
}
],
"tentative_id": "d_init_01"
},
{
"description": "Salesforce automation triggers cover event-driven logic used to enforce business rules and automate record processing inside the Salesforce platform. This dimension fits the target skill because Salesforce developers commonly implement triggers to react to record changes and coordinate downstream actions.",
"exemplar_skills": [
"Triggers",
"Apex triggers",
"trigger frameworks",
"trigger handlers",
"order of execution",
"bulk processing"
],
"in_scope": "Triggers, Apex triggers, trigger frameworks, trigger handlers, record change automation, bulk processing, order of execution, governor-limit-aware trigger design",
"name": "Salesforce Automation Triggers",
"out_of_scope": "Flows, process automation, approval processes, validation rules, page layouts, these are declarative Salesforce automation or UI configuration rather than Apex trigger code",
"overlap_flags": [
{
"reason": "Both involve Salesforce platform behavior, but triggers are developer-authored automation rather than instance setup.",
"with_dim_id": "platform-administration-and-instance-setup",
"with_dim_name": null,
"with_role": "ServiceNOW Developer"
}
],
"tentative_id": "d_init_02"
}
],
"merge_log": [],
"placed": {
"name": "Triggers",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 2 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [
"d_init_02"
],
"skill_id": "triggers"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"onchange-scripts",
"onsubmit-scripts",
"onload-scripts",
"dispatchers",
"notifications",
"feature-flags",
"health-checks",
"task-assignment-rules"
],
"requires": [],
"skill_id": "triggers",
"suppress_on_match": []
},
"skill_id": "triggers",
"split_log": [],
"typed": {
"alternatives_considered": [
"Architecture: ruled out \u2014 triggers are not a system-shape pattern.",
"Tool: ruled out \u2014 triggers are not software operated by a user.",
"Methodology: ruled out \u2014 triggers describe a mechanism, not a way of working."
],
"confidence": 0.78,
"name": "Triggers",
"reasoning": "By the Concept vs Methodology rule, triggers are a named database behavior/pattern for reacting to data changes, not a standalone tool, language, or format.",
"skill_id": "triggers",
"subtype": "database_trigger",
"type": "Concept"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "application",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "code",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "deployment",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "design",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "development",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "engineering",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "implementations",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "lifecycle",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "production",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "release",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "service",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "solutions",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "test",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"QA",
"SFDC",
"Salesforce",
"Triggers"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "Data Scientist",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "data-scientist",
"source": "db"
},
"final_input_skills": [
{
"skill": "automation",
"tag": "in_db"
},
{
"skill": "QA",
"tag": "new"
},
{
"skill": "SFDC",
"tag": "new"
},
{
"skill": "Salesforce",
"tag": "new"
},
{
"skill": "Triggers",
"tag": "new"
},
{
"skill": "application",
"tag": "new"
},
{
"skill": "code",
"tag": "new"
},
{
"skill": "deployment",
"tag": "new"
},
{
"skill": "design",
"tag": "new"
},
{
"skill": "development",
"tag": "new"
},
{
"skill": "engineering",
"tag": "new"
},
{
"skill": "implementations",
"tag": "new"
},
{
"skill": "lifecycle",
"tag": "new"
},
{
"skill": "production",
"tag": "new"
},
{
"skill": "release",
"tag": "new"
},
{
"skill": "service",
"tag": "new"
},
{
"skill": "solutions",
"tag": "new"
},
{
"skill": "test",
"tag": "new"
}
],
"persistence": {
"items": [
{
"chosen_role_id": 7,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming for Data Automation",
"id": 93,
"rationale": "Lightweight scripting used to automate repetitive analysis tasks, data preparation, and report generation. This is a useful split because data scientists often need practical automation without owning full pipelines.",
"slug": "programming-for-data-automation",
"source": "db"
},
"dimension_id": 93,
"input_skill": "automation",
"llm_role": null,
"matched_chosen_role": true,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Data Scientist",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "data-scientist",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 553,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 7,
"dimension": {
"difficulty_hint": null,
"display_name": "Quality Assurance Testing",
"id": null,
"rationale": "Validating software behavior against requirements through manual and exploratory testing. QA belongs here because it commonly refers to the role of checking functionality, finding defects, and confirming fixes before release.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "QA",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 7,
"dimension": {
"difficulty_hint": null,
"display_name": "Salesforce Platform Development",
"id": null,
"rationale": "Covers building and customizing solutions on the Salesforce platform. SFDC belongs here because it commonly refers to Salesforce development work across objects, automation, UI, and Apex-based business logic.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "SFDC",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 7,
"dimension": {
"difficulty_hint": null,
"display_name": "Salesforce Platform Development",
"id": null,
"rationale": "Building and customizing business applications on the Salesforce platform. This covers declarative and programmatic development used by a Salesforce Developer to implement objects, automation, UI, and integrations.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Salesforce",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 7,
"dimension": {
"difficulty_hint": null,
"display_name": "Database Triggers",
"id": null,
"rationale": "Database triggers are procedural actions that run automatically in response to data changes or other table events. This skill belongs here when it refers to trigger logic, timing, and side effects tied to inserts, updates, deletes, or schema events in a database platform such as Salesforce-backed data handling.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Triggers",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 7,
"dimension": {
"difficulty_hint": null,
"display_name": "Salesforce Automation Triggers",
"id": null,
"rationale": "Salesforce automation triggers cover event-driven logic used to enforce business rules and automate record processing inside the Salesforce platform. This dimension fits the target skill because Salesforce developers commonly implement triggers to react to record changes and coordinate downstream actions.",
"slug": "d_init_02",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Triggers",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
}
],
"new_skills_created": 0,
"role_dimension_saved": 0,
"skill_dimension_saved": 0,
"skipped": 6
},
"planner_output": null,
"run_id": "2f36746a-f68a-49c2-b646-3c524dd0b9ee"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.
Loading…