The Measurer Test | Arunesh Parab

AI isn't replacing all workers equally. It's coming first for the roles built around tracking, reporting, and coordinating — the measurers. This framework helps you evaluate any role before you hire for it.

The Core Question

Don't ask "Can AI help this person?" Ask "Should this be an agent problem from day one?"

The first question assumes the role exists. The second challenges whether it should. That shift changes hiring decisions.

The 6-Question Rubric

Score each dimension 1 (low automation potential) to 5 (high automation potential). Total the scores.

1. Making vs. Measuring

Is this role building, selling, or deciding — or mostly tracking and reporting on what others do?

Score 1: Pure builder, seller, or decision-maker
Score 5: Pure tracker, reporter, or coordinator

2. Repeatability

Are outputs genuinely one-off, or recurring reports, status updates, and approval flows?

Score 1: Every output is unique and context-dependent
Score 5: Recurring templates with variable data

3. Data Availability

Is the information they need already in your tools, or locked in conversations and relationships?

Score 1: Locked in tacit knowledge, relationships, and unstructured conversations
Score 5: Fully available in logs, CRM, tickets, analytics

4. Judgment Complexity

Are they resolving genuinely messy trade-offs, or applying clear thresholds to structured data?

Score 1: Ambiguous decisions with incomplete information and competing stakeholders
Score 5: Clear rules applied to structured data

5. Error Risk

If AI gets this wrong, what's the blast radius?

Score 1: Catastrophic — legal liability, safety, key relationship damage
Score 5: Cheap to catch and fix, low-stakes

6. Oversight Ease

Can a human review the AI's output quickly and spot mistakes?

Score 1: Review takes as long as doing it yourself
Score 5: Mistakes are obvious at a glance

Interpreting Scores

24–30: Build an agent. Don't open the role. Design a workflow or internal tool.

18–23: Hybrid role. Let AI handle the measuring. Keep humans for the deciding.

12–17: Keep & streamline. The person stays. Automate the repetitive parts so they focus on judgment work.

6–11: Protect & amplify. High-judgment, high-stakes work. Give them AI tools; don't replace them with AI tools.

Pattern Recognition

After scoring dozens of roles, clear patterns emerge:

High scores (automate):

Product ops and internal reporting
Cross-team coordination and status aggregation
Analyst-style "glue" roles synthesizing data across systems
Approval flow management

Low scores (protect):

Senior engineers with system-level ownership
Product owners with direct customer accountability
Technical leads making architectural trade-offs
Anyone whose job requires reading a room, not a dashboard

How to Apply

Before posting any new role, score it against all 6 dimensions
If it scores above 24, design the workflow before opening the requisition
If it scores 18–23, redesign the job description around the judgment parts only
Review existing roles annually — automation potential shifts as your tools improve

Try the interactive version of this rubric to score a role on your team.

Read the full analysis: Stop Hiring Measurers. Build Agents Instead.

The org design lesson isn't "fire measurers later." It's "don't build those roles in the first place." Hire builders and owners. Give them agents who do the measuring.