From duty to outcome: ten CV bullets rewritten in front of you

Open any twenty CVs from a Cairo job board and eighteen of them describe a job description rather than a person. "Responsible for handling customer complaints." "Worked on the monthly financial reports." "Assisted the marketing team." Every one of those sentences is true, and every one of them could have been written by the colleague who sat next to you and did the work badly.

The fix is not stronger adjectives. It is a change of subject: stop describing what you were assigned, and start describing what changed because you were there.

The formula

Every strong bullet has three parts, and most weak ones are missing the third.

1. Action — a verb that only a person can do. Rebuilt, negotiated, migrated, cut, trained, automated.
2. Mechanism — how, briefly. This is where your actual skill lives.
3. Outcome — the number, the time saved, the money, the rate, the error that stopped happening.

If you have no number, use a scale instead: how many people, how many accounts, how many SKUs, how many branches. "Trained 14 new agents" carries weight even without a performance figure attached.

Ten rewrites

1. Before: Responsible for handling customer complaints.
   After: Handled 60–80 escalated complaints a week and cut average resolution time from 3 days to 26 hours by moving repeat issues into a shared FAQ the whole team could edit.
   Why: the volume shows the pressure, the mechanism shows judgement, the time shows the result.

2. Before: Worked on the monthly financial reports.
   After: Closed the monthly accounts for three entities and moved close from day 12 to day 6 by rebuilding the intercompany reconciliation in Excel with a single source sheet.
   Why: "worked on" hides whether you assembled it or checked somebody else's work.

3. Before: Assisted the marketing team with social media.
   After: Ran the Instagram and TikTok accounts (48k followers), publishing 5 posts a week; grew monthly reach from 90k to 310k over eight months with a content calendar planned around payday and Ramadan.
   Why: a local timing insight is the part a foreign candidate could not have written.

4. Before: Good knowledge of Excel.
   After: Built the commission model the sales team is paid from — 11 tiers, 240 reps — replacing a manual sheet that produced 20+ payroll disputes a quarter.
   Why: nobody believes a self-assessed skill level. Everybody believes a thing you built.

5. Before: Participated in the ERP implementation project.
   After: Owned the inventory module during our SAP B1 rollout across 4 warehouses: wrote the data migration mapping for 9,300 SKUs and trained 22 storekeepers over three weeks.
   Why: "participated" is the most forgettable word on any CV. Name your module.

6. Before: Developed new features for the company website.
   After: Shipped the checkout rebuild on a Laravel/Next.js stack; cut card-payment failures from 9% to 2.4% by adding retry handling for Fawry timeouts, on a store doing about 40,000 orders a month.
   Why: the failure rate is the business result. The stack is the keyword payload.

7. Before: Managed the company's social insurance and HR files.
   After: Ran payroll and social insurance filings for 180 employees with zero late submissions in 24 months, and closed a legacy Form 6 backlog of 40 leavers.
   Why: in compliance work, "nothing went wrong for two years" is the achievement.

8. Before: Taught mathematics to secondary school students.
   After: Taught Grade 10–12 maths to 140 students a year; rebuilt the Grade 11 revision series after a weak cohort and lifted the class average from 63% to 78% the following term.
   Why: teaching CVs almost never carry outcome data, so the first one that does stands out.

9. Before: Designed marketing materials and social media posts.
   After: Designed the packaging and shelf display for a 6-SKU launch that entered 220 pharmacies; ran three creative variants in a paid test and kept the one with a 41% lower cost per click.
   Why: designers get taken seriously the moment they attach a commercial number to taste.

10. Before: Responsible for the warehouse team.
    After: Supervised 17 staff across two shifts; introduced a cycle-count routine that brought stock accuracy from 91% to 99.2% and removed roughly EGP 400k of annual write-offs.
    Why: operations roles convert to money more easily than any other function. Do the conversion yourself, before the reader has to.

Rules I would apply to your own draft tonight

• Never open with "Responsible for". It describes the org chart, not you. Same for "Duties included", "Tasked with" and "Helped in".
• Three to five bullets for your current role, two for the one before, one each for anything older than six years. Recency is worth more than completeness.
• One number per bullet is plenty. Three numbers in one line stops reading like evidence and starts reading like a dashboard.
• Approximate honestly. "About 40,000 orders a month" is credible and defensible. "Increased efficiency by 300%" is neither, and it will be the first thing you are asked about.
• If you truly have no numbers, use scale, frequency, or the thing that stopped breaking. "Rewrote the induction pack so new joiners stopped calling IT on day one" is a result.

The interview test

Read your rewritten bullet and ask: could I talk about this for four minutes if pressed? What was the baseline, what did I change, what did it cost, what would I do differently? If the answer is no, the bullet is inflated and you should shrink the claim until you can defend it. A modest, specific, defensible line beats a spectacular one that collapses in the room. Inflated CVs do not usually fail at the screening stage; they fail at minute eleven of the interview, which is a far more expensive place to fail.