Build things people use every day
Software that runs behind real counters, in a team small enough that you will recognise your own work in it.
9 roles are open right now
They're listed below, each with what the work actually is. If none of them fit but the company does, write to us anyway — we read speculative mail properly and we reply either way.
info@merilsoft.comWhat we're hiring for
Engineering
What you'd actually be doing
You ship to production
We run 15 products and a custom development practice. The thing you build goes behind somebody's counter and gets used during a Friday dinner rush.
Small enough to matter
A team of about 10. The person on a customer's demo is usually the person who built the thing being demoed, and that is not going to change.
Product work, not ticket work
Scope arrives as a problem rather than a specification. If you would rather be handed the specification, this is an honest warning.
Four steps, no unpaid take-homes
However long it takes, you will always know which step you are on.
Write to us
No form and no portal. An email with what you have built and what you want to build next is enough — we read all of them.
A conversation
A call about your work and ours. You will get a straight answer about the role, the pay range and the company's size rather than a pitch.
Something real
A paid exercise or a walkthrough of work you already own — your choice. No unpaid take-homes and no whiteboard algorithms.
Meet the team
You talk to the people you would actually work beside, and you get to ask them the awkward questions without anyone from hiring in the room.
What working here actually involves
We are not currently advertising specific roles, and this page does not pretend otherwise — there are no invented postings below and no structured data claiming vacancies that do not exist. What follows is an honest description of the work, for anyone deciding whether a speculative email is worth their time.
The defining fact is that we build and operate our own product. Pacific POS processes live transactions in real businesses, which means the person who writes a feature is the person who hears about it when it breaks. That closes a feedback loop most engineering jobs never close, and it makes the work more careful and considerably more satisfying than shipping into a void.
It also means the work is broad rather than deep in one layer. A small team building a POS, an EHR, a fleet system and client software does not have a dedicated specialist for each concern — people move between product work, infrastructure, and the occasional client engagement. That suits some engineers enormously and suits others badly, and it is worth knowing which you are before applying.
We are based in Melville, New York. If you write, tell us what you have built and what you would want to work on here — specifics beat a cover letter. We read everything, and we reply to say no as well as yes, because not hearing back is the worst part of applying anywhere.
Think you'd fit?
Write to info@merilsoft.com with what you've built. We answer within one business day, same as everyone else.