Framework for Actionable Resume Feedback

Sat 30 November 2024

Improving a resume can create opportunities and result in 6 figure differences in total compensation for software engineers. A resume signals competence at solving an employers' problems, but not everyone has the work history suited for their desired career. By creating levels of criteria for a resume, one can understand an applicants' current position and which edits open opportunities. The post explores a framework for framing content and does not advise on content for a resume. I have software engineering expertise, but the principles apply to any career path.

Level 0 - Readability

Mistakes here will raise red flags with human and automated evaluations. A resume is readable if it is organized, consistent, and without any obvious writing errors.

Level 1 - Basics

A resume requires contact information, work history, accomplishments and career specific info. For a software engineer, it's specific technical proficiencies and keywords. With the correct keywords, an applicant passes automated filters. At this level, a human reviewer will understand the facts but not the value of the work.

Level 2 - Impact

Level 2 shows an understanding what is important to the business. Generally, impact can be found in the format I had result X by doing Y. The closer the X and Y are to solving an employers problem, the more convincing resume. Understanding the reasoning for a project is difficult after leaving a company, so remember to record the impact while working.

Level 3 - Details and Context

Ambiguous and relational words signal an opportunity to showcase various skills to an employer. Here are examples not matching level 3's criteria.

1. Improved application on mobile devices with a mobile UI overhaul for job applications in React
2. Optimized the CI/CD process for faster build times
3. Led the development of a real time chat feature securing a customer contract

With examples 1 and 2, an applicant seems to have technical skills with build processes and frontend development but the words improved and faster hide details. By adding details, an applicant communicates additional business and communication skills. Here are revised examples.

1. Doubled the application start rate on mobile devices from 500 to 1000 applicants a day with a mobile UI overhaul for job applications in React.
2. Optimized the CI/CD process resulting in the p90 build time running 10x faster saving ~15 SWE hours a day.

Providing metrics with a baseline to ground the employer and show an applicant's history of quantifying their impact. People also leave out the surrounding project context. Here are examples contextualizing details an applicant may forget.

3a. Led the development of a real time chat feature on a 3 month deadline to secure a customer contract

3b. Led the development of a real time chat feature coordinating changes across 4 teams to secure a customer contract.

The same project can showcase different skills with added context. In this case, the applicant's ability to handle time constraints and organizational complexity. Level 3 is met when every line has intent, but do not tell a cohesive story.

Level 4 - Narratives

Narratives disqualify jobs which aren't suited for the applicant but make the applicant appealing narrative matches the job. level 4 suits applicants whom desire a specific role. If an employer buckets the applicant into a concise statement when reading a resume, the resume tells an effective narrative. Here are 2 example ideas.

New engineer growing fast with full stack engineering chops.

DevOps engineering manager with experience building platform teams from the ground up.

Every statement in the resume needs to contribute to the final narrative.

Applying the Levels

Recently, I've been giving resume feedback to multiple people in various career stages. When reading a resume, I go through each level until the resume fails to meet the criteria. The focus of the feedback depends on the level the resume fails to meet. I've found the framework helpful to give actionable feedback. Not all jobs require level 4 resumes. If I'm applying to be a cashier at McDonalds, I don't need a narrative for how I was born to be a cashier. Like any generalization, it's important to verify if the framework is helpful for the applicants' personal context and goals.