SYSTEMS THAT KEEP WORK MOVING SYSTEMS THAT KEEP WORK MOVING

DATA THAT STAYS CORRECT UNDER FAILURE DATA THAT STAYS CORRECT UNDER FAILURE

IDEMPOTENT JOBS THAT RETRY SAFELY IDEMPOTENT JOBS THAT RETRY SAFELY

QUERIES SHAPED FOR THE DATA THEY READ QUERIES SHAPED FOR THE DATA THEY READ

POINT-IN-TIME RECOVERY BEFORE INCIDENTS POINT-IN-TIME RECOVERY BEFORE INCIDENTS

DISTRIBUTED TRACING AT SERVICE BOUNDARIES DISTRIBUTED TRACING AT SERVICE BOUNDARIES

Loading

Remote contracts · outsourced backend work · Kathmandu, Nepal

Hire a backend engineer in Nepal for systems that stay correct under failure.

I am Sabudh Thapa, a backend and distributed systems engineer based in Kathmandu, Nepal. I take remote contracts with teams that need event-driven workers, PostgreSQL performance work, data infrastructure, and production recovery done properly, not just shipped.

What I take on

Backend platforms and APIs

Fastify, Express, and Python services with clear service boundaries, authentication and authorization, audit trails, and recovery paths designed before launch.

Event-driven and distributed systems

Kafka workers that survive duplicate messages, retries, replay, and ordered shutdown: idempotent producers, deduplication keys, dead-letter queues, backoff, and consumer-lag visibility.

PostgreSQL performance and data infrastructure

Query design, indexing, read-model separation, and routing analytical workloads to DuckDB over Parquet when row-store plans stop paying off. Screener queries went from 8-22 seconds to under 600ms this way.

Production recovery and observability

Point-in-time recovery, migration safety gates for destructive SQL, OpenTelemetry tracing across service boundaries, and dashboards that prove the system is healthy rather than assume it.

How engagements work

Scoped, written down, and measured.

Project contracts. A defined system or migration with a written scope, invariants, and acceptance checks. Best for a data pipeline, a worker fleet, a query path, or a recovery tool.

Part-time retainers. A fixed weekly block for a team that already has a backend and needs it to stop breaking under load, retries, or schema change.

Full-time remote contracts. Embedded in your team, your repo, your on-call, from Nepal. This is how I currently work with a US financial-data company.

Every engagement starts with a short discovery pass: read the code, list the failure modes, agree on what "done" means. You get findings before you commit to a larger scope.

Why a backend engineer in Nepal

Timezone that overlaps

Kathmandu is UTC+5:45. My afternoon covers the full European morning and the start of the US East Coast day, and I keep a flexible window for standups and incident calls.

Senior work, Nepal rates

Outsourcing to Nepal costs less than hiring in the US or Europe. The reason to hire me is the work itself: idempotent, resumable, observable systems with the failure path designed first.

Evidence, not claims

Read the accomplishments, run the backpressure playground, or read the engineering notes before you email.

Stack

TypeScript / Node.js Python Rust PostgreSQL Kafka / Avro Redis DuckDB / Parquet / S3 Docker / AWS OpenTelemetry

Frequently asked

Do you work with teams outside Nepal?

Yes. Most of my contract work is remote for companies in the United States and Europe, embedded in their repositories, review process, and on-call.

What work is a good fit?

Backend services, Kafka or queue-based workers, PostgreSQL performance, data pipelines and reconciliation, production recovery, and observability. Anything where correctness under retries and partial failure is the hard part.

What is not a good fit?

Frontend-only work, mobile apps, WordPress or site-builder projects, and fixed-price work without access to the codebase. I will say so early rather than take the contract.

How does an engagement start?

Email a short description of the system and what is going wrong. I do a discovery pass on the code, send you written findings and a scope, and work starts once the scope and rate are agreed.

Which timezone do you work in?

Nepal Time, UTC+5:45. I overlap the full European workday morning and the first hours of the US East Coast day, and I shift hours for standups and incidents.

Can you join an existing outsourced team?

Yes. I have worked as the backend engineer inside multi-vendor teams, owning service boundaries, migrations, and reliability while others owned product and frontend.

Tell me what is breaking.

A few lines about the system, the stack, and the failure you are seeing is enough to start.

[email protected]