Working as a full stack developer from Butwal
What it is like building software for international clients from Butwal, Nepal — timezone overlap, the local developer scene outside Kathmandu, and how remote work actually runs from Lumbini Province.
Nepal's software industry gets written about as though it were only Kathmandu. Most of it is. But the part of the job that requires being in Kathmandu has been shrinking for years, and I have spent five of them building software from Butwal, in Lumbini Province, about 250 km west of the capital.
Why this works now and did not before
Three things changed. Fibre reached the mid-west, so a video call is no longer a negotiation with the connection. Payment rails — Wise, Payoneer, the marketplaces — made getting paid from abroad ordinary rather than an ordeal. And the industry stopped treating remote work as a concession.
The result is that the constraint on working from a smaller city is no longer infrastructure. It is proximity to other developers, which is a real cost and worth naming.
The timezone maths
Nepal runs on UTC+5:45, one of the very few 45-minute offsets in the world. Practically:
- Australia: two to four hours ahead. A full overlapping working day. Most of my recent work has been for Australian clients, and this is why.
- India and Southeast Asia: near-identical hours.
- Europe: my afternoon is their morning. Comfortable for a daily sync.
- United States: no natural overlap. It works on a scheduled window and asynchronous written updates, and it works badly if a team insists on doing everything in meetings.
That last point is the honest limitation. If your team runs on live conversation, a 10-to-12-hour offset is a real cost, and no amount of goodwill removes it.
What the work has looked like
The projects have not been small-town projects. A clinic management system for Australian cannabis and telehealth practices, built on Medusa v2 with a prescription portal integrated. A thrift marketplace shipped to iOS and Android with eSewa checkout and Nepal Can Move handling delivery. A retail platform for shops in Nepal built around the paper credit ledger a small business actually runs on — a product shaped by the market it is in rather than imported from one that already has barcode scanners and card terminals.
That last one is worth dwelling on. Building from Butwal makes you take low-bandwidth and flaky-network cases seriously, because you experience them. Developers on reliable connections tend to treat those as edge cases. For a large share of the world's users they are the normal case.
On the local scene
Butwal has a growing number of developers and a handful of small agencies, and Tribhuvan University's affiliated colleges here produce a steady stream of CSIT graduates. What it does not have is the density of Kathmandu — fewer meetups, fewer people to ask, a smaller pool for hiring into a team.
I have handled that the way most people outside a capital do: online communities, open source, and staying deliberately in touch with people I have worked with. It is a workable substitute. It is not the same thing, and pretending otherwise would be dishonest.
If you are hiring from here
The questions worth asking a developer outside Kathmandu are the same ones worth asking any remote developer: can I see the code, who has verified them, what does their overlap with my team actually look like, and what happened on a project that went wrong.
My answers are on my background and in the case studies, and you can start a conversation here.