How an IT Specialist Can Describe Work Results in a Resume to Get Noticed
A new feature has appeared on HH: when an employer opens a response to a vacancy, a separate block now appears at the top of the resume where AI automatically highlights the candidate's achievements.
What most often appears in this block:
- result-oriented formulations: «implemented», «optimized», «launched»;
- specific achievements listed in the experience or «About Me» section;
- and if AI doesn't find results — hobbies might appear there… For example: «I love board games» or «I play Dota».
And this is a risk. If, instead of technical achievements, the employer first sees hobbies, the overall impression can be spoiled even before reviewing the experience.
Additionally, a new function has appeared in the same window: the employer can ask you a clarifying question about your achievements.
The conclusion is simple: the market is increasingly result-oriented. Without them, a developer's or engineer's resume performs worse.
Step 1. First, you need to see your results
Many IT specialists feel that «there were no special achievements — I just wrote code.» Most often, this is not true — you just aren't used to articulating them.
Here are questions that will help «unearth» results:
- What metrics improved thanks to your work? Latency, RPS, uptime, test coverage?
- What was the state of the system «before» and what did it become «after»? Refactoring, migration, transition to a new stack?
- What technical problems did you solve? Fixed a memory leak, patched a critical production bug, sped up deployment?
- Were there tasks that only you were trusted with? Complex integrations, architectural decisions, code reviews for the entire team?
- Did your solutions help reduce costs or increase revenue? For example: optimized DB queries and reduced server load, automated a manual process, migrated to the cloud and cut infrastructure costs.
- Did you participate in projects outside your direct area? Helped other teams, implemented DevOps practices, participated in hiring?
- Mentored juniors or middles? Onboarded new colleagues?
- What would have happened if you had performed poorly? Service downtime, data loss, release disruption?
- What numbers can you add? Number of microservices, traffic volume, team size, project delivery timelines, test coverage percentage.
A useful trick is to look at colleagues' GitHub profiles, their presentations at meetups, and public cases on LinkedIn. Often, we do serious technical things but don't consider them achievements.
Step 2. Formulating the result correctly
Finding the result is half the battle. It's important to describe it competently.
1. Use perfective verbs
«Implemented», «optimized», «migrated», «reduced», «launched», «covered with tests».
Ideally, all experience should be built around results, rather than a list of technologies and responsibilities.
❌ «Engaged in backend development with Python» ✅ «Migrated a monolithic application to a microservices architecture, reducing deployment time from 40 minutes to 5»
❌ «Worked with databases» ✅ «Optimized SQL queries, reducing response time for critical endpoints from 3 seconds to 200 ms»
2. Emphasize relevant stack and scale
Highlight what's important for the position you're applying for. For a high-load position — traffic/load numbers. For a product team — impact on business metrics. For a platform role — infrastructure scale.
3. Answer the question «so that what?»
You did something — but why, and with what effect?
«Wrote a CI/CD pipeline» — so that what? «Configured a CI/CD pipeline on GitHub Actions, which reduced time from commit to production from 2 hours to 15 minutes and allowed the team to perform up to 10 releases per day».
Conclusion
Today, an IT specialist's resume is not a list of technologies, but proof of engineering value.
AI already searches the text for specific results and brings them to the top. If you haven't written them out, the system will do it for you. And it's not guaranteed to be in the way you want.
Do you face difficulties describing technical achievements? Or is the hardest part precisely articulating how your code changed the product?