Skip to main content

Tracks and Rubrics

Occupation-Ops wins by depth, not by generic breadth.

Primary track​

The current flagship track is:

  • AI Frontend Architect

This is the main wedge for candidates moving toward:

  • AI Frontend Engineer
  • Angular Architect
  • Copilot UI Engineer

Adjacent tracks​

The next adjacent tracks in the repo are:

  • Frontend Engineer
  • Full-Stack AI Engineer

Why rubrics matter​

Role-specific rubrics move the repo away from generic prose generation and toward a stronger scoring model.

Rubrics make it possible to:

  • score proof density
  • detect unsupported claims
  • measure recruiter scan readiness
  • compare visible proof against role expectations
  • render the same evaluation into Markdown, JSON, and HTML

Contributor direction​

New tracks should not be added as shallow templates. They should come with:

  • a clear target role
  • a structured rubric
  • realistic proof criteria
  • tests or golden outputs where possible