This is especially fun with the subvariant "Try as you might, no amount of engineering or operational effort can cram that 0.1% number down, so it scales directly with the size of the business, and eventually you need an organization housing the teams housing specialists in X."
In some cases the percentage of users with particular exceptions goes up over time, as e.g. your userbase broadens from sophisticated early adopters to folks more likely to make operational errors or e.g. your risk tolerance matures and you start flying less close to the sun.
Example of second: There's a reason big, boring companies with KYC policies spell out *exactly* what it means for an ID to match an individual, and there exist compelling reasons why startups probably would not write that document on day 34 when asked for their KYC policy.
Interview question at fintech company: "What would be an appropriate way to represent a user's KYC status?"
Junior engineer: "A boolean."
Intermediate engineer: "A state machine and audit logs."
Senior engineer: "None of the following is legal advice. Hope you've got a coffee."
Junior engineer: "A boolean."
Intermediate engineer: "A state machine and audit logs."
Senior engineer: "None of the following is legal advice. Hope you've got a coffee."
(That's a good meme format if anyone wants it ;) )
