Coding Interview Prep for Rwanda: What Employers Actually Ask

If you have been preparing for coding interviews using LeetCode, HackerRank, or YouTube channels aimed at FAANG candidates, you are over-preparing for the wrong thing. Most Rwandan employers do not run whiteboard algorithm marathons. They do not ask you to invert a binary tree on the spot. They do not care if you can implement Dijkstra's algorithm from memory.

That said, the interview is still technical. The format just looks different. Here is what you will typically encounter in Kigali:

Stage 1: Initial screening. A short call or email exchange. The recruiter or hiring manager checks that your background matches the role, asks about your salary expectations, and confirms your availability. Nothing deeply technical here.

Stage 2: Technical assessment. This is where Rwandan interviews diverge. Most companies use one of two formats: a take-home project (build something in two to five days) or a live coding session (45 to 90 minutes, screen shared). Some companies do both. Very few use traditional whiteboard interviews.

Stage 3: Behavioral and culture fit. A conversation about your work style, past challenges, teamwork experience, and career goals. In Rwanda's small tech scene, this round carries more weight than it might in a larger market. Companies invest heavily in team dynamics because replacing someone in a small team is expensive.

Some larger organizations (banks, telecoms, government agencies) add extra steps: HR interviews, panel interviews, or formal written tests. Startups tend to be faster and more informal.

Based on the types of roles and companies operating in Kigali, here are the technical areas that come up most often:

JavaScript and front-end fundamentals. How does the event loop work? What is the difference between let, const, and var? How do you manage state in React? These are baseline questions for web development roles. You should be able to answer them without hesitation.

REST API design. How would you design an API for a given feature? What HTTP methods would you use? How do you handle authentication? How do you structure error responses? API questions test whether you can build full systems, not just front-end interfaces.

Database queries. Write a SQL query to get specific data from a table with joins. Explain the difference between SQL and NoSQL. How do you handle database migrations? Most production applications in Rwanda use PostgreSQL or MySQL.

Mobile money integration. For any company that handles payments (which is many of them): How would you integrate MoMo payments into a web app? How does the MoMo API callback system work? What happens when a payment times out? How do you handle duplicate transactions? If you have built a MoMo or Airtel Money integration project, walk the interviewer through it step by step.

Practical problem-solving. You are given a bug report or a feature request and asked to talk through how you would approach it. This tests your debugging process, your ability to break down problems, and how you communicate technical decisions.

Deployment and infrastructure basics. How do you deploy a web application? What is CI/CD? How do you handle environment variables? Companies want developers who can ship code to production, not just write it locally.

Rwandan tech companies are not asking behavioral questions to fill time. In a market where teams are small and talent is relatively scarce, hiring someone who cannot collaborate or communicate creates real damage.

Common behavioral questions and what they test:

"Tell me about a time you disagreed with a teammate." They want to know if you can handle conflict without blowing up the team. Your answer should show that you listened to the other perspective and found a resolution.

"Describe a project where you got stuck. What did you do?" This tests your problem-solving process when things go wrong. Strong answers show that you tried multiple approaches, asked for help when needed, and eventually found a solution. Weak answers describe giving up or pretending you have never been stuck.

"Why do you want to work here specifically?" Research the company before the interview. Know what they build, who their customers are, and why their mission matters to you. Generic answers like "I want to grow my career" tell the interviewer nothing.

"What is a project you are proud of?" This is your chance to walk through your portfolio. Pick your strongest project, explain what it does, what decisions you made, what you learned, and what you would improve. Be specific. Technical depth matters here.

For international organizations and NGOs: You may also get questions about working across time zones, communicating with non-technical stakeholders, and handling ambiguous requirements. Practice explaining technical concepts in plain language.

Take-home projects. You receive a brief (build an API for a task manager, create a dashboard with these features, etc.) and have two to five days to complete it. This is the most common format in Rwanda.

How to stand out with a take-home:

• Read the brief carefully. Build exactly what they asked for. Do not add unnecessary features.
• Write clean, well-organized code. Use meaningful variable names. Add comments where the logic is not obvious.
• Include a README that explains how to set up and run your project.
• Write at least a few basic tests. Even five tests show you understand the practice.
• Deploy it. A live URL is more impressive than a GitHub link alone.
• If the role involves payments, add a MoMo sandbox integration if it fits the brief. It shows initiative.

Live coding sessions. You share your screen and solve a problem in real time. This is less about getting the perfect answer and more about how you think.

How to handle a live coding session:

• Talk through your thought process out loud. The interviewer wants to see how you approach problems, not just the final answer.
• Ask clarifying questions before you start coding. "Should this handle edge case X?" shows thoroughness.
• Start with a simple, working solution. Then optimize if time allows.
• If you get stuck, say so. Explain what you have tried and what you think the issue might be. Asking for a hint is better than sitting in silence.
• Practice beforehand by solving problems while talking out loud. It feels awkward at first. It gets easier.

If you have an interview coming up in one to two weeks, here is what to focus on:

Days 1 to 3: Review your own projects. Be ready to explain every project in your portfolio. For each one: what it does, what technologies you used, what was hard, what you would change. If you built a MoMo integration, be ready to explain the full flow from user click to payment confirmation.

Days 4 to 7: Practice common technical questions. Write REST API endpoints by hand. Write SQL queries. Explain JavaScript concepts out loud. Build a small project from scratch in under two hours to prove to yourself that you can code under time pressure.

Days 8 to 10: Research the specific company. What do they build? Who are their customers? What tech stack do they use (check their job postings or LinkedIn)? What challenges would you face in their domain? Prepare two to three thoughtful questions to ask them.

Days 11 to 14: Mock interviews. Find a friend or fellow developer and practice. Have them ask you both technical and behavioral questions. Practice talking through problems out loud. Practice explaining your projects concisely.

If you do not yet have portfolio projects to discuss, that is the gap to fill before applying. McTaba's Tech Foundations course (approximately RWF 30,000) covers the fundamentals, and the Full-Stack course (approximately RWF 1,200,000) gives you portfolio-ready projects including payment integrations.