From Individual Contributor to Manager in African Tech

Moving from individual contributor to manager in African tech means trading the work you're best at for work you've never done — and most companies will hand you the title with zero training. The transition succeeds when you start doing manager-shaped work before the promotion (mentoring, coordinating, owning outcomes beyond your tickets), learn to measure yourself by your team's output, and resist the urge to remain the hero engineer. The WEF lists leadership and social influence among the fastest-rising skills (Future of Jobs Report 2025); here's how the leap actually works.

TL;DR:

• Management is a career change, not a promotion. Different skills, different scoreboard.

• Win the role by visibly doing pieces of it first; survive it by letting go of being the best builder in the room.

• The IC path is a legitimate alternative — choose management for the right reasons, not as the only raise available.

First: should you even want this?

The honest fork most African tech careers hit around year five: in many local companies, management is the only visible path to seniority and pay — the staff/principal IC track barely exists outside international employers. So engineers, designers and analysts become managers by economic gravity rather than by inclination, and teams inherit reluctant leaders.

Run the test before chasing the title: Do you feel energy (not just tolerance) for unblocking others? Did you enjoy the mentoring, coordinating parts of your last project more than the building? Can you accept that your output will become invisible — measurable only through other people's work? Three yeses: proceed. Three nos: the remote-first IC track (see our data career paths and remote work guides) now pays as well or better — management is no longer the only door.

Phase 1: Earn it before the title (3–6 months out)

1. Collect leadership evidence deliberately: onboard the next hire, run the standup when your lead travels, own a cross-team deliverable. This is the wins file from our promotion guide, with a leadership column.

2. Tell your manager you want the path — explicitly, in a career conversation: "When a team lead opening comes, I want to be the candidate. What would I need to show?" Write down the answer; deliver it visibly.

3. Practise the unglamorous mechanics now: running a tight meeting, writing a clear weekly update (the managing-up template works downward too), giving one piece of direct feedback to a peer without drama.

4. Watch real managers like a student. Note what your best manager does in conflict, and what your worst one ruins. You're assembling your playbook from live examples.

Phase 2: The first 90 days with the title

1. Re-onboard yourself — the first-90-days playbook applies in full, with one addition: one-on-ones with every report in week one. Ask each: what should I keep, change, never touch?

2. Do not redesign anything for 30 days. The reflex to prove yourself through immediate reorganisation is how new managers manufacture resistance. Earn context first.

3. Set the operating rhythm early: weekly one-on-ones (non-negotiable, never skipped for "busy"), a team planning cadence, and a visible definition of done. Predictability is the first gift a manager gives a team.

4. Learn to delegate outcomes, not tasks. "Own the reconciliation feature end-to-end; here's what success looks like; pull me in when blocked" grows people. Handing out subtasks keeps you the bottleneck with extra steps.

5. Shield, then translate. Your two core jobs in the African startup context: absorbing chaos from above (founder pivots, investor pressure — see our managing-up guide from the other side now) and translating business pressure into clear priorities below.

The three traps that break new managers here

• The hero trap: production breaks, and you dive in to fix it yourself — faster, cleaner, like always. Do it twice and you've taught the team that ownership is decorative and 2am is your problem. The fix: sit on your hands, coach the on-call through it, review after. Slower once; faster forever.

• The shadow-IC trap: keeping the juiciest technical work for yourself "to stay sharp." Your calendar fills, both jobs suffer, and your strongest report quietly interviews elsewhere (possibly via our job board — we see this weekly). Keep a small technical surface — code reviews, architecture input — and hand the building to the team.

• The big-man trap: the cultural one. African workplace hierarchy can seduce new managers into distance — the closed door, the title in the email signature, feedback delivered as decree. The managers people actually follow here blend authority with access: decisive in the room, reachable after it. Respect flows to competence and fairness far longer than to status.

"The hardest sentence for every new manager we coach is 'my job is no longer to be the best engineer.' The ones who internalise it in three months build teams; the ones who fight it for a year build resentment — and usually boomerang back to IC roles, bruised," says Abraham Iyiola, Founder of CareerBuddy.

Your new scoreboard (because the old one is gone)

1. Team throughput and quality — shipped outcomes, not your commits.

2. Retention and growth of your people — did anyone get promoted from your team this year? Did your best people stay?

3. Predictability — does leadership trust your estimates and your bad-news-early communication?

4. Hiring — every strong hire you close is compounding output; interview craft (from the other side of our interview guides) becomes a core skill.

5. Your own dispensability — the paradoxical one: a team that runs well during your two-week leave is the strongest possible case for your next promotion.

A tale of two transitions (both real patterns)

Transition A — Tunde, senior backend engineer to team lead at a Lagos fintech. Six months before the opening existed, he started running the weekly tech sync and owning the intern's onboarding. When the role opened, the decision meeting lasted ten minutes — he was already doing the job. His first 90 days: thirty days of pure listening (he kept a "do not touch yet" list of things that annoyed him), then one process change (a deploy checklist the team co-wrote), then his first hire. Eighteen months later his old role has been backfilled twice while his team's attrition is zero. His verdict: "I write code four hours a week and miss it every day. I also wouldn't go back."

Transition B — Chiamaka, star analyst to analytics manager at a bank, promoted suddenly when her boss left. No preparation phase, no training, a team of five inherited overnight — the common African-corporate version. What saved her: she treated it as a new job, not an extension. Week one one-on-ones surfaced that two reports were flight risks over stalled growth; she built each a development plan and took both off the market. She kept Friday afternoons for her own technical work — enough to stay credible in review meetings, not enough to bottleneck. Her hardest lesson came at month four, fixing a report herself at midnight rather than coaching the analyst who'd built it: "He told me later he almost resigned that week — not because I fixed it, but because of what it said about my trust."

Different routes, same destination, same two lessons: the preparation you can control beats the ceremony you can't, and the team is always watching what you do when it would be faster to do it yourself.

FAQ

How much more do managers earn than ICs in African tech?

Locally, team leads typically earn 20–40% above senior ICs (lead/principal bands in our salary guide). But remote senior IC roles often beat local management pay entirely — which is exactly why the choice should be about the work, not the raise.

Can I go back to IC if I hate managing?

Yes, and it's increasingly destigmatised — the "boomerang" is common and often career-positive. Frame it honestly ("I learned I create more value building") and keep the leadership experience as a differentiator; ex-managers make exceptional senior ICs.

How do I manage former peers — especially friends?

Name it once, directly: "This is awkward for both of us, so let's set how we'll work." Then be scrupulously consistent — the fastest way to lose a team is visible favouritism toward old allies. Friendships survive fairness; they rarely survive special treatment exposed.

What if I'm managing people older than me?

Common in Nigerian tech and delicate in a culture that honours age. Lead with respect for their experience, consult them visibly, and let your competence justify the structure. Authority asserted loudly is authority already lost.

What training should I actually get?

One good management book beats most courses (start with "The Manager's Path"), a peer group of other new managers beats both, and a mentor two levels up beats everything. Leadership Academy-style programs help most at the 12-month mark, once you have real problems to bring.

How long until I feel competent?

Six months to stop feeling fraudulent; eighteen to feel skilled. The discomfort is the curriculum — every manager you admire once quietly Googled "how to run a one-on-one."

Making the leap — or hiring for one? Leadership roles across African tech are on jobs.thecareerbuddy.com, and our promotion-case guide gets you into the conversation.

Written by Abraham Iyiola, Founder, CareerBuddy — placing senior tech and business talent across Africa since 2018. Connect on LinkedIn.

Featured image: Photo by Christina @ wocintechchat.com on Unsplash.