Skip to content
01 / EngineeringFor CTOs, engineering leads, and hiring teams

Systems thathold up underreal load.

Seven years building AI, web, and mobile products that survive contact with production — across fintech ledgers, high-traffic commerce, and corporate systems nobody is allowed to break.

I’m an engineer and an entrepreneur. This is the software engineer half — the same engagements, weighted toward architecture and implementation. See my tech entrepreneur work

01Case studies

The problem, and how it was actually built.

Client names are withheld under NDA. The architecture, constraints, and trade-offs are exactly as shipped.

Challenge

Migration advice is scattered across government pages, forum threads, and agents who are paid whether or not you get in. It goes stale quietly: a fee changes, a quota fills, a route closes, and the version circulating is still last year's. The cost of believing it is not an inconvenience — it is a year of someone's life. Most people who lose that year were eligible for something. Nobody told them the truth early enough, in a language they read, with the numbers as they actually stand today.

Approach

Eligibility is computed in tested, auditable code rather than delegated to a model — the rules are the product, so they have to be inspectable and they have to be right. AI sits around that core, not inside it: two models independently verify each rule against its official government source, and a human signs off before anything publishes. Every statistic on the site carries a link to the page it came from and the date it was last checked, so a reader can audit the claim instead of trusting it. Routes are scored 0–100 across eligibility, affordability, timing, and refusal risk; costs are itemised and converted to the user's currency with estimates explicitly labelled as estimates; timelines are calculated backwards from real intake dates rather than quoted as averages. Built on Next.js on Vercel with Firebase behind it, localised across English, French, and German, with uploaded documents encrypted and deletable by the person who uploaded them.

Stack

Next.jsTypeScriptFirebaseRules engineLLM verification pipelinei18n (EN/FR/DE)Vercel
SectorAI Products

Challenge

Professionals know that showing up on LinkedIn compounds into work, and post nothing anyway. The blockers are never effort: a blank page at the end of a long day, an evening lost to a single post, the fear of sounding machine-generated in front of people who hire, and a profile that goes quietly stale while the market moves. Existing tools solved the wrong half — they made it easy to publish more, not easier to sound like yourself.

Approach

A Next.js application on Vercel with Firebase for identity and data, publishing through LinkedIn's official OAuth API — no browser extension, no cookie scraping, tokens encrypted at rest — because an account that gets banned is worse than an account that goes quiet. A daily generation pipeline drafts in the user's own voice from field-specific news, then runs its own output back through a detection pass that flags and rewrites machine-sounding patterns before a human ever sees it. Scheduling derives send times from each account's own engagement history rather than a global 'best time to post'. Publishing is approval-gated by design: the automation drafts, the user decides, and the model never gets to speak unsupervised on someone's professional record. Around that sit profile optimisation against ATS keywords, a lightweight CRM for recruiters and warm leads, and monthly reviews of consistency and engagement. Stripe handles subscriptions; the interface ships in English and French.

Stack

Next.jsTypeScriptFirebaseLinkedIn OAuth APILLM generation pipelineStripeVercel
SectorAI Products

Challenge

A financial platform was losing customers to slow, unreliable transaction handling. Payment options were limited, response times were unpredictable under load, and outages were frequent enough that clients had stopped trusting the reporting.

Approach

Rebuilt the backend around Spring Boot microservices with Spring Security enforcing access at the service boundary, so a failure in one path could no longer take down settlement. Integrated multiple payment gateways behind one interface and implemented encryption protocols protecting sensitive financial data both in transit and at rest. Real-time analytics were layered on the transactional store rather than a nightly export, so operations could see the state of the business as it happened.

Stack

JavaSpring BootSpring SecurityMicroservicesPostgreSQLStripeDocker
SectorFintech
IN · Dec 2021 — Mar 2022

Challenge

Filing a federal tax return meant navigating rules most residents could not reasonably be expected to know. Any automation had to be exactly right: a miscalculated return is not a bug you apologise for, it is a regulatory problem for the filer.

