Not sure about the author, but having a few hundreds interviews under my belt (as the interviewer) some of those statements are incomplete.

Your example is complete, but if I see statements like: "decreased latency by 5%" I will ask you if are we talking about median or long tail latency. Another example would be "developed a ML model that increased revenue by X%". Here it is missing how the population is affected. If you say overall then I will ask you things like: "For which slice of the population did you see the biggest improvement with the new model? Any regression?" or "Did you run any control group".

While I might or might not care about the technicalities of your answer the important thing is that if you can't convince me that you know what you are talking about then it is as parent said, bullshit and I will stop likely paying attention to you and mind my business as I will suggest a no-hire.

If, instead, it looks like you really did those things you mentioned it is a nice ice breaker and genuine candidates seem to perform well when they get the tension out of the way by answering something they know.

PS: If I were to interview you I would ask "How" because as I mentioned it is a complete statement in my mind :)

You want all that on a resume?

No, but hints work. Like the latency one adding "on p99" makes me think it is a specification that adds a lot with just 2 words and the credibility weight it adds is huge (IMHO).