Hiring Guide
What to Ask a PolicyCenter Developer in the First Ten Minutes
Six questions that separate configuration experience from exposure, with the answers worth listening for — and the follow-ups that catch a rehearsed reply.
Read moreHIRING GUIDE
Screening KYC Technologists Without a Compliance Background
Three questions that do the work. You do not need to know the regulation to tell whether a candidate has built the system that satisfies it.
In this article
The short version
- Screen for trade-offs, not regulatory recall. You can judge reasoning without knowing the rulebook.
- Ask what they deliberately left manual. The answer separates builders from advisers immediately.
- Straight-through rate is the number that matters. People who owned the system know theirs.
- Corporate and retail onboarding are near-different disciplines. Screen for the one you actually run.
The situation
You are a technology hiring manager and the open role is KYC — onboarding orchestration, customer risk rating, entity resolution, or a remediation programme. You can assess engineering ability comfortably. What you cannot assess is whether the candidate understands the compliance context well enough to make good decisions in it, and compliance colleagues are not always available for every first-round screen.
The good news is that you do not need regulatory knowledge to do this well. You need to ask about decisions rather than rules, because the quality of someone's reasoning is legible even when the subject matter is not.
The principle: decisions, not recall
KYC technology is a continuous negotiation between three pressures: the compliance file has to be defensible, the operations team has to absorb whatever the system cannot decide, and the customer walks away if onboarding takes too long. Every design choice moves at least two of those.
Anyone who has genuinely built or run one of these systems talks in those terms without being prompted. Anyone who has only advised on a target state talks about principles and frameworks. That difference is audible to a technologist with no compliance background at all.
You are not testing whether they know the regulation. You are testing whether they have made expensive decisions and can explain the reasoning.
The questions that do the work
1. “What did you automate, and what did you deliberately leave to a human?”
The best single question on this brief. It asks for a judgement rather than a fact, and the second half is where the signal is.
Strong candidates have clear examples of things they chose not to automate — an edge case where the data was too unreliable, an ownership structure too unusual to codify, a decision the business wanted a person to make. They can explain who agreed that and why. Weak candidates treat every manual step as a failure they had not got round to fixing yet.
2. “What happened to your straight-through rate?”
A number, and one the candidate should either know or be able to describe the movement of. It does not matter that you have no benchmark to compare it against — you are testing whether they measured the thing their work existed to change.
Follow up with the other half: and what did that do to the operations queue? Someone who improved automation while quietly pushing more cases into manual review has not improved anything, and the ones who understand that say so themselves.
3. “What did you do when a vendor went down?”
Modern KYC leans on identity, document and data providers, all of which fail differently and some of which fail silently. Fallback design is where onboarding either degrades gracefully or stops.
You are listening for whether they had a plan: queue and retry, fall back to manual, accept a lower-confidence check with a flag for later review. Candidates who have never thought about it will answer as though vendors do not fail.
Two more, if the role warrants it
For corporate onboarding: “How did you handle a customer who appeared three times in different systems?” Entity resolution and duplicate handling quietly break risk rating, screening and reporting all at once, and corporate onboarding lives or dies on it.
For anything touching review cycles: “After you changed the trigger logic, how did you show coverage had not dropped?” The question tests whether they think about evidence, which is the habit that matters most in this domain.
Telling a policy person from a build person
Both are legitimate profiles and you usually need one specifically. The tells are consistent.
| Signal | Build background | Policy background |
|---|---|---|
| Detail level | Names systems, vendors, fields | Names frameworks and principles |
| Numbers | Volunteers rates and volumes | Describes outcomes qualitatively |
| Failure stories | Has several, specific | Has few, general |
| Operations view | Knows the queue and the SLA | Refers to “the business” |
| Trade-offs | Explains what was given up | Explains what was required |
Neither column is wrong. But if you are hiring someone to deliver an orchestration rebuild and every answer sits in the right-hand column, that is worth knowing before the technical panel.
Answers that should worry you
- “We followed the policy.” Fine as a starting point, concerning as a whole answer. Policy never covers every case; someone had to decide the rest.
- Perfect automation claims. Nobody automates onboarding end to end. A candidate who implies otherwise either did not own it or is not levelling with you.
- No mention of operations. Every deferred decision lands on a team with a queue. Not knowing that is a real gap.
- Vendor names with no opinions. Anyone who has integrated these providers has views on which ones are painful.
When to bring compliance in
You can run first-round screening alone. Bring a compliance colleague into the second round when the role owns risk rating design, review trigger logic, or anything that will be presented to audit — those are the areas where a plausible-sounding answer can still be wrong in ways only a practitioner will catch.
For orchestration, integration, entity resolution and data work, a technologist asking the questions above will get you a long way on their own.
