<story><title>What a great technical resume can do for you</title><url>https://www.meetleet.com/blog/what-a-great-technical-resume-can-do-for-you</url></story><parent_chain><item><author>ingvul</author><text>&amp;gt; Refactored our front&amp;#x2F;end experience using React.&lt;p&gt;vs&lt;p&gt;&amp;gt; Increased user engagement 27% by refactoring our front-end experience in React.&lt;p&gt;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&amp;#x2F;pedantic). Reasons:&lt;p&gt;- 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&amp;#x27;s a resume!) so please don&amp;#x27;t just drop a 27% there as if it means a lot&lt;p&gt;- I can imagine that the goal of the team&amp;#x2F;company was to &amp;quot;increase the user engagement&amp;quot;, even perhaps &amp;quot;increase the user engagement by X%&amp;quot; and the product team thought &amp;quot;alright, let&amp;#x27;s refactor our front-end in React; no idea if it will bring an increase of X% or X&amp;#x2F;2%, but let&amp;#x27;s do it&amp;quot;. But it&amp;#x27;s impossible to say that React (or any other tech) will bring you an increase of engagement in %X exactly. You just don&amp;#x27;t know that number, the number comes after; you may have some hypothesis but that&amp;#x27;s all. So, what you are actually telling me is this: &amp;quot;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%.&amp;quot; Again, you weren&amp;#x27;t aiming for that number, it just happened.&lt;p&gt;- you are not going to get hired for that 27%. Imagine there&amp;#x27;s another candidate that says &amp;quot;Increased user engagement 89% by refactoring our front-end experience in React&amp;quot;. What now? Is him better than you? Again, context is king, but you cannot put that much context in a resume.</text></item></parent_chain><comment><author>PragmaticPulp</author><text>As a hiring manager, most of the “Increased revenue by 27%” type lines on tech resumes are clearly awkward attempts to implement generic Internet resume advice. When was the last time a company attributed sales growth to some developer making a change? Don’t try to take credit for things that the company, as a whole, accomplished.&lt;p&gt;The two places I like to see specific numbers are when communicating project scale or demonstrating some quantifiable change that was directly attributable to a person’s work. Good examples:&lt;p&gt;“Reduced AWS bill by 40% by profiling server code and implementing strategic optimizations”&lt;p&gt;“Architected cloud backend to support 500,000 daily users”&lt;p&gt;“Reduced average page load time by 57% percent”&lt;p&gt;If there isn’t an obvious, direct relationship between the person’s actions and the business outcome then I simply ignore it. If the person can only cite company-level achievements that don’t directly relate to their work, I assume they’re reaching because they can’t otherwise demonstrate how they personally contributed.</text></comment>
<story><title>What a great technical resume can do for you</title><url>https://www.meetleet.com/blog/what-a-great-technical-resume-can-do-for-you</url></story><parent_chain><item><author>ingvul</author><text>&amp;gt; Refactored our front&amp;#x2F;end experience using React.&lt;p&gt;vs&lt;p&gt;&amp;gt; Increased user engagement 27% by refactoring our front-end experience in React.&lt;p&gt;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&amp;#x2F;pedantic). Reasons:&lt;p&gt;- 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&amp;#x27;s a resume!) so please don&amp;#x27;t just drop a 27% there as if it means a lot&lt;p&gt;- I can imagine that the goal of the team&amp;#x2F;company was to &amp;quot;increase the user engagement&amp;quot;, even perhaps &amp;quot;increase the user engagement by X%&amp;quot; and the product team thought &amp;quot;alright, let&amp;#x27;s refactor our front-end in React; no idea if it will bring an increase of X% or X&amp;#x2F;2%, but let&amp;#x27;s do it&amp;quot;. But it&amp;#x27;s impossible to say that React (or any other tech) will bring you an increase of engagement in %X exactly. You just don&amp;#x27;t know that number, the number comes after; you may have some hypothesis but that&amp;#x27;s all. So, what you are actually telling me is this: &amp;quot;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%.&amp;quot; Again, you weren&amp;#x27;t aiming for that number, it just happened.&lt;p&gt;- you are not going to get hired for that 27%. Imagine there&amp;#x27;s another candidate that says &amp;quot;Increased user engagement 89% by refactoring our front-end experience in React&amp;quot;. What now? Is him better than you? Again, context is king, but you cannot put that much context in a resume.</text></item></parent_chain><comment><author>marcinzm</author><text>The exact number is irrelevant, the fact that there is a number is relevant. That means the developer not only understood the business requirements but also measured the impact afterwards. That&amp;#x27;s a very valuable skill in many companies that use metrics to make decisions.&lt;p&gt;In fact it doesn&amp;#x27;t even matter if the number was utter BS and unscientific in measurement. So are probably 80% of metrics in companies that are metrics driven. But the manager running the team still needs a metric to meet their goals and this developer shows that they can deliver that.</text></comment>