The Job Market is BROKEN

The Job Market Is Broken

Corporate recruiter Lee reviews ten technology resumes and argues that a resume’s job is to earn interviews—not simply document experience. His central recommendation is to make relevant skills and business impact easy to identify, especially during a fast initial screen.

Core framework: Keywords, what, and why

• Keywords are the skills and tools a hiring manager needs to see for a role.
• What explains what the candidate actually did using those relevant skills.
• Why connects the work to a business purpose or outcome that a nontechnical hiring manager can understand.

Lee says a resume needs all three. Keywords alone can look like keyword stuffing; tasks without relevant skills may suggest the wrong specialty; and work without a clear business reason is hard to evaluate.

He calls work that sounds adjacent to the role—but doesn’t demonstrate the required experience—a “hot dog instead of a hamburger.” His “Bob” metaphor represents a nontechnical recruiter or manager. Candidates should explain their work plainly enough for that person to understand why it mattered.

Resume-review playbook

• Choose a clear target role or technical stack. For software engineering, Lee recommends selecting a recognizable specialty—such as Java, Python, .NET, front end, embedded, mobile, or AI—instead of presenting as a generalist. Build a resume for a specific job title rather than tailoring it to just one job posting.
• Make the first skim count. Lee says recruiters may spend about 20 seconds locating a role’s core qualifications. Put the most relevant skills and experience where they are easy to find.
• Use simple formatting and concise bullets. He prefers a plain, conventional layout. For a role held for less than three years, he recommends limiting the experience to three bullets, each short enough to scan quickly.
• Lead with the relevant technology, then explain the purpose. For example, a software engineer could describe using Java, Spring Boot, SQL, REST APIs, and AWS to build a customer-facing purchasing website. This makes both the technical fit and business purpose clear.
• Translate technical work into business value. Don’t stop at “built a report,” “automated a workflow,” or “improved a staging environment.” Explain how the work helped customers, reduced risk, prevented disruption, supported decisions, or enabled revenue.
• Use language a nontechnical reader can follow. Several candidates listed specialized tools or project descriptions without explaining them. Lee recommends describing the work in plain language and clarifying unfamiliar terms.
• Keep skills aligned with the target job. Irrelevant tools and excessive detail can obscure the qualifications a hiring team is seeking. Lee recommends checking the keywords requested for the role and keeping those terms current; he says his own keyword lists need updating roughly every three months.
• Order employment history in reverse chronological order. One resume listed roles in the wrong order, making the candidate’s work history confusing. Lee also cautions that very short job tenures can raise questions.
• Address relocation when relevant. For applications outside your current city, state a realistic relocation plan and date if you genuinely intend to move. Lee suggests keeping the stated move within three months of applying.
• Be selective with numbers. Lee generally advises against putting numbers in resume bullets except where relevant to employment or education dates, contact details, or sales and management results. Numbers without a clear explanation of their significance do not strengthen a bullet.
• For interns, show technical basics and coachability. Demonstrate relevant languages, APIs, databases, or cloud experience, along with the ability to collaborate, take direction, and accept feedback.

Role-specific examples

• Software engineer: The first resume mixed Java, Python, and ServiceNow without making the candidate’s target stack clear. Lee found that the bullets did not show enough relevant engineering work or explain why it mattered.
• Front-end engineer: A Lithuania-based candidate had a 1-in-15 interview rate, which Lee considered reasonable for the market. He liked the evidence of a tech-lead role and multilingual sites, but said the bullets needed to explain the sites’ purpose and business value more clearly.
• Data engineer: The candidate showed pipeline and data-platform experience, but some bullets explained what reports enabled without saying why those reports mattered. Lee highlighted a stronger example that connected real-time data to more profitable trading decisions.
• Cloud engineer: This resume was getting about one interview per 50 applications. Lee considered it workable but improvable: clarify the cloud specialty, make certifications easy to find, add missing role-specific terms, and tie security or infrastructure changes to their business impact.
• Full-stack engineer: One resume’s short job tenures, reversed date order, and unclear bullets made it difficult to identify the candidate’s full-stack skills or the outcomes of the work.
• Software engineering intern: Lee found some evidence of technical ability and teamwork, but said the resume needed clearer details about languages, APIs, cloud, and AI tools—and a more understandable description of the project.
• Data analyst: A candidate reported about 250 applications and five interviews—roughly one interview per 50 applications. Lee saw relevant analysis experience but noted gaps in Excel, industry context, data visualization, and explanations of how findings influenced decisions.
• Cybersecurity/SOC analyst: A candidate reported more than 300 applications with no callbacks. Lee said the resume did not make core security, networking, threat-detection, or communication skills apparent, and that its formatting and wording made the candidate’s qualifications difficult to assess.
• Full-stack engineer in Germany: Lee criticized a long, hard-to-read resume with unclear bullet points and skills buried in the document. He recommended condensing the experience and making the front-end and back-end stack explicit.
• Software engineering intern in New York City: Lee recommended foregrounding technical tools in project bullets and explaining the project’s purpose in plain language. He also advised addressing relocation if the candidate was applying to roles far from home and truly planned to move.

Metrics and targets mentioned

Lee claims his resume approach can produce one interview per seven applications in general. He gives lower expected rates for harder searches: one per 20 for fully remote roles and one per 100 for international roles. He says a 1-in-100 rate can still be strong for an international candidate.

The first software-engineer candidate had applied for three months and submitted more than 150 applications without an interview. Other candidate-reported results included 1 in 15 for a front-end engineer in Lithuania, roughly 1 in 50 for a cloud engineer and a data analyst, 1 in 75 for an intern and a Germany-based full-stack engineer, and more than 300 applications without a callback for a cybersecurity candidate. These are individual examples, not industry benchmarks.

Business perspective

Lee frames corporate work as ultimately supporting a company’s ability to serve customers and sell products—his “everyone sells shoes” analogy. His practical point is that candidates should connect their work to customers, operations, risk, or revenue rather than relying on effort or technical complexity alone. He also describes the market as a recessionary environment, making clear positioning and readable resumes especially important.

Presenter/source: Lee, corporate recruiter and host of Headless Headhunter. The resume examples were submitted by job seekers.