Student projects that impress Kenyan employers

Hiring managers at Kenyan tech companies see hundreds of portfolios from new graduates. Most look the same: a weather app, a to-do list, a calculator. These projects show you completed a tutorial. They do not show you can build something useful.

What stands out:

• Projects that solve a local problem. A tool that helps a campus vendor track inventory, an SMS reminder system for clinic appointments, or a fare calculator for matatu routes. Context matters. A project built for the Kenyan market shows you understand the environment you will work in.
• Integration with real APIs. Building with M-Pesa Daraja API, Africa's Talking SMS, or the Paystack payment gateway shows you can work with external systems, which is what most developer jobs involve.
• Projects that are deployed and accessible. A live URL beats a GitHub repo every time. If the employer can click a link and use your project, you have already passed the first filter.
• Clear documentation. A README that explains what the project does, how to run it, and what technologies it uses. Screenshots or a demo video help.

These are categories, not prescriptions. Pick one that interests you and build your own version:

Payment-integrated apps. Anything that processes payments through M-Pesa or card. A donation platform, a split-bill calculator that actually sends money, or an event ticketing system. Employers building fintech products want developers who have touched payment APIs.

SMS or USSD tools. Kenya runs on SMS and USSD. A bus tracking system that sends SMS alerts, a student result checker via USSD, or an appointment booking bot. Build these with Africa's Talking or Twilio.

Dashboard or admin panel. A data dashboard for a school, clinic, or small business. It shows you can handle data, build interfaces, and think about what users need to see.

Open-source contribution. Contributing to an existing open-source project demonstrates you can read other people's code, follow contribution guidelines, and collaborate. One meaningful pull request to a known project carries weight.

Final-year project, polished. If your university requires a final-year project, treat it as a portfolio piece. Deploy it, write proper documentation, and make it presentable. Most students let their final-year project die after grading. Do not be one of them.

For a step-by-step approach to building your first real project, see the first real project guide.

GitHub: every project needs a repository with clean code, a README, and meaningful commit messages. Employers check your GitHub. Get started with GitHub here.

Live demo: deploy your project so it is accessible via a URL. Vercel, Netlify, and Railway offer free tiers that work for student projects. A live demo lets the employer use your project without cloning a repo.

Portfolio site: a simple one-page site with your name, a short bio, and links to your top three projects. Building a portfolio without clients covers how to do this.

Two-minute explanation: practise explaining each project in two minutes or less. What problem does it solve? What technologies did you use? What was the hardest part? This comes up in every technical interview.

• Too many unfinished projects. Five half-built apps signal that you start things but do not finish them. Three completed, deployed projects are better.
• No README or documentation. If the employer cannot understand what your project does in thirty seconds, they move on.
• Copied tutorials. If your project is identical to a YouTube tutorial, it shows you can follow instructions. It does not show you can think. Add a unique feature, change the context, or solve a different problem using the same tech.
• Ignoring mobile. Most Kenyan users are on phones. If your web app does not work on a mobile browser, you missed the point.