Why pre-screen data governance managers before the interview
Governance fails in a recognisable way. A policy is written, a catalogue is bought, ownership is assigned to people who did not agree to it, and a year later nothing has changed except the number of documents. Managers who succeed start from a problem teams already feel, usually a report nobody trusts, and build ownership from there. A short screen asks what was adopted and what it changed, which separates the two approaches immediately.
What actually matters when screening Data Governance Manager candidates
- 01
Technical depth
Check depth on cataloguing and lineage tooling: Collibra, Alation or Purview, DAMA-DMBOK domains, master data matching rules, retention schedules, and how they defined data quality dimensions and thresholds.
- 02
Real incidents and findings
Probe actual governance failures they handled: a DSAR they could not fulfil, a broken lineage feeding a regulatory report, duplicate customer records, or a failed audit finding.
- 03
Risk judgement
Assess how they rank data risk: classification tiers, critical data element selection, GDPR or CCPA exposure, cross-border transfers, and where they accepted risk rather than blocking a release.
- 04
Getting things fixed
Look for evidence they moved stewards and engineers to act: data owner appointments, governance council agendas, policy adoption rates, quality scorecards trending up, issues closed in the log.
Pre-screening questions to ask Data Governance Manager candidates
12 questions grouped by what they test. Ask the same set in every screen and score answers on a consistent scale, or send them as an async video screen and compare answers side by side.
Policies teams follow
3 questions01Can you tell me about your previous experience managing data governance?
Listen forScope described in domains and teams covered, with what they owned rather than what a committee agreed.
Experience described by framework used, or a remit that never extended beyond producing documents.
02Can you provide an example of a successful data governance project you have managed?
Listen forA change teams adopted with what it fixed, plus evidence it survived after their attention moved elsewhere.
Success measured by delivery of a policy or a tool, with no behaviour change described.
03Can you provide an example of a data governance policy you have created and implemented?
Listen forA specific policy with how compliance was checked and what happened the first time someone breached it.
Policies published with no enforcement, or breaches noticed but never acted on.
Quality measured
3 questions04How do you ensure data quality in your governance efforts?
Listen forQuality measured with named dimensions and a figure they can quote, plus who is accountable when it drops.
Quality described as improved with no measurement, or checks that run with nobody watching the output.
05How do you assess the effectiveness of a data governance strategy?
Listen forEffectiveness judged on outcomes such as trusted reports or reduced duplication, not on catalogue coverage alone.
Effectiveness measured by how many assets are catalogued, or by attendance at governance meetings.
06How have you used metrics or analytics to improve data governance in the past?
Listen forMeasurement used to find a specific problem, with the intervention that followed and whether the number moved.
Dashboards produced for reporting upward, with no decision that came out of them.
Privacy obligations
2 questions07What steps do you take to ensure compliance with data protection laws in data governance?
Listen forSpecific obligations named for the jurisdictions involved, translated into controls such as retention and access limits.
Regulations named with no operational control attached, or compliance treated as the legal team's remit.
08Can you describe your approach to data security in governance projects?
Listen forClassification driving access decisions, with an example of restricting access to a dataset people wanted open.
Security deferred entirely to the security team, or broad access retained because narrowing it was unpopular.
Settling disputes
4 questions09How would you handle a situation where teams are in conflict about data usage?
Listen forA decision reached with a clear owner named, rather than the disagreement escalated or left to consensus.
Disputes resolved by allowing both versions to continue, or every conflict escalated to an executive.
10How do you ensure collaboration and buy-in from all relevant stakeholders?
Listen forOwnership agreed with named people who accepted it, tied to something they already cared about fixing.
Owners assigned without their agreement, or buy-in described as running awareness sessions.
11Can you describe explaining a complex data governance issue to non-technical stakeholders?
Listen forThe issue framed as a business consequence, with a specific decision that changed because of the explanation.
Explanations that rely on governance terminology, or briefings with no decision attached.
12Have you ever had to manage a data governance crisis? If so, how did you handle it?
Listen forA real incident such as a breach or a wrong report published, with containment, notification and what changed afterwards.
No incident they have handled, or a crisis resolved with no structural change following it.
How to score responses
Score every candidate on the same four criteria immediately after the screen. At this stage you are shortlisting for panel interviews, not making the final call.
Technical depth
35%5Names specific catalogue and lineage implementations, quality rule sets they authored, and reference or master data models they governed end to end.
Real incidents and findings
30%5Recounts named incidents with root cause, affected systems and reports, remediation steps, and the control that stopped recurrence.
Risk judgement
20%5Prioritises by regulatory and business impact, justifies documented risk acceptances, and distinguishes critical data elements from noise.
Getting things fixed
15%5Shows named owners recruited, council decisions logged, and measurable movement in quality scores or open issue backlog.
Governance dies as a policy nobody follows and a catalogue nobody updates, and it interviews well throughout. A one-way video screen asks what was adopted.
Try it on HirevireScreening FAQ
Process basics
How long should a pre-screening round for this role take?
Fifteen minutes across eight to ten questions, answered async. Enough to establish what was adopted and by whom, test their approach to data quality measurement, and hear how they handled a dispute between teams.
Is this a technical role or a stakeholder role?
Both, and candidates lean one way. A technical manager may build a catalogue nobody adopts; a stakeholder manager may agree principles nobody can implement. Decide which gap you have before weighting the questions.
Evaluating answers
What is the strongest signal when screening a governance manager?
A policy still in force after they left. It shows the change was built into how teams work rather than sustained by their attention. Ask who owns it now and whether anything has been enforced under it.
How do I judge data quality claims?
Ask what they measured and what the number was. Managers doing real work quote completeness or accuracy figures and their trend. Anyone who describes quality as improved with no measure has run an initiative, not a programme.
Go deeper on this role
Sanat has been hiring since 2012 and watching the recruitment industry change up close ever since, and turned that screening process into Hirevire's video screening platform. LinkedIn
