A senior frontend role often starts with product delivery, but the highest leverage work is usually the work that changes how many teams build, test, release and operate software.
Payments work is where frontend engineering quickly stops being only about screens. The user interface has to explain money movement clearly, handle failure states carefully and protect trust when providers, banks, compliance rules and network conditions are all part of the experience.
At Kingmakers, my work progressed from shipping and stabilising product features into owning shared architecture, platform conventions, reliability patterns and engineering standards across a large React monorepo.
A large part of that ownership grew through payments work across BetKing and SuperSportBet. What started as fixing and improving payment journeys evolved into owning React withdrawals, modernising KingPay and strengthening the shared platform around those flows.
The Career Arc
| Period | Primary focus |
|---|---|
| 2023 | Payments stabilisation and production feature delivery |
| 2024 | React withdrawals ownership and safer rollout patterns |
| 2025 | Platform migrations, i18n foundations and shared infrastructure |
| 2026 | Architecture, auth consolidation, observability and engineering standards |
Owning React Withdrawals
The React withdrawals product covered the full journey from first interaction to final status. That meant building user-facing paths while also thinking through validation, rollout safety and operational support.
- Withdrawals landing experience
- First-account journey for users setting up withdrawals
- Bank validation with retry handling
- Withdrawal status and confirmation states
- Controlled beta rollout through to full production release
A good payments experience is not just fast. It is understandable, recoverable and boring in the right places.
Payments, Compliance and Provider Integration
Payments also required careful communication around compliance and provider behaviour. The frontend had to make financial outcomes transparent while integrating with several payment rails and market-specific journeys.
- Nigerian tax transparency and compliance UI
- Card vaulting journeys
- Bank and USSD flows
- Wallet journeys
- Provider integrations including Paystack, Interswitch, OPay and Paga
Modernising KingPay
The KingPay rewrite moved the product onto Remix and Tailwind, giving the team a cleaner foundation for multi-market delivery across Nigeria, South Africa and Zambia.
The value was not only a newer stack. It was a more maintainable payments surface that could share architectural conventions, reuse platform patterns and support future product changes with less friction.
Reliability as Product Work
Payments made reliability visible. Slow networks, provider timeouts and unclear errors become user trust problems, so the work needed production readiness from the start.
- Centralised fetch handling with timeout behaviour
- Request diagnostics and richer observability context
- OpenTelemetry instrumentation across critical flows
- E2E test suites for deposit and withdrawal journeys
- Quality gates through linting, type checks and SonarQube
High-Volume Systems and the BFF Layer
Major sporting events create a different kind of pressure. Traffic can arrive in bursts, payment and account journeys become more sensitive, and every slow provider call or unclear failure mode becomes more visible to customers.
The BFF layer was important because it was not just forwarding requests. It helped decide whether the frontend should receive cached data, whether a backend API needed to be called, or whether a third-party provider was part of the journey.
During World Cup-scale traffic peaks, Grafana metrics across those BFF services made it possible to benchmark request volume against public peak-event figures while giving the team a clearer view of routing behaviour, caching pressure and provider dependency pressure. That made the system easier to reason about when the product was under real load.
- Used monitored BFF services to understand high-volume request patterns
- Reasoned about when to call backend APIs, serve cached responses or depend on third-party providers
- Used Grafana evidence to understand traffic, failures and production behaviour during peak betting periods
Shared Infrastructure
The platform work focused on removing repeated decisions from individual teams and turning them into reusable foundations.
- Shared Cloudflare Worker entry patterns for auth and observability
- Customer notification and toast infrastructure with feature-flagged rollout
- Translations and i18n foundations for multi-market applications
- Authentication consolidation across sportsbook, promotions and Pick 11 journeys
- Backend-for-frontend patterns using Cloudflare Workers, Hono and TypeScript
Migrations That Reduced Drag
Large frontend systems accumulate complexity quietly. Some of the most valuable work was reducing that drag through planned migrations and deletion of legacy paths.
- My Accounts migration from MUI to Remix and Tailwind
- Material Tailwind migration to a newer shared package
- Islands architecture migration toward CMS-driven and Tailwind-based frontend composition
- Help Centre migration from Pages-style hosting to Worker-backed delivery
Standards, Documentation and Review
Platform ownership also showed up in the engineering standards that help teams move faster without becoming less careful.
- Commit conventions and pull-request playbooks
- React guidelines and multi-locale documentation
- Workers URL security policy
- Storybook documentation and deployable preview workflows
- Pipeline caching, lint/type gates and release protection
What This Adds to the CV
The strongest CV version of this work is not simply that I built payment screens or migrated frameworks. The stronger story is ownership across product delivery, provider integration, compliance communication, rollout safety, shared infrastructure, team standards and platform reliability.
- Built and owned React Withdrawals end-to-end
- Led a Remix/Tailwind rewrite of a multi-market payments product
- Integrated payment providers and compliance UI across regulated markets
- Improved reliability through observability, diagnostics and regression coverage
- Created shared infrastructure for Workers, notifications, translations, i18n and authentication
- Led migrations that reduced legacy drag and standardised modern React delivery
- Authored standards that made code review, release notes, localisation and CI/CD safer to repeat
The Operating Principle
Good platform work makes the right thing easier to do repeatedly, especially when delivery pressure is high.
My time at Kingmakers has been about more than individual features: it has also been about the systems, standards and feedback loops that helped teams ship those features with more confidence.