Chief Knowledge Officer
Owns what the company knows: where it is written down, whether it can be found, and whether it survives the people who leave.
Who to hire
The shape of person who does this job well — and whether you should be hiring it at all yet.
A seat in knowledge businesses — consultancies, law and accounting firms, engineering practices, research organisations — where the inventory walks out of the door every evening. Elsewhere it is a part of the CIO or COO seat. The test is simple: if a key person resigning would cost you months, you have a knowledge problem and probably no owner for it.
Education
Information science, library science, consulting or engineering. The discipline is as much editorial as technical.
Experience
8+ years running knowledge or practice management, including one migration where the content survived. Ask how they got people to contribute, because that is the hard part.
Vertical / domain experience
Matters in professional services, where the knowledge is the product, and in regulated engineering, where the record is the evidence.
What it pays, roughly
$119,995 median, Canada — for Administrative services managers, the closest occupation Statistics Canada actually measures, measured from $104,000 to $123,718 over 192,795 people. That occupation is broader than this role, so read it as an anchor, not a salary band — and note that a startup usually pays below it in cash and above it in equity.
Credentials and certifications
What exists, who issues it, and whether it means anything for this seat. A credential is evidence of a floor, never of judgment — and in a few of these roles it is a legal requirement rather than a nice-to-have.
| Credential | Issued by | When it matters |
|---|---|---|
| Knowledge management frameworks and benchmarking | APQC | The established body of practice in this field. |
| Library and information science qualifications | Accredited LIS programmes | Genuinely relevant: taxonomy, retrieval and curation are a profession. |
| CDMP — data management | DAMA International | Where the knowledge estate overlaps structured data. |
What this role does at each stage
The same title means three different jobs depending on how much money is in the bank. Read the stage you are at, then read the next one — that is what you are hiring toward.
Nobody. One document per decision, somewhere everyone can read it.
Still nobody. The discipline is a habit at this stage, not a function: write down what was decided and why.
A seat in a knowledge business, or part of the CIO’s seat elsewhere, once onboarding takes longer than it should because nothing is written down.
Who it sits beside
A specialist seat is defined as much by the seats around it as by its own work — which hat it reports through, which one asks the adjacent question, and which one it must stay independent of.
Works hand in hand with the Chief Learning Officer, who often reports into this seat: knowledge management captures what the company knows, learning gets it into people’s heads.
Can one person hold this and something else?
The whole point of the many-hats problem: which of these jobs merge safely into one person, and which merges quietly cost you money or control.
Merges well with
Knowledge and learning merge naturally, and both merge into the CIO where the question is mostly about systems rather than content.
Keep separate from
No conflict. The failure mode is a knowledge function with no editorial authority — it produces a repository nobody trusts.
Reading a candidate
What good looks like in an hour, and what should stop the process.
Good signals
- Asks what people cannot find today
- Measures retrieval, not contribution volume
- Prunes as much as they publish
Red flags
- Buys a wiki and declares victory
- No taxonomy
- Mistakes volume for knowledge
What this role runs on
The software categories this seat lives in, each linked to the screen of who sells it — the incumbent, the challengers and what the lock-in is.