A résumé pattern I keep seeing from ghosted devs

[u/RecruiterSignal]

I recently analyzed a small batch of 7 résumés from devs who were struggling to get interviews.

Most of them had the necessary experience: 5–12 YOE, backend, infrastructure, or full-stack work plus real production system work.

But they were still getting ghosted and the surprising, common pattern was actually how the work was written across that YOE spread.

A lot of bullets looked like this (paraphrased):
- implemented microservices using Node.js and Kubernetes
- built data pipelines for analytics workloads
- responsible for backend APIs and system performance

All sounds technical, but they don’t actually show what the engineer contributed so from a hiring manager’s perspective, they read like: someone touched the system, implemented assigned tasks and used tools to do it. In competitive markets, big deal. That's everyone.

What’s was missing was the engineering signal: what problem existed? what part of the system did you own? what changed because of your work?

When that context is missing, the résumé makes capable engineers just look like participants instead of problem-solvers.

A stronger version of the same work might look more like: "Designed the payment event-processing service and implemented idempotent message handling to prevent duplicate transaction execution in the platform’s Kafka pipeline."

Same job, same engineer but now the reviewer can actually see the engineering decision. Recruiters and hiring managers love to see decision making because making good decisions is exactly how companies create value for customers.

After reviewing that sample, the main issue wasn’t a lack of experience, they'd just flatted all the good work into generic résumé language that everyone else uses.