Naol Aboma
Let's talk
View engineering workSelected case studiesView experienceProfessional timelineDownload resumePDF · 102 KBOpen GitHub@naolabomaOpen LinkedInNaol AbomaContact Naolnaolaboma@gmail.com
Available for relevant Go / backend opportunities

NAOL ABOMA · BACKEND SOFTWARE ENGINEER

I build reliable backend systems in Go.

I work on transaction flows, external integrations, messaging, caching, auth, and observability—especially across fintech and distributed systems.

View engineering work Download resume
CORE SIGNAL
GoDistributed systemsFintechMicroservicesKafkaRedisgRPCKubernetes

01 / SELECTED WORK

Systems worth explaining.

Three projects that show how I think about concurrency, transaction state, low-connectivity systems, and service boundaries.

01Go · AI integration · Concurrent services

JobGen

An AI-assisted job platform that aggregates remote roles, matches them to candidate profiles, and supports CV improvement workflows.

  1. 01React + TypeScriptCV and job-search experience
  2. 02Go REST APIAuth, orchestration, validation
  3. 03Domain servicesAggregation, matching, CV workflows
  4. 04Data & integrationsMongoDB, Redis, MinIO, Gemini, job sources
  • Go
  • Gin
  • MongoDB
  • Redis
  • MinIO
  • React
Read case study
02Fintech · Payment lifecycle · Go

Invoice Payment System

A payment workflow that creates invoices, initiates hosted payment links, records callbacks, and keeps invoice status in sync.

  1. 01Next.js clientInvoice and payment actions
  2. 02Go + Gin APIValidation and delivery layer
  3. 03Use casesInvoice and callback state transitions
  4. 04MongoDB + SantimPayDurable records and hosted payment initiation
  • Go
  • Gin
  • MongoDB
  • REST
Read case study
03Thesis · Edge ML · Go backend · IoT

Smart Elderly Care & Emergency Response

A co-developed wearable prototype that detects falls on-device, sends emergency alerts over GSM, and reports telemetry to a Go caregiver platform.

  1. 01Wearable6-axis IMU · 50 Hz · on-device SVM
  2. 02A9G GSM / GPRSEmergency SMS and event telemetry
  3. 03Go + Gin APIDevice auth, JWT, RBAC, clean architecture
  4. 04PostgreSQL + ReactPersistence and caregiver dashboard
  • Go
  • Gin
  • PostgreSQL
  • GORM
Read case study

02 / EXPERIENCE

Professional backend work.

Building services where payment state, external dependencies, and failure handling have to be explicit.

Jan 2026 — Present

Current role

EagleLion System Technology

Backend Software Engineer

Building Go backend services for a digital-banking platform under development, including transaction workflows, external integrations, event-driven processing, and reliability mechanisms.

  • Work across REST and gRPC service boundaries, authentication, authorization, and data-access flows.
  • Implement transaction and payment workflows, external biller integrations, and explicit error handling.
  • Use Redis for duplicate-transaction protection and Kafka for event processing, with observability through OpenTelemetry and Prometheus.
  • Go
  • gRPC
  • Kafka
  • Redis
  • MongoDB
  • Oracle
  • Kubernetes

Previous experience

SantimPay

Backend & payment systems

Worked on Go services around invoice payments, payment links, transaction status, callbacks, and database-backed payment workflows.

  • Go
  • REST
  • Payments
  • MongoDB

Earlier experience

INSA Ethiopia

Machine learning

Worked in Python on preprocessing, feature engineering, opinion mining, and anti-malware-related machine-learning work.

  • Python
  • scikit-learn
  • TensorFlow

Earlier experience

Kuraz Tech

Backend engineering

Built Laravel APIs and worked with Docker-based CI/CD workflows.

  • Laravel
  • REST
  • Docker
  • CI/CD

Earlier experience

Elsewedy Electric

Software & IT systems

Worked on APIs, IT infrastructure, and ERP backup automation.

  • APIs
  • Automation
  • Infrastructure

03 / ENGINEERING EXPERTISE

Depth first, range second.

Go and backend systems lead. Everything else supports the work of shipping and operating reliable services.

Primary

Go

The language I reach for to build explicit, testable backend services.
  • Golang
  • Gin
  • Chi
  • fasthttp

Backend systems

Service design

Interfaces, failure behavior, and maintainable boundaries before framework detail.
  • REST
  • gRPC
  • Microservices
  • Clean Architecture
  • JWT
  • PASETO
  • RBAC

Distributed data

State & messaging

Designing the path from a request to durable state—and what happens on retry.
  • Kafka
  • Redis
  • PostgreSQL
  • MongoDB
  • Oracle
  • MySQL

Infrastructure

Operate what ships

Delivery and visibility are part of the service, not an afterthought.
  • Docker
  • Kubernetes
  • ArgoCD
  • Jenkins
  • CI/CD
  • S3 / MinIO
  • Vault
  • OpenTelemetry
  • Prometheus

Additional experience

Across the boundary

Enough range to collaborate across product, data, and device layers.
  • Python
  • TypeScript
  • React
  • Node.js
  • NestJS
  • PHP
  • C++
  • scikit-learn
  • TensorFlow

04 / ENGINEERING NOTES

Thinking in failure modes.

Short notes on the backend details that tend to matter after the demo works. This structure is ready for local articles as the library grows.

01

Payments

Designing APIs for duplicate requests

Idempotency keys, request identity, and the race between “check” and “write.”Follow on LinkedIn 02

Reliability

Redis under concurrent duplicate protection

Why atomicity, expiry, and failure policy matter more than a cache lookup.Follow on LinkedIn 03

System design

Transaction state machines

Making allowed transitions and terminal states explicit in payment services.Follow on LinkedIn 04

Go

Bounded concurrency in Go

Using contexts, worker limits, and cancellation to make goroutines operationally safe.Follow on LinkedIn 05

Messaging

Kafka consumer idempotency

What at-least-once delivery means for side effects, retries, and durable state.Follow on LinkedIn 06

Operations

Observability across a request path

Connecting structured logs, traces, metrics, and useful correlation identifiers.Follow on LinkedIn

05 / ABOUT

An engineer across boundaries.

I'm a computer engineering graduate who moved toward backend systems because the hardest product problems often live behind the interface.

My professional work centers on Go services, transaction workflows, external integrations, and reliability. My engineering background also spans machine learning and embedded systems, which helps me reason across system boundaries.

“Make the state explicit. Bound the failure. Leave the next engineer a system they can reason about.”

Sep 2021 — Jun 2026

Electrical & Computer Engineering

Addis Ababa University · Computer Engineering streamCGPA 3.64 / 4.0

Dec 2024 — Nov 2025

A2SV

Selective Google-backed software engineering programSolved 500+ data structures and algorithms problems.

National university entrance exam

Ranked 19th

among 600,000+ students · score 639

Languages

Afaan Oromo — NativeAmharic — FluentEnglish — Professional working proficiency

HAVE A BACKEND PROBLEM?

Building reliable systems is what I enjoy most.

If you're working on Go, distributed systems, fintech, or infrastructure, I'd be happy to connect.

Email Naol LinkedIn
naolaboma@gmail.com