Hackathons in Kenya for university students: the recurring ones and how to enter

These are the hackathons Kenyan university students should have on their radar. Not all run every year, so follow the organisers on social media for announcements.

• GDG on Campus Solution Challenge: annual, global. Teams build a project addressing a UN Sustainable Development Goal using Google technology. Your campus GDG chapter coordinates participation. Submissions open around January each year.
• Safaricom M-Pesa hackathons: Safaricom periodically runs hackathons focused on M-Pesa API integrations. These are often open to students and have cash prizes. Watch the Safaricom developer portal for announcements.
• Microsoft Imagine Cup: annual global competition for student teams. Build a tech solution that makes a difference. Regional rounds feed into a global final. Applications open around October each year.
• iHub and Nairobi tech community hackathons: iHub and other Nairobi tech hubs host themed hackathons throughout the year, often partnering with companies or NGOs. Follow iHub on Twitter and LinkedIn for dates.
• University-hosted hackathons: Strathmore, JKUAT, UoN, and others host internal or inter-university hackathons. Your tech club or CS department usually announces these. These are the easiest to enter and the best place to start.
• IEEEXtreme: a 24-hour global programming challenge for IEEE members. More competitive programming than traditional hackathon, but worth trying if you enjoy algorithms.

Keep a calendar. Most hackathons announce two to four weeks before the event. If you find out the day before, you have already missed team formation and preparation time.

Check the McTaba events page for upcoming hackathons and tech events we track across Kenya.

Most hackathons in Kenya use one of these registration methods:

• Online form: a Google Form or a platform like Devpost, Eventbrite, or Luma. Fill in your details, your team (if you have one), and your tech stack.
• Through your campus community: GDG on Campus leads, MLSA ambassadors, and tech club presidents often get early access to hackathon registrations and can register teams directly.
• Walk-in registration: some smaller university hackathons allow you to show up on the day and register. But do not count on this for popular events.

If the hackathon requires a team and you do not have one, say so in the registration form. Many events have a team-matching session on the first day. You can also post in campus WhatsApp groups or tech community channels looking for teammates.

Most student hackathons are free. If someone asks you to pay a large fee for a hackathon registration, verify the event is legitimate before paying. Check the organiser credentials and look for past event photos or coverage.

If you have never been to one, read the full breakdown of what happens at a hackathon. Here is the short version:

Before the event: the theme is announced, either in advance or on the day. You form your team (usually two to five people) and decide on roles. Not everyone needs to code. Teams need designers, presenters, and people who understand the problem.

During the event: you have 24 to 48 hours to build a working prototype. This means choosing a problem, designing a solution, building it, and preparing a demo. You will not sleep much. Most hackathons provide food, wifi, and power outlets. Bring your own laptop, charger, and extension cable.

At the end: teams present their projects to judges, usually in three to five minute demos. Judges score based on the problem you solved, how well your solution works, your tech implementation, and your presentation. Winners get prizes: cash, gadgets, internship offers, or cloud credits depending on the event.

You will not win your first hackathon. That is fine. The point is to build under pressure, work with a team, and finish something. Those skills transfer directly to real jobs.

Learn one stack well enough to build something in a day. You do not need to know everything. If you can build a simple web app with HTML, CSS, JavaScript, and a backend (Node.js, Python Flask, or even Firebase), you can contribute. If you cannot code yet, learn enough to deploy a basic page before the event.

Pick a team with mixed skills. A team of four backend developers will struggle with the demo. Get someone who can design a decent UI, someone who can present clearly, and at least one person who can connect to an API. If you are all beginners, that is fine too. Just assign roles clearly.

Prepare your environment before the event. Install your code editor, set up Node.js or Python, test that your tools work, and make sure your laptop has enough battery life or bring a charger. Do not spend the first two hours of the hackathon downloading software.

Practice pitching. Judges give you three to five minutes. You need to explain the problem, show your solution, and demo it. Practice this with a timer. Most teams lose points not because their code is bad, but because their demo is disorganised.

For detailed tips on performing well, read how to do well at a hackathon.

Hackathons in Kenya are not listed in one central place. You need to check multiple sources:

• Your campus tech clubs: GDG on Campus, MLSA, IEEE, and local tech clubs share hackathon opportunities in their WhatsApp and Telegram groups. Join at least one.
• Twitter and LinkedIn: follow accounts like iHub, GDG Nairobi, Safaricom Developers, and KamiLimu. They post about upcoming events.
• Devpost: a global hackathon platform. Filter by Africa or remote-friendly to find events you can participate in from Kenya.
• McTaba events page: we list tech events and hackathons relevant to Kenyan students. Check the events page regularly.
• University notice boards: both physical and digital. Some hackathons are only advertised through department emails or faculty WhatsApp groups.

Set a goal: participate in at least two hackathons per academic year. By the time you graduate, you will have four to eight hackathon projects on your portfolio. That is more than most job applicants can show.