re GP comment: it's more about the tone -- one should seem confident and well-acquainted with what they choose to show -- than the actual numbers. If you told me that you improved conversion rates by 2%, or 20%, I would barely know the difference, but I would see both of those very differently than just "improved conversion rates". If you don't have numbers, I would try to be specific in some other area instead (e.g. technologies used, names of big clients). Similarly, phrases like "had creative input across the full stack" might give me pause -- what does that mean? It implies a low amount of impact; why not say something more attractive, like "contributed and assisted others across the full stack"?
You can basically make them up - just make up something plausible for your field. It's not like everybody else isn't rounding up anyway.
I’ll admit, companies like that do exist and somehow survive!
It's not necessarily a case of GIGO, either. Take VSCode, for example. Tons of useful features. How many of them can be linked directly to increases in Microsoft's revenue?
One would hope that the VSCode devs are trying to build a good text editor according to their own taste and intuition (while also listening to outside feedback). It would be a complete waste of time to try to 'validate' every feature added.
I've seen this a lot online, but as someone who struggled to add this sort of data to my CV before, where exactly are people getting these stats?
Every company I've worked for either didn't know how changes affected things like uptime or conversion rate or page views or didn't share the information with the engineering team.
Do most people just make up these stats? Guess and hope it's somewhat correct? Work for companies that just happen to tell their engineering teams everything about the impact of their work? Actually go out and measure it themselves somehow, like throgh Google Analytics?
Just feels like it may be difficult for the author to show this sort of data, since they may not have access to it at all.