By bzc ∙ Published Mon Nov 24 2025 ∙ 2 min read
As a hiring manager reviewing resumes particularly of software engineers, some clearly stand out more than others.
The worst are those that simply mention the language they used:
Built features in ReactJS
When I take a step back to really think about it, the difference between a great resume which lands interviews, and a poor one which gets rejected - comes down to how you spin the story.
Software engineers for example often only state what they used, or what they did. But they are missing the impact and outcome. What was the result to the business and the customer? Was it faster, more reliable, resolve technical debt, or save money?
Even if you're a product engineer and don't deal much with org-wide innovation did you perhaps deliver on timeline?
When describing your impact try to avoid weak verbs such as "helped", "supported, "worked on" and instead try "led", "launched", "built", "improved", 'automated', "analyzed" which improves the readers understanding of your contribution as opposed to your teams.
Though be careful not to fall into the trap of overselling to the point where it doesn't sound creditable. Statements like "architectured the backend data pipeline" sounds impressive in a vacuum but does it make sense for your role and if we drill into the details will it be because you were the only software engineer therefore you were chosen by default? Additionally if you were questioned on it deeply could you back the decisions made?
Or if you "improved bundle size by 500%", was it because everyone else forgot to turn on production build mode? What would sound more impressive in these instances is to provide context to the situation and why your contribution was pivotal. For the bundle size example I personally would be more impressed if you stated honestly that the team had knowledge gaps and you jumped in with initiative highlighting several low hanging fruit that led to high value performance gains such as setting the build production mode.
Be sure to include the technologies/tools outside of the language too such as NextJS, Playwright, Bun.
It may seem obvious to you or that it doesn't matter, but you'd be surprised how much hinges on the details.
Often you may pass the initial screening and the hiring manager can still reject because you haven't expressed the expected skills.
You're giving too much credit to the person screening your resumes. Yes resumes can vary, but so does the opinion of the reader. When hiring managers go through 100s of candidates for any given role, you're better to make something clear than to assume they'll read between the lines.
Software engineers underestimate the importance of minor points in their resumes. That's why Kipnu provides a framework when adding employment contributions to ensure that skills are highlighted while keeping the overall resume brief and to the point.
Once you have clear points, consider how they're ordered and whether you have too much or too little. Aim for at least 3 which shows a range of work but no more than 10 to ensure you points are reasonably leveled - unless you were at a role for a considerable amount of time.