Approach

Directed the platform end to end — a rules engine for federal tax calculation with the compliance logic isolated from the presentation layer, so a rule change never meant touching the UI. Rigorous QA testing and secure coding practices upheld data integrity and confidentiality across the filing lifecycle. Backend systems and database queries were optimised for the filing-season traffic spike, and a documented REST API backed the mobile clients.

Stack

JavaSpring BootREST APIsSwaggerPostgreSQLAgile
SectorPublic Sector
MarketIN

Challenge

Teams were rebuilding the same components against the same Figma files and getting different results each time. Nothing was documented, visual regressions shipped unnoticed, and page performance was drifting downward release by release.

Approach

Built the library on atomic design principles, taking each component from Figma mockup through to a fully responsive, optimised widget with accessibility and web standards respected rather than retrofitted. Storybook became the single source of documentation, with Chromatic running visual regression on every change so a styling regression failed CI instead of reaching production. Performance budgets were enforced as part of the same pipeline.

Stack

TypeScriptReactNext.jsStorybookChromaticTailwind CSSStyled Components
SectorDesign Systems
Jun 2021 — Sep 2021

Challenge

Shift management ran on paper and messaging apps. Staff did not reliably know when they were working, and managers had no view of coverage until someone failed to turn up.

Approach

Built the frontend as a set of reusable components on React with MUI and Ant Design, so new scheduling views could be assembled rather than rewritten. API integration used JWT for session handling and OAuth for third-party authorisation, keeping employee data behind a proper authentication boundary rather than a shared login.

Stack

JavaScriptReactMUIAnt DesignJWTOAuth
SectorSaaS
CM · 2018 — 2021

Challenge

A rotating set of regional clients needed web applications built end to end, on budgets that could not absorb a specialist per layer, and with junior staff who needed to be brought up to a standard while the work shipped.

Approach

Standardised on React frontends against Laravel backends using the MVC pattern, which gave every project the same shape and made a codebase legible to whoever picked it up next. Mobile-first design throughout, since the regional default is a phone on a patchy connection. Backend optimisation and PostgreSQL management kept operations predictable as data grew, and interns were trained on the same codebases they were shipping.

Stack

ReactLaravelPHPTailwind CSSPostgreSQLMVC
SectorCorporate Systems
MarketCM
02Capabilities

What I actually build.

Four areas where the depth is real. Everything else I will happily hand to someone better.

Secure financial systems

Transaction processing and regulated platforms, where correctness is not negotiable.

  • Payment gateway integration and encryption in transit and at rest
  • Compliance-driven design against industry data standards
  • Real-time analytics on top of transactional workloads

Design systems at scale

Component libraries built to be documented, tested, and handed over.

  • Atomic design, from Figma mockup to responsive production widget
  • Storybook documentation with Chromatic visual regression testing
  • Performance budgets held to strong Core Web Vitals scores

Full-stack product engineering

Java and Spring on the backend, React and Next.js on the front, end to end.

  • Spring Boot microservices with Spring Security and Spring Cloud
  • REST APIs documented with Swagger, consumed by web and mobile clients
  • PostgreSQL and MySQL schema design and query optimisation

Technical leadership

The part that decides whether a team keeps shipping after you leave.

  • Mentoring junior engineers through code review and design sessions
  • Agile sprint management across multidisciplinary, distributed teams
  • Alignment with product managers, designers, and clients on scope
03Technical arsenal

Tools chosen for the job, not the résumé.

Languages

Daily drivers

JavaNextJSJavaScript (ES6)TypeScriptDartSQL

Backend

Where the rules live

Spring BootSpring CloudSpring SecuritySpring RESTMicroservicesLaravel

Frontend

Product surface

ReactNext.jsReduxInertiaTailwind CSSMUIAnt DesignStyled ComponentsMotion

Mobile

Cross-platform

FlutterDart

Data

Persistence

