Skip to content
Sheriff.

About

From interfaces to the systems behind them

I’m a software engineer at Axon Information Systems in Accra, working on platforms for government revenue, payroll, aviation and elections.

Story

How my work has changed

I started on the frontend, building invoicing and stock-management screens for a national VAT platform and the interface for a receipt reconciliation system. The frontend work kept leading me back to the same questions: why is this query slow, why does this number not match, what happens when the partner’s system is down?

Answering them moved me steadily toward the backend — first writing APIs, then modelling domains, and eventually designing how whole systems fit together.

Today most of my time goes to system architecture, PostgreSQL and SQL Server data models, APIs and integrations, and the background services that move data between them. I work with datasets in the tens of millions of rows, deploy to Azure Kubernetes Service and customer infrastructure, and spend a fair amount of time troubleshooting production behaviour.

I also co-lead small teams: breaking down work, reviewing designs and code, and helping junior engineers become confident owners of their parts of the system.

Principles

How I work

Habits that have held up across payroll, tax and integration-heavy systems.

  1. 01

    Understand the problem first

    Architecture follows the business process it serves. On payroll and tax systems that means learning how validation, approval and reporting actually happen before choosing services or schemas.

  2. 02

    Design for failure

    Integrations time out, partners send malformed data and jobs are interrupted. Retries, idempotent writes and reconciliation are part of the design, not later fixes.

  3. 03

    Measure before optimizing

    Query plans, timings and production traces decide where effort goes. Most of the large wins I have seen came from a small number of measured bottlenecks.

  4. 04

    Keep systems observable

    Structured logs, traces and error reporting should let someone unfamiliar with a service explain what it did and why.

  5. 05

    Prefer simple systems

    A single well-indexed database and a background worker often outperform a distributed design. Additional moving parts need a concrete reason.

  6. 06

    Share knowledge

    Reviews, written decisions and pairing make a team faster than any individual contribution. I treat mentoring as part of delivery.

Experience

Progression of responsibility

Axon Information Systems

Accra, Ghana

Systems integrator delivering government, revenue, aviation and election platforms across West and Southern Africa.

  1. Software Engineer

    • Co-lead backend delivery for national payroll and taxation platforms, guiding teams of around four engineers.
    • Design APIs, background services and reporting queries over PostgreSQL datasets of 20M+ records.
    • Own integrations with aviation, maritime and payment partners, including reconciliation and invoicing engines.
    • Deploy and operate .NET services on Azure AKS with Docker, Kubernetes and Keycloak.
    • Mentor junior engineers and advise frontend teams on API contracts and implementation.

  2. Junior Software Engineer

    • Built invoicing and stock management features for a national VAT monitoring platform.
    • Delivered the frontend for a receipt reconciliation platform and tuned its matching performance.
    • Supported on-premise deployments on customer infrastructure and ERP integrations.

Capabilities

Technologies I use

Backend

APIs, background services and business logic for regulated domains.

  • C#
  • .NET
  • ASP.NET Core
  • REST
  • GraphQL
  • Hot Chocolate
  • Entity Framework
  • Dapper
  • Wolverine

Data

Relational data at volume: modelling, reporting and performance.

  • PostgreSQL
  • SQL Server
  • MySQL
  • MariaDB
  • MongoDB
  • Table partitioning
  • Query optimization
  • Large datasets
  • Cross-database operations

Infrastructure

Containerised deployments on Azure and customer-hosted environments.

  • Docker
  • Kubernetes
  • Azure AKS
  • Azure
  • Helm
  • FluxCD
  • IIS
  • Azure DevOps

Identity & Observability

Access control and production visibility.

  • Keycloak
  • Sentry
  • OpenTelemetry
  • Seq

Frontend

Enough depth to build and guide product interfaces end to end.

  • Svelte
  • React
  • TypeScript
  • JavaScript
  • Tailwind CSS

Let’s build reliable systems.

I’m interested in teams working on hard backend problems — data-heavy platforms, integrations and systems that have to stay correct under load. Open to remote roles as a:

  • Senior Backend Engineer
  • Senior .NET Engineer
  • Senior Software Engineer
  • Backend-focused Full-Stack Engineer
Get in touch Download résumé