Skills you need to be a information architect
8 skills a hiring manager would actually test for, each with the level this role expects and what it is used for. Not a syllabus — the shape of the job.
Build my path to this roleUpskili checks what you can already do, then sequences only what is missing. No account needed.
What the role requires
Ordered by how much the job depends on it. The bar is the proficiency expected of a competent information architect — not mastery, and not a passing acquaintance.
-
Information architecture modeling
Essential
Designs site maps, taxonomies, and navigation structures for complex digital products.
Strong -
Card sorting and tree testing
Essential
Validates and iterates on information structures with real user data.
Strong -
Figma or Sketch
Important
Creates wireframes and content hierarchy prototypes for stakeholder review.
Strong -
Content inventory and audit
Important
Evaluates existing content to identify gaps, overlaps, and restructuring needs.
Strong -
User research synthesis
Important
Translates user mental models into actionable structural design decisions.
Working -
Taxonomy management software (e.g., PoolParty)
Useful
Builds and maintains controlled vocabularies and metadata schemas.
Working -
HTML/CSS understanding
Useful
Communicates effectively with developers about structural markup implications.
Working -
Workshop facilitation
Useful
Leads cross-functional sessions to align on structure and labeling.
Working
An order worth learning it in
A list of ten skills is the same unhelpful answer a catalogue gives, just sorted. This is where to actually start.
Start here
Essential to the role, and reachable from a standing start. Everything below rests on these.
- Card sorting and tree testing
- Figma or Sketch
- Content inventory and audit
- User research synthesis
Then this
The rest of what the role is assessed on. Harder, and it builds on the foundation above.
- Information architecture modeling
What sets you apart
Not what gets you hired, but what separates doing the job from being trusted with it.
- Taxonomy management software (e.g., PoolParty)
- HTML/CSS understanding
- Workshop facilitation
You almost certainly have some of this already.
That is the point of starting from the role rather than a course. Upskili checks what you can do, then builds a path across only the gap.
See my path to information architect