Do Kenyan Banks and Telcos Hire Developers Without Degrees?

Open any developer job posting from Safaricom, Equity Bank, KCB, or Airtel Kenya. Under "Requirements" you will find some version of: "Bachelor's degree in Computer Science, Information Technology, or a related field."

That line is real. HR put it there. It is in the job description template that has been used since 2015. And for the first screening pass, it functions as a filter. A recruiter with 300 CVs on their desk uses the degree checkbox to reduce the stack to a manageable size.

But here is what happens next. The hiring manager on the technical team gets the shortlist. They look at GitHub profiles, portfolio projects, and previous experience. If a candidate without a degree has a stronger technical profile than candidates with degrees, the hiring manager picks up the phone and calls HR to ask for an exception.

Does this happen every time? No. Does it happen often enough to be worth trying? Yes.

The key insight: the degree requirement is an HR policy, not an engineering one. Engineers want people who can write code. HR wants people who check boxes. Your job is to make the engineers want you badly enough that they fight the HR battle on your behalf.

1. Get referred internally. This is the strongest move. If someone who already works at the company submits your CV with a note saying "I have seen this person's code, they are good," your application goes to a different pile. The degree filter becomes a suggestion rather than a rule.

How to get referrals: Attend tech meetups in Nairobi. Build relationships with developers at target companies through NairobiJS, GDG Nairobi, or industry events. Contribute to open-source projects that employees at these companies also contribute to. Network genuinely. Do not ask for referrals on the first conversation. Build a relationship first.

2. Enter through a contract or outsourcing role. Banks and telcos hire many developers through outsourcing firms and on contract terms. These roles have softer requirements because the outsourcing company, not the bank, is your employer. Once you are inside the building, doing good work, converting to permanent staff becomes much easier. And by then, your work record speaks for itself.

3. Build something they use. This sounds unusual, but it works. Build a tool, an integration, or a proof-of-concept that is relevant to the company's work. A demonstration M-Pesa integration for a bank's use case. An API monitoring dashboard. Share it on LinkedIn and tag the company's engineering team. When you apply, reference this project. It is the strongest possible signal that you can do the job.

Not all corporates are equally rigid. Based on patterns in the Kenyan market, here is a general guide.

More flexible:

• Digital-first banks and fintechs with corporate backing (like M-Shwari, Fuliza, and NCBA Loop). These teams operate more like startups within the corporate structure.
• Innovation labs and accelerator programs run by banks (Equity's FinTech incubator, KCB's innovation hub). They value speed and creativity over credentials.
• Telco developer platforms and API teams. These are the teams building tools for other developers, and they tend to hire like tech companies rather than traditional corporates.

Less flexible:

• Core banking system teams at large banks. These roles involve sensitive financial infrastructure, and HR policies are stricter.
• Government-adjacent institutions (Central Bank, Capital Markets Authority). Degree requirements are structural and rarely waived.
• Roles requiring specific professional certifications (CISA, CISSP for security roles). These have credential requirements beyond just a degree.

The pattern is clear: the closer a team operates to a startup culture, the more flexible they are about degrees. The more traditional and regulated the environment, the stricter the requirements.

Here is the most practical advice in this entire article: you do not need to get into a bank as your first job.

Start at a startup or agency. Work for two years. Build a track record. Ship code. Get promoted. Then apply to the bank.

For mid-level developer roles (3+ years of experience), the degree requirement softens dramatically at most Kenyan corporates. The hiring manager cares about your last three years of work, not whether you have a BSc. Your experience effectively becomes your credential.

This path is slower than going directly from bootcamp to corporate, but it is the most reliable. And it has a bonus: by the time you join the bank, you have real-world experience that makes you more effective than a fresh CS graduate who has only written academic code.

Two years at a startup where you shipped code weekly, debugged production issues at 2 AM, and integrated M-Pesa callbacks under deadline pressure is worth more practical education than four years of university exams. Banks know this. Their engineering teams know this. The HR policy just has not caught up yet.

Understanding what these companies need helps you position yourself effectively.

Banks need:

• Developers who understand payment flows, transaction processing, and financial data integrity
• Security-conscious coding practices (input validation, encryption, authentication)
• Experience with APIs, especially M-Pesa Daraja, card payment gateways, and inter-bank transfer systems
• Ability to work with large codebases and follow coding standards
• Understanding of compliance requirements (though you learn these on the job)

Telcos need:

• API developers who can build and maintain platform services
• Mobile-first thinking (most telco customers interact via phone)
• Experience handling high-volume, real-time systems
• Knowledge of SMS, USSD, and mobile money integration
• Data processing skills for analytics and reporting

Notice: nothing on either list says "must have a degree." These are skill requirements. If your portfolio demonstrates these skills, you are what they need, regardless of what certificate you hold.

If working at a Kenyan bank or telco is your target, here is a realistic plan:

1. Build skills. Focus on JavaScript/TypeScript, React, Node.js, and PostgreSQL. Add M-Pesa integration and security best practices. These are the most in-demand skills at Kenyan financial institutions.
2. Build a portfolio. Include at least one project with payment processing, user authentication, and proper error handling. A fintech-style app (loan calculator with M-Pesa repayment, expense tracker with bank-grade security) signals alignment with what banks build.
3. Get your first job anywhere. A startup, agency, or freelance work. The goal is paid experience on your CV. Two years is the sweet spot before targeting corporates.
4. Build your network. Attend fintech meetups. Connect with engineers at target companies on LinkedIn. Engage with their content. When a role opens, your name is already familiar.
5. Apply strategically. Target roles at innovation labs, digital banking teams, and API platforms first. These are the most degree-flexible parts of corporate tech. Avoid applying to core banking system roles where credential requirements are strictest.

At McTaba Labs, our curriculum includes M-Pesa integration, payment processing, and security fundamentals. The African Stack that Kenyan banks and telcos are building with. 26 weeks, 8 production-grade apps. KES 120,000 with M-Pesa instalment plans.