You do not have to hire from San Francisco or London to ship serious software. You do have to know how to grow people.
BOU has been hiring engineers in Abuja since the company started. Some of the engineers who ship our hardest systems today walked in five years ago not knowing what a pull request was. That is not a knock on them. It is the actual lesson.
The talent is here. The polish often isn't.
The raw ability of the engineers we have interviewed in Nigeria is, on average, equal to anywhere else we have worked. Pattern recognition, problem-solving, the willingness to sit with a hard bug for three days — all there.
What is not always there is the surface layer. The way they format a commit message. The instinct to write a README. The habit of leaving the code base cleaner than they found it. The reflex to ask "what is this going to look like for the next person who reads it?"
That surface layer is what people mistake for talent. It is not. It is exposure.
What actually works to build engineers
We have tried a lot of things. Some worked, most did not. The three that actually move the needle:
1. Pair on real work, every day, for the first six months
Not pair-programming-as-ceremony. Pair as "you sit next to the person doing the hard task and you watch the choices they make." After about three months of that, the muscle memory shifts. They stop writing code for the demo and start writing code for the next engineer.
2. Give them a product to own end-to-end, fast
Nothing accelerates an engineer like being responsible for the thing that breaks at 2am. We hand engineers ownership of a real surface — a feature, an endpoint, a small product — within their first year. The leap they make in the next twelve months is bigger than any course or certification.
3. Make code review feel like teaching, not gating
The fastest way to kill a junior engineer is to send back a PR with three line comments and no context. The second fastest is to approve their bad code because you are too tired to explain why it is bad. We try to do neither. Reviews at BOU are slow and detailed for the first year an engineer is here, and faster after that. The engineers who survive that come out very, very good.
The narrative we reject
There is a tired idea — popular both inside and outside Africa — that to ship "serious" software you need to import senior engineers from somewhere else. We have not found that to be true. We have hired remotely from elsewhere. The local engineers we trained are, in most cases, just as strong.
The cost of importing seniority is not just the salary. It is the cultural mismatch with the customer. It is the engineer who builds a beautiful payment flow that fails the first time it meets a Nigerian bank's actual quirks. It is the design decision that assumes a credit card when the user has a USSD code.
Build local. Train hard. Ship a lot.
The soft bigotry of low expectations is the most expensive thing on a Nigerian engineering team. Pay people like they are world-class, hold them to that bar, and most of them will get there.
The kind of engineer we look for
Less interested in their CV than in how they think. Less impressed by the language they prefer than by the way they debug. Curious. Willing to ask a question they think is stupid. Willing to be wrong in front of the whole team.
If that is you, we are hiring. If you run a Nigerian engineering team and you are wondering whether to invest in growth or just keep buying senior hires, we would tell you the math on growth is better.
What this has meant for BOU
It has meant we can ship five or six products with a team that other groups would call too small. It has meant our retention is, frankly, embarrassing-good — because we ask a lot and we trust a lot, and engineers who get that combination tend to stay. It has meant our technology arm grew without us ever having to compromise the kind of person we hire.