Written for the machine that reads it first.
Most applications in Kenya are filtered by software before a recruiter opens one. This builds a résumé that survives that pass without turning into keyword soup.
Amara Otieno
Mar 2024 – Present
- Built dashboards in Power BI tracking churn for 2M+ subscribers, cutting reporting time by 60%
- Automated daily ETL pipelines in Python, replacing manual spreadsheets across three teams
- Rebuilt the weekly supply report as a scheduled query, saving a day of manual work each week
- Cleaned and reconciled three years of vendor records ahead of a migration
What it actually does.
Built from your profile
The first draft is assembled from the experience, education and certificates you entered once. It runs both ways, so a finished résumé saves back to the record and the next one starts from it.
Readability check
The draft is read back the way tracking software reads it: which fields parsed, which dates were ambiguous, which sections a filter would drop. You see it before you send, not after the silence.
Language that matches the role
Career records carry the vocabulary a field actually uses here, down to the certifications and tools named locally. Bullets are rewritten toward it, and nothing is invented.
Tailoring against a posting
Paste a posting and you get one copy aimed at it, not an edit to the version you keep. It also names the gap: what the posting asks for that your record does not yet show.
Export that keeps its shape
Fonts embedded whole, so no glyph is dropped and it looks the same on their screen as yours. The text layer stays selectable, which is what keeps it readable by the software that opens it first.
Four passes, not forty drafts.
The order matters. Structure first, then content, then language, then the specific application.
- 01
Import what exists
Start from your profile, or paste an existing résumé so the first draft is not a blank page.
- 02
Pick a template
Every one is single column, because that is the layout a parser reads correctly.
- 03
Run the check
Fix whatever the parser could not find before the document goes anywhere.
- 04
Tailor per role
For a specific posting, reorder against it and export a copy for that application only.
Who gets it.
Every tool is on every tier. What a tier buys is credits, which is how much model work you can spend in a week.
The catalogue is open today and needs no account. The app itself is in invite-only beta.
Compare tiers- FreeKES 0
- 2 templates
- ProKES 500 a month
- IncludedIncluded
- ProfessionalKES 900 a month
- IncludedIncluded
What it will not fix.
The builder controls the document. Most of what decides an outcome sits outside it.
5 stated
- 01It cannot make you a match. A clean, parseable page gets your record read accurately; it does not change what the record says.
- 02It does not know the employer's system. Parsers differ, and a page that survives one is likely but not certain to survive the next.
- 03It will not invent experience. Every line comes from what you entered, which is the only version of the document worth sending.
- 04It is not a cover letter, a portfolio, or a referral, and for most roles here at least one of those matters more than formatting.
- 05It exports a document, not an application. Where you send it, and when, is still the part that decides.
Common questions.
If yours is not here, ask. We answer in writing so the answer is quotable, and we correct the record when we get one wrong.
Ask usKnow the role before you write for it.
The tailoring is only as good as what you are aiming at. Start from the career record, then build the page.