ROSAI: Role-Oriented Skills Assessment for AI — A Framework for Role-Relative AI Readiness
Author: Prasanjit Saha
Version: 1.0
Repository: Zenodo
DOI: 10.5281/zenodo.22801326
ROSAI Framework · Version 1.0
A framework for measuring AI readiness relative to what a role actually expects.
ROSAI — Role-Oriented Skills Assessment for AI — is a framework developed by Prasanjit Saha for assessing professional AI readiness relative to the mix of responsibilities expected from a role.
AI capability is multidimensional. AI readiness is role-relative. ROSAI represents a target role as a blend of responsibilities, dynamically adjusts the importance of seven AI capability dimensions, and reports capability separately from Evidence Strength and Assessment Confidence.
Developed by Prasanjit Saha · Version 1.0 · September 2026
Research records: Zenodo · SSRN
Product / Business · Software Engineering · Data / ML · Operations / Transformation · Design / UX · Leadership / Governance
AI Fluency · Applied AI Judgement · Build & Execution · Evaluation & Reliability · Data & ML Capability · Responsible AI & Governance · Business & Organizational Impact
The role composition changes the relative importance of the seven capabilities.
ROSAI Score + Evidence Strength + Assessment Confidence. Each answers a different question.
AI capability belongs to the individual. AI readiness exists in relation to a role.
How well does this person's AI capability fit what this role actually expects?
“AI-ready” is increasingly used as a professional label, but it has no single practical meaning.
For one person, AI readiness may mean using generative AI effectively for research and productivity. For another, it may mean building RAG systems, integrating AI APIs or deploying ML workflows. A Product Manager may be expected to identify strong AI use cases and evaluate product quality. A senior leader may need to make sound decisions on AI strategy, governance, risk and adoption.
These can all be legitimate forms of AI capability. They are simply not the same capability.
Job titles are imperfect proxies for responsibility. Two people called “Product Manager” may be expected to perform very different combinations of product, engineering, data, transformation and leadership work. ROSAI therefore evaluates readiness against the responsibility mix of the target role.
The same person can be highly AI-ready for one role and less AI-ready for another without their underlying capability changing.
AI literacy, AI competency and professional AI proficiency already have substantial research and framework literature. Existing work includes validated AI-literacy scales, workforce competency frameworks, role-sensitive professional skills models and role-adaptive assessments. The references below identify the work discussed in the formal paper.
ROSAI does not claim to have invented multidimensional AI capability or role-aware assessment.
ROSAI proposes an assessment architecture built around four combined design choices:
A role is represented as a percentage mix of responsibilities rather than one fixed occupational label.
The role composition mathematically determines the relative importance of the capability dimensions.
Demonstrated capability, supporting evidence and confidence in interpretation are not collapsed into one number.
A severe weakness in a capability identified as core to the role cannot always be averaged away by unrelated strengths.
This is a proposed contribution, not a claim that ROSAI is the first framework in history to combine these ideas. Version 1.0 makes the methodology explicit enough to be tested, challenged and improved.
ROSAI models the target role as a six-component vector whose values sum to 100%.
| Responsibility | Example share |
|---|---|
| Product / Business | 50% |
| Software Engineering | 20% |
| Operations / Transformation | 15% |
| Leadership / Governance | 10% |
| Data / ML | 5% |
| Design / UX | 0% |
This could represent a hands-on AI Product Manager. It is not intended to be the standard profile for every Product Manager.
Different role-relative reading
Different role-relative reading
Different role-relative reading
Practical understanding of AI concepts, capabilities, limitations and common solution patterns sufficiently to work effectively with AI.
Ability to decide when, where and how AI should be used, including trade-offs across value, accuracy, latency, cost, privacy, risk and human oversight.
Ability to move from an AI idea toward a working prototype, workflow, integration, production implementation or managed delivery.
Ability to determine whether an AI system is reliable enough for its intended use through evaluation, validation, monitoring, edge-case testing and controls.
Ability to understand and work with data and machine-learning concepts at the depth required by the role.
Ability to recognize and manage privacy, security, permissions, fairness, explainability, auditability, human oversight, regulatory exposure and responsible deployment.
Ability to connect AI activity to adoption, productivity, customer outcomes, cost, revenue, workflow redesign, prioritization and organizational change.
ROSAI deliberately separates building something with AI from creating value with AI.
The target role composition is combined with a versioned role–capability model to derive the relative importance of each capability.
A role-heavy requirement for Build & Execution will assign more weight to that dimension. A leadership/governance-heavy role may assign more importance to Responsible AI & Governance and Business & Organizational Impact.
Weighted averages can hide severe gaps. A candidate can score extremely well in several dimensions and mathematically compensate for a major weakness elsewhere.
ROSAI therefore includes a non-compensatory safeguard for capabilities that the target role identifies as core. In Version 1.0, the public methodology exposes the principle, while operational thresholds remain versioned implementation parameters.
A severe gap in a capability that the role itself defines as core should not always be averaged away by unrelated strengths.
How well does the assessed capability profile fit this role?
Represents role-adjusted AI capability.
How strongly are the relevant capability claims supported?
Can include live products, repositories, demos, design documentation, case studies, measurable outcomes, publications, employer work or references.
How confidently can the available assessment signal be interpreted?
Considers completion, consistency, scenario alignment, response quality and supporting evidence.
Evidence Strength and Assessment Confidence do not directly increase or decrease the ROSAI Score in Version 1.0.
SCORE-AI is the first reference implementation. It uses an approximately 15-minute, 18-question assessment combining multiple signal types rather than relying entirely on self-rated proficiency.
Structured questions provide consistency and scalability. Adaptive scenarios provide an applied reasoning signal.
The adaptive cases are evaluated against four common criteria:
The grading model is intended to act as a rubric executor rather than an unconstrained judge. It is instructed to score explicit content, avoid rewarding jargon and avoid inferring experience that the respondent did not state.
The operational assessment stores framework, rubric, prompt and grader-model versions to support later reproducibility testing.
Target role composition · Responsibility level · Structured responses · Practical-experience signals · Optional evidence · Adaptive scenario responses
ROSAI Score · Evidence Strength · Assessment Confidence · Seven capability scores · Role-relevant strengths · Development priorities
Not publicly disclosed in Version 1.0:
ROSAI distinguishes framework transparency from answer-key disclosure. The public paper exposes the methodology needed to understand, critique and cite the framework, while keeping the operational answer key from becoming a gaming guide before validation is complete.
A person's lowest absolute capability is not automatically the most useful thing to improve.
A Data/ML gap may be highly consequential for an ML-heavy role and far less consequential for a leadership role where Data/ML depth has low importance.
ROSAI Version 1.0 is a practitioner-designed framework and testable methodology. It has not yet undergone psychometric validation or peer review.
It is currently not:
The framework contains formal equations. Formalization makes the methodology explicit; it does not make the methodology empirically validated.
ROSAI should evolve through evidence rather than author judgement alone.
A framework for AI readiness should itself be evidence-driven.
SCORE-AI — Skills, Capability, Outcomes, Role-fit & Evidence for AI — is the first public implementation of ROSAI.
Define a target role mix, complete the assessment, provide optional evidence and receive a role-oriented capability profile: ROSAI Score, Evidence Strength, Assessment Confidence, seven capability scores, strengths, development priorities and a downloadable report.
Free · ~15 minutes · No sign-up · No sign-in
ROSAI Version 1.0 is publicly documented as a practitioner-designed framework and testable methodology. The same framework paper is available through both Zenodo and SSRN for citation, discovery and long-term access.
Author: Prasanjit Saha
Version: 1.0
Repository: Zenodo
DOI: 10.5281/zenodo.22801326
Author: Prasanjit Saha
Platform: SSRN
SSRN Abstract ID: 7479102
DOI: 10.2139/ssrn.7479102
These are two public records of the same ROSAI v1.0 framework paper. Their presence on Zenodo and SSRN should not be interpreted as peer review or empirical validation.
Saha, P. (2026). ROSAI: Role-Oriented Skills Assessment for AI — A Framework for Role-Relative AI Readiness (Version 1.0). Zenodo. https://doi.org/10.5281/zenodo.22801326
All-versions Zenodo DOI: 10.5281/zenodo.22800584
Saha, P. (2026). ROSAI: Role-Oriented Skills Assessment for AI — A Framework for Role-Relative AI Readiness. SSRN. https://doi.org/10.2139/ssrn.7479102
Bibliographic entries from the formal ROSAI paper. The paper contains the definitive bibliography.