I quantified almost nothing in my CV. I just provided numbers when they were objectively available: date of birth, scores in school, etc. Other than that, I just wrote about the experience and the projects I worked for.
Usually, if you read carefully, the examples with "quantization" apply to jobs where numbers are "Gods" - and those are usually sales (or other related or similar activities).
I explained herehere the structure of my CV, just in case you need some inspiration.
Notes:
I do not imply that quantization must be avoided at all costs. If you have some relevant numbers, it is OK to show them. It is the "quantization at all costs" which I speak against.
As stated in a comment, some tech companies seem to be big fans of numbers. However, in my personal opinion, most tech companies don't reject you from the start just because of that.
Normally, if a company really wants numbers, they will specifically ask, either you directly, or through the public communication channels (e.g., on their web page).
If you will ever encounter a large number of potential employers asking for numbers, then start thinking to make some updates to the CV. In my almost 20 years of employment, nobody ever asked me about "self-marketing" numbers during interviews.
A good hint from @PaulKaram in a comment
We say that most companies do not need quantization, but only the list of the required skills. The truth maybe is somewhere in between. Compare the following:
- I am proficient in using C, C++, pythonPython, and rubyRuby
- I am proficient in using 4four programming / scripting languages: C, C++, pythonPython, and rubyRuby
Is statement 2 more "quantified" than statement 1, just because it makes the numbers explicit? Does statement 2 provide more information? For me, statement 2 is actually more difficult to read, because I need to throw away the "junk" infoinformation.