Featured2022 - now
Real-time financial data · Software Engineer
Portfolio · 2026Open to new opportunities
Nana AboagyeBoateng.
Software engineer working across the stack: APIs, data models, and the interfaces on top. Interested in correctness, clarity, and systems that keep working long after launch. Based in Accra.
CurrentlySoftware Engineer
Scroll to explore
Selected Work / 03
Engineering notes, not screenshots.
A short list of systems I'm proud of. Click any card for the write-up: the problem it had to solve, the shape of the solution, and what it actually cost.
2021 - 2022
Healthcare NGO platform
Rare Disease Ghana
2023
Commerce platform
The Bag Shop Gh
Content-first web app
Nana AJ
In progress
Booking + marketplace system
Diimple
About / 01
A software engineer who treats correctness and craft as the same problem.
I'm Nana Aboagye Boateng, a software engineer with 5+ years in production across fintech, healthcare, and government systems. I've built APIs that handle real traffic, designed schemas that hold up under load, and kept maintaining codebases long after the launch post went out. I care more about what's still running in two years than what demos well on a Tuesday.
My default stack is TypeScript end-to-end (Node, Next.js, Postgres, Mongo), with a side of C#/.NET when it earns its place. I lean on types, tests, and boring tools over clever ones, and I pay attention to the seams between systems: contracts, migrations, observability, the unglamorous parts that decide whether a service survives its second year.
Away from the keyboard I shoot photos, play video games, and occasionally get lost in the details of a well-designed object. All of it feeds back into the work.
Nana A. BoatengEngineer · '25
“Build like you're going to maintain it, design like you'll use it every day.”
Experience / 02
A track record of real production code.
Five years across fintech, healthcare and government work, enough time to learn where systems actually break and what it takes to keep them honest.
01 / Jan 2023
Jan 2023 - Present
Accra, Ghana
Software Engineer
at Persol Systems Limited
Building responsive web applications on a product team: component systems, front-end/back-end integrations, and the testing and review culture that keeps shipping predictable.
- Built reusable React/Redux components that lifted team delivery speed ~30%
- Wired front-end and back-end integrations for robust, dynamic user-facing flows
- Set up automated testing patterns that caught regressions before release
- Ran code reviews focused on clarity, correctness and team-wide consistency
ReactReduxTypeScriptNode.jsJest
02 / 2022
2022 - Present
Remote · Ghana
Software Engineer
at CediRates
Lead engineer on a real-time financial data platform: FX and fuel prices across Ghana, reaching ~15K monthly organic visitors from Google search, built to stay correct and responsive under real traffic.
- Designed the caching + read path that holds p95 under 125ms on recent production traffic
- Built the ingestion pipeline around retries and stale-while-revalidate so upstream flakiness stays off the front end
- Led the v2 rewrite onto Postgres + Redis when the access patterns outgrew the original document-store model
- Instrumented the stack with structured request logs, latency percentiles, and error-class aggregates, so regressions stopped being surprises
TypeScriptNext.jsNode.jsPostgreSQLRedisDockerAWS
03 / 2021
2021 - 2022
Accra, Ghana
Software Engineer
at Rare Disease Ghana
Engineered a Next.js platform for a healthcare NGO: accessibility-first, content-driven, and built to survive a small team running it long after handoff.
- Rebuilt the sign-up flow end-to-end, lifting volunteer conversions ~75%
- Wrote the volunteer-registration service and the admin tooling around it
- Shipped WCAG-aligned components used across the site
- Halved page load (~60%) through image pipeline and render-path work
Next.jsReduxTailwind CSSSEO
04 / Sep 2020
Sep 2020 - Oct 2022
Accra, Ghana
Software Engineer
at Ghana Standards Authority
Built internal tools for a government standards body: inventory tracking and operational tooling that had to be reliable for non-technical staff running it every day.
- Designed and built an internal inventory-tracking tool used across teams
- Cut page-load time ~40% by profiling the render path and trimming the bundle
- Refactored legacy React/Redux stores into patterns a new hire could navigate
- Tightened the API contract between frontend and backend teams
ReactReduxJavaScriptCSS3HTML5
05 / 2020
2020 - 2021
Remote
Software Engineer
at Freelance
Built and shipped production web systems end-to-end for clients across industries, from schema design and auth to deploys and the on-call that followed.
- Designed the data model and query paths for small-scale commerce systems
- Integrated payments and auth with a strict bias toward failure modes
- Tuned hot queries and added the indexes and caches they actually needed
- Wrote the docs + runbooks so the systems could be handed off cleanly
ReactNode.jsPostgreSQLAWSDocker
The stack
Tools I've earned scars with.
Typed end-to-end, tested where it matters, boring where it can be. Motion and the occasional WebGL shader when the brief actually earns them.
Principles / 04
Engineering taste, written down.
Five beliefs I keep coming back to. Not a process deck, just the actual load-bearing opinions behind the code I ship.
01
Correctness
Types, invariants, tests at the seams that matter. If the compiler can prove it, I'd rather not find out at 3am. Bugs shipped cheap are bugs paid for with interest.
TypesTestsInvariants
02
Schema over scale
Most 'scalability' problems aren't scaling problems, they're a data model that stopped being honest two years ago. Fix the model, and most of the fancy infra you thought you needed quietly becomes optional.
Data modelMigrationsIndexes
03
Write the postmortem first
Before shipping, ask: how will this fail, and how will I know? If I can't answer that, the feature isn't ready, no matter how clean the PR looks. Failure is a design input, not a surprise.
Failure modesDry-runRunbook
04
Observability is a feature
Logs, metrics, traces, meaningful alerts, all shipped alongside the code, not bolted on after the first incident. You can't fix what you can't see; every service I ship ships with eyes.
LogsMetricsAlerts
05
Deployable = fixable
A system you can't safely deploy ten times a day is a system you can't safely fix. Small PRs, fast pipelines, painless rollbacks. Everything else is downstream of that.
CI/CDRollbacksSmall PRs
Building
Diimple
A beautician locator + booking app for Ghana.
Learning
Rust on the edge
Exploring Axum, sqlx, and Cloudflare Workers for a side project.
Philosophy
Build like someone's counting on it.
Because someone usually is. Registering a company, shipping a product, publishing a piece, each one has a reason behind it. That tends to produce engineers who care about correctness, not just cleverness.
Listening
Rod Wave on loop
Heavy rotation while I code. When I'm not listening, I'm probably deep in a game, it's how I reset.
Contact / 06Building something hard?
Building something hard?
Let's talk.
Open to new roles & collaborations·Accra, Ghana ·