Skip to content

Careers

Work that gets read

Every change here is reviewed by somebody who will say so if it is wrong, and the standards are enforced by the build rather than by whoever is most senior in the room. That is the whole offer, and it is the reason people who join tend to get better quickly.

Open roles

6 roles · press / to search

  1. 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

  2. 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

  3. 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

  4. 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

  5. Cloud & DevOps

    Platform Engineer

    Own pipelines, infrastructure as code and deploys that roll back — across client accounts we do not own.

    Full-time Remote Anywhere in Nepal

  6. Design

    Product Designer

    Design interfaces for systems with real constraints, and hand over something an engineer can build without guessing.

    Contract Remote Within 4 hours of UTC+5:45

How we hire

Four steps, and you hear back at every one

Written with who you meet and roughly how long it takes, because those are the two things a candidate is actually deciding on and almost no posting says either.

  1. 01

    You send something real

    A CV if you have one, but what we actually read is the work — a repository, a pull request, an app, a piece of writing. Tell us which part of it you want us to look at and why.

    Who
    Nobody from us yet
    How long
    20 minutes of your time

  2. 02

    A first conversation

    A call with an engineer, not a recruiter. We talk about what you have built and what you want to be doing in a year. You should leave it knowing what the job is and what it pays.

    Who
    The team you would join
    How long
    45 minutes

  3. 03

    A working session on real code

    We open a repository together and work on something in it — reading, changing, arguing about a design. No whiteboard algorithms and no take-home you do alone at the weekend. If you would rather submit a written exercise instead, ask, and we will scope one.

    Who
    Engineers from that team
    How long
    90 minutes

  4. 04

    A decision, with reasons

    An offer with the number in it, or a no with something useful attached. Either way you hear back — a silent rejection is a small cruelty that costs the sender nothing.

    Who
    Engineering leadership
    How long
    Within a week of the last conversation

Open application

Nothing here fits you

Then write to us anyway. The list above is only ever the work we have already scoped, and a role here gets written around a person at least as often as the other way round. Arriving at the wrong moment is not a reason for us to say no.

Write to info@teispace.com

Put these four things in it

  1. The work you want us to look at, and which part of it — a repository, a pull request, an app in a store, something you wrote.
  2. What you want to be doing in a year. It is the question the first call opens with anyway.
  3. Where you are and how you want to work — on-site in Pokhara, hybrid, or remote from elsewhere in Nepal.
  4. Your CV if you have one. It is the least interesting attachment and we read it last.