> ## Content Index
> Fetch the complete content index at: https://www.ariet.net/llms.txt
> Use this file to discover other available public pages before exploring further.

# We hire for the role, but we should hire for what the role does to the system
- URL: https://www.ariet.net/we-hire-for-the-role-but-we-should-hire-for-what-the-role-does-to-the-system/
- Published: 2026-11-03T12:27:38.000Z
- Updated: 2026-11-03T12:27:38.000Z
- Author: Richard Thackeray
- Tags: Enterprise Architecture

Reproduced from a LinkedIn post from June 2026

**Who this is for:** Hiring managers, recruiters and anyone who writes job specs or sits on interview panels; also architects who have been recruited against a list of frameworks.

**BLUF:** Job specs and competency-based interviews describe the inside of a role, but organisations mostly fail at the interfaces between roles. The people who add most value are drawn to those interfaces, so hiring should spend as much time on how a candidate treats the edges of their role as on what they do within it.

---

I’ve always thought I’d make a good recruiter, not because I have a nice haircut and an Eton accent, but because I understand the role well and, in doing so, can discover and describe it. In discovering impact in the mind of a practitioner, you are focusing less on knowledge of frameworks, etc., and more on how this person is going to add value to an organisational system.

Most job specs are descriptions of bounded territories. Here is the role, its responsibilities and where your work starts and stops.

That framing isn't accidental, as it reflects how we think about organisations: a collection of discrete components, each with its own defined interior. Get enough of those components filled with competent people, and the system works.

Except it doesn't work reliably, and I think the job spec is part of why.

A job spec describes what a role does internally. The activities, the behaviours, the deliverables. What it almost never describes is what the role does to the system around it. How it connects to the adjacent parts. What it enables, or blocks, or translates. What falls apart when it faces inward instead of outward.

In any system with real interdependencies, and organisations are nothing but interdependencies, the failure modes almost never live inside the roles. They live at the interfaces: the handoff assumed by both sides, the decision that fell into the gap between two functions, or the thing that's technically everyone's problem and therefore practically nobody's.

The people who generate disproportionate value are rarely the ones who execute their role definition most precisely. They're the ones who are drawn to those interfaces. They notice what's falling through the gaps and don't need permission to care about something adjacent. Maybe the biggest successes are those who can grow themselves and the role into what the organisation really needs.

But the job spec didn't ask for that; it asked for someone who fits the component's shape.

Enterprise architecture is a good example. The whole value proposition of EA is understanding how parts of a system relate to each other, where the tensions are, what the adjacencies mean, and what breaks when the connections are wrong. It's a discipline that only works at interfaces, and yet EA gets recruited against a technical skills inventory and a list of frameworks. Which measures capability inside the role, not orientation toward the system it's supposed to serve.

A job spec can only describe the interior of a role, because that's what a job spec is: a definition of a component. It cannot capture how someone relates to the edges of their responsibility, whether they treat a boundary as a limit or as a place of interest and what they do when something lands in the gap between their role and someone else's.

That's not a skill you can inventory, and it's almost invisible in a competency-based interview, because competency-based interviews are also about the interior.

What would it mean to hire differently? To spend as much time understanding how a candidate relates to the boundaries of their role as what they do within it? To ask not just what they've delivered, but what they noticed that wasn't theirs to notice?

The people who add the most value to complex systems are often the hardest to hire for, precisely because what makes them valuable falls outside the frame the job spec creates.

---

*A note on how I write. The observations, questions and arguments are mine; so is the experience behind them. I work with Claude, an AI assistant, on research and drafting, and I edit and check until I can stand behind each statement. Any errors are mine too.*