backend engineer
Six years designing backend systems — from payment pipelines to internal platforms — with a focus on reliability, clean data models, and code the next engineer can actually read.
{
"name": "Bishan Tamang",
"role": "Backend Engineer",
"based_in": "Remote (UTC+5:45)",
"focus": ["APIs", "distributed systems", "reliability"],
"stack": ["Go", "Python", "PostgreSQL",],
"status": "available for hire",
"response_time": "< 24h"
}
about
I started out fixing slow SQL queries and ended up owning the services they belonged to. These days I work mostly on backend architecture — API design, data modeling, and the infrastructure that keeps everything running when traffic doesn't behave.
I care about boring reliability: predictable deploys, clear error messages, dashboards that tell you the truth at 3 AM. Outside of work I contribute to a couple of open-source tooling projects and write occasional notes on distributed systems.
stack
experience
projects
A distributed transaction ledger with idempotent writes and exactly-once processing for financial events.
2M events/day · p95 38msA small rate-limiting library implementing token-bucket and sliding-window strategies for Node services.
Adopted by 6 internal servicescontact
Best reached by email — I usually reply within a day.