Revamp Your CV: How to Write Bullets That Land Interviews

Most CVs I read are not missing achievements. They are burying them in sentences that do not land. "Responsible for managing the deployment pipeline" tells me nothing. "Cut deployment time 70 percent by rebuilding the CI pipeline across 100+ microservices" tells me everything. Same engineer. Same work. One bullet gets read past. The other gets a call.

The difference is mechanical, and once you see it you cannot unsee it. Here is how to write a CV bullet that actually does its job.

The XYZ formula

Steal this and run it on every line that matters. Achieved X, as measured by Y, by doing Z. It forces the result to the front, attaches a number, and names what you actually did.

Watch what it does to a flat line:

• Before: "Worked on improving user engagement."

• After: "Boosted user engagement 40 percent by rebuilding the onboarding flow."

• Before: "Responsible for cloud infrastructure."

• After: "Cut AWS costs 45 percent, saving A$150K a year, by re-architecting the infrastructure for a global e-commerce platform."

The shape is the same every time: outcome, number, method. If a bullet does not have all three, it is not finished.

Lead with your best, and lead with the result

You have about seven seconds before a recruiter decides to keep reading. Do not save the good stuff for the bottom. Put your strongest, most relevant achievement first in each role, and start the line with what changed, not the task. "Reported to the Head of Engineering and drove adoption of a security-first, cloud-first culture across 1,000+ deployments a month and 100+ microservices" earns attention in the first line. A duty does not.

Use verbs that carry weight

If your CV is a list of "managed," "helped," and "responsible for," it reads as passive. Swap them for verbs that show you moved something: rebuilt, introduced, spearheaded, automated, designed, cut, shipped. Not to sound impressive, but because they are more accurate. You did not "help with" the migration. You led it. Say so.

• "Introduced trunk-based development, TDD, and behavioural testing across the team."
• "Improved codebase quality by adding types to 4,500+ TypeScript files through automation."

The so-what test

Here is the single check that finishes a bullet. After you write it, ask "so what?" If the line does not answer it, it is not done.

"Migrated the database." So what? "Migrated the database to Postgres with zero downtime, cutting query latency 60 percent." Now it is done. Keep asking until every line earns its place. And weave your skills into these achievements rather than dumping them in a keyword list. A skill shown in action is worth ten skills listed in a row.

A note on non-standard titles

One more thing, because it trips up good people. If your internal title does not match the market, translate it. A "Measurement Manager" at a big tech company who actually does product work should read as "Product Manager." A "Senior Integration Engineer L2" is a "Senior Backend Engineer" to everyone outside your old company. This is not lying. It is making yourself legible. The deeper version, getting found in recruiter searches, I covered here.

Keep it relevant, and keep it clean

Whether your CV runs one page or four, the only rule that matters is relevance. Tailor it to the role like it was built for that role, and cut what does not serve it. Proofread it twice, because typos read as carelessness. And if pulling the numbers out of your past work is the hard part, I wrote a whole guide on how to find them.

Your CV is written for one audience: the recruiter and the hiring manager who have seconds to decide. Write every line so they cannot miss what you actually did.

If you want the version with the formulas already built in, the Careersy tech resume handbook and templates are made for the ANZ market.