What a great technical resume can do for you
> Refactored our front/end experience using React.<p>vs<p>> Increased user engagement 27% by refactoring our front-end experience in React.<p>Do tech interviewers actually prefer the second description over the first one? To be honest, I find the second one out of context (and a bit robotic/pedantic). Reasons:<p>- sure, 27% may look like a decent increase, but what was the metric you guys used? How many users you have? One cannot put all of this info in a resume of course (because it's a resume!) so please don't just drop a 27% there as if it means a lot<p>- I can imagine that the goal of the team/company was to "increase the user engagement", even perhaps "increase the user engagement by X%" and the product team thought "alright, let's refactor our front-end in React; no idea if it will bring an increase of X% or X/2%, but let's do it". But it's impossible to say that React (or any other tech) will bring you an increase of engagement in %X exactly. You just don't know that number, the number comes after; you may have some hypothesis but that's all. So, what you are actually telling me is this: "hey, we wanted to increase our user engagement by some percentage and so we refactored our front-end in React. Later on, our analytics tool told us that the user engagement increased by 27%." Again, you weren't aiming for that number, it just happened.<p>- you are not going to get hired for that 27%. Imagine there's another candidate that says "Increased user engagement 89% by refactoring our front-end experience in React". What now? Is him better than you? Again, context is king, but you cannot put that much context in a resume.