0113 capability categories
AI and data
Define the work across data foundations, analysis, models, evaluation, production integration, reliability, governance, and decision support.
- AI engineering
- Data architecture
- Business intelligence
Specialist capability map
Find the responsibility before the role title.
A useful hiring brief begins with the work that is not covered, the decisions the person must make, and the team they must join. Werkon uses that context to define a role, seniority, screening evidence, collaboration model, and an honest availability check.
Role map
Start with the discipline, then narrow by context and responsibility.
The categories below organize a hiring conversation. They help identify adjacent disciplines and screening needs, but they do not promise a person, location, rate, or start date.
0217 capability categories
Cloud, DevOps and infrastructure
Cover the path from environments and delivery automation to cloud architecture, reliability, identity, networks, databases, support, and recovery.
- Cloud engineering
- Site reliability
- Infrastructure as code
0310 capability categories
Backend and full-stack
Match product and platform responsibilities to engineers who can work across APIs, services, data models, integrations, established systems, and maintainable delivery.
- Node.js
- Python web
- .NET and C#
046 capability categories
Frontend
Specify interface architecture, product behavior, accessibility, responsive systems, performance, testing, and the framework context that already shapes the application.
- React
- Angular
- HTML and CSS
0513 capability categories
Mobile, embedded and interactive
Separate native or cross-platform mobile work from devices, firmware, connected systems, robotics, simulation, and real-time interactive products.
- iOS and Android
- Embedded systems
- Game engines
0618 capability categories
Product, delivery, quality and security
Connect discovery, product direction, design, delivery leadership, testing, reliability evidence, defensive controls, and authorized security review.
- Product management
- Quality engineering
- Security architecture
Capability brief
Turn the gap into evidence that can be screened.
A role request becomes useful when the team can describe the work, the decisions, the surrounding system, the level of independence, and what credible evidence would look like.
- 01
Name the uncovered responsibility
Describe the outcomes, decisions, backlog, operational duties, risks, and current owner instead of beginning with a technology label.
- 02
Set context and seniority
Clarify the existing team, architecture, users, constraints, authority, ambiguity, communication needs, and how independently the person must operate.
- 03
Define screening evidence
Choose proportionate evidence such as work discussion, code or artifact review, a bounded practical exercise, system reasoning, references, or verified credentials when required.
- 04
Confirm model and availability
Agree who directs the work, expected collaboration, timing, access, security, commercial constraints, and whether suitable capability is actually available for the engagement.
Hiring boundaries
A category is a search path, not a candidate claim.
The role architecture makes the request clearer. It does not replace a current availability check, evidence-based screening, or an engagement-specific decision about fit.
- No fictional inventory
- A published role category does not mean Werkon has a named person waiting, operates in a particular region, or can promise a start date. Those facts must be confirmed when the request is known.
- Tools are supporting evidence
- Framework or platform experience matters when the work requires it, but it does not by itself prove system judgment, communication, reliability, or ownership of the responsibility.
- Seniority is contextual
- A senior title should correspond to the ambiguity, decision authority, technical breadth, leadership, and operating responsibility required in this team, not only years worked.
- Consequential work is scoped
- Security testing must be authorized. Compliance and regulated work require the right specialist authority. Production, data, and safety access must be narrow, deliberate, and reviewable.
Verified role guides
Browse role pages only after their evidence is complete.
This catalog grows as each role receives current primary research, an explicit responsibility and assessment model, a page-specific visual, technical checks, and real browser review. A published guide remains a capability definition, not a claim of a waiting person.
AI and data
Roles for production AI, data platforms, analytics, models, evaluation, pipelines, architecture, and decision support, each separated from its adjacent responsibilities.
- AI engineersDefine production AI engineering responsibility across evaluation, integration, secure delivery, operation, human control, and continuity before checking capability and current availability.
- Big data engineersDefine large-scale data engineering responsibility around measured workload, partitions, time, state, recovery, reconciliation, performance, cost, and continuity.
- Business intelligence analystsDefine governed metric and reporting responsibility around decision questions, dimensional semantics, lineage, quality, accessible communication, interpretation, and correction.
- Computer vision engineersDefine production vision responsibility around scene and capture contracts, data rights, annotation, evaluation, human review, monitoring, incidents, and correction.
- Data architectsDefine cross-system data responsibility around business meaning, source authority, models, contracts, platform tradeoffs, governance, migration, and evolution.
- Data pipeline engineersDefine dependable batch and stream responsibility around contracts, time, state, replay, quality, lineage, observability, recovery, and reconciliation.
- Data scientistsDefine defensible investigation and modeling responsibility around decision framing, study design, data fitness, inference, prediction, uncertainty, reproducibility, review, and correction.
- Data visualization expertsDefine accurate and accessible visual-evidence responsibility around meaning, encoding, interaction, alternatives, responsiveness, provenance, publication, and correction.
- Deep learning specialistsDefine justified neural-model responsibility around baselines, representations, training, reproducibility, evaluation, robustness, efficiency, transfer, monitoring, and rollback.
- ETL developersDefine source-to-target load responsibility around extraction boundaries, transformations, validation, quarantine, merge behavior, restart, reconciliation, recovery, and continuity.
- Machine learning engineersDefine production-model responsibility around reproducibility, features, artifacts, registry control, inference, field monitoring, rollback, retraining, and continuity.
- NLP specialistsDefine language-system responsibility around corpora, metadata, annotation, retrieval, classification, extraction, generation, evaluation, review, safety, and correction.
- Spark and Hadoop engineersDefine established-estate responsibility around measured workload fit, Spark execution, YARN resources, HDFS storage, identity, recovery, migration, cost, and retirement.
Cloud, DevOps and infrastructure
Roles for software delivery, cloud platforms, infrastructure, reliability, security, databases, systems and operations, each tied to explicit authority and recovery evidence.
- CI/CD engineersDefine verifiable-release responsibility around source, builds, tests, artifacts, provenance, environments, approvals, deployment, exposure, observation, recovery, and continuity.
- Cloud engineersDefine cloud-workload responsibility around tenancy, identity, networks, infrastructure, runtimes, data, observability, resilience, recovery, security, cost, and exit.
- Cloud migration expertsDefine migration responsibility around inventory, dependencies, strategy, foundations, data, rehearsal, cutover, rollback, reconciliation, stabilization, source retirement, and exit.
- Cloud security specialistsDefine cloud-security responsibility around threats, shared control ownership, identity, networks, data, configuration, software, detection, response, recovery, evidence, and residual risk.
- Cloud solutions architectsDefine cloud-architecture responsibility around business context, quality priorities, boundaries, options, tradeoffs, decisions, delivery, operation, governance, evolution, and exit.
- Database administratorsDefine database-administration responsibility around data meaning, transactions, workload, access, maintenance, availability, backup, restore, change, recovery, and continuity.
- DevOps engineersDefine DevOps responsibility around change flow, trusted artifacts, environments, infrastructure, release, production feedback, recovery, platform usability, cost, and learning.
- Docker specialistsDefine container responsibility around build inputs, image identity, provenance, runtime users and privileges, host boundaries, networks, storage, resources, health, recovery, and lifecycle.
- Infrastructure as code engineersDefine infrastructure-change responsibility around desired and observed state, providers, modules, plans, policy, authority, apply, drift, recovery, cost, and lifecycle.
- IT support specialistsDefine accountable support responsibility around verified intake, user context, identity, devices, services, diagnosis, restoration, communication, escalation, security, knowledge, and continuity.
- Kafka specialistsDefine event-system responsibility around source authority, contracts, schemas, keys, partitions, producers, consumers, effects, security, operation, replay, recovery, and lifecycle.
- Kubernetes specialistsDefine orchestration responsibility around workload fit, desired state, scheduling, exposure, identity, networks, storage, disruption, observability, recovery, upgrades, and lifecycle.
- Network administratorsDefine network-operating responsibility around service paths, topology, addressing, naming, routing, access, configuration, observation, troubleshooting, recovery, and lifecycle.
- Serverless engineersDefine managed-event responsibility around workload fit, trigger contracts, identity, retries, concurrency, effects, observability, recovery, cost, and provider lifecycle.
- Site reliability engineersDefine reliability-engineering responsibility around user journeys, service objectives, telemetry, alerts, change, capacity, incidents, recovery, automation, toil, and learning.
- Systems administratorsDefine systems-administration responsibility around inventory, lifecycle, identity, privilege, configuration, patching, services, storage, observation, recovery, and handoff.
- Virtualization specialistsDefine virtualization responsibility around workload fit, VM identity, placement, capacity, virtual networks, storage, migration, availability, recovery, upgrades, and exit.
Backend and full-stack
Roles for services, APIs, integrations and product systems, each tied to explicit contracts, data effects, delivery evidence, operation, recovery and compatible evolution.
- Go developersDefine Go-engineering responsibility around service contracts, packages, concurrency, contexts, external effects, modules, testing, diagnostics, recovery, and evolution.
- Java and Spring developersDefine Java and Spring responsibility around domain contracts, proxies, transactions, authorization, configuration, dependencies, JVM evidence, recovery, and migration.
- MEAN stack developersDefine MEAN responsibility around Angular product state, Express middleware, Node runtime behavior, MongoDB access models, consistency, recovery, and stack exit.
- MERN stack developersDefine MERN responsibility around React state and rendering, Express and Node authority, MongoDB record models, effect reconciliation, recovery, and stack exit.
- .NET and C# developersDefine .NET responsibility around C# contracts, ASP.NET Core request authority, runtime behavior, data effects, recovery, migration, and support lifecycle.
- Node.js developersDefine Node.js responsibility around runtime validation, modules, event-loop work, streams, integrations, external effects, shutdown, and recovery.
- NoSQL specialistsDefine NoSQL responsibility around store fit, record models, access paths, partitions, consistency, migration, operation, and recovery.
- PHP and Laravel developersDefine PHP and Laravel responsibility around product behavior, request authority, data effects, queues, modernization, support, and recovery.
- Python, Django and Flask developersDefine Python web responsibility around framework and protocol fit, request authority, data and task effects, modernization, support, and recovery.
- Ruby on Rails developersDefine Rails responsibility around product authority, Active Record, jobs, performance, modernization, maintenance, and recovery.
Frontend
Roles for accessible product interfaces, semantic interaction, browser behavior, state, responsive systems, testing, performance and maintainable delivery.
- Angular developersDefine Angular responsibility around semantic interfaces, accessibility, component and state boundaries, server authority, browser evidence, performance, delivery, and upgrades.
- HTML and CSS specialistsDefine semantic and presentation responsibility around native controls, focus, the cascade, resilient layout, user preferences, browser evidence, and maintenance.
- Jamstack developersDefine Jamstack responsibility around rendering fit, content publication, browser and API boundaries, caching, performance, deployment, and recovery.
- React developersDefine React responsibility around semantic components, state identity, events and Effects, server authority, hydration, browser evidence, and recovery.
- Svelte developersDefine Svelte responsibility around semantic components, runes, load and actions, server authority, rendering, adapters, browser evidence, and recovery.
- Vue developersDefine Vue responsibility around semantic components, props and events, reactive ownership, routing, server authority, hydration, browser evidence, and recovery.
Mobile, game, and embedded
Roles for device-aware products, native and cross-platform interfaces, embedded constraints, game runtimes, connectivity, testing, distribution, performance, and lifecycle ownership.
- Android developersDefine Android responsibility around adaptive interfaces, lifecycle and state, data and server authority, background work, accessibility, device evidence, signing, release, and recovery.
- Blockchain developersDefine justified ledger responsibility around shared state, contracts, keys, external data, governance, verification, deployment, response, and recovery.
- C++ game developersDefine real-time game responsibility around gameplay state, object lifetime, frame budgets, multiplayer authority, tools, target packages, and live recovery.
- Embedded systems engineersDefine device responsibility around hardware contracts, timing, resources, drivers, protocols, power, signed updates, target evidence, and field recovery.
- Firmware engineersDefine low-level device responsibility around reset, startup, memory, registers, interrupts, drivers, boot trust, exact images, production evidence, and recovery.
- Flutter developersDefine cross-platform product responsibility around shared state, adaptive interfaces, native seams, plugins, target evidence, signed releases, upgrades, and recovery.
- Godot developersDefine interactive-product responsibility around scenes, resources, simulation, rendering, input, multiplayer authority, asset imports, target exports, and recovery.
- iOS developersDefine native iOS responsibility around lifecycle, state, adaptive and accessible interfaces, concurrency, privacy, device evidence, signed archives, release, and recovery.
- IoT developersDefine end-to-end connected-product responsibility across device identity, constrained communication, data meaning, command safety, fleet updates, and recovery.
- React Native developersDefine cross-platform mobile responsibility across shared React logic, deliberate Android and iOS seams, native dependencies, signed releases, upgrades, and recovery.
- Robotics engineersDefine physical-system responsibility across models, sensing, frames, estimation, planning, control, target evidence, safety boundaries, and recovery.
- Unity developersDefine real-time product responsibility across interaction, state, timing, assets, target performance, content delivery, release, and recovery.
- Unreal Engine developersDefine real-time product responsibility across gameplay ownership, cooked content, network authority, target evidence, packaging, patching, and recovery.
Product and delivery
Roles for product direction, analysis, research, design, facilitation, planning, risk, coordination, delivery evidence, and accountable learning.
- Agile project managersDefine delivery responsibility across outcomes, flow, dependencies, forecasts, risk, governance, releases, learning, and continuity.
- Business analystsDefine analysis responsibility across operating needs, workflows, decisions, rules, information, requirements, acceptance, change, and outcomes.
- Interaction designersDefine interaction responsibility across tasks, product states, actions, feedback, recovery, inclusive input, patterns, and implementation evidence.
- Product designersDefine end-to-end product-design responsibility across problem framing, journeys, interaction, content, visual systems, feasibility, and product learning.
- Product managersDefine product responsibility across user and organizational needs, strategy, outcomes, priorities, roadmaps, learning, and lifecycle decisions.
- Prototyping expertsDefine prototype responsibility across risky assumptions, fidelity, workflows, interactions, technical boundaries, test evidence, disposal, and production handoff.
- Scrum MastersDefine Scrum Master responsibility across empirical control, accountabilities, self-management, productive events, impediment removal, and measurable team improvement.
- Technical project managersDefine technical project responsibility across accepted baselines, interfaces, dependency logic, schedules, readiness, controlled change, release, and service transition.
- UI designersDefine interface-design responsibility across visual hierarchy, typography, spacing, color, responsive states, themes, tokens, components, and implementation review.
- UX researchersDefine research responsibility across questions, ethics, recruitment, consent, fieldwork, analysis, evidence, product decisions, and repository continuity.
Quality and security
Roles for compliance, assurance, adversarial testing, product quality, defensive operations, secure architecture, and software test evidence.
- Compliance specialistsDefine compliance responsibility across obligations, scope, control ownership, operating evidence, testing, exceptions, remediation, monitoring, and assurance boundaries.
- Ethical hackersDefine authorized security testing across written scope, safe execution, reproducible findings, remediation evidence, retesting, disclosure, and cleanup.
- Performance testersDefine performance responsibility across representative workloads, latency distributions, correctness, bottlenecks, capacity, recovery, cost, and regression evidence.
- QA engineersDefine quality responsibility across product risk, test bases, behavior models, exploration, automation, defects, regression, residual risk, and release evidence.
- Security analystsDefine defensive responsibility across telemetry, detection, investigation, vulnerability context, incident response, recovery, and learning.
- Security architectsDefine security architecture across protected outcomes, trust boundaries, threat scenarios, control design, quality tradeoffs, verification, and decision continuity.
- Security testersDefine repeatable security testing across requirements, application and platform surfaces, controlled execution, findings, remediation, retest, and regression evidence.
- Test automation engineersDefine automated feedback across product risk, test layers, architecture, data, environments, CI diagnosis, flake ownership, maintenance, and handoff.
[ WORKFLOW / SYSTEMS AUDIT ]
THE FIRST ENGAGEMENT
Start with one real workflow
A Systems Audit is the usual starting point. If the opportunity is already clear, we can move directly into a focused build.
Show Us the WorkflowStart with the free automation readiness checklistOBSERVEQUANTIFYDECIDEBUILD
Continue with the work
Choose the next useful path.
Stay with the operating question. The technology can wait until the work is clear.
01
Compare team models
Decide whether the gap belongs inside client-led augmentation, a dedicated team, managed engineering, or project delivery.
Open path02Explore Werkon Systems
Start with an owned system outcome when the need is broader than one specialist role.
Open path03Read the philosophy
See how client ownership, system fit, and human authority shape every engagement.
Open path