3 ms·
Your CV should provide examples of wins. eg decreased time to enter orders from 15 minutes to 5 minutes; increased widget production rate from 5000 / hr to 8000
by GianFabien 3y ago
Your CV should provide examples of wins. eg decreased time to enter orders from 15 minutes to 5 minutes; increased widget production rate from 5000 / hr to 8000 / hr; reduced hosting costs by 5% to $1.5M, etc.
Your technical competence needs to be reflected in the business benefits you have contributed to. Even refactoring code can be a win if it speeds up things, reduces costs, increases profits etc.
Increased profits are always considered to be "good".
- quickthrower2 3y agoThe problem with this is it tells you nothing about how competent the candidate is. It tells you about the success of a metric of an IT project. And it is easy to make up. It is usually a “we” thing and it if they say “I” then I am suspicious. And say they single handily sped up some system. Maybe it was a half day of profiling and fixing some string copying bug. Yes that fix moved a needle and is “Worth millions” but is it? Many people could do the same fix. I am suspicious of team metrics (period!) and I am suspicious of them being used to judge a developer. What you really want to know is can they fix stuff, are they thinking in alignment with the business. Chasing metrics often isn’t that. Metrics are a necessary evil: they are part truth part bullshit and require nuance to interpret.