Most Kenyan job applications are lost before a recruiter reads a single line. Applicant-tracking systems (ATS) screen CVs automatically, and a poorly formatted file gets rejected before it reaches a human being. Getting past that filter is a craft, not luck.
A strong resume in the Kenyan market has one job: to get you a phone screen. It does that by being easy to scan, honest about what you have done, and formatted so that both a machine and a 30-second human read can extract the key facts. Once you have a solid base document, remember to tailor it to each specific role you apply for — a generic CV sent to every employer will underperform a customised one every time.
The structure that works — for banks, consultancies, development finance institutions, and research organisations — is consistent: contact details at the top, a two-line professional summary, then reverse-chronological experience with bullet points that describe outcomes, not duties. Follow that with education, skills, and any certifications. One page if you have fewer than five years of experience. Two pages maximum if you do not. Before you submit, check it against the job description with an ATS scanner to confirm your keywords match what the system is looking for.
Bullet points should answer the question a recruiter is implicitly asking: "So what?" Not "Managed a team" but "Managed a five-person credit analysis team, cutting turnaround time by 30%." Numbers are persuasive. Vague verbs are not. When your CV is ready, take the time to write a targeted cover letter that connects your experience directly to the employer's stated needs.
For finance and economics roles specifically, include any quantitative tools you use: SQL, Python, R, Stata, Excel modelling, Bloomberg. Kenyan hiring managers at banks and funds treat these as signals of rigour — list them honestly and specifically.
The most common mistakes on Kenyan CVs: photos (omit unless specifically requested — if an employer does ask, you will need a compliant passport-size photo that meets standard dimensions), date of birth (omit), a generic "objective statement" instead of a targeted summary, and formatting so complex it breaks on ATS systems. Plain is better than designed.