A technology listed as a bare noun tells a reader that you have heard of it. Attaching a verb tells them what you did with it. Screening that reads context is looking for the relationship between a tool and an activity, so "Python" on its own contributes far less than "wrote the reconciliation script in Python". The word count barely changes and the meaning changes completely.
What the Bare Noun Leaves Out
Consider two entries. The first reads "Salesforce". The second reads "Administered Salesforce for a 40-seat sales team, including permission sets and two custom objects". Both are one line. Only the second establishes that you configured rather than clicked.
The gap is not decorative. A hiring manager for an administrator role and a hiring manager for a user role are looking for different things, and the bare noun matches neither precisely. It sits in the middle, doing half the job for both.
Three Things the Verb Supplies
- Depth, since using, configuring and administering are different roles
- Recency, when the verb sits inside a dated position
- Context, because the same tool is used differently in different settings
Choose the Verb That Matches Your Actual Level
Verbs carry a claim about seniority, so pick accurately. Overclaiming is exposed at interview and underclaiming costs you the shortlist.
- Used, ran, entered: you operated it as intended by someone else
- Built, wrote, configured, modelled: you created something inside it
- Administered, owned, integrated: you were responsible for it working
- Migrated, implemented, rolled out: you moved an organisation onto it
- Designed, architected: you determined how it should work at scale
If you are unsure which applies, ask what would happen if the tool broke on a Monday morning. If someone else fixes it, you are in the first two bands.
Where the Verb Should Live
Keep a short skills list for scanning, then put the verb-led evidence in the experience section where the date and the employer already supply context.
That arrangement does two useful things. The list stays readable for a human skimming in ten seconds, and the evidence sits next to the role it belongs to, which is what makes it credible rather than a claim floating at the top of the page.
A Worked Pair
Skills line: "SQL (4 years, daily), Power BI (report author), Excel including Power Query"
Experience bullet: "Rewrote the weekly sales reconciliation in SQL, replacing a four-hour manual process, and published the result as a Power BI dashboard used by six regional managers"
The list is the index. The bullet is the proof. Neither works as well alone.
The Padding Problem
Long technology lists are usually a symptom of uncertainty about which items matter. The instinct is to include everything in case something matches, and the effect is that the strong entries lose prominence among the weak ones.
A reader who sees forty technologies assumes several are exaggerated and discounts the whole block. Ten with verbs attached is more persuasive than forty without, and it also protects you from being asked to demonstrate the one you listed but barely touched.
Sector Differences That Matter
Software and data roles expect a detailed technical block and readers will look for it specifically. Engineering roles want standards and methods named alongside tools. Clinical, legal and education roles care far more about registration and statutory frameworks than about software, and a long tools list in those fields reads as misjudged emphasis.
Read three adverts in your target field. If all three name specific software, invest in the block. If none do, the same space is better spent on outcomes.
Verbs Without Outcomes Are Only Half Done
A verb establishes involvement. A number establishes significance. "Built a reporting dashboard" is better than "Power BI" and weaker than "Built a reporting dashboard used weekly by 30 branch managers, replacing a manual spreadsheet".
Where you genuinely have no figure, use scope instead: the number of users, the size of the dataset, the period it covered, the team it served. Something countable almost always exists.
Where the Verb Gets Lost
Even a well-written bullet can arrive stripped of its verb if the layout interferes. Two constructions cause most of the damage.
Skill Tables and Columns
A three-column grid pairing tool names with self-assessed levels reads cleanly on screen and can extract as an interleaved run of words, separating each tool from its description. The verbs end up attached to the wrong nouns, or to nothing.
Compound Bullets
A single bullet carrying three achievements joined by semicolons dilutes each one. One achievement per bullet, each opening with its verb, extracts reliably and skims better.
- Weak: "Responsible for reporting, data quality and training; also managed the migration"
- Better as three bullets, each starting with Built, Owned and Migrated respectively
Test it by copying your PDF into a plain text editor. If verbs and tools have drifted apart, the layout is the problem rather than the wording.
Frequently Asked Questions
Should I Delete My Skills List Entirely?
No. Keep a short one for scanning and human filtering, then support each important entry with verb-led evidence in your employment history.
How Many Technologies Should I List?
Eight to twelve for a technical role and fewer elsewhere. Past roughly fifteen the section starts to look like padding.
Do Proficiency Ratings Help?
No. Star ratings and progress bars carry no verifiable meaning, often contain no extractable text, and consume space that facts could occupy. Use duration and frequency instead.
What If I Used a Tool Only on a Course?
Say that plainly, with the context. "Used Python during a 12-week course project" is honest and still useful. Listing it alongside four years of professional use without distinction is what causes problems at interview.
Does This Apply to Soft Skills Too?
Yes, and more strongly. "Communication" as a bare noun is the least informative entry on most CVs. The evidence belongs in a bullet describing what you communicated, to whom, and what it achieved.
A Fifteen-Minute Rewrite
Take your skills section, strike out anything you would not want questioned, and for each survivor find the bullet in your history that proves it. Add the verb and a number to that bullet. The skills block gets shorter, the experience section gets stronger, and the document stops asking the reader to guess what you can actually do.
InsightCircle
