Careers Engineering
Senior Full-Stack Engineer
Own a product surface end to end — schema, API, interface and the deploy — inside a client’s own repository and to their standards.
Full-time Hybrid Pokhara, Nepal
Posted 18 Aug 2026
The job
Most of our work is not greenfield. You join a system that already has users, already has a schema somebody chose two years ago, and already has opinions encoded in it that nobody wrote down. The job is to make that system better without stopping it, and to leave behind a repository the client’s own engineers can work in after we are gone.
You would own a surface rather than a ticket queue: the data model, the API in front of it, the interface on top, and the pipeline that ships it. The person who scopes the work is the person who builds it — that is the whole arrangement, and it only works if the people doing it can hold the full picture.
What you would be doing
- Design the schema and the API before writing the interface, and be able to defend both when the requirements move.
- Work directly in the client’s repository, under their review process and their CI — not in a copy we hand over at the end.
- Write the migration and the rollback together. A change that cannot be undone is not finished.
- Review other people’s work properly, including the parts you did not want to read.
- Write the weekly update that goes to the client, in prose, describing what actually happened.
What we need from you
Four or five things, not fifteen. A long list filters out the people who read it honestly and keeps the ones who do not.
- You have taken at least one non-trivial system from a schema to production and then lived with it afterwards.
- You are fluent in TypeScript on both sides of the wire, and comfortable in a relational database without an ORM in front of you.
- You can read a codebase you did not write and change it without breaking things you did not know were there.
- You write. Not documentation as a chore — commit messages, review comments and design notes that a colleague can act on.
What would help, and is not required
- You have worked under someone else’s standards — an enterprise client, an agency, or an open-source project with a strict review culture.
- You have run a migration on live data and know what you would do differently.
- You have published something and maintained it after the launch.
What you would work with
- TypeScript
- Next.js
- Node.js
- PostgreSQL
- Prisma
- Docker
- GitHub Actions
It takes about ten minutes and goes to a person, not to an applicant tracking system. You will hear back either way.
Also open
Other roles
Engineering
Engineering Internship
Six months on real work with a named mentor, real review, and your name on commits that ship.
Internship On-site Pokhara, Nepal
Engineering
Mobile Engineer (Flutter)
Ship apps to two stores from one codebase, including the offline case that nobody specifies until it fails.
Full-time Hybrid Pokhara, Nepal
AI & Agents
AI Engineer, Agents & Retrieval
Build agent loops that can be audited and retrieval that holds up on somebody else’s documents, not on the demo set.
Full-time Hybrid Pokhara, Nepal