Competency questions, rejection patterns & what works
How to structure STAR answers the way assessors actually score them. The six avoidable reasons most applications fail. And the five characteristics every successful application shares.
Competency questions & application questionnaires
Most applicants know the STAR method. Few apply it correctly. The distribution of content within a STAR answer is where applications diverge.
How most people use STAR vs. how it should be used
Common (weak) distribution
Too much context. The evaluator already knows the sector — they want to know what you specifically did.
Effective distribution
The Action section is what evaluators are scoring. Describe specifically what you decided, what you did, and why — not what the team did.
Recruiter view: The word 'we' is one of the most reliable signals of a weak competency answer. Assessors are evaluating your individual competency, not your team's. If your answer is primarily about what 'we' did, rewrite it to make your specific contribution and decisions unambiguous.
Common competency question mistakes
Using 'we' throughout the answer
Fix: Replace with 'I decided', 'I initiated', 'I was responsible for' — make your individual contribution specific and unambiguous.
Choosing an example where you weren't the decision-maker
Fix: Select examples where you led or owned an outcome. Supporting roles make weak answers for most competency questions.
Hypothetical or general examples ('In situations like this, I would...')
Fix: Use a specific past example only. 'I would' answers score poorly. If you can't find a real example, find a closer one.
Spending most of the answer on background and context
Fix: One to two sentences on context only. The evaluator wants to know what you did and why — allocate your word count accordingly.
No quantified result
Fix: End every competency answer with a measurable outcome, even approximate: 'reduced processing time by approximately 30%', 'team of 7 delivered on time within budget'.
UN core competencies — what assessors are evaluating
Communication
Clear, concise written and oral expression adapted to audience
Teamwork
Collaboration, sharing credit, supporting colleagues across hierarchies
Planning & Organising
Goal-setting, prioritisation, delivering under time and resource constraints
Accountability
Ownership of results and decisions, transparent about setbacks
Client Orientation
Understanding and responding to the needs of internal/external stakeholders
Creativity
Generating novel approaches to challenges, openness to change
Commitment to Continuous Learning
Self-awareness of knowledge gaps, active skill development
Technological Awareness
Understanding and appropriate use of technology in work context
Common rejection patterns
Most rejections happen for predictable, avoidable reasons. Understanding the patterns lets you fix them before submission.
Recruiter view: Eligibility disqualifications are the largest category of rejection and also the most avoidable. They never reach a hiring manager. Before spending time on a cover letter, verify every eligibility criterion line by line against your profile. Nationality, language, degree field, and years of experience are the four most common disqualification triggers.
What strong applications have in common
Across sectors and seniority levels, the applications that consistently reach interview share the same five characteristics.
Specificity over breadth
One concrete, detailed example with figures and outcome is more credible than three vague claims. Strong applications choose depth over coverage. Recruiters can extrapolate capability from one well-evidenced example; they cannot extrapolate from three vague ones.
Organisational literacy
Strong applicants demonstrate they understand how the organisation actually works — its funding model, its mandate constraints, its recent strategic shifts. This is visible in the vocabulary they use, the challenges they acknowledge, and the way they frame their motivation.
Language alignment
Strong applications mirror the exact vocabulary of the job description. If the JD uses 'results-based management', the application uses 'results-based management'. This is not keyword matching — it is demonstrating that you understand what the role actually requires.
Evidence density
In strong applications, almost every bullet point in the work history contains a figure, scale indicator, or measurable outcome. Not because it was forced in, but because the applicant has been doing work of consequence and describing it accurately.
Explicit eligibility coverage
Strong applicants address every stated requirement directly — not assuming the reader will infer it. If the JD requires French at working level, it is declared explicitly. If a specific type of experience is required, there is a bullet that makes it unambiguous. Nothing is left for the reviewer to guess.
Apply where your profile is strongest
Civium scores your CV against every vacancy — so you focus effort on the roles where your profile genuinely matches.
Stop checking 75+ career pages manually
Create your free account and preview your matches — no card required to get started.
Preview free · Start trial when ready