Career Navigation

Skills-in-Use CV Pattern

6 min read

Skills-in-Use CV Pattern

Dimension: Capability · Type: Foundation

A writing pattern for CV bullets, cover-letter sentences, and interview answers. Name the skill, the action it enabled, and the context it produced impact in.

Introduced by Rathan Kinhal (EY Switzerland) at the Upskilling for the Future session of the UN Inter-Agency Career Week 2026, on 6 May 2026. Reinforced and extended in the The Skills Shift session by Olga Lehtinen (UNICC), who tied the pattern directly to how AI screening configurations are now reading CVs. The pattern overlaps with the well-established CAR (Context, Action, Result) and STAR families of competency-statement structures, applied here to written application bullets.

The framework

A CV bullet, a cover-letter sentence, or an interview answer all have the same skeleton:

Because of [skill], I delivered [outcome] in [context].

Three parts. Each does specific work.

When to use it

  • Whenever you write a CV bullet that names a skill or capability.
  • When drafting a cover-letter sentence that needs to demonstrate a specific competency.
  • When preparing answers for a competency-based interview.
  • When updating your LinkedIn profile and want skills-section claims to be backed up by visible work.

The three parts

  • Skill. The named capability. Specific, not generic. “Stakeholder negotiation at ministerial level” beats “communication”. “Results-based programme design with sex-disaggregated indicators” beats “M&E”.
  • Outcome. What you produced or achieved. Quantify where possible. Numbers, percentages, time saved, decisions influenced, milestones reached.
  • Context. The situation. Programme, country, scale, constraint. Just enough that the outcome is interpretable and the skill’s transferability is visible.

The order can rotate (context-skill-outcome, outcome-skill-context) but the three components must all be present. A bullet that has only two of the three reads as either a list of duties (skill-context) or a list of brags (outcome-context) or generic resume language (skill-outcome with no anchor).

Steps

  1. Identify the target skill. Read the JD’s language carefully. Match the skill name in your bullet to the JD’s terminology where it is honest. (See JD Colour-Coded Breakdown for the source.)
  2. Pull the relevant achievement. From your BASIC bank, pick the one that best demonstrates this skill in action with measurable impact.
  3. Write the three-part bullet. Test against the pattern. If any of the three pieces is missing, rewrite.
  4. Cut padding. Words like “successfully”, “effectively”, “responsible for” do not carry information. Strip them.
  5. Iterate against the JD. A bullet that works in isolation may still need re-tuning to mirror the JD’s language. The point is not generic strength; it is specific fit.

Worked examples

Generic, weak bullet: “Responsible for project management and stakeholder engagement on a multi-country health programme.”

This has neither outcome nor specific skill. Reads as a duty list.

Skills-in-Use rewrite: “Because of multi-country results-based programme management, I delivered baseline data three weeks ahead of plan with 92% completeness across three pillars in a six-country gender-equality flagship programme, allowing the mid-term evaluation to proceed on schedule.”

Skill (multi-country results-based programme management), outcome (three weeks ahead of plan, 92% completeness, evaluation on schedule), context (six-country gender-equality flagship programme).

Generic, weak bullet: “Strong communication and negotiation skills.”

This has skill but no outcome and no context. Reads as a self-assessment.

Skills-in-Use rewrite: “Because of multilingual stakeholder negotiation, I led the drafting and signing of memoranda of understanding with health ministries across six West African countries, securing programme sign-off in 11 weeks against an 18-week target.”

Skill, outcome (six MoUs signed, 11 weeks against 18), context (West African health ministries).

Generic, weak bullet: “Used AI tools to improve team productivity.”

Reads as buzzword. Skill is too generic; outcome and context absent.

Skills-in-Use rewrite: “Because of prompt-engineering and Power BI integration, I built a partner-reporting dashboard that cut quarterly report preparation time from 14 person-days to 2, freeing the team to expand monitoring coverage by two countries.”

Skill, outcome (14 days to 2, two extra countries covered), context (partner-reporting dashboard).

The capability-language rewrite move

Day 5 Session 4 reinforced the same pattern from the AI-screening side. Olga Lehtinen’s prescription was specifically about how to translate duty lists into capability language so that the bullet surfaces inside both an AI-configured screen and a human panel reading for evidence.

Three concrete rewrite moves she demonstrated, all consistent with the “because of X, I delivered Y in Z context” pattern:

  • Replace duty descriptions with capability descriptions. Instead of “I prepared meetings” or “I supported preparing meetings”, write “I synthesised input that informed decision-making and aligned stakeholders”. The first names a duty; the second names a capability.
  • Replace tenure with outcomes. Instead of “five years in programme support”, write “enabled faster alignment across teams and reduced decision time”. The first names how long; the second names what changed.
  • Replace certificates with digital work habits. Instead of “completed data analytics training”, write “use data and AI tools weekly to analyse, summarise, and improve inputs”. The first names a credential; the second names active practice.

The connection to AI screening: AI does not decide what to value; it amplifies what the system is configured to value. As panels and ATS configurations move toward evidence, capability-language bullets surface where duty-and-tenure bullets do not.

The implication for the pattern above: the “skill” component of “because of X, I delivered Y” should be in capability language, not in duty language. “Because of multi-country results-based programme management” is capability language; “because of five years in programme management” is tenure language. The pattern only works if the skill component is named correctly.

For the broader formula that puts capability, outputs, and evidence in three explicit components, see Capability + Outputs + Evidence, which is the AI-screening-specific operationalisation of the same logic.

Pitfalls

  • Padding the skill name with adjectives. “Strong leadership skills” is weaker than “stakeholder negotiation at ministerial level”. Specificity carries the credibility.
  • Quantifying the activity instead of the impact. “Trained 12 enumerators” is an activity. “92% data completeness” is the impact. The pattern wants the impact.
  • Context-padding. If the context line takes more words than the outcome, rewrite. Context is anchor, not narrative.
  • Using the same bullet across all applications. The skill name should align with the JD’s language; that means re-tuning the skill phrase for each role. The achievement underneath stays the same; the framing shifts.
  • Stretching the truth to fit. A bullet that overstates the outcome will not survive the interview. The pattern works because it is verifiable.

When not to use it

When you are writing personal essay-style content (a fellowship application, a values-driven cover letter for a role that explicitly asks for narrative). The pattern is right for skills-evidence claims; it is not right for purpose-and-fit narrative. Use both forms in different parts of a strong application.

How I use it

Personal note pending. Davide to fill.

Notes compiled by Davide Piga. Last updated 2026-05-09.

Graph View

Backlinks