Modern companies are obsessed with making data-driven decisions. Candidates that want to write a winning resume must quantify their achievements whenever possible to give hiring managers the numbers that they want.
Usually candidates use the work history section of their resume to speak to specific skills and accomplishments that are relevant to their desired position. However, not every role readily lends itself to quantifiable measures at first glance. In any case, it is always better to show rather than tell how good you are at your job.
Arriving at numbers that tell a story might take an extra step or two for someone working in a software development position, the creative professions, or if a previous position lacked performance tracking metrics. Here we’ll discuss you how candidates can find the right numbers and frame them properly to convey skills development and aptitude.
To illustrate, let’s look at what KPIs might look like for a software developer job and pin them to something that might appear on a resume.
Stable code percentage – Often used to gauge the effectiveness of a development team, stable code deployment refers to creating changes to a product that doesn’t “break” other parts of the product. A candidate might speak to a high rate of stable code deployment over the course of a project or tenure; typically, this is done by illustrating a high percentage of uptime.
Less than 1% of code deployed resulted in application downtime over the development period.Percentage of testable code written – This KPI speaks to how well a programmer’s work performs in automated testing systems, and in doing so, provides groundwork for other programmers to build upon. A well-tested codebase is indicative of how well a development team onboards programmers. Code coverage, which is a percentage of the codebase that are executed when the automated tests run, is a measure a candidate might apply on a resume.
Increased code coverage from 65% to 95% over two months.Reducing code churn – Code always changes during the development process, but fewer changes result in faster production times. Reducing code churn means less coding is needed to build features and improvements, and concurrently indicates how easy it is to make changes during the development cycle. A candidate might speak to reducing code churn by a certain percentage.
Reduced code churn by 20% while building new features into the product.Documentation produced – A key component of effective collaboration, documentation is a way for programmers to effectively share their work with the broader team. Having documented development notes is highly valuable for companies because it adds transparency and eliminates gatekeeping in product development. A candidate might speak to the quantity or frequency characterizing their documentation efforts.
Produced weekly documentation during six-month development cycle.
Absent formal KPIs in prior positions, candidates might apply the numbers that they know into resume statements that communicate value. Mention how many were on the team that they led; quantify the size of the budget they oversaw; or even characterize a past company’s annual revenue. All add detail that may be advantageous to the candidate.
Examples might look like: