That is the whole culture statement. It means bugs get fixed instead of triaged, and it means everyone here has sat with a customer at month-end. If that appeals, one of these is probably yours.
You will own a module end to end — schema, service class, AJAX surface and the screen. Deep PHP and MySQL, and an opinion about why posted entries should be immutable.
Apply for this roleBuild the screens people use eight hours a day on a mid-range Android over patchy data. Tailwind, vanilla JS, real care about payload size.
Apply for this roleSit with a new client, map their chart of accounts, migrate the old data and stay until month-end closes cleanly. Accounting background essential.
Apply for this roleFirst response on the helpdesk. You will reproduce the bug, write it up properly and tell the customer the truth about the timeline.
Apply for this roleTurn eight modules into documentation someone can follow without a call. Screenshots, worked examples, no marketing voice.
Apply for this roleRun demos on the prospect's own numbers. You will need to understand a trial balance well enough to be useful in the room.
Apply for this roleNothing fits but you think we should meet? Send a note to hello@primeerp.com explaining what you would work on.
Work where you like. We fly the team together once a quarter because some conversations need a whiteboard.
You ship your module. No committee between you and the customer using it on Monday.
Courses, certifications, conference tickets. Ask, do not apply.
For you and your immediate family, from day one.