Product Manager, Designer, Developer: Which Role Fits You?

Imagine a Nairobi fintech is building a new savings feature for their mobile app. Three people are critical to making it happen.

The product manager talks to 30 users in Eastlands and Westlands, analyses competitors, reviews M-Pesa transaction data, and decides: we will build a round-up savings feature that rounds M-Pesa payments to the nearest KES 100 and puts the difference into a savings pot. She writes a requirements document, prioritises it against five other features, and convinces leadership it is worth the engineering effort.

The designer takes those requirements and creates the experience. Where does the savings toggle live? How does the user see their pot growing? What happens when they try to withdraw? She tests three different interface designs with real users, discovers that the first version confuses people over 40, and simplifies it. The final design uses green progress bars because Kenyan users associate green with money.

The developer takes the designs and builds the actual feature. She writes the API endpoint that calculates round-ups, integrates with the M-Pesa Daraja API for automatic deductions, builds the database schema for savings pots, implements the frontend components matching the designs, and writes tests to make sure a rounding error does not steal someone's money.

Same product, three completely different workdays. Which one sounds like yours?

Developers spend most of their time writing code, reading other people's code, debugging why something does not work, and sitting in code reviews. A typical day at a Nairobi startup might include a 15-minute standup, 4 to 5 hours of focused coding, an hour of code review, and scattered Slack conversations with designers and PMs about edge cases.

What developers need: logical thinking, patience with detail, comfort with being stuck, and the ability to break complex problems into small steps. You do not need to be a maths genius. You need to enjoy the process of figuring things out, even when the error message makes no sense.

The Kenyan job market favours developers heavily. Nairobi has hundreds of developer openings at any given time: startups, banks, telecoms, agencies, and remote roles. Full-stack JavaScript, Python, Flutter, and Java are the most in-demand languages.

Starting salaries range from KES 40,000 to KES 120,000 for juniors. Mid-level developers earn KES 120,000 to KES 300,000. Seniors earn KES 250,000 to KES 700,000. Remote roles paying in USD can multiply these figures.

The downside: development can feel isolating. You spend hours alone with your screen. The dopamine hit of shipping a feature is followed by six bug reports. You need to keep learning because the technology changes constantly. And there is a ceiling if you do not want to move into management. Eventually, individual contributor roles top out and further growth means leading teams, which is a fundamentally different job.

Development is right for you if: you enjoy puzzles, you can sit with a problem for hours without getting frustrated, you get satisfaction from making something work, and you prefer building to talking about building.

Designers in Kenyan tech usually wear two hats. UX (user experience) involves researching how people use products, creating user flows, wireframing screens, and testing prototypes. UI (user interface) involves the visual layer: colours, typography, spacing, icons, and making everything look polished.

A designer's day might include a user interview in the morning, wireframing in Figma for three hours, a design review with the engineering team, and updating a component library in the afternoon. Designers talk to people more than developers do. They attend user research sessions, present their work to stakeholders, and negotiate with engineers about what is feasible to implement.

What designers need: visual taste, empathy for users, strong communication skills, and the ability to accept that your beautiful design will be questioned, revised, and sometimes cut entirely because engineering cannot build it in time.

The Kenyan design market is smaller than development but growing quickly. Fintech companies, health tech startups, and e-commerce platforms are investing in design teams. Safaricom's design team has grown significantly. Companies like Kyosk, iProcure, and M-KOPA have dedicated design roles.

Junior designers in Nairobi earn KES 40,000 to KES 100,000. Mid-level designers earn KES 120,000 to KES 250,000. Senior designers and design leads earn KES 250,000 to KES 500,000. Freelance design work for international clients can push earnings higher, especially if you specialise in mobile app design for African markets.

Design is right for you if: you notice when an app's spacing is off, you enjoy talking to people about their problems, you think visually, and you care about how things feel, not just whether they function.

Product managers spend their days in meetings, conversations, and documents. They talk to users, analyse data, write requirements, prioritise features, coordinate with engineering and design, and communicate progress to leadership. They do not build the product themselves. They decide what should be built and why.

A PM's day at a Nairobi fintech might include a morning user interview, a prioritisation meeting where five features compete for two engineering sprints, writing a product requirement document over lunch, an afternoon sync with the engineering team about technical constraints, and an end-of-day report to the CEO on product metrics.

What PMs need: clear thinking, strong communication, comfort with ambiguity, data literacy, and thick skin. You will make decisions that some team members disagree with. You will cut features that designers spent weeks on. You will tell engineers that the thing they built needs to change. The job is fundamentally about making hard choices with incomplete information.

PM roles in Kenya are fewer than developer or designer roles, and most are not entry-level. Companies want PMs who understand the business, the technology, and the users. Most Kenyan PMs moved into the role from engineering, design, business analysis, or consulting. Pure entry-level PM positions exist but are rare.

Associate PMs in Nairobi earn KES 80,000 to KES 150,000. Mid-level PMs earn KES 150,000 to KES 350,000. Senior PMs and heads of product earn KES 300,000 to KES 700,000. At the VP/CPO level in well-funded companies, compensation can exceed KES 1,000,000 monthly, but these positions are extremely few in Kenya.

Product management is right for you if: you enjoy strategy and trade-offs, you are comfortable talking to both engineers and executives, you prefer deciding over executing, and you can handle the fact that you do not directly make anything. You enable others to make things.

The best way to decide is to try all three. Not for months. For a weekend each.

Developer test. Build a simple web page with HTML, CSS, and JavaScript. Follow a tutorial if you need to. Does the process of writing code, seeing it work, and fixing bugs feel satisfying? Or does it feel like pulling teeth? If you enjoy the building process, development might be your path. If you found it tedious but were more interested in what the page should do and for whom, you might be a PM. If you were more excited about making it look good, design might call.

Designer test. Pick an app you use daily. Open Figma (it is free) and try to redesign one screen. Do not worry about learning every tool feature. Focus on whether rearranging elements, choosing colours, and thinking about how a user would flow through the screen energises you. If you lose track of time in Figma, take that seriously.

PM test. Pick a product you think could be better. Write a one-page document explaining what you would change, why users want it, how you would measure success, and what the trade-offs are. If you enjoyed the thinking, research, and writing process, product management might suit you.

Also pay attention to how you naturally behave in group projects. Do you gravitate toward building the thing? Designing how it looks? Or organising the team and deciding what to build? Your instinct in unstructured situations often points to your natural role.

The lines between these roles are not walls. They are more like hedges you can push through if you want to.

Many product managers in Kenya started as developers. They understood the engineering constraints, which made them more effective PMs. The transition usually happens after 3 to 5 years of development experience, when someone realises they are more interested in the "what" and "why" than the "how."

Some designers learn to code and become "design engineers" or "creative developers" who can both design and implement interfaces. This combination is rare and valuable. Companies love people who can go from Figma to a working React component without needing a handoff process.

Developers who learn design principles ship better-looking products. PMs who can read code ask better technical questions. Designers who understand engineering constraints create more buildable designs. Every role benefits from understanding the others.

If you are early in your career in Kenya, start with development. It is the most hireable skill, it gives you the deepest understanding of how tech products work, and it provides a strong foundation for moving into design or product management later. You can always specialise or switch after you have a solid base.

McTaba's 26-week programme builds this foundation: full-stack development with React, Node.js, and production deployments. Whether you stay a developer or eventually move into product or design, understanding how software is built from the inside gives you a permanent advantage.