Career Readiness and the Career Readiness Score

There is no single universal readiness number. Readiness is always measured against a target role, because the requirements of a software engineering role, a data role and a public-service role are genuinely different. Changing a target role recalculates role-specific readiness while preserving all previously earned evidence and the person's Talent Record.

Airaw considers evidence of several kinds. The exact weighting is proprietary and is not published, but the categories are deliberately transparent:

• Learning — training completed against the requirements of the target role.
• Assessments — performance on skill and role-specific assessments.
• Skills — capability demonstrated, not merely listed.
• Projects — practical work recorded with verifiable detail.
• Consistency — sustained activity rather than a single burst.
• Practical exposure — internships, campus activity and applied work where recorded.
• Communication — structured communication assessment results.
• Career-specific evidence — items that a particular role expects and others do not.

Readiness describes preparation. Eligibility is a separate, employer-defined test — marks, batch year, backlogs, location or other criteria an organisation sets for a specific opportunity. Airaw keeps the two apart deliberately: a student can be eligible and not yet ready, or ready and not eligible, and both facts are shown honestly.

Where evidence does not exist, Airaw reports insufficient evidence rather than inventing a low score. This matters for fairness: a student who has not yet attempted something has not failed it, and an employer screening a candidate sees the distinction. See AI recruitment.

Every readiness view carries its reasoning: which requirements are met, which are not, and what evidence supports each conclusion. Airaw does not publish its scoring internals or any detail that would let the measurement be gamed, and it does not present a score without the reasons behind it.