We are a Pokhara software company with a second office in Iowa. The systems we build — ERPs, point of sale, billing, delivery — are the ones our clients open first thing every morning. That is the standard the work is held to.
People across the company
Offices — Pokhara and Burlington
Service lines you could work on
Teams are small, so you are not one of thirty people on a ticket queue. You take a module from the client conversation through to the release, and you keep it running afterwards.
ERP, e-commerce, POS, delivery, waste billing, mobile, web, consulting, security. People move between them, which is how you end up senior rather than specialised too early.
New frameworks get picked up on projects, not in your evenings. Seniors review code properly and explain the note instead of quietly changing the line.
The Iowa office means some client work runs on US hours. We plan around that rather than expecting people to be awake for it — overlap is scheduled, not assumed.
About two weeks from the CV arriving to a written answer, and you hear back at every stage in between.
Your CV and anything you have built. A repository, a live site or a college project all count. A covering note is welcome but not required.
Forty-five minutes with the person you would report to. What you have worked on, what you want next, and what the work here actually involves.
A short task close to real work, done in your own time, or a paid trial day for senior roles. Never an unpaid week.
An offer with the salary written in it, or a no with a reason. Either way you hear back — silence is not one of the outcomes.
We open roles a few times a year, and fastest for developers. Send your CV anyway — we read what arrives and come back to it when something opens that fits what you do.
One email, your CV, and a line about the kind of work you want to be doing in two years. That is the whole application.
