Ownership of real surface area
Modules, not tickets. People here typically own a functional area end to end — data model, logic, interface and the customer conversations that shaped it.
Careers
Engineering software that runs other people’s businesses
Product engineering, implementation consulting, QA and customer support roles across our Princeton Junction, Oxford and Chennai offices — on a platform that has been in continuous development since 2007.
Engineering, implementation, QA and support roles across Princeton Junction, Oxford and Chennai — working on software that runs other people's businesses.
Working here
The bug you fix today posts to somebody’s ledger tomorrow.
ERP is unusually consequential software. When it works, a finance team closes the month without a weekend. When it does not, a warehouse ships the wrong thing and an auditor asks why. That raises the standard for everyone who touches it.
We are a small enough company that the person who writes a module also hears from the customer using it. Engineers sit close to implementation consultants, consultants sit close to support, and nobody is more than one conversation away from the reason a decision was made. If you want anonymity inside a large delivery machine, this is the wrong place.
- One product, six industry editions — deep rather than scattered
- Offices in the USA, the UK and India working the same codebase
- Infrastructure the company owns, so you can see the whole stack
- Direct contact with the people who use what you build
What the job actually gives you
Not perks. Scope.
We would rather describe the work honestly than list benefits that sound the same at every company. Specific terms of employment vary by office and role and are discussed openly during the process.
Genuinely cross-border work
Requirements arrive from three continents. Multi-currency, multi-entity and multi-jurisdiction are not edge cases here; they are Tuesday.
Structured training, then trust
New joiners work through the same role-based curricula and sandbox labs we use to train customers, so you learn the domain properly before you are put in front of one.
The whole stack is visible
Because the platform runs on a company-owned exclusive cloud facility, engineers can follow a problem from the interface to the infrastructure without hitting a vendor boundary.
Short distance to the decision
Product, delivery and support meet regularly and argue in the same room. Good arguments change the roadmap; seniority on its own does not.
Long-horizon craft
The codebase has been maintained continuously since 2007 and is expected to run for decades more, which rewards people who care about the version of the system that exists in five years.
Currently hiring
The disciplines we recruit for.
These are role categories rather than dated vacancies. Email the role and office that interest you and we will reply with what is genuinely open, what it pays and where it sits.
Implementation Consultant
Run discovery and process mapping with customers, configure the industry edition to match, and stay with the account through parallel run and go-live.
ERP Support Engineer
Own incoming issues end to end across finance, inventory and payroll modules, reproduce them against real configurations and work with engineering on the fix.
Full-Stack Developer
Build and extend modules on the shared financial core, from the data model through to the interface, on a codebase that has been in continuous development since 2007.
QA Engineer
Design and automate regression coverage across six industry configurations, and be the person who stops a posting bug from ever reaching a customer ledger.
Business Analyst
Translate how a customer actually works into a configuration the platform can support, and write the requirements engineering builds against.
Sales Consultant
Qualify honestly, demonstrate the modules that match the prospect’s problem, and scope engagements that the delivery team can stand behind.
These listings are indicative, not dated vacancies. Openings, headcount and locations change through the year, and we would rather not publish a job that has already been filled. Email contact@arthasystems.com with the role and office you are interested in and we will tell you exactly what is open right now.
The process
Four conversations, no riddles.
We do not run puzzle interviews. We look at whether you can reason about somebody else’s business, explain your thinking, and finish things.
01
Email us
Send a CV and a short note naming the role category and office. Tell us what you have actually built or delivered — specifics beat adjectives.
02
Introductory call
A conversation about your background, what you want next, and what the role really involves day to day, including the parts that are hard.
03
Working session
A practical exercise close to the real job — a piece of code, a configuration problem or a customer scenario — discussed with the people you would work alongside.
04
Offer conversation
Terms, team, start date and expectations, discussed directly. Whatever the outcome, you get a decision and a reason rather than silence.
Start the conversation
Nothing above fits, but you still want in?
Send us the work you are proudest of and tell us where you think you would be useful. Speculative applications get read by a human at all three offices.