Skip to main content
Hiring Senior Engineers in a Talent-Scarce Market: What Nigeria Taught Me — Anselm Fowel
Leadership

Hiring Senior Engineers in a Talent-Scarce Market: What Nigeria Taught Me

5 min read
875 views
Share:

Hiring senior engineers is hard everywhere. Hiring them in a market like Nigeria's, where the most talented people are routinely recruited by companies paying in dollars or pounds from abroad without ever leaving their bedrooms, is a different sport entirely. Building strong teams here taught me lessons that turned out to apply far beyond this market, because scarcity simply makes the universal truths impossible to ignore.

You compete in a global talent market whether you like it or not.
You compete in a global talent market whether you like it or not.

You are competing globally whether you like it or not

The talented engineer you want to hire is, at this very moment, being courted by a startup in London and a contract in San Francisco, all from the same laptop they would use to work for you. Pretending you compete only against local salaries is the single fastest way to lose your best candidates in the final round, confused about why your "competitive" offer was declined.

You have to understand the global market your people can access from their desk, and then decide, honestly, what you offer instead of simply trying to match a number you often cannot match. Denial is not a strategy. Clear-eyed differentiation is.

What we offer instead of the highest salary

Since we cannot always win on raw compensation against a dollar-denominated remote contract, we win, deliberately, on the things that remote contract cannot give.

  • Ownership. Real responsibility for systems that genuinely matter, handed over early and meant sincerely.
  • Proximity to impact. Building financial infrastructure that people in your own market, your own family, actually use.
  • Growth velocity. The kind of scope and challenge that makes someone a dramatically stronger engineer in two years.
  • A team worth belonging to. Peers who push you and leaders who protect your time and your growth.

None of these are free; they require a real culture rather than a slogan. But they are durable in a way that a salary number, which someone can always outbid, simply is not.

Hire for trajectory, not just the current resume

In a scarce market, the engineer with the perfect ten-year resume is rare and fiercely expensive, and you will lose most bidding wars for them. But the sharp, hungry engineer five years into their career who is clearly underplaced, doing work beneath their ability at a company that does not see them, is everywhere. And they are very often the better bet.

Enjoying this article?

Get more like it in your inbox — practical engineering leadership, fintech, and AI. No spam, unsubscribe anytime.

Hire the person who will be excellent in eighteen months, and then make absolutely sure the eighteen months of growth you promised actually happen.

I have built some of my strongest teams by hiring for slope rather than intercept, betting on trajectory and then investing hard in growth so the bet pays off. It requires a real commitment to development, but in a scarce market it is often the only way to field a senior team at all.

The interview as a two-way audition

Senior candidates worth having are evaluating you at least as hard as you are evaluating them, and a sloppy, disrespectful, or chaotic interview process tells them, accurately, exactly what working here will feel like day to day. They are right to walk away from it.

We treat our process as a representative sample of our engineering culture: clear, fast, technically honest, and respectful of the candidate's time. That reputation compounds in a tight market, where engineers talk to each other constantly, and a good process quietly brings the next strong candidate through the door before you have even advertised.

Building a pipeline, not just filling a seat

In a scarce market, reactive hiring, scrambling to fill a seat the moment it opens, is a losing game; the good people are not available on your timeline. So we invest in the long game: relationships with strong engineers long before we have a role for them, a visible engineering brand through writing and talks, and genuine investment in the community that produces the talent. The best hire is often someone who has watched the team from a distance for a year and already wanted in. That patience is itself a competitive advantage that the panicked seat-filler never gets to enjoy.

Retention starts at the offer

If you hire someone by overselling the role, painting a picture you cannot deliver, you have started a quiet countdown to their disappointment from the moment they accept. I would genuinely rather lose a candidate to honesty in the interview than win them with a story that the first month exposes as fiction.

The engineers who stay are the ones for whom the job turned out to be what we honestly promised it would be. In a scarce market, where every departure is painful and slow to replace, that integrity is not just ethics; it is one of the most effective retention strategies you have.

Anselm Fowel, CTO and fintech architect
Anselm Fowel — CTO & fintech architect

Conclusion: scarcity clarifies

A talent-scarce market is unforgiving, but it is also clarifying. It strips away the luxury of competing purely on money and forces you to build something genuinely worth joining and staying for. Offer real ownership, hire for trajectory and deliver on it, run a process that respects people, build a pipeline before you need it, and tell the truth in the offer. Do that, and you can field a world-class team even when the world is trying to hire it out from under you.

Enjoyed this article? Share it with others!

Share:

Get new posts in your inbox

Occasional, practical notes on engineering leadership, fintech, and building with AI. No spam, unsubscribe anytime.

Comments (10)

Leave a Comment

Comments are moderated and will appear after review.

Bashir Danjuma

July 23, 2026

Does the "Conclusion: scarcity clarifies" still hold on a 7-engineer team? We're at the smaller end of that and some of these patterns feel like they need a dedicated ops person to run properly.

Tosin Alabi

July 17, 2026

Small addition: this only holds when the manager themselves has been coached this way. Copy-pasting the technique without the underlying model tends to fall flat.

Ayodeji Adebayo

July 13, 2026

Junior eng, 6 months into my first fintech role, so a lot of this is above me, but the "The interview as a two-way audition" bit made a concept click that I had been nodding along to in code review for months. Thanks for writing at a level that doesn't gatekeep newer engineers out.

Rachel Lewis

July 6, 2026

14 months into my first eng job at a mid-size fintech, so a lot of this is above me, but the "What we offer instead of the highest salary" bit made a concept click that I had been nodding along to in code review for months. Thanks for writing at a level that doesn't gatekeep newer engineers out.

Ikechukwu Ibe

July 1, 2026

Yes to all of this. Especially the closing.

Zainab Danjuma

June 27, 2026

Refreshing to read this framed for our market rather than lifted from a Silicon Valley playbook. Specifically the "The interview as a two-way audition" piece — CBN have opinions, and that changes the design constraints in ways the US-centric literature never touches.

Lauren Hall

June 25, 2026

Would add: the incentives inside the calibration room matter as much as the actual conversation with the engineer.

Alex Carter

June 23, 2026

Broadly agree, but the "The interview as a two-way audition" advice assumes the engineer is receptive to feedback in the first place. In a team that has just been through a re-org the sequencing has to change.

Kojo Yeboah

June 19, 2026

Does the "You are competing globally whether you like it or not" still hold on a 4-engineer team? We're at the smaller end of that and some of these patterns feel like they need a dedicated ops person to run properly.

Segun Adeoye

June 18, 2026

Sharing this internally.

About the author

Anselm Fowel

Anselm Fowel

Chief Technology Officer & fintech architect. 16+ years leading engineering across AlliancePay, Mondu, Transalliance, Global Accelerex, and Fidelity Bank — writing here about engineering leadership, fintech architecture, and AI in production.

Read next

Subscribe to the newsletter

Practical notes on engineering leadership, fintech, and building with AI — delivered to your inbox. No spam, unsubscribe anytime.

Anselm Fowel

Chief Technology Officer | Fintech Architect | Engineering Leader

Building the future of financial technology through innovative engineering and strategic leadership.

Expertise

  • CTO Advisory
  • Fintech Architecture
  • Team Leadership
  • Technical Strategy
  • System Design

Get In Touch

[email protected]
Lagos, Nigeria

© 2026 Anselm Fowel. Crafted with passion.