PostgreSQLMySQLOracleFirebaseStrapi

Tooling & platforms

How the work ships

GitDockerGitHub ActionsMavenWebpackSwaggerStorybookChromaticCloudflareStripeFigmaAgile
04Experience

Track record.

Roles, dates, and what each one actually moved.

Blue Window Ltd.

Current role

2023 — 2025

Remote

Software Engineer — Design Systems

Owned a production component library from Figma handoff through to documented, visually tested release.

  • Built pixel-perfect, accessible components on atomic design principles, from Figma mockup to fully responsive optimised widgets
  • Configured Storybook for component documentation and Chromatic for visual regression testing
  • Streamlined component libraries and tightened performance budgets, landing strong Core Web Vitals scores

Mar 2022 — Sep 2023

Douala, CM · Remote

Founder & Principal Engineer

Architected and deployed secure, scalable software for financial applications — transaction processing and real-time data analytics.

  • Integrated multiple secure payment gateways and implemented encryption protocols protecting financial data in transit and at rest
  • Improved response times by 30% and reduced system downtime by 40% through a backend architecture revamp
  • Maintained a 100% client satisfaction rate while adhering to industry data standards
  • Mentored junior engineers on secure coding, design, and database management through code review

Dec 2019 — Mar 2022

Remote · Cameroon

Software Engineer

Directed end-to-end development and deployment of websites and applications with hands on experience in working with both frontend & Backend teams.

  • Delivered regulatory-compliant tax calculations at 99% accuracy
  • Optimised backend systems and database queries, cutting processing times by 25%
  • Built the APIs backing the mobile applications, enabling secure and efficient data exchange
  • Ran Agile sprints across a multidisciplinary team of engineers, designers, and QA

Jun 2021 — Sep 2021

Remote

Frontend Engineer

Built the frontend for a digitised workshift application aimed at workplace efficiency.

  • Built reusable, modern frontend components with React, MUI, and Ant Design
  • Integrated APIs using JWT and OAuth for secure data handling and authorisation

Independent & Client Projects

Nov 2018 — Sep 2021

Douala, CM

Full-Stack Engineer

Delivered web applications end to end for a rotating set of clients, and trained the interns behind them.

  • Built responsive applications with React, Laravel, and Tailwind CSS on mobile-first principles
  • Integrated REST APIs from Laravel backends using the MVC architectural pattern
  • Handled backend optimisation and PostgreSQL database management
  • Trained and followed up interns, handing them curated practical skills
05How I work

Opinions earned the expensive way.

Scope is the real architecture decision

Most systems fail from doing too much too early, not from picking the wrong framework. I cut scope to the workflow that proves the thesis, then build that properly.

Regulated work sets the floor

Building for financial and public-sector platforms means compliance and data integrity are design inputs, not a review gate at the end. That discipline carries into everything else.

Components are a contract

A component library nobody can read is a liability. Storybook documentation and visual regression testing are how a design system survives its second team.

Empathetic technical leadership

Leading remote teams across three time zones taught me that async clarity beats synchronous heroics. Written decisions, visible reasoning, no ambient context.

06Credentials

Education, certification, and the unpaid half.

Education

BSc Computer Science

Software Engineering major

African Institute of Computer Science · Cameroon

Languages

French
Bilingual
English
Bilingual
Chinese
Basics
Russian
Basics

Certification

  • Meta Front-End Developer

    Meta · 2024

  • Google Africa Developer Training Program

    Google · 2021

Community

  • Co-Founder Bio Foundation

    Volunteer club supporting local technical education.

  • Contributor Open Source Cameroon

    Ongoing contributions to the regional open-source community.

  • Mentor Code4Africa

    Mentored underprivileged students through JavaScript development fundamentals.

07Contact

Let’s talk architecture.

If you need a seasoned engineering consultant to lead your next product lifecycle, drop me a message and let's shape the future of tech together.

Based
Douala, Cameroon · WAT (UTC+1)
Response
Within two working days