About Me

Engineer, builder, and problem solver

Full stack engineer, backend and platform focused

I build systems that hold up in production.

I'm Nasr Hassan Mpalang'ombe, a full stack engineer based in Tanzania with a backend and platform focus. I build reliable APIs, web platforms, and IoT systems for teams that need software to work in the real world.

My core backend language is Go. I also work with TypeScript, Laravel, PostgreSQL, Docker, and API design, and I stay close to the infrastructure layer: Linux, networking, deployment, and observability. That means I can take a product from data model to production without handing it between teams.

Today I work as a Backend Engineer at Switch Africa and run CodeGraphics. Over the past 4+ years I've delivered 100+ projects across fintech, healthcare, education, logistics, and IoT, from payment gateways and school ERPs to smart-meter platforms and mobile apps.

Tanzanianasrkihagila@gmail.comBackend Engineer at Switch Africa
Let's work together

Backend & APIs

Go and TypeScript services, payments, auth, queues, and APIs built to stay maintainable.

Platform & infrastructure

Linux, Docker, CI/CD, observability, and deployments that are reproducible.

Networking & automation

Routing, wireless networks, MikroTik, RADIUS, and software that controls infrastructure.

IoT & realtime

Device telemetry, MQTT pipelines, live dashboards, and realtime data flows.

Web platforms

Fast, accessible Next.js and React products with clean, considered UX.

AI integrations

Practical RAG, OpenAI, and automation features that ship to production.

Currently

  • Backend Engineer

    Current

    Switch Africa

  • Founder

    CodeGraphics

  • Tanzania

    EAT, UTC+3

  • CGPA 4.36 / 5.00

    Dissertation grade A

Available for select freelance and contract work, especially backend architecture, API integrations, and production web platforms.

How I work

  • Reliability first

    Error handling, testing, and observability are part of the build, not an afterthought.

  • Scale by default

    Schemas, caching, and deployment choices that hold up as usage grows.

  • Clear communication

    Small, visible progress and plain-language updates from kickoff to launch.

  • Clean handover

    Documented decisions and code the next developer can actually maintain.