Proven
On your CV and visible in your code. This is the part of your profile that survives a technical interview, and the part a tailored CV is built out of.
Launching 22 November 2026
Prove your skills. Get hired.
Your CV is a claim. Your codeYour commitsYour projectsYour history is the evidence. hirable AI reads both, tells you which skills you can actually prove, and shows you exactly what stands between you and the job you want.
Free tier at launch · 7 days of Pro, no card · R80–R100 a month after that.
—Days
—Hours
—Minutes
—Seconds
23 skills proven by code
8 claimed, nothing behind them
Pro
Naledi's career profile
Job readiness
0%Ready
Skills with evidence
0
of 31 detected
Claimed, unproven
0
interviewers ask about these
Years of experience
0
from your dated roles
Repositories read
0
3 hidden by you
Evidence behind your skills
Proven
Working
Claimed only
The idea
Anyone can list a skill. Not everyone can show it.
Every CV is a set of claims, and an interview is where the unbacked ones fall over. hirable AI puts your repositories next to your CV and sorts every skill into three honest buckets — because knowing which bucket you are in is the whole game.
Working
In your repositories but nowhere on your CV. Usually the most valuable discovery in the report: you already have it, you are just not being paid for it.
Claimed
On your CV with nothing behind it. We name these plainly, count them, and tell you what to build — because an interviewer is going to find them either way.
In the box on day one
What hirable AI does the moment it launches.
Not a roadmap — this is the product that ships on 22 November 2026. Nine things, each of which works on its own the first time you sign in.
Reads your CV properly
Text pulled out page by page, including two-column layouts — the ones that turn into nonsense everywhere else. Roles, dates, skills and your summary come out structured.
Reads your GitHub, on your terms
Signing in with GitHub grants no repository access at all — that is a separate, deliberate step, and you choose repo by repo what is exposed. Hidden means unread.
Separates proof from claim
Every skill labelled proven, working or claimed, with the evidence attached — the repository, the language, the commits behind it.
Scores you against a real posting
Paste a link or the advert text. You get a match percentage, what you have, what you cannot show, and how far off you actually are.
Searches the live market
Up to 100 current listings for your role scored against your skills and sorted into tiers — 100%, 95–99%, 85–94% and down — so you apply where you already qualify.
Tells you what to learn, free first
Real links to real courses, official sources first. And when a certification is not worth the money, it says so — "skip it" is a first-class answer here.
Gives you a project to prove it
Shaped for the gap and pinned to a repository you already own, because an extension keeps the git history that shows the work. Fresh repos go unfinished.
Writes the CV for that one job
Typeset in LaTeX around the projects that actually fit the posting, and downloadable as PDF or source. Built from proof, not from adjectives.
Keeps score while you improve
Your GitHub is re-read every few hours in the background. Streaks, commits, new skills and readiness over time — daily, weekly, monthly, yearly.
Inside the app
Six screens, and what each one is for.
A preview of the interface as it stands today, with a sample profile in it. Black on white, dense where it needs to be, and every number traceable to something real in your account.
Naledi's career profile
Gaps that keep coming up
Language mix
Best matches
Senior Backend Engineer · Yoco · Cape Town
91%
Platform Engineer · Takealot · Cape Town
84%
Backend Engineer (Python) · Luno · Remote, ZA
76%
Site Reliability Engineer · Standard Bank · Johannesburg
61%
Overview. One page that answers "am I employable yet?" — readiness, evidence, the gaps that keep repeating, and the jobs you are closest to.
Your skills
What you can prove
Python strong
FastAPI strong
PostgreSQL strong
Docker consistent
React consistent
SQLAlchemy consistent
REST APIs strong
Pytest emerging
Git strong
CI/CD consistent
Claimed on your CV, not visible in code
Kubernetes
AWS
Kafka
Microservices
Agile
Gaps worth closing
Terraform
gRPC
Redis
Observability
Found in your code, missing from your CV
Alembic
Async Python
GitHub Actions
Vite
Skills. Three buckets, with the evidence behind each one — and the skills hiding in your repositories that never made it onto your CV.
Senior Backend Engineer
What you have
Python
PostgreSQL
REST APIs
Docker
CI/CD
Testing
What they want that you cannot show
Kubernetes
Terraform
Do these first — Kubernetes
Why it matters · asked for by 3 of the 4 jobs you are tracking
What to learn · Kubernetes Basics (kubernetes.io) — free · "Intro to Kubernetes", Microsoft Learn — free
Free
A project to prove it · add a Helm chart and a readiness probe to naledi/orders-api, the repo you already ship
Worth a certification? · CKA is R4 000 and hiring managers here ask for the cluster you ran, not the badge
Skip it
Job fit. A diagnosis with a prescription attached: why the gap matters, what to learn, what to build, and whether the certification is a waste of money.
Market readiness
0%Market
How the 87 listings scored
Focus on next
Kubernetes
Would take 12 listings past 85%, and 4 of them to 100%
Terraform
Would take 7 listings past 85%
Redis
Would finish 3 listings you are one skill away from
Market. Real listings, scored against your evidence and tiered, so you stop guessing which adverts are worth an afternoon.
CV tailored for Senior Backend Engineer · Yoco
\section*{Selected work}
\textbf{orders-api} — Python, FastAPI,
PostgreSQL, Docker
\item 14k req/day, p95 under 90ms
\item Alembic migrations, 87% coverage
\textbf{ledger-sync} — Python, Celery,
Redis, GitHub Actions
\item Idempotent settlement pipeline
\item Zero-downtime deploys
\section*{Skills}
Python · FastAPI · PostgreSQL ·
Docker · CI/CD · Testing · REST
Naledi Mokoena
Selected work
Skills
Python
FastAPI
PostgreSQL
Tailored CV. Rewritten around the projects that fit this one posting, typeset in LaTeX, out as PDF or source.
Progress
Streak
0
days in a row
Job readiness over time
Commits, last 14 days
Recent milestones
Docker moved from claimed to proven4 days ago
New skill detected: GitHub Actions9 days ago
Readiness passed 70% for the first time3 weeks ago
Progress. A background worker re-reads your GitHub every few hours, so the work you did today counts today — not whenever you remember to press refresh.
How it works
Four steps, about ten minutes.
Sign in
Google, GitHub or LinkedIn. Identity only — no passwords, and no repository access yet.
Upload your CV
One PDF. Roles, dates and claimed skills come out structured, two-column layouts included.
Choose your repositories
Tick the ones you are happy to be read. Everything else stays invisible to the analysis.
Point it at a job
Paste a posting or search the market. Get the gap report, the plan, and the CV that fits.
Pricing at launch
Knowing where you stand is free.
The question "am I employable yet?" costs nothing to answer. You pay when you want the market search, the fit reports and the CV that wins the interview.
Free
R0 / month
Forever, no card.
- Your skill profile, from your CV and your code
- Progress over time — daily to yearly
- Job readiness and the gaps behind it
- GitHub connected, repositories private by default
- One tracked job, so you can try the whole flow
Growth
R80 / month
Most people land here.
- Everything in Free
- Live job search, tiered 100% / 95% / 85%
- Unlimited jobs in your list
- Certifications from Credly and Microsoft Learn
- The AI fit report on any posting
- Rebuild your profile as often as you like
Pro
R100 / month
For when you are actually applying.
- Everything in Growth
- Your CV rewritten for one specific posting
- Typeset and downloadable as PDF or LaTeX
- Project ideas aimed at your most expensive gap
- Priority GitHub refresh — today's work counts today
Seven days of Pro, free, on every new account. No card is stored, so nothing is
ever charged automatically — when the trial ends you simply drop back to Free and keep
everything you made.
Claim a trial at launch
Launch day
22.11.2026
Sunday, 22 November 2026 · 09:00 SAST · hirable.ai opens to everyone
—Days
—Hours
—Minutes
—Seconds
Now
Private build
The full flow runs end to end — CV, GitHub, skills, market, fit reports, tailored CV.
October
Closed beta
The launch list gets in first, in batches, while we watch the analysis against real profiles.
22 Nov
Public launch
Open sign-ups, all three plans live, and seven free days of Pro on every new account.
After
Role-level readiness
A job-ingestion pipeline so readiness can be scored against a whole role, not only the jobs you saved.
Straight answers
The questions people ask first.
Does it read my private repositories? +
Only if you say so, repo by repo. Signing in with GitHub grants no repository access
at all — connecting your code is a separate step, and anything you leave hidden is
never read, never charted, and never quoted in a tailored CV.
What happens when the AI is unavailable? +
Everything falls back to a keyword taxonomy and the interface tells you that is what
happened. The analysis gets blunter; it does not disappear, and it never pretends to
be something it is not.
Is the readiness score a market-wide number? +
Not on the overview — that one is the average across the jobs you saved and analysed,
and it is labelled as such. The market page is the separate, wider number: up to 100
live listings for a role, scored against your evidence.
Do I need a card for the free trial? +
No. Payments run through iKhokha as one-off payment links rather than card mandates,
so no card is ever stored and nothing renews behind your back. A paid month is a
paid-up 31-day window, and paying again extends it.
Will it invent things to fill out my CV? +
No. A tailored CV is assembled from proven skills and real repositories, and the
learning links are curated rather than generated — the model is instructed to keep
real URLs rather than write its own.
Launch list
Be hirable by 22 November.
Early access goes out in batches before launch day, oldest signups first. One email when it is your turn, one on launch day. Nothing else.