Thoughts on Presenting Resume Statistics

Usually, when writing about work achievements, if there are data, we present the data; if there are no data, we point out the contributions so that the other understands the value you can bring, for example:

• Changing process A reduced CI time by 30%
• Implementing B reduced communication costs by 30%
• Optimizing website loading speed by 2 seconds, Reduced Lighthouse FCP by 30%, LCP by 45%

Sometimes, it can be quite troublesome to quantify achievements as it is an art in itself because many statistics lack meaning:

• The context cannot be clearly communicated. (Keeping resumes concise inevitably omits details)
• Can the other party understand the value brought by the numbers? (Perhaps it would be clearer to state how much money is saved or earned, but that involves too many unrelated variables)
• There’s no need or time to collect statistics (precise statistics also incur costs, and can be difficult to quantify)

Achievements with clear rules can be stated, like TOEIC scores, but more often, the real world involves various trade-offs and premises. One-sided facts can be quantified, but they serve merely as conversational hooks and are not the main point. It is best to have a reasonable explanation behind the achievements.