1. Home
  2. Blog
  3. Canon
  4. Years Experience Broken Metric
Why “Years of Experience” Is a Broken Metric

Why “Years of Experience” Is a Broken Metric

Time elapsed is not competence acquired. Why we need to replace chronological aging with 'Project Density' and 'Decision History'.

- 2025-06-30 - Archade Standards Bureau

Why “Years of Experience” Is a Broken Metric

Time elapsed is not competence acquired. Why we need to replace chronological aging with 'Project Density' and 'Decision History'.

The "Temporal" Fallacy

Open any job board. Indeed, LinkedIn, Archinect. What is the first filter? "Years of Experience."

  • "Junior: 0-3 Years."
  • "Intermediate: 4-7 Years."
  • "Senior: 8+ Years."

This is the laziest metric in human history. It assumes that Time is a proxy for Competence. It assumes that 1 Year = 1 Unit of Learning.

This is a lie. In Architecture, Time is not linear. Some years are "Empty." Some years are "Dense."

The "Tale of Two Architects"

Let's compare two candidates. Both have "5 Years of Experience." On LinkedIn, they look identical. They both cost $90,000.

Candidate A (The Repetitive Loop):

  • Worked at a firm doing cookie-cutter suburban housing.
  • Spent 5 years doing the exact same permit set for the exact same house type.
  • Encountered 1 type of zoning code.
  • Encountered 0 complex consultants.
  • Result: They don't have 5 years of experience. They have 1 year of experience, repeated 5 times.

Candidate B (The Deep Dive):

  • Worked at a high-intensity firm on a $2B Airport Terminal.
  • Spent 5 years navigating a complex BIM model with 400 linked files.
  • Coordinated with Acoustic, Bag Handling, Fire Engineering, and Facade consultants.
  • Managed 500 RFIs.
  • Result: They have "20 years" of exposure compressed into 5 chronological years.

If you hire Candidate A for a complex job, you fail. If you hire Candidate B, you get a bargain. "Years" measures attendance. It does not measure outcome.

Competence is built through Decision-Making. A resume doesn't show decisions. It only shows "Tenure." An Archade profile shows Nodes of Responsibility. It allows a hiring manager to see the complexity of the work, not just the duration of the job.

The Metric of "Project Density"

We need to retire the Calendar. We need to start measuring "Exposures."

An Exposure is a unit of professional friction. It is when you touch a system, make a decision, and see the result.

A pilot logs "Flight Hours," but they also log "Landings." Flying in a straight line is easy. Landing in a storm is hard. We need to count the Landings.

Quantifying Density

What if your resume didn't list dates, but listed Counts?

  • System Exposures: "I have coordinated 12 Curtain Wall packages."
  • Jurisdictional Exposures: "I have passed the NYC DOB review 8 times."
  • Financial Exposures: "I have managed $50M of Change Orders."

This is Granular Competence. This is Machine Readable. A "Curtain Wall" is a node. A "DOB Review" is a node. We can count them.

A 25-year-old with High Density (many exposures) should be paid more than a 40-year-old with Low Density (few exposures). Currently, the 40-year-old gets paid more simply because they didn't die for 15 more years. That is "Pension Logic," not "Performance Logic."


The "Scar Tissue" Record

Competence is built through scar tissue. You learn when things go wrong. You learn when the waterproofing fails. You learn when the contractor claims a delay.

A resume doesn't show scars. It shows "Tenure." "I was at Firm X for 3 years." Great. Did you learn anything? Or did you hide in the bathroom?

An Archade profile shows Nodes of Responsibility. It allows a hiring manager to see the complexity of the work.

  • "Oh, you worked on the Shoreditch Tower?"
  • "That project had a Cantilevered Facade."
  • "And you were the Technical Lead?"

I don't need to ask how many years you have. I know that if you survived the "Shoreditch Cantilever," you have the scars. You have the knowledge.


Toward a "Competence Score"

Imagine a world where your "Market Value" is determined by your Verified Project Graph.

  • Your Score: Calculated based on the Volume and Complexity of verified nodes you are attached to.
  • The Adjustment: Weighted by the reputation of the Firms you worked with. (A year at Herzog & de Meuron might be weighted 2x a year at a generic office).

In this world:

  1. Talented Youth Rise: A brilliant 24-year-old ("Sarah") who runs a massive job gets the "Score" of a Senior. She gets the salary of a Senior. The ageism of "Wait your turn" is destroyed.
  2. Experienced Elders Shine: An older architect who maybe doesn't know the latest software—but has solved 500 complex site problems—has a massive "Exposure Score." They are valued for their wisdom, not discarded for their age.

We move from "Biased Hiring" (Age/Gender/Race) to "Blind Competence Hiring" (Data/Results).


Summary: Accuracy over Aging

Time is a lazy metric. It is a heuristic we use because we are too lazy to measure the truth.

But Data allows us to be precise. By documenting the actual moves you take on a project—the systems you touch, the teams you lead—you are building a record that makes "Years of Experience" irrelevant.

Measure the density, not the dates. Don't tell me how long you've been here. Tell me what you've handled.

Scale your value.

Turn your time into a structured record of technical exposures. Show the density. Show the scars. Get paid for the reality.

Build Your Competence Graph →

Read Next

Why AEC Lacks Shared Standards for Professional Proof
canon5 min
Why AEC Lacks Shared Standards for Professional Proof
Architecture is a technical field with an amateur record. Why we lack a universal language for competence, and why that's an economic disaster.
Toward a Canon of Professional Signal in AEC
canon5 min
Toward a Canon of Professional Signal in AEC
We have a canon of buildings; we need a canon of signals. What are the 'Global Truths' that define a high-performance AEC professional?
The Vocabulary Problem in Architecture Careers
canon5 min
The Vocabulary Problem in Architecture Careers
Vague titles lead to vague value. Why we need to move from poetic job descriptions to a technical taxonomy of professional action.

Machine-Readable Feeds

  • AEC News (XML)
  • Projects (JSON)
  • Global (JSON)
  • Signals (XML)
  • Jobs (XML)

Discovery Maps

  • Global Sitemap
  • Projects Graph
  • Organization Index
  • AEC Datasets

Intelligence Routes

  • Discovery Signals
  • Freshness Log
  • Dataset Catalog

© 2026 Archade. All rights reserved.

••Blog•Pricing•Help•Credentials•
Privacy Policy•Terms of Service•Legal•