The problems are really underspecified for statisticians, too. Leetcode is normally very clear on the requirements. > it is very important that the uncertainty

The problems are really underspecified for statisticians, too. Leetcode is normally very clear on the requirements. > it is very important that the uncertainty in the number of trials is taken into account because over-estimating a fraction is a costly mistake. This is not some precise jargon that is meaningless to the layman but completely clearly specified to a professional statistician. It's more like the specification written by your non-technical product manager for how some technical feature should work. A skilled data scientist will have the experience and the context to figure out what it's probably asking for, but he might write down a few more clarifying details before giving it to a junior on his team to implement. If testing these kind of guess-what-the-stakeholder probably-means skills is the point of this test, it's quite good at it. But that's not what leetcode is for.