A job description is a structural map. Five signals that tell you whether a role is on the compression side or the appreciation side of the AI economy.
Most professionals evaluate a job description by reading the responsibilities and the salary band. The more useful read is structural: a job description is a map that predicts whether the role compresses or appreciates over the next 24 months. Five signals in the text tell you what side of the AI compression curve the role sits on. Read them before you accept the offer; read them every quarter for the role you currently hold.
The structural reading takes 5-10 minutes per JD once you know what to look for. The payoff is real: the difference between accepting an exposed role and an appreciating role is often the difference between a 24-month wage stagnation and a 24-month wage compounding by 30-50%. Most professionals never do this analysis.
Signal 1: How the verbs cluster
Look at the verbs in the responsibilities section. If they cluster around 'produce, draft, prepare, compile, generate, format, summarise, populate, maintain, update', the work is on the production layer. If they cluster around 'decide, prioritise, negotiate, advise, own, lead, architect, design, set strategy, drive', the work is on the judgement layer. The first set is being substituted; the second set is appreciating.
Count the ratio. If 80% of the verbs are production-tier, you are reading an Execution-band JD regardless of what the title says. If 50/50, you are reading an Operator-band role. If 70-80% are judgement-tier, you are reading an Architect-band role. The verbs are the most reliable structural signal in the document.
Signal 2: How accountability is described
Look for explicit accountability language. 'Accountable for', 'owns the outcome of', 'responsible for the call on' indicate roles where the buck stops with the postholder. 'Supports', 'assists', 'helps to', 'contributes to', 'works with' indicate roles where someone else owns the outcome and the postholder is in the production tier. Accountability language correlates directly with the durability framework in authority bands.
The single most-revealing test: search the JD for the word 'own'. A senior role that does not contain ownership language anywhere in the responsibilities is most likely an inflated-title execution role. A junior role that does contain ownership language for at least one outcome is unusually well-positioned for its tier.
Signal 3: How stakeholder scope is described
Single-team scope is more compressible than cross-functional scope. Cross-functional scope is more compressible than executive-stakeholder scope. The richer and more senior the stakeholder scope a role describes, the more durable the role. If the job description is silent on stakeholder scope and only describes deliverables, that itself is a signal: the role is execution-tier.
Specific phrases that signal durability: 'partnering with the leadership team', 'briefing the board', 'representing the function externally', 'managing relationships with senior counterparties', 'cross-functional alignment with [other senior functions]'. These signal architect-band scope. If absent, the role is producer-band.
Signal 4: How tooling is mentioned
If the job description requires fluency with specific specialist platforms (e.g., Salesforce admins for CRM-deep work, SAP consultants for ERP, regulated-industry tooling), that is specialist work that AI augments but does not substitute. If the job description requires generic 'attention to detail' or 'working with data' in vague terms, that is generic production work that AI is substituting.
Modern signal: explicit AI-tooling fluency requirements. JDs that specify experience with Cursor, Claude Code, dedicated industry-AI platforms, or AI-orchestration tooling indicate roles where the AI-augmented architect-layer work is part of the spec. JDs that mention nothing about AI in 2026 are signalling either organisational lag (which has its own structural-risk implications) or genuine work where AI is irrelevant (durable physical or relational work). Both are readable signals.
Signal 5: How seniority interacts with the work
A job description for a senior role that lists tasks indistinguishable from the junior version of the same role is a yellow flag. It usually means the seniority is in the title, not the work. Genuine seniority involves judgement, accountability, and stakeholder scope that is structurally different from junior work. The compression hits the title-only senior roles fastest because they have the salary expectation of seniority and the structural exposure of the production tier.
The diagnostic test: read the senior JD, then mentally substitute the title with the junior version of the same role. If the responsibilities still read coherently with the junior title, the seniority is title-only. If they break down (because junior couldn't credibly own those decisions), the seniority is structural.
Combining the signals
Each signal alone is informative; the combined reading is more reliable. The strongest durable JD has: judgement verbs dominant + explicit ownership + executive-stakeholder scope + specialist-and-AI tooling fluency + structurally-different senior responsibilities. Most JDs in 2026 fail at least one of these tests; a JD that passes all five is unusually well-positioned.
The weakest JD has: production verbs dominant + supporting/contributing language + single-team scope + generic skill claims + senior responsibilities that read like junior work. This is the configuration the structural framework reads as 'high exposure regardless of title' and the configuration that compresses fastest under AI tooling adoption.
What to do with the reading
If the JD reads durable, the role is worth pursuing on structural grounds even if the salary is moderate. The structural slope is more valuable than the starting salary over 24 months.
If the JD reads exposed, accept the role only if you can negotiate scope expansion at the offer stage or have a clear architect-layer migration path inside the first 12 months. Otherwise the role is a step into the compression zone.
If you're already in an exposed role, use the JD-reading framework on your own job description as a baseline, then on the next-band JD as a target. The gap between the two is the migration plan.
Reading job descriptions structurally takes practice. The structural inventory of what AI cannot do is in what AI cannot replace; the framework articles (authority bands, compression curve, executor-to-architect migration) cover the macro picture. The role-by-role taxonomy this article references lives on the roles directory.
Run your structural assessment
The AI Career Index is free to take. Get your structural snapshot in 10 minutes, including your durability score, archetype, and projection.
Take the Free Assessment