Abdullah Nettoor Backend engineer who stays for the whole job

Backend systems · Products people actually run · Kochi, India

I build the systems behinduseful products.

Somebody hands me a mess of spreadsheets, WhatsApp threads and half-remembered rules. I hand back software that holds the day together. Domain, backend, interface, launch, and the awkward week after launch. I stay for all of it.

Engineer the whole useful path.

Engineering practice

The work I enjoy sits between a product question and a system that has to keep its promises.

The work between an idea and a reliable system.

Observe

Start with the work, not the feature list.

I go looking for the repeated handoff, the state nobody wrote down, and the exact moment someone stops trusting the record and reaches for their phone instead.

In practiceHibah began with a donor programme run out of a spreadsheet and a WhatsApp group. That gap was the brief.
Model

Give the messy parts hard edges.

Domain models, permissions, state transitions and failure modes should make the system easier to explain to the person running it. If it takes a diagram to defend, the model is wrong.

In practicePumpOS pins shifts, stock, credit and reporting to a single business-day record. One day, one truth.
Build

Pick the tool for the constraint in front of you.

Go when the service needs to be small and fast. Flutter when one codebase has to reach every screen. TypeScript for the web. Swift when it should feel native on a Mac. No loyalty, only fit.

In practicetqwp is a small Go API for running concurrent work with retries you can actually configure.
Ship

Own the path until a person can use it.

A clean backend that never meets a user is a hobby. Quality shows up after contact with product behaviour, deployment, and a Tuesday afternoon with bad connectivity.

In practiceLive products, public repositories, and an extension submitted to Raycast. All of it is out there to be judged.

Selected decisions

Judgment leaves a trace.

A technology list says what I have touched. These examples say more: the constraint, the engineering concern, and where the result can be inspected.

PumpOS · Continuity

The counter keeps moving even when the network doesn't.

Built around an offline-ready desktop client that syncs when the connection returns, with event history and auditable business-day snapshots so staff can trace how a number became the number.

Hibah · Trust

Stay out of the money. Keep every receipt.

Donors pay the organisation directly over UPI. Hibah never touches the funds. It structures the rest: reference verification, contribution state, team roles and reminders, so the ledger holds up without a payment gateway in the middle.

tqwp · Concurrency

Expose retries without making the happy path harder.

A small Go package. Enqueue tasks, process them with a pool of workers, decide exactly how failures get another go. Nothing else.

Technical range

Capability, not inventory.

I move across layers when the product requires it, with backend systems as the center of gravity.

Systems

Domain modeling that survives the second customer. APIs, concurrent processing, event-driven workflows, and auth that says no to the right people.

Data

PostgreSQL, MongoDB, Neo4j, Redis. Audit histories, ledgers, and the operational state everyone forgets to model until it goes missing.

Delivery

Docker, Kubernetes, cloud platforms, clients that stay in sync. Deployment, and then the part that matters: what the system does once real people are on it.

Languages

Go for the backbone. TypeScript for the web. Dart and Flutter across platforms. Swift for the Mac. Python and SQL for everything in between.

Experience

Engineering in context.

Current

Backend Engineer

HCL Cloud Native Labs

By day I build cloud-native backend systems at HCL. Nights and weekends go to my own products, native tools and open source, because the best way to learn what a system needs is to be the one who gets the 11pm bug report.

Primary focus

Backend systems and the shape of a service

Product practice

Fuzzy problem in, shipped path out

Core language

Go

Broader range

Flutter, TypeScript, Swift, cloud

Portrait of Abdullah Nettoor

Away from the architecture diagram

Ordinary work is full of hidden machinery. I like taking the cover off.

Every fuel station, charity and money-pool runs on handoffs, records and the same fifty decisions made again and again. That is where software earns its keep, and where most of it quietly fails. I bring a designer's eye to backend work and a backend engineer's suspicion to product decisions. Based in Kochi. Two bachelor's degrees, in Commerce and Theology, which explains why I care about both the ledger and the people trusting it.

Kochi, KeralaBackend engineeringIndependent makerOpen source

Start a conversation

Have a difficult system worth untangling?

I’m open to thoughtful backend work, product collaborations, and conversations with people building software for real operations.