Small team.
Short loop.
Real users.
Fourteen people building software used by candidates preparing for the exams that decide their next decade. If you want your work in someone's hands within a fortnight, this is a good place to do it.
The shape of the team
0
People
Engineering, content, support
0 days
Release cycle
Idea to a learner's hands
0
Open roles
Kathmandu and remote
0
Leave days
Plus every festival holiday
What we are hiring for
Content roles are as important here as engineering ones. A perfect app with a mediocre question bank is a mediocre product.
Nothing here fits you?
Write anyway, but be specific about what you would build or fix here. A paragraph about that is far easier to act on than a general expression of interest.
hello@lacspace.comThe parts that are actually ours
Everyone lists health cover. The first two below are the ones that genuinely differ between employers, and the ones we would defend hardest.
Real ownership
You ship it
You own a surface end to end. There is no committee between your idea and a release, and there will not be one at fifty people either.
Fourteen-day cycles
Short loop
Everything released is in a learner's hands that fortnight. You see the effect of your work while you still remember writing it.
Hybrid, genuinely
Two days in
Two days in the Kathmandu office, three wherever you work best. Content roles are frequently fully remote.
Learning budget
NPR 60,000/year
Courses, books, conferences, a certification you want. No approval process for anything under the cap.
Health cover
You and family
Medical insurance covering you, a partner and children, with no waiting period from your start date.
Proper equipment
You choose it
A machine that suits your work, plus a real test-device pool for the mobile team rather than one shared handset.
Paid leave
22 days plus festivals
Twenty-two days annual leave on top of every public and festival holiday. Taking it is expected, not merely permitted.
Work that matters
Visibly
The people using what you build are preparing for exams that decide their next decade. That is unusually motivating on a difficult Tuesday.
No committee between
an idea and a release.
Fourteen-day cycles, over-the-air releases where the platform allows it, and support conversations read by the people who build the thing. It is the main advantage of being small, and it is the thing we are least willing to trade away for process as we grow.
- You own a surface end to end, including its bugs
- Content editors and engineers sit together, not in separate functions
- Support threads are read by the team, not summarised for them
- Decisions are written down, so being remote that day costs you nothing
Four steps, and we pay for the exercise
The whole thing takes about two weeks. Nobody is left waiting in silence, and nobody works unpaid.
Apply
One email with a CV and a few lines on why this. No cover letter template, no fifteen-field form, no account to create.
A reply within three working days, either way.
A conversation
Forty-five minutes with the person you would work with. About your work and ours — not a quiz on algorithm trivia.
You learn what the job actually is.
A paid exercise
A small, real problem from our actual backlog, timeboxed to four hours. We pay for your time whether or not you get an offer.
Both sides see real work, not a whiteboard.
Decision
A decision within a week of the exercise, with feedback you can use either way. No indefinite silence.
A clear yes or no, and a reason.
Hard constraints,
which is what makes it interesting.
Offline-first sync on a patchy connection. Audio delivery on metered data. Scoring integrity against motivated users. Rendering Devanagari and Hangul correctly on a four-year-old Android handset. None of these are solved problems here, and all of them matter to somebody's exam.
- Offline-first architecture with conflict resolution that has to be right
- Server-side scoring and anti-tamper on a public leaderboard
- Multi-script rendering and typography across Nepali, Korean and Japanese
- Performance budgets set against low-end devices, not flagships
Build here for
here.
Plenty of Nepali engineers spend their careers building software for users they will never meet, in markets they will never visit. Everyone on this team can walk into a coaching centre in Kathmandu and watch somebody use what they built. That changes how you make decisions.
Three products,
one shared core.
Work on iSmartExams and you are working on infrastructure that also carries iSmartClass and iSmartKid. Engineers here move between products when it makes sense, which keeps the work varied without changing employer.
Before you apply
Still stuck?
A person answers in Nepali or English, usually within a quarter of an hour.
Contact supportOne email. Three working days for a reply.
A CV and a few lines on why this. No form to fill in, no account to create, and a real answer either way.