Notes on Resume Writing: Shifting from Duties to Agency
A few honest notes on why passive resume bullet points fail to build trust, and how to write active achievements that stand out.
I've noticed a pretty exhausting pattern lately in my screening pile. Everyone seems to think that using big, academic-sounding corporate buzzwords makes them look senior. They draft sentences like *"Utilized synergistic methodologies to maximize departmental throughput"* and honestly, it makes my eyes roll.
When I'm scanning a resume on a tight deadline, I don't have the energy to translate corporate code. I just want to know what you actually built, how you did it, and what happened after you finished.
If you built an internal feature that saved your team ten hours a week, just say that. No need to dress it up. *"Built an internal tool that saved the team 10 hours of manual work weekly."* That is clear, valuable, and immediately builds trust. Direct communication is honestly a rare skill in a hiring pipeline.
Simple is always better than complex.
Lately, there is also a huge wave of resumes that look like they were generated by a machine. You see the exact same verbs over and over: *spearheaded, orchestrated, revolutionized, leveraged.*
When every single bullet point claims you *revolutionized* a legacy database, it starts to feel fake. Real project work is messy. It involves collaboration, small iterations, and constant adjustments. If your resume reads like a flawless tech manifesto, I immediately get skeptical.
Instead, give me specific, quiet details. Tell me you *'automated the test suite, reducing release time from two hours to twenty minutes.'* That is incredibly specific, highly believable, and shows me exactly what you are capable of doing on a real team.
Specific details build trust far better than copy-pasted machine text.
Another common issue is listing bullet points that look like they were lifted straight from an internal company handbook. Bullet points like *"Responsible for attending weekly syncs and drafting code updates"* are completely empty. Every single engineer attends meetings and writes code.
What I actually want to know is: *why did those meetings or code updates matter?* Did the code update fix a bottleneck in the checkout flow? Did the weekly syncs help resolve a major blocker? If your daily tasks don't have a clear connection to what the project achieved, it feels like wasted space.
You don't need to claim you single-handedly saved the business millions of dollars. Just show a clear purpose. If your job was managing the client dashboard, explain how your updates made it load faster, making it easier for clients to view their metrics. That proves you understand the actual value of your work.
And please, stop forcing arbitrary percentages into every single sentence. I see so many bullets claiming a candidate *'improved database performance by 87.4%'* or *'boosted team efficiency by 43%.'* Where do these exact numbers even come from?
Recruiters are naturally skeptical of overly precise, unexplained percentages. If you list an exact number, you'll probably get asked how you calculated it during a call.
Instead, just represent the real scale of your work. Tell me the size of the database, the number of active users, or the size of the budget you managed. Writing *"Migrated a database of 10,000 active users to a new host"* is incredibly clear, honest, and highly trustworthy. It gives the team a realistic picture of your capabilities without the over-optimized hype.
Keep it honest, check your spelling, and write down what you actually built. The trust starts there.