November 2, 2026
Hiring tech people for museums and heritage
Picture the interview. Your preferred candidate for Head of Infrastructure loves the collection, asks brilliant questions about the archive and then, a week later, accepts an offer from a consultancy across town. Nobody did anything wrong. You just lost to a bigger budget.
We see this pattern often. Cultural and heritage organisations need the same data, cyber, cloud and digital people as banks, consultancies and tech firms with far deeper pockets. Trying to win that race on salary alone is a race you will not win. The good news is that it is not the only race.
This guide is for directors, CEOs and heads of digital who need to fill difficult, high-stakes tech roles and want to do it well.
Stop competing on the wrong thing
Salary matters. Pretending otherwise insults candidates. But in our experience, the people who thrive in museums and heritage bodies rarely choose them for pay. They choose them because the work means something: protecting a collection, opening an archive to the public, keeping a charity's supporters safe.
So lead with what a better-paying employer cannot offer. That usually means:
- A mission the candidate can explain to their friends with pride
- Problems with real public value, not another quarterly sales dashboard
- Breadth: one engineer may touch infrastructure, applications and security in the same month
- Stability and a working culture that respects life outside work
Then be honest about the salary early. A clear range in the first conversation saves everyone a month of hope followed by a polite no.
Write the brief for the job, not the wish list
Heritage job descriptions often try to hire three people in one. A "Digital Manager" who runs the website, manages the CRM, leads on data protection and secures the network is not a role. It is a staffing plan.
Before you advertise, ask yourselves:
- What must this person deliver in their first 12 months?
- Which two or three skills are non-negotiable, and which can we teach?
- Who will this person report to, and does that manager understand the work?
- If we could only fix one problem with this hire, what would it be?
A sharper brief attracts sharper candidates. It also tells experienced tech people that you know what you are asking for, which is half the battle in a sector they may not know well.
Find the people who are not looking
The strongest cyber analysts, data engineers and platform leads are usually busy doing their current jobs well. They do not scroll the same job boards your advert sits on.
Reaching them takes a mix of approaches. Sometimes a well-placed advert in the right specialist channel works. Sometimes it takes direct, targeted conversations with people who have never thought about working in culture, but who light up when they hear about the collection or the mission. For the most senior and hardest roles, a dedicated search is often the right call. The point is to match the approach to the role, not to force every vacancy through the same process.
Hire for values and technical depth, equally
A brilliant engineer who resents the pace of a public institution will leave. A lovely person who cannot run your SQL Server estate will leave you exposed. You need both.
A simple framework we use:
- Can they do it? Test the core technical skill with a real problem from your environment.
- Will they enjoy it here? Talk openly about budgets, governance and how decisions get made.
- Will they stay? Ask what would make them leave in year two, and listen carefully.
Retention is the real measure of a good hire in this sector. Rehiring the same role every 18 months drains small teams and erodes the institutional knowledge that heritage organisations depend on.
Move faster than your committee wants to
Cultural organisations are careful by nature, and that is a strength when you are looking after irreplaceable objects. It is a weakness in a hiring process. Good tech candidates often have more than one conversation on the go, and long gaps between stages are where they drift away.
- Agree the interview panel and dates before the role goes live
- Keep it to two or three stages
- Give feedback within days, not weeks
- Have sign-off for the offer ready before final interviews
What this looks like in practice
One national museum with sites in more than one region has worked with us for five years. Over that time we have filled twelve technical and leadership roles for them, from cyber security analysts and Linux administrators to infrastructure managers and a head of platforms and development. Every role they engaged us on was filled.
They could never lead on salary. What worked was positioning each role around the mission and stability of the institution, reaching people who were not actively looking, assessing technical depth and cultural fit in equal measure, and giving honest feedback on salary and pace throughout. The people placed have stayed, which in this sector is worth as much as the hire itself.
If you want to see how we work with museums, galleries, archives and heritage trusts more broadly, our page on tech recruitment for mission-led, cultural and heritage organisations sets it out.
Questions to take into your next leadership meeting
- Which of our open tech roles would hurt most if it stayed empty for six months?
- Can we explain, in two sentences, why a strong engineer should choose us over a bank?
- Is our hiring process quicker than the candidate's other options?
- Are we hiring for the next 12 months or the next five years?
The collection needs a team
Your collection, your archive and your audiences depend on people most visitors will never meet. The organisations that hire them well do not outbid the market. They out-explain it, out-pace it and look after people once they arrive.
If you have a data, digital, cyber, cloud or tech leadership role that is proving hard to fill, register your vacancy with us. We will talk it through, give you an honest view of the market and suggest the approach that fits the role best.
Photo: Tek monde, CC BY-SA 4.0, via Wikimedia Commons
Back to news