Pipeline run
8d18a030-892f-473f-bb91-e976096f443e
Pipeline LLM cost (USD)
API 1: $0.0116
API 2: $0.0005
API 3: $0.0000
Total: $0.0121
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
Native mobile development with Android, Git, and REST is a common, well-established stack that is widely used but not typically categorized as cloud-native or legacy.
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 (23)
Android SDK
Android
REST
Git
Continuous Integration
Linux
Scripting
Push Notifications
Offline Storage
Threading
Performance Tuning
Benchmarking
Optimization
Sensors
Gyroscope
Accelerometer
Cloud Message APIs
Android UI Design Principles
Android Design Principles
Interface Guidelines
Backup
System Monitoring
Disaster Recovery
Skill cluster (5 dimension groups, role-scoped)
Device APIs and Hardware Features
Sensors
Integration Protocols & Standards
REST
Performance and Resource Tuning
Benchmarking
Push Notifications and Deep Links
Push Notifications
Cross-cutting / unaligned
Android SDK
Android
Git
Continuous Integration
Linux
Scripting
Offline Storage
Threading
Performance Tuning
Optimization
Gyroscope
Accelerometer
Cloud Message APIs
Android UI Design Principles
Android Design Principles
Interface Guidelines
Backup
System Monitoring
Disaster Recovery
Signals
Skill
full-stack-engineer
0.17
Alias
—
—
KRA
flutter-developer
0.50
Post-classification
Centroidupdated · n=62
Alias collision log—
New-role queue—
New skills captured15
New KRA captured—
Captured for admin review
Android SDK
primary
↔
Native Mobile Developer
pending
Continuous Integration
primary
↔
Native Mobile Developer
pending
Linux
primary
↔
Native Mobile Developer
pending
Scripting
↔
Native Mobile Developer
pending
Offline Storage
↔
Native Mobile Developer
pending
Performance Tuning
↔
Native Mobile Developer
pending
Optimization
↔
Native Mobile Developer
pending
Gyroscope
↔
Native Mobile Developer
pending
Cloud Message APIs
↔
Native Mobile Developer
pending
Android UI Design Principles
↔
Native Mobile Developer
pending
Android Design Principles
↔
Native Mobile Developer
pending
Interface Guidelines
↔
Native Mobile Developer
pending
Backup
↔
Native Mobile Developer
pending
System Monitoring
↔
Native Mobile Developer
pending
Disaster Recovery
↔
Native Mobile Developer
pending
Status:
completed
Created: 2026-05-27T15:26:36.159723Z
Updated: 2026-06-12T16:29:40.291965Z
API 3 duration: 29858 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
Native Mobile Developer
→Android Developer
sub-role · 0.99 domain · Software Engineering CASE DOMAINslug: native-mobile-developer · id: 75 · source: db · sub-role slug: android-engineer
Domain=Software Engineering → sub-role android-engineer; The JD is clearly for an Android app developer focused on native mobile development, SDKs, UI, APIs, storage, performance, and mobile tooling.
Matched skills
Android SDKRESTful APIsAndroid UI design principlesoffline storagethreadingperformance tuningtouchgyroscopesaccelerometerscloud message APIspush notificationsGitcontinuous integrationLinuxscripting
Matched dimensions
Android Native Mobile DevelopmentMobile UI/UX ImplementationAPI IntegrationOffline-first Mobile EngineeringMobile Performance OptimizationMobile DevOps and Version ControlReliability and MaintainabilityCross-functional Collaboration
Matched KRAs
Connect Android applications to back-end servicesDesign applications around natural user interfacesSupport different screen sizesBenchmarking and optimizationBuild applications with emphasis on performance, scalabilityComplete the development activities on scheduleCollaborate with clients and other teams
Resolution:
in_db
— role exists in library; skill↔dim and role↔dim links saved when applicable.
0
New skills
0
Skill↔dim saved
0
Role↔dim saved
1
Skipped
Job description
1. Strong knowledge of Android SDK, different versions of Android, and how to deal with different screen sizes 2. Familiarity with RESTful APIs to connect Android applications to back-end services 3. Strong knowledge of Android UI design principles, patterns, and best practices 4. Experience with offline storage, threading, and performance tuning 5. Ability to design applications around natural user interfaces, such as touch 6. Familiarity with the use of additional sensors, such as gyroscopes and accelerometers 7. Knowledge of the open-source Android ecosystem and the libraries available for common tasks 8. Familiarity with cloud message APIs and push notifications 9. A knack for benchmarking and optimization 10. Understanding of Googles Android design principles and interface guidelines 11. Proficient understanding of code versioning tools – Git 12. Familiarity with continuous integration 13. Experience designing and building applications with an emphasis on performance, scalability, high-reliability and maintainability. 14. Learn, suggest and implement new technologies/techniques. 15. Complete the development activities on schedule with high quality. 16. Should demonstrate excellent Interpersonal skills and should be able to collaborate with clients and other teams. Desired Profile:- Qualification:- B.E/B.Tech or any equivalent Strong written and verbal English communication & presentation skills Must have good management skills Good task and priority management skills Quality conscious and efficiency oriented & multitasking Self-management and professional approach. Understanding of backup process, system monitoring, performance tuning, disaster recovery, and scripting for Linux Ability to adapt to a dynamic work environment and must be able to multi-task and work with minimal guidance Keen desire to learn and incorporate new tools & technologies & share with the team Experience: 4+ years Behavioural Competencies: - • Decision making ability • Analytical ability • People Management • Ownership • Innovation
Skills from this JD
Each row merges API 1 extraction, API 2 library match / v3 orchestration (dimensions + locked dims), and API 3 persistence tags.
Android SDK
Primary
New / orchestrated
API 3: new canonical path (new)
New / unmatched skill (orchestrated in API 2)
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
Derived legacy fields
- Category
- Mobile Development
- Sub-category
- general
- Skill nature
- TOOL
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Android
Primary
Library skill
API 3: existing canonical (in_db)
Existing skill (matched library)
Canonical: Android
id=1595
· android
Aliases — catalog
- Android (CANONICAL)
Context tags (catalog)
API Level
Android SDK
Android Studio
Firebase
Gradle
Java
Jetpack
Kotlin
LiveData
MVVM
Material Design
RecyclerView
Retrofit
Room
XML
Stored enrichment (catalog DB)
- Category
- Platform
- Sub-category
- Mobile Platform
- Vendor
- License
- apache_2
- Year introduced
- 2008
- Confidence
- 0.95
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Android appears in large volumes of mobile job postings and remains a standard platform in hiring pipelines; Google continues active platform releases and OEM ecosystem support, indicating broad adoption.
Skill profile (library / DB)
- Skill nature
- PLATFORM
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 9
- Sub-category id
- 1201
- 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) |
REST
Primary
Library skill
API 3: existing canonical (in_db)
Existing skill (matched library)
Canonical: REST
id=11
· rest
Aliases — catalog
- REST (CANONICAL) primary
Context tags (catalog)
API
API design
API versioning
CRUD
DELETE
GET
HATEOAS
HTTP
JSON
OAuth
OAuth2
OpenAPI
POST
PUT
Postman
RESTful
Swagger
URI
Webhooks
XML
authentication
client-server
content negotiation
endpoint
endpoints
middleware
resource
resource-oriented
serialization
stateless
status codes
versioning
web services
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Api Architecture Style
- Year introduced
- 2000
- Confidence
- 0.88
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: REST is a default API architecture in many job descriptions and is widely supported by major vendors/frameworks; OpenAPI and RESTful endpoints remain standard in hiring pipelines.
Skill profile (library / DB)
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 2
- Sub-category id
- 2122
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
API Design and Contracts Catalog dimension db id 3
Library dimension (catalog)
Roles linked in library: Backend Developer, Fullstack Developer, Fullstack Developer
-
API Interface and Contract Design Catalog dimension db id 289
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Go Backend Developer, Kotlin Backend Developer, Node.js Backend Developer, PHP Backend Developer, Python Backend Developer, Ruby Backend Developer, Scala Backend Developer
-
Integration Protocols & Standards Catalog dimension db id 271
Library dimension (catalog)
Roles linked in library: Pega Developer
-
Standards, Protocols & Compliance Catalog dimension db id 452
Library dimension (catalog)
Roles linked in library: Engineering Manager, Sitecore Dev
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
API Design and Contracts
api-design-and-contracts
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
API Interface and Contract Design
api-interface-and-contract-design
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Integration Protocols & Standards
integration-protocols-standards
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Standards, Protocols & Compliance
standards-protocols-compliance
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Git
Primary
Library skill
API 3: existing canonical (in_db)
Existing skill (matched library)
Canonical: Git
id=1002
· git
Aliases — catalog
- Git (CANONICAL)
Context tags (catalog)
CI/CD
GitHub
GitLab
branching
checkout
clone
commit
fork
merging
pull request
rebase
remote
repository
stash
versioning
Stored enrichment (catalog DB)
- Category
- Tool
- Sub-category
- Version Control Tool
- Vendor
- Linus Torvalds
- License
- gpl_v2
- Year introduced
- 2005
- Confidence
- 0.99
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Git is a hiring-pipeline staple: it appears in the vast majority of software engineering job descriptions and is the default VCS on GitHub/GitLab/Bitbucket.
Skill profile (library / DB)
- Skill nature
- TOOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 13
- Sub-category id
- 730
- 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) |
Continuous Integration
Primary
New / orchestrated
API 3: new canonical path (new)
New / unmatched skill (orchestrated in API 2)
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
Derived legacy fields
- Category
- Software Development Practices
- Sub-category
- general
- Skill nature
- PRACTICE
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Linux
Primary
New / orchestrated
API 3: new canonical path (new)
New / unmatched skill (orchestrated in API 2)
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
Derived legacy fields
- Category
- Operating Systems
- Sub-category
- general
- Skill nature
- TOOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Version strategy
- UNVERSIONED
Scripting
Secondary
New / orchestrated
API 3: new canonical path (new)
New / unmatched skill (orchestrated in API 2)
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
Derived legacy fields
- Category
- Programming Languages
- Sub-category
- general
- Skill nature
- LANGUAGE
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Push Notifications
Secondary
Library skill
API 3: existing canonical (in_db)
Existing skill (matched library)
Canonical: push notifications
id=1605
· push-notifications
Aliases — catalog
- push notifications (CANONICAL) primary
- Push Notifications (CANONICAL)
Context tags (catalog)
A/B testing
APNs
Firebase Cloud Messaging
analytics
background updates
delivery tracking
message queue
mobile push
notification center
notification channels
notification payload
opt-in
push analytics
real-time updates
rich notifications
scheduling
service workers
subscription model
user engagement
user segmentation
web push
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Notification Delivery Concept
- Confidence
- 0.88
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Push notifications are a standard mobile/web capability and appear routinely in JDs for iOS, Android, and frontend roles; major vendors like Apple APNs and Firebase Cloud Messaging actively support them.
Skill profile (library / DB)
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 2
- Sub-category id
- 2134
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Background Execution and Lifecycle Catalog dimension db id 87
Library dimension (catalog)
Roles linked in library: Hybrid Mobile Developer, React Native Developer, iOS Developer
-
Push Notifications and Deep Links Catalog dimension db id 320
Library dimension (catalog)
Roles linked in library: Ionic Developer, React Native Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Background Execution and Lifecycle
background-execution-and-lifecycle
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Push Notifications and Deep Links
push-notifications-and-deep-links
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Offline Storage
Secondary
New / orchestrated
API 3: new canonical path (new)
New / unmatched skill (orchestrated in API 2)
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
Derived legacy fields
- Category
- Mobile Development
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Threading
Secondary
Library skill
API 3: existing canonical (in_db)
Existing skill (matched library)
Canonical: threading
id=2349
· threading
Aliases — catalog
- threading (CANONICAL) primary
Context tags (catalog)
GIL
asynchronous
concurrent programming
context switching
deadlock
lock-free
multithreading
mutex
parallelism
race condition
semaphore
synchronization
task scheduling
thread pool
thread-safe
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Concurrency Concept
- Confidence
- 0.93
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Threading is a core concurrency concept in most mainstream languages and appears routinely in job descriptions for backend, systems, and desktop roles; it’s a standard interview topic rather than a niche tool.
Skill profile (library / DB)
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 2
- Sub-category id
- 7
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Concurrency and Async Workflows Catalog dimension db id 292
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Python Backend Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Concurrency and Async Workflows
concurrency-and-async-workflows
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Performance Tuning
Secondary
Library skill
API 3: existing canonical (in_db)
Existing skill (matched library)
Canonical: query tuning
id=3553
· query-tuning
Aliases — catalog
- query tuning (CANONICAL) primary
- Query Tuning (CANONICAL)
Context tags (catalog)
SQL
SQL optimization
caching
cost estimation
cost-based optimization
data retrieval
database indexing
database optimization
database performance
database profiling
database statistics
database tuning
execution plan
execution time
indexing
join strategies
load balancing
parameter sniffing
query analysis
query complexity
query execution
query performance
query profiling
query rewriting
resource allocation
resource utilization
statistics
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Query Optimization
- Confidence
- 0.82
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Common in DB/analytics job descriptions and vendor docs; PostgreSQL, MySQL, SQL Server, and Oracle all expose EXPLAIN/ANALYZE and tuning guides, showing broad hiring-pipeline demand.
Skill profile (library / DB)
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 2
- Sub-category id
- 3067
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Relational Database Design Catalog dimension db id 4
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Backend Developer, Kotlin Backend Developer, Node.js Backend Developer, Python Backend Developer, Ruby Backend Developer, Scala Backend Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Relational Database Design
relational-database-design
|
— | — |
Skipped — no persistable v3 meta for new skill
skill_not_in_db_v3_proposed
|
Benchmarking
Secondary
Library skill
API 3: existing canonical (in_db)
Existing skill (matched library)
Canonical: benchmarking
id=52
· benchmarking
Aliases — catalog
- benchmarking (CANONICAL) primary
Context tags (catalog)
A/B testing
SLA
baseline
benchmark suite
bottleneck
capacity planning
comparison analysis
data analysis
key performance indicators
latency
latency assessment
load testing
microbenchmark
p95
p99
performance analysis
performance baseline
performance metrics
performance profiling
performance tuning
profiling
regression testing
resource utilization
response time
result visualization
scalability
scalability testing
stress testing
system optimization
test automation
throughput
throughput measurement
Stored enrichment (catalog DB)
- Category
- Methodology
- Sub-category
- Benchmarking Process
- Confidence
- 0.90
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Benchmarking is a standard performance-validation practice in JDs for software, data, and ML roles; it appears alongside profiling, load testing, and SLA work across major employers, indicating broad hiring-pipeline adoption.
Skill profile (library / DB)
- Skill nature
- METHODOLOGY
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 8
- Sub-category id
- 3547
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Backend Service Performance and Scalability Tuning Catalog dimension db id 389
Library dimension (catalog)
Roles linked in library: Kotlin Backend Developer, Scala Backend Developer
-
Performance and Resource Tuning Catalog dimension db id 373
Library dimension (catalog)
Roles linked in library: Go Backend Developer
-
Performance and Scalability Tuning Catalog dimension db id 11
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Backend Developer, Node.js Backend Developer, PHP Backend Developer, Python Backend Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Backend Service Performance and Scalability Tuning
backend-service-performance-and-scalability-tuning
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Performance and Resource Tuning
performance-and-resource-tuning
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Performance and Scalability Tuning
performance-and-scalability-tuning
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Optimization
Secondary
New / orchestrated
API 3: new canonical path (new)
New / unmatched skill (orchestrated in API 2)
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
Derived legacy fields
- Category
- Software Development
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Sensors
Secondary
Library skill
API 3: existing canonical (in_db)
Existing skill (matched library)
Canonical: sensors
id=992
· sensors
Aliases — catalog
- sensors (CANONICAL) primary
Context tags (catalog)
IoT
actuators
analog sensors
calibration
data acquisition
digital sensors
embedded systems
environmental monitoring
machine learning
real-time data
real-time monitoring
sensor fusion
sensor integration
sensor networks
signal processing
smart devices
wireless sensors
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Hardware Interaction Concept
- Confidence
- 0.78
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Sensors are broadly used across IoT, robotics, automotive, and industrial roles; job postings commonly list sensor integration alongside embedded systems and hardware interfaces.
Skill profile (library / DB)
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 2
- Sub-category id
- 1510
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Device APIs and Hardware Features Catalog dimension db id 95
Library dimension (catalog)
Roles linked in library: Android Developer, Native Mobile Developer, iOS Developer
-
Device APIs and Hardware Integration Catalog dimension db id 171
Library dimension (catalog)
Roles linked in library: Hybrid Mobile Developer, React Native Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Device APIs and Hardware Features
device-apis-and-hardware-features
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
|
Device APIs and Hardware Integration
device-apis-and-hardware-integration
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Gyroscope
Secondary
New / orchestrated
API 3: new canonical path (new)
New / unmatched skill (orchestrated in API 2)
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
Derived legacy fields
- Category
- Mobile Sensors
- Sub-category
- general
- Skill nature
- TOOL
- Volatility
- FAST
- Typical lifespan
- SHORT_LIVED
- Version strategy
- VERSIONED
Accelerometer
Secondary
Library skill
API 3: existing canonical (in_db)
Existing skill (matched library)
Canonical: accelerometer
id=3494
· accelerometer
Aliases — catalog
- accelerometer (CANONICAL) primary
Context tags (catalog)
3D motion
IoT devices
MEMS
automotive applications
calibration
data acquisition
gesture recognition
navigation systems
real-time monitoring
robotics
sensor fusion
signal processing
stability control
vibration analysis
wearable technology
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Sensor Concept
- Confidence
- 0.90
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Accelerometer appears in embedded/IoT and mobile hardware JDs, but far less often than mainstream software skills; market demand is concentrated in sensor, robotics, and device teams rather than broad hiring pipelines.
Skill profile (library / DB)
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 2
- Sub-category id
- 2709
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Device Capabilities and Sensors Catalog dimension db id 379
Library dimension (catalog)
Roles linked in library: Ionic Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Device Capabilities and Sensors
device-capabilities-and-sensors
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Cloud Message APIs
Secondary
New / orchestrated
API 3: new canonical path (new)
New / unmatched skill (orchestrated in API 2)
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
Derived legacy fields
- Category
- Cloud Services
- Sub-category
- general
- Skill nature
- TOOL
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Android UI Design Principles
Secondary
New / orchestrated
API 3: new canonical path (new)
New / unmatched skill (orchestrated in API 2)
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
Derived legacy fields
- Category
- Mobile Development
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Android Design Principles
Secondary
New / orchestrated
API 3: new canonical path (new)
New / unmatched skill (orchestrated in API 2)
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
Derived legacy fields
- Category
- Mobile Development
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Interface Guidelines
Secondary
New / orchestrated
API 3: new canonical path (new)
New / unmatched skill (orchestrated in API 2)
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
Derived legacy fields
- Category
- Mobile Development
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Backup
Secondary
New / orchestrated
API 3: new canonical path (new)
New / unmatched skill (orchestrated in API 2)
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
Derived legacy fields
- Category
- Data Management
- Sub-category
- general
- Skill nature
- PRACTICE
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
System Monitoring
Secondary
New / orchestrated
API 3: new canonical path (new)
New / unmatched skill (orchestrated in API 2)
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
Derived legacy fields
- Category
- Infrastructure Tools
- Sub-category
- general
- Skill nature
- PRACTICE
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Disaster Recovery
Secondary
New / orchestrated
API 3: new canonical path (new)
New / unmatched skill (orchestrated in API 2)
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
Derived legacy fields
- Category
- Infrastructure Tools
- Sub-category
- general
- Skill nature
- PRACTICE
- 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 |
|---|---|---|---|---|---|---|
| Android | in_db |
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| REST | in_db |
API Design and Contracts
api-design-and-contracts
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| REST | in_db |
API Interface and Contract Design
api-interface-and-contract-design
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| REST | in_db |
Integration Protocols & Standards
integration-protocols-standards
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| REST | in_db |
Standards, Protocols & Compliance
standards-protocols-compliance
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Git | in_db |
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Push Notifications | in_db |
Background Execution and Lifecycle
background-execution-and-lifecycle
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Push Notifications | in_db |
Push Notifications and Deep Links
push-notifications-and-deep-links
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Threading | in_db |
Concurrency and Async Workflows
concurrency-and-async-workflows
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Performance Tuning | new |
Relational Database Design
relational-database-design
|
— | — | Skipped — no persistable v3 meta for new skill | skill_not_in_db_v3_proposed |
| Benchmarking | in_db |
Backend Service Performance and Scalability Tuning
backend-service-performance-and-scalability-tuning
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Benchmarking | in_db |
Performance and Resource Tuning
performance-and-resource-tuning
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Benchmarking | in_db |
Performance and Scalability Tuning
performance-and-scalability-tuning
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Sensors | in_db |
Device APIs and Hardware Features
device-apis-and-hardware-features
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| Sensors | in_db |
Device APIs and Hardware Integration
device-apis-and-hardware-integration
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Accelerometer | in_db |
Device Capabilities and Sensors
device-capabilities-and-sensors
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Library artifacts (this run)
| Kind | Detail | DB id |
|---|---|---|
| canonical_skill_proposed | Android SDK | type=Mobile Development subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Continuous Integration | type=Software Development Practices subtype=general nature=PRACTICE lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Linux | type=Operating Systems subtype=general nature=TOOL lifespan=EVERGREEN | |
| canonical_skill_proposed | Scripting | type=Programming Languages subtype=general nature=LANGUAGE lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Offline Storage | type=Mobile Development subtype=general nature=CONCEPT lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Optimization | type=Software Development subtype=general nature=CONCEPT lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Gyroscope | type=Mobile Sensors subtype=general nature=TOOL lifespan=SHORT_LIVED | |
| canonical_skill_proposed | Cloud Message APIs | type=Cloud Services subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Android UI Design Principles | type=Mobile Development subtype=general nature=CONCEPT lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Android Design Principles | type=Mobile Development subtype=general nature=CONCEPT lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Interface Guidelines | type=Mobile Development subtype=general nature=CONCEPT lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Backup | type=Data Management subtype=general nature=PRACTICE lifespan=MULTI_YEAR | |
| canonical_skill_proposed | System Monitoring | type=Infrastructure Tools subtype=general nature=PRACTICE lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Disaster Recovery | type=Infrastructure Tools subtype=general nature=PRACTICE lifespan=MULTI_YEAR | |
| dimension_skill_link_proposed | Performance Tuning ↔ Relational Database Design |
nano JD Parser — gpt-4.1-nano click to toggle
JD type
fail
Show raw JSON
{
"JD_type": "fail",
"archetype_override_applied": true,
"archetype_override_matched_skills": [
"versioning",
"open-source",
"recovery",
"benchmarking",
"Monitoring",
"Git",
"APIs",
"threading",
"Cloud",
"Android",
"sensors",
"push notifications",
"Task"
],
"role_archetype": "Engineering"
}
API 1 — extract-from-jd click to toggle
{
"final_skills": [
{
"is_primary": true,
"skill_name": "Android SDK"
},
{
"is_primary": true,
"skill_name": "Android"
},
{
"is_primary": true,
"skill_name": "REST"
},
{
"is_primary": true,
"skill_name": "Git"
},
{
"is_primary": true,
"skill_name": "Continuous Integration"
},
{
"is_primary": true,
"skill_name": "Linux"
},
{
"is_primary": false,
"skill_name": "Scripting"
},
{
"is_primary": false,
"skill_name": "Push Notifications"
},
{
"is_primary": false,
"skill_name": "Offline Storage"
},
{
"is_primary": false,
"skill_name": "Threading"
},
{
"is_primary": false,
"skill_name": "Performance Tuning"
},
{
"is_primary": false,
"skill_name": "Benchmarking"
},
{
"is_primary": false,
"skill_name": "Optimization"
},
{
"is_primary": false,
"skill_name": "Sensors"
},
{
"is_primary": false,
"skill_name": "Gyroscope"
},
{
"is_primary": false,
"skill_name": "Accelerometer"
},
{
"is_primary": false,
"skill_name": "Cloud Message APIs"
},
{
"is_primary": false,
"skill_name": "Android UI Design Principles"
},
{
"is_primary": false,
"skill_name": "Android Design Principles"
},
{
"is_primary": false,
"skill_name": "Interface Guidelines"
},
{
"is_primary": false,
"skill_name": "Backup"
},
{
"is_primary": false,
"skill_name": "System Monitoring"
},
{
"is_primary": false,
"skill_name": "Disaster Recovery"
}
],
"jd_role": null,
"nano_parsed": {
"JD_type": "fail",
"archetype_override_applied": true,
"archetype_override_matched_skills": [
"versioning",
"open-source",
"recovery",
"benchmarking",
"Monitoring",
"Git",
"APIs",
"threading",
"Cloud",
"Android",
"sensors",
"push notifications",
"Task"
],
"role_archetype": "Engineering"
},
"rejected": false,
"rejection_reason": null,
"run_id": "8d18a030-892f-473f-bb91-e976096f443e",
"stage3_signals": {
"alias_found": false,
"alias_match_roles": [],
"kra_match_roles": [
{
"display_name": "Flutter Developer",
"kra_matches": [
{
"kra_text": "optimize responsiveness and performance",
"sentence": "A knack for benchmarking and optimization",
"similarity": 0.5089
},
{
"kra_text": "optimize responsiveness and performance",
"sentence": "Experience designing and building applications with an emphasis on performance, scalability, high-reliability and maintainability.",
"similarity": 0.501
},
{
"kra_text": "collaborate with design, product, and backend teams",
"sentence": "Keen desire to learn and incorporate new tools \u0026 technologies \u0026 share with the team",
"similarity": 0.4968
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 74,
"score": 0.5022,
"slug": "flutter-developer",
"total_count": null
},
{
"display_name": "Kotlin Backend Developer",
"kra_matches": [
{
"kra_text": "performance and reliability tuning",
"sentence": "A knack for benchmarking and optimization",
"similarity": 0.5462
},
{
"kra_text": "performance and reliability tuning",
"sentence": "Experience designing and building applications with an emphasis on performance, scalability, high-reliability and maintainability.",
"similarity": 0.4807
},
{
"kra_text": "performance and reliability tuning",
"sentence": "Understanding of backup process, system monitoring, performance tuning, disaster recovery, and scripting for Linux",
"similarity": 0.4638
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 84,
"score": 0.4969,
"slug": "kotlin-server-backend-developer",
"total_count": null
},
{
"display_name": "PHP Backend Developer",
"kra_matches": [
{
"kra_text": "performance and reliability tuning",
"sentence": "A knack for benchmarking and optimization",
"similarity": 0.5462
},
{
"kra_text": "performance and reliability tuning",
"sentence": "Experience designing and building applications with an emphasis on performance, scalability, high-reliability and maintainability.",
"similarity": 0.4807
},
{
"kra_text": "performance and reliability tuning",
"sentence": "Understanding of backup process, system monitoring, performance tuning, disaster recovery, and scripting for Linux",
"similarity": 0.4638
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 86,
"score": 0.4969,
"slug": "php-backend-developer",
"total_count": null
},
{
"display_name": "Scala Backend Developer",
"kra_matches": [
{
"kra_text": "performance and reliability tuning",
"sentence": "A knack for benchmarking and optimization",
"similarity": 0.5462
},
{
"kra_text": "performance and reliability tuning",
"sentence": "Experience designing and building applications with an emphasis on performance, scalability, high-reliability and maintainability.",
"similarity": 0.4807
},
{
"kra_text": "performance and reliability tuning",
"sentence": "Understanding of backup process, system monitoring, performance tuning, disaster recovery, and scripting for Linux",
"similarity": 0.4638
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 87,
"score": 0.4969,
"slug": "scala-backend-developer",
"total_count": null
},
{
"display_name": "Go Backend Developer",
"kra_matches": [
{
"kra_text": "performance tuning and resource efficiency",
"sentence": "A knack for benchmarking and optimization",
"similarity": 0.5347
},
{
"kra_text": "performance tuning and resource efficiency",
"sentence": "Quality conscious and efficiency oriented \u0026 multitasking",
"similarity": 0.5044
},
{
"kra_text": "code review and testing support",
"sentence": "Proficient understanding of code versioning tools \u2013 Git",
"similarity": 0.4335
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 81,
"score": 0.4909,
"slug": "go-backend-developer",
"total_count": null
}
],
"skill_match_roles": [
{
"display_name": "Fullstack Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"REST"
],
"role_id": 15,
"score": 0.1667,
"slug": "full-stack-engineer",
"total_count": 6
},
{
"display_name": "Pega Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"REST"
],
"role_id": 24,
"score": 0.1667,
"slug": "pega-developer",
"total_count": 6
},
{
"display_name": "Python Backend Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"REST"
],
"role_id": 80,
"score": 0.1667,
"slug": "python-backend-developer",
"total_count": 6
},
{
"display_name": "Go Backend Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"REST"
],
"role_id": 81,
"score": 0.1667,
"slug": "go-backend-developer",
"total_count": 6
},
{
"display_name": "Backend Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"REST"
],
"role_id": 1,
"score": 0.1667,
"slug": "backend-engineer",
"total_count": 6
}
]
},
"stage4_decision": {
"alias_collision_detected": false,
"case": "DOMAIN",
"chosen_role": {
"display_name": "Native Mobile Developer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 75,
"score": 0.99,
"slug": "native-mobile-developer",
"total_count": null
},
"confidence": 0.99,
"is_new_role": false,
"llm2_fired": false,
"llm2_reasoning": null,
"matched_dimensions": [
"Android Native Mobile Development",
"Mobile UI/UX Implementation",
"API Integration",
"Offline-first Mobile Engineering",
"Mobile Performance Optimization",
"Mobile DevOps and Version Control",
"Reliability and Maintainability",
"Cross-functional Collaboration"
],
"matched_kras": [
"Connect Android applications to back-end services",
"Design applications around natural user interfaces",
"Support different screen sizes",
"Benchmarking and optimization",
"Build applications with emphasis on performance, scalability",
"Complete the development activities on schedule",
"Collaborate with clients and other teams"
],
"matched_skills": [
"Android SDK",
"RESTful APIs",
"Android UI design principles",
"offline storage",
"threading",
"performance tuning",
"touch",
"gyroscopes",
"accelerometers",
"cloud message APIs",
"push notifications",
"Git",
"continuous integration",
"Linux",
"scripting"
],
"new_role_display_name": null,
"new_role_slug": null,
"queued": false,
"reasoning": "Domain=Software Engineering \u2192 sub-role android-engineer; The JD is clearly for an Android app developer focused on native mobile development, SDKs, UI, APIs, storage, performance, and mobile tooling.",
"sub_role": {
"confidence": 0.99,
"display_name": "Android Developer",
"reasoning": "The JD is overwhelmingly Android-specific, naming Android SDK, Android UI principles, Android ecosystem, and Android design guidelines with no iOS signals.",
"role_id": 4,
"slug": "android-engineer"
}
},
"stage5_updates": {
"centroid_n_after": 62,
"centroid_updated": true,
"collision_log_id": null,
"new_kra_attached": null,
"new_skills_attached": [
{
"is_primary": true,
"queue_id": 14391,
"role_display_name": "Native Mobile Developer",
"role_slug": "native-mobile-developer",
"skill_name": "Android SDK",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 14392,
"role_display_name": "Native Mobile Developer",
"role_slug": "native-mobile-developer",
"skill_name": "Continuous Integration",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 14393,
"role_display_name": "Native Mobile Developer",
"role_slug": "native-mobile-developer",
"skill_name": "Linux",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 14394,
"role_display_name": "Native Mobile Developer",
"role_slug": "native-mobile-developer",
"skill_name": "Scripting",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 14395,
"role_display_name": "Native Mobile Developer",
"role_slug": "native-mobile-developer",
"skill_name": "Offline Storage",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 14396,
"role_display_name": "Native Mobile Developer",
"role_slug": "native-mobile-developer",
"skill_name": "Performance Tuning",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 14397,
"role_display_name": "Native Mobile Developer",
"role_slug": "native-mobile-developer",
"skill_name": "Optimization",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 14398,
"role_display_name": "Native Mobile Developer",
"role_slug": "native-mobile-developer",
"skill_name": "Gyroscope",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 14399,
"role_display_name": "Native Mobile Developer",
"role_slug": "native-mobile-developer",
"skill_name": "Cloud Message APIs",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 14400,
"role_display_name": "Native Mobile Developer",
"role_slug": "native-mobile-developer",
"skill_name": "Android UI Design Principles",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 14401,
"role_display_name": "Native Mobile Developer",
"role_slug": "native-mobile-developer",
"skill_name": "Android Design Principles",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 14402,
"role_display_name": "Native Mobile Developer",
"role_slug": "native-mobile-developer",
"skill_name": "Interface Guidelines",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 14403,
"role_display_name": "Native Mobile Developer",
"role_slug": "native-mobile-developer",
"skill_name": "Backup",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 14404,
"role_display_name": "Native Mobile Developer",
"role_slug": "native-mobile-developer",
"skill_name": "System Monitoring",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 14405,
"role_display_name": "Native Mobile Developer",
"role_slug": "native-mobile-developer",
"skill_name": "Disaster Recovery",
"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": 2541,
"existing_alias_text": "Android",
"input_term": "Android",
"matched_canonical": {
"category_id": 9,
"display_name": "Android",
"id": 1595,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "android",
"sub_category_id": 1201,
"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": 106,
"existing_alias_text": "REST",
"input_term": "REST",
"matched_canonical": {
"category_id": 2,
"display_name": "REST",
"id": 11,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "rest",
"sub_category_id": 2122,
"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": 1613,
"existing_alias_text": "Git",
"input_term": "Git",
"matched_canonical": {
"category_id": 13,
"display_name": "Git",
"id": 1002,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "git",
"sub_category_id": 730,
"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": 2557,
"existing_alias_text": "Push Notifications",
"input_term": "Push Notifications",
"matched_canonical": {
"category_id": 2,
"display_name": "push notifications",
"id": 1605,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "push-notifications",
"sub_category_id": 2134,
"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": 3639,
"existing_alias_text": "threading",
"input_term": "Threading",
"matched_canonical": {
"category_id": 2,
"display_name": "threading",
"id": 2349,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "threading",
"sub_category_id": 7,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 alias DB write disabled",
"alias_persisted": false,
"existing_alias_id": 5584,
"existing_alias_text": "Query Tuning",
"input_term": "Performance Tuning",
"matched_canonical": {
"category_id": 2,
"display_name": "query tuning",
"id": 3553,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "query-tuning",
"sub_category_id": 3067,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "embedding_alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 189,
"existing_alias_text": "benchmarking",
"input_term": "Benchmarking",
"matched_canonical": {
"category_id": 8,
"display_name": "benchmarking",
"id": 52,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "benchmarking",
"sub_category_id": 3547,
"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": 1602,
"existing_alias_text": "sensors",
"input_term": "Sensors",
"matched_canonical": {
"category_id": 2,
"display_name": "sensors",
"id": 992,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "sensors",
"sub_category_id": 1510,
"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": 5047,
"existing_alias_text": "accelerometer",
"input_term": "Accelerometer",
"matched_canonical": {
"category_id": 2,
"display_name": "accelerometer",
"id": 3494,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "accelerometer",
"sub_category_id": 2709,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
}
],
"candidate_roles": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
},
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
},
{
"display_name": "Engineering Manager",
"id": 121,
"rationale": null,
"role_archetype": null,
"slug": "engineering-manager",
"source": "db"
},
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
},
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "React Native Developer",
"id": 73,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-native-developer",
"source": "db"
},
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
},
{
"display_name": "Ionic Developer",
"id": 434,
"rationale": null,
"role_archetype": null,
"slug": "ionic-developer",
"source": "db"
},
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
}
],
"chosen_role": {
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": "Domain=Software Engineering \u2192 sub-role android-engineer; The JD is clearly for an Android app developer focused on native mobile development, SDKs, UI, APIs, storage, performance, and mobile tooling.",
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
},
"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": "Android",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Design and Contracts",
"id": 3,
"rationale": "Designing request/response shapes and the rules that govern client-server interaction. This cluster is coherent because full stack engineers often own the contract between UI behavior and backend implementation.",
"slug": "api-design-and-contracts",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Interface and Contract Design",
"id": 289,
"rationale": "Designing backend service interfaces and contracts that other systems consume, including endpoint and operation shape, request/response payloads, schema and validation, pagination, filtering, idempotency, versioning, status codes, and backward compatibility across REST, GraphQL, gRPC, and OpenAPI-based APIs.",
"slug": "api-interface-and-contract-design",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Integration Protocols \u0026 Standards",
"id": 271,
"rationale": "Standards and protocols for integrating Pega applications.",
"slug": "integration-protocols-standards",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Standards, Protocols \u0026 Compliance",
"id": 452,
"rationale": "Ensure teams adhere to industry standards, security protocols, and regulatory compliance requirements.",
"slug": "standards-protocols-compliance",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Engineering Manager",
"id": 121,
"rationale": null,
"role_archetype": null,
"slug": "engineering-manager",
"source": "db"
},
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"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": "Git",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Background Execution and Lifecycle",
"id": 87,
"rationale": "App lifecycle handling and deferred work mechanisms that keep iOS behavior reliable when the app is backgrounded, suspended, or relaunched. This is important for sync, refresh, and user-visible continuity.",
"slug": "background-execution-and-lifecycle",
"source": "db"
},
"input_skill": "Push Notifications",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "React Native Developer",
"id": 73,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-native-developer",
"source": "db"
},
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Push Notifications and Deep Links",
"id": 320,
"rationale": "Mechanisms for receiving notifications and routing users into the right in-app destination from external entry points. React Native developers use these flows to re-engage users and restore context after taps or app launches.",
"slug": "push-notifications-and-deep-links",
"source": "db"
},
"input_skill": "Push Notifications",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Ionic Developer",
"id": 434,
"rationale": null,
"role_archetype": null,
"slug": "ionic-developer",
"source": "db"
},
{
"display_name": "React Native Developer",
"id": 73,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-native-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Concurrency and Async Workflows",
"id": 292,
"rationale": "Programming techniques for handling concurrent requests, asynchronous I/O, and coordination of background execution in Python services. This cluster is coherent because backend developers must safely manage throughput and responsiveness.",
"slug": "concurrency-and-async-workflows",
"source": "db"
},
"input_skill": "Threading",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Database Design",
"id": 4,
"rationale": "Modeling and operating relational persistence for backend services. Includes schema design, normalization, indexing, transactions, and query tuning for operational data stores.",
"slug": "relational-database-design",
"source": "db"
},
"input_skill": "Performance Tuning",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Backend Service Performance and Scalability Tuning",
"id": 389,
"rationale": "Techniques for improving throughput, latency, and resource efficiency in backend services across runtimes. This includes profiling and bottleneck analysis, benchmarking, load testing, allocation and GC tuning, async and contention analysis, and query/connection efficiency using platform-appropriate tools such as JFR or BenchmarkDotNet.",
"slug": "backend-service-performance-and-scalability-tuning",
"source": "db"
},
"input_skill": "Benchmarking",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Performance and Resource Tuning",
"id": 373,
"rationale": "Improving throughput, latency, memory use, and CPU efficiency in Go backend services. This cluster is coherent because Go developers often profile hot paths, reduce allocations, and tune concurrency to meet service SLOs.",
"slug": "performance-and-resource-tuning",
"source": "db"
},
"input_skill": "Benchmarking",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Performance and Scalability Tuning",
"id": 11,
"rationale": "Techniques for improving throughput, latency, and resource efficiency in PHP backend services. This includes profiling, query optimization, concurrency limits, memory use, and bottleneck analysis.",
"slug": "performance-and-scalability-tuning",
"source": "db"
},
"input_skill": "Benchmarking",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Device APIs and Hardware Features",
"id": 95,
"rationale": "iOS platform APIs that expose hardware and device capabilities to apps. This cluster covers the concrete integrations iOS engineers use for camera, sensors, location, and media experiences.",
"slug": "device-apis-and-hardware-features",
"source": "db"
},
"input_skill": "Sensors",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
},
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Device APIs and Hardware Integration",
"id": 171,
"rationale": "Platform capabilities exposed through mobile devices that shared apps commonly integrate with. This includes sensors, camera, location, Bluetooth, file access, and other device-bound features that require platform-aware adaptation.",
"slug": "device-apis-and-hardware-integration",
"source": "db"
},
"input_skill": "Sensors",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "React Native Developer",
"id": 73,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-native-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Device Capabilities and Sensors",
"id": 379,
"rationale": "Platform capabilities exposed through Ionic plugins and browser/mobile APIs. Ionic developers use these integrations for camera, location, file access, and other device-aware behaviors in shared apps.",
"slug": "device-capabilities-and-sensors",
"source": "db"
},
"input_skill": "Accelerometer",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Ionic Developer",
"id": 434,
"rationale": null,
"role_archetype": null,
"slug": "ionic-developer",
"source": "db"
}
]
}
],
"input_final_skills": [
"Android SDK",
"Android",
"REST",
"Git",
"Continuous Integration",
"Linux",
"Scripting",
"Push Notifications",
"Offline Storage",
"Threading",
"Performance Tuning",
"Benchmarking",
"Optimization",
"Sensors",
"Gyroscope",
"Accelerometer",
"Cloud Message APIs",
"Android UI Design Principles",
"Android Design Principles",
"Interface Guidelines",
"Backup",
"System Monitoring",
"Disaster Recovery"
],
"input_llm_skills": [
"Android SDK",
"Android",
"REST",
"Git",
"Continuous Integration",
"Linux",
"Scripting",
"Push Notifications",
"Offline Storage",
"Threading",
"Performance Tuning",
"Benchmarking",
"Optimization",
"Sensors",
"Gyroscope",
"Accelerometer",
"Cloud Message APIs",
"Android UI Design Principles",
"Android Design Principles",
"Interface Guidelines",
"Backup",
"System Monitoring",
"Disaster Recovery"
],
"new_aliases_persisted": 0,
"run_id": "8d18a030-892f-473f-bb91-e976096f443e",
"skills_detail": [
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Android SDK",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Mobile Development",
"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": "android-sdk",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Android",
"alias_type": "CANONICAL",
"id": 2541,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 9,
"display_name": "Android",
"id": 1595,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "android",
"sub_category_id": 1201,
"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": "Android",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Android",
"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": "REST",
"alias_type": "CANONICAL",
"id": 106,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 2,
"display_name": "REST",
"id": 11,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "rest",
"sub_category_id": 2122,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Design and Contracts",
"id": 3,
"rationale": "Designing request/response shapes and the rules that govern client-server interaction. This cluster is coherent because full stack engineers often own the contract between UI behavior and backend implementation.",
"slug": "api-design-and-contracts",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Interface and Contract Design",
"id": 289,
"rationale": "Designing backend service interfaces and contracts that other systems consume, including endpoint and operation shape, request/response payloads, schema and validation, pagination, filtering, idempotency, versioning, status codes, and backward compatibility across REST, GraphQL, gRPC, and OpenAPI-based APIs.",
"slug": "api-interface-and-contract-design",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Integration Protocols \u0026 Standards",
"id": 271,
"rationale": "Standards and protocols for integrating Pega applications.",
"slug": "integration-protocols-standards",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Standards, Protocols \u0026 Compliance",
"id": 452,
"rationale": "Ensure teams adhere to industry standards, security protocols, and regulatory compliance requirements.",
"slug": "standards-protocols-compliance",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Engineering Manager",
"id": 121,
"rationale": null,
"role_archetype": null,
"slug": "engineering-manager",
"source": "db"
},
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
]
}
],
"input_skill": "REST",
"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": "Git",
"alias_type": "CANONICAL",
"id": 1613,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 13,
"display_name": "Git",
"id": 1002,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "git",
"sub_category_id": 730,
"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": "Git",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Git",
"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": "Continuous Integration",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Software Development Practices",
"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": "continuous-integration",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Linux",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Operating Systems",
"skill_nature": "TOOL",
"sub_category": "general",
"typical_lifespan": "EVERGREEN",
"version_strategy": "UNVERSIONED",
"volatility": "STABLE"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "linux",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Scripting",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Programming Languages",
"skill_nature": "LANGUAGE",
"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": "scripting",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "push notifications",
"alias_type": "CANONICAL",
"id": 4339,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Push Notifications",
"alias_type": "CANONICAL",
"id": 2557,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 2,
"display_name": "push notifications",
"id": 1605,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "push-notifications",
"sub_category_id": 2134,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Background Execution and Lifecycle",
"id": 87,
"rationale": "App lifecycle handling and deferred work mechanisms that keep iOS behavior reliable when the app is backgrounded, suspended, or relaunched. This is important for sync, refresh, and user-visible continuity.",
"slug": "background-execution-and-lifecycle",
"source": "db"
},
"input_skill": "Push Notifications",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "React Native Developer",
"id": 73,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-native-developer",
"source": "db"
},
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Push Notifications and Deep Links",
"id": 320,
"rationale": "Mechanisms for receiving notifications and routing users into the right in-app destination from external entry points. React Native developers use these flows to re-engage users and restore context after taps or app launches.",
"slug": "push-notifications-and-deep-links",
"source": "db"
},
"input_skill": "Push Notifications",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Ionic Developer",
"id": 434,
"rationale": null,
"role_archetype": null,
"slug": "ionic-developer",
"source": "db"
},
{
"display_name": "React Native Developer",
"id": 73,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-native-developer",
"source": "db"
}
]
}
],
"input_skill": "Push Notifications",
"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": "Offline Storage",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Mobile Development",
"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": "offline-storage",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "threading",
"alias_type": "CANONICAL",
"id": 3639,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 2,
"display_name": "threading",
"id": 2349,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "threading",
"sub_category_id": 7,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Concurrency and Async Workflows",
"id": 292,
"rationale": "Programming techniques for handling concurrent requests, asynchronous I/O, and coordination of background execution in Python services. This cluster is coherent because backend developers must safely manage throughput and responsiveness.",
"slug": "concurrency-and-async-workflows",
"source": "db"
},
"input_skill": "Threading",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
}
]
}
],
"input_skill": "Threading",
"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": "query tuning",
"alias_type": "CANONICAL",
"id": 5119,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Query Tuning",
"alias_type": "CANONICAL",
"id": 5584,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 2,
"display_name": "query tuning",
"id": 3553,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "query-tuning",
"sub_category_id": 3067,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Database Design",
"id": 4,
"rationale": "Modeling and operating relational persistence for backend services. Includes schema design, normalization, indexing, transactions, and query tuning for operational data stores.",
"slug": "relational-database-design",
"source": "db"
},
"input_skill": "Performance Tuning",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
}
],
"input_skill": "Performance Tuning",
"matched_via": "embedding_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": "benchmarking",
"alias_type": "CANONICAL",
"id": 189,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 8,
"display_name": "benchmarking",
"id": 52,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "benchmarking",
"sub_category_id": 3547,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Backend Service Performance and Scalability Tuning",
"id": 389,
"rationale": "Techniques for improving throughput, latency, and resource efficiency in backend services across runtimes. This includes profiling and bottleneck analysis, benchmarking, load testing, allocation and GC tuning, async and contention analysis, and query/connection efficiency using platform-appropriate tools such as JFR or BenchmarkDotNet.",
"slug": "backend-service-performance-and-scalability-tuning",
"source": "db"
},
"input_skill": "Benchmarking",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Performance and Resource Tuning",
"id": 373,
"rationale": "Improving throughput, latency, memory use, and CPU efficiency in Go backend services. This cluster is coherent because Go developers often profile hot paths, reduce allocations, and tune concurrency to meet service SLOs.",
"slug": "performance-and-resource-tuning",
"source": "db"
},
"input_skill": "Benchmarking",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Performance and Scalability Tuning",
"id": 11,
"rationale": "Techniques for improving throughput, latency, and resource efficiency in PHP backend services. This includes profiling, query optimization, concurrency limits, memory use, and bottleneck analysis.",
"slug": "performance-and-scalability-tuning",
"source": "db"
},
"input_skill": "Benchmarking",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
}
]
}
],
"input_skill": "Benchmarking",
"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": "Optimization",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Software Development",
"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": "optimization",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "sensors",
"alias_type": "CANONICAL",
"id": 1602,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 2,
"display_name": "sensors",
"id": 992,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "sensors",
"sub_category_id": 1510,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Device APIs and Hardware Features",
"id": 95,
"rationale": "iOS platform APIs that expose hardware and device capabilities to apps. This cluster covers the concrete integrations iOS engineers use for camera, sensors, location, and media experiences.",
"slug": "device-apis-and-hardware-features",
"source": "db"
},
"input_skill": "Sensors",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
},
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Device APIs and Hardware Integration",
"id": 171,
"rationale": "Platform capabilities exposed through mobile devices that shared apps commonly integrate with. This includes sensors, camera, location, Bluetooth, file access, and other device-bound features that require platform-aware adaptation.",
"slug": "device-apis-and-hardware-integration",
"source": "db"
},
"input_skill": "Sensors",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "React Native Developer",
"id": 73,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-native-developer",
"source": "db"
}
]
}
],
"input_skill": "Sensors",
"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": "Gyroscope",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Mobile Sensors",
"skill_nature": "TOOL",
"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": "gyroscope",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "accelerometer",
"alias_type": "CANONICAL",
"id": 5047,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 2,
"display_name": "accelerometer",
"id": 3494,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "accelerometer",
"sub_category_id": 2709,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Device Capabilities and Sensors",
"id": 379,
"rationale": "Platform capabilities exposed through Ionic plugins and browser/mobile APIs. Ionic developers use these integrations for camera, location, file access, and other device-aware behaviors in shared apps.",
"slug": "device-capabilities-and-sensors",
"source": "db"
},
"input_skill": "Accelerometer",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Ionic Developer",
"id": 434,
"rationale": null,
"role_archetype": null,
"slug": "ionic-developer",
"source": "db"
}
]
}
],
"input_skill": "Accelerometer",
"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": "Cloud Message APIs",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Cloud Services",
"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": "cloud-message-apis",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Android UI Design Principles",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Mobile Development",
"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": "android-ui-design-principles",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Android Design Principles",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Mobile Development",
"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": "android-design-principles",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Interface Guidelines",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Mobile Development",
"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": "interface-guidelines",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Backup",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Data Management",
"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": "backup",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "System Monitoring",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Infrastructure Tools",
"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": "system-monitoring",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Disaster Recovery",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Infrastructure Tools",
"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": "disaster-recovery",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"Android SDK",
"Continuous Integration",
"Linux",
"Scripting",
"Offline Storage",
"Optimization",
"Gyroscope",
"Cloud Message APIs",
"Android UI Design Principles",
"Android Design Principles",
"Interface Guidelines",
"Backup",
"System Monitoring",
"Disaster Recovery"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": "Domain=Software Engineering \u2192 sub-role android-engineer; The JD is clearly for an Android app developer focused on native mobile development, SDKs, UI, APIs, storage, performance, and mobile tooling.",
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
},
"chosen_role_resolution": "in_db",
"final_input_skills": [
{
"skill": "Android SDK",
"tag": "new"
},
{
"skill": "Android",
"tag": "in_db"
},
{
"skill": "REST",
"tag": "in_db"
},
{
"skill": "Git",
"tag": "in_db"
},
{
"skill": "Continuous Integration",
"tag": "new"
},
{
"skill": "Linux",
"tag": "new"
},
{
"skill": "Scripting",
"tag": "new"
},
{
"skill": "Push Notifications",
"tag": "in_db"
},
{
"skill": "Offline Storage",
"tag": "new"
},
{
"skill": "Threading",
"tag": "in_db"
},
{
"skill": "Performance Tuning",
"tag": "in_db"
},
{
"skill": "Benchmarking",
"tag": "in_db"
},
{
"skill": "Optimization",
"tag": "new"
},
{
"skill": "Sensors",
"tag": "in_db"
},
{
"skill": "Gyroscope",
"tag": "new"
},
{
"skill": "Accelerometer",
"tag": "in_db"
},
{
"skill": "Cloud Message APIs",
"tag": "new"
},
{
"skill": "Android UI Design Principles",
"tag": "new"
},
{
"skill": "Android Design Principles",
"tag": "new"
},
{
"skill": "Interface Guidelines",
"tag": "new"
},
{
"skill": "Backup",
"tag": "new"
},
{
"skill": "System Monitoring",
"tag": "new"
},
{
"skill": "Disaster Recovery",
"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": 75,
"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": "Android",
"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": 1595,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 75,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Design and Contracts",
"id": 3,
"rationale": "Designing request/response shapes and the rules that govern client-server interaction. This cluster is coherent because full stack engineers often own the contract between UI behavior and backend implementation.",
"slug": "api-design-and-contracts",
"source": "db"
},
"dimension_id": 3,
"input_skill": "REST",
"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": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 11,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 75,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Interface and Contract Design",
"id": 289,
"rationale": "Designing backend service interfaces and contracts that other systems consume, including endpoint and operation shape, request/response payloads, schema and validation, pagination, filtering, idempotency, versioning, status codes, and backward compatibility across REST, GraphQL, gRPC, and OpenAPI-based APIs.",
"slug": "api-interface-and-contract-design",
"source": "db"
},
"dimension_id": 289,
"input_skill": "REST",
"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": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 11,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 75,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Integration Protocols \u0026 Standards",
"id": 271,
"rationale": "Standards and protocols for integrating Pega applications.",
"slug": "integration-protocols-standards",
"source": "db"
},
"dimension_id": 271,
"input_skill": "REST",
"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": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 11,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 75,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Standards, Protocols \u0026 Compliance",
"id": 452,
"rationale": "Ensure teams adhere to industry standards, security protocols, and regulatory compliance requirements.",
"slug": "standards-protocols-compliance",
"source": "db"
},
"dimension_id": 452,
"input_skill": "REST",
"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": "Engineering Manager",
"id": 121,
"rationale": null,
"role_archetype": null,
"slug": "engineering-manager",
"source": "db"
},
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 11,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 75,
"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": "Git",
"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": 1002,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 75,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Background Execution and Lifecycle",
"id": 87,
"rationale": "App lifecycle handling and deferred work mechanisms that keep iOS behavior reliable when the app is backgrounded, suspended, or relaunched. This is important for sync, refresh, and user-visible continuity.",
"slug": "background-execution-and-lifecycle",
"source": "db"
},
"dimension_id": 87,
"input_skill": "Push Notifications",
"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": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "React Native Developer",
"id": 73,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-native-developer",
"source": "db"
},
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 1605,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 75,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Push Notifications and Deep Links",
"id": 320,
"rationale": "Mechanisms for receiving notifications and routing users into the right in-app destination from external entry points. React Native developers use these flows to re-engage users and restore context after taps or app launches.",
"slug": "push-notifications-and-deep-links",
"source": "db"
},
"dimension_id": 320,
"input_skill": "Push Notifications",
"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": "Ionic Developer",
"id": 434,
"rationale": null,
"role_archetype": null,
"slug": "ionic-developer",
"source": "db"
},
{
"display_name": "React Native Developer",
"id": 73,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-native-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 1605,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 75,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Concurrency and Async Workflows",
"id": 292,
"rationale": "Programming techniques for handling concurrent requests, asynchronous I/O, and coordination of background execution in Python services. This cluster is coherent because backend developers must safely manage throughput and responsiveness.",
"slug": "concurrency-and-async-workflows",
"source": "db"
},
"dimension_id": 292,
"input_skill": "Threading",
"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": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 2349,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 75,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Database Design",
"id": 4,
"rationale": "Modeling and operating relational persistence for backend services. Includes schema design, normalization, indexing, transactions, and query tuning for operational data stores.",
"slug": "relational-database-design",
"source": "db"
},
"dimension_id": 4,
"input_skill": "Performance Tuning",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Skipped \u2014 no persistable v3 meta for new skill",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 75,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Backend Service Performance and Scalability Tuning",
"id": 389,
"rationale": "Techniques for improving throughput, latency, and resource efficiency in backend services across runtimes. This includes profiling and bottleneck analysis, benchmarking, load testing, allocation and GC tuning, async and contention analysis, and query/connection efficiency using platform-appropriate tools such as JFR or BenchmarkDotNet.",
"slug": "backend-service-performance-and-scalability-tuning",
"source": "db"
},
"dimension_id": 389,
"input_skill": "Benchmarking",
"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": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 52,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 75,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Performance and Resource Tuning",
"id": 373,
"rationale": "Improving throughput, latency, memory use, and CPU efficiency in Go backend services. This cluster is coherent because Go developers often profile hot paths, reduce allocations, and tune concurrency to meet service SLOs.",
"slug": "performance-and-resource-tuning",
"source": "db"
},
"dimension_id": 373,
"input_skill": "Benchmarking",
"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": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 52,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 75,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Performance and Scalability Tuning",
"id": 11,
"rationale": "Techniques for improving throughput, latency, and resource efficiency in PHP backend services. This includes profiling, query optimization, concurrency limits, memory use, and bottleneck analysis.",
"slug": "performance-and-scalability-tuning",
"source": "db"
},
"dimension_id": 11,
"input_skill": "Benchmarking",
"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": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 52,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 75,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Device APIs and Hardware Features",
"id": 95,
"rationale": "iOS platform APIs that expose hardware and device capabilities to apps. This cluster covers the concrete integrations iOS engineers use for camera, sensors, location, and media experiences.",
"slug": "device-apis-and-hardware-features",
"source": "db"
},
"dimension_id": 95,
"input_skill": "Sensors",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
},
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 992,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 75,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Device APIs and Hardware Integration",
"id": 171,
"rationale": "Platform capabilities exposed through mobile devices that shared apps commonly integrate with. This includes sensors, camera, location, Bluetooth, file access, and other device-bound features that require platform-aware adaptation.",
"slug": "device-apis-and-hardware-integration",
"source": "db"
},
"dimension_id": 171,
"input_skill": "Sensors",
"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": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "React Native Developer",
"id": 73,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-native-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 992,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 75,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Device Capabilities and Sensors",
"id": 379,
"rationale": "Platform capabilities exposed through Ionic plugins and browser/mobile APIs. Ionic developers use these integrations for camera, location, file access, and other device-aware behaviors in shared apps.",
"slug": "device-capabilities-and-sensors",
"source": "db"
},
"dimension_id": 379,
"input_skill": "Accelerometer",
"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": "Ionic Developer",
"id": 434,
"rationale": null,
"role_archetype": null,
"slug": "ionic-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 3494,
"skill_tag": "in_db",
"skipped_reason": null
}
],
"new_skills_created": 0,
"role_dimension_saved": 0,
"skill_dimension_saved": 0,
"skipped": 1
},
"planner_output": null,
"run_id": "8d18a030-892f-473f-bb91-e976096f443e"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.
Loading…