Skip to content
Alpas — we help, you grow

Careers

You could be next

We are a small studio in Lalitpur building custom software, mobile apps and business platforms for companies in Nepal, Australia and New Zealand — and the civic systems Nepal’s cities run on. If you want your work in front of real users rather than parked in a demo environment, this is a good place to do it.

careers @ alpastechnology.com
$whoami
alpas — software design and development, Lalitpur, since 2018
$ls ./team
15 people · engineering · design · delivery · QA
$cat ./what-we-ship
17 shipped projects — business platforms and civic systems, Nepal and abroad
$./join --apply
Reading applications. Send us the work, not just the CV.

Open roles

open_roles = []

No roles posted right now

We would rather list nothing than list a job we are not really hiring for. But this is a small studio and that changes quickly — we read every open application, and good ones have created roles before.

Send an open application

How this place works

alpas.config
team_size
15 people, Kupondol, Lalitpur
shipping_since
2018
work_split
Business software and civic systems, side by side, at home and abroad
discovery
Every build opens with service blueprinting, not a sprint
handover
Documented architecture and trained staff are deliverables
who_uses_it
Businesses in Nepal, Australia and New Zealand — and citizens across Nepal on Nagarik Alert and LMC Alert
languages
Nepali and English, treated as two design problems rather than a translation pass
ownership
You own a surface end to end, not a ticket queue

What you would work with

Product

  • Service blueprinting
  • Journey mapping
  • Prototyping
  • Design systems

Web

  • React
  • TypeScript
  • Node
  • Python
  • REST & API-first

Mobile

  • Android
  • iOS
  • Cross-platform

Data & AI

  • Classification & triage
  • Workflow automation
  • Analytics

Platform

  • Cloud infrastructure
  • Observability
  • DevSecOps

How we hire

Four stages, and you hear back at every one of them.

  1. 01

    You send something real

    A CV is fine, but what we read first is the work — a repo, a case study, a Figma file, an app on a store, a thing you fixed that nobody asked you to fix.

  2. 02

    A conversation, not a quiz

    Forty-five minutes on what you have built and how you decide. No whiteboard algorithms, no trick questions about the language spec.

  3. 03

    A small piece of the real thing

    A short, scoped exercise close to work we actually do, with a deadline you agree to. We give written feedback either way, and we never ship unpaid exercise work.

  4. 04

    Meet the people you would sit with

    You talk to the team you would join and ask them anything. Then a decision, with a reason, in writing.

What you get out of it

  • Work that ships to real users, not to a demo environment
  • A say in how the thing gets built, from the discovery phase onward
  • Small team, so your name is on what you make
  • Time with the people who use it — clients here and overseas, and the cities we build with

Send us the work

A repo, a case study, an app on a store, a design file — whatever you would want us to judge you on. Tell us what you did and what you would do differently now.