An information architect does not usually write the words that end up on a page; they decide where that page sits, what it is called, what lives next to it, and how someone finds it in the first place. The primary pull is Organization applied to knowledge itself rather than to physical things or schedules — the distinct contribution is building the categories, hierarchies, and navigation structures that let everything a technical author, a UX writer, or a product team produces actually be findable, rather than existing as isolated, unconnected pages. It is deeply underrated work precisely because it succeeds invisibly: nobody notices good information architecture, they only notice bad information architecture, in the form of a website or a knowledge base where the thing they need is definitely somewhere but they cannot find it.
The daily texture is closer to systems thinking than to writing — card-sorting exercises with real users to see how they naturally group content, auditing thousands of existing pages to find duplication and gaps, and building the taxonomy and navigation model that a much larger team of writers and designers will then build content into for years.
Kitsune can talk through anything on this page — whether it might suit you, what to do next, questions this page doesn't answer. Everything here is yours to read either way.
Titled "information architect" roles have genuinely thinned in the UK job market even as the underlying skill has become more valuable embedded inside other roles — job postings citing information architecture specifically fell from 55 to 37 over a recent twelve-month period even as demand for the underlying discipline grew inside content design, UX, and platform teams [survey_aggregator, itjobswatch.co.uk 2026]. This makes the honest picture more complicated than a simple growth story: the standalone job title is contracting while the skill itself is becoming table stakes for senior content design and UX roles, so many people who do this work now hold a different job title entirely. Where the dedicated title does survive, pay is high relative to the rest of the field — UK figures put the median around £85,000, with London roles often quoted between £95,000 and £130,000 [survey_aggregator, itjobswatch.co.uk / industry salary reporting 2026] — reflecting how few people are genuinely good at large-scale structural thinking about content.
There is no dedicated undergraduate degree; entrants typically arrive from content design, UX design, library and information science, or technical writing, and build information architecture skill through practice — running card sorts and tree tests, auditing real content sets, and studying established methods (Richard Saul Wurman's foundational work, the "Polar Bear Book" by Rosenfeld and Morville, both still the field's standard references). A library and information science postgraduate qualification is a genuine if less common route in, given the direct overlap between cataloguing and digital information architecture.
The documented posting decline likely reflects organisational restructuring (skill moving inside UX/content-design/platform roles) at least as much as direct AI displacement -- the field's most genuinely ambiguous attribution case.
Standalone title likely keeps contracting; underlying skill's value rises as an embedded competency in other senior roles.
People drawn to Information Architectare often drawn to these — in the order they're closest. The ones marked sit in a different field entirely.