Industrial software starts with the engineering and operational domain.
Zemerc develops the applications that govern industrial records and provides the engineering and technical services around those records. Both require people who understand the discipline as well as the system.
- 0Disciplines
- 0Applications
- 0Operating areas
- 0Industries served
The portfolio at a glance.
Current portfolio counts, not projected capability.
- 0ApplicationsEach independently operable
- 0Operating areasProjects through to governance
- 0DisciplinesMost roles touch more than one
- 0IndustriesEnergy, offshore, process, EPC
9 disciplines, with many roles spanning more than one.
Each role is grounded in the operational discipline behind the record, not only in the software that holds it.
- Software engineeringApplication engineering covers governed records, approval routes, immutable audit history and the controls required to keep those records reliable under operational pressure.
- Industrial digitalisationTaking a record a team already keeps, on paper, in a spreadsheet or in somebody’s head, and establishing it in a system that enforces the rules the team already works to.
- Process and technical safetyHazard analysis, barriers and safety-critical elements, operating envelopes, management of change and the safety case.
- Asset integrity and reliabilityInspection, corrosion, risk-based inspection, fitness-for-service, defects and reliability, held as registers an auditor can read back years later.
- Commissioning and completionsSystemisation, inspection and test records, punch clearance, the certificate sequence and handover, where the evidence has to survive the move from construction to operations.
- Risk and assuranceEnterprise risk, control effectiveness kept separate in design and in operation, audit, and the governance that makes a reported position defensible.
- Data and AIGoverned data, provenance, retrieval and assistive capability built so that it supports an accountable engineer rather than quietly replacing their judgement.
- Professional engineering servicesEngineering and technical work carried out around the applications, by people who understand both the discipline and the system holding its record.
- Implementation and customer successConfiguration, migration, deployment and the first live period, working with the record owner and the person who signs it, not around them.
Explore the disciplines.
Select a discipline to see the work it covers and the operating area it supports.
Application engineering covers governed records, approval routes, immutable audit history and the controls required to keep those records reliable under operational pressure.
Twenty-seven independently operable applications, each developed and released as a standalone product.
- Scale
- 27 applications
- Each one
- independent product and release lifecycle
Built with operationsApplications are shaped with the teams who keep the record. 
On the assetCondition and competence assessed where the work actually happens.
Three principles that shape how the work is delivered.
The domain is the job
These applications are not generic software with an industrial label. Work here involves understanding what a barrier is, why an approved record is superseded rather than edited, and why some figures should not exist.
Built with the people who run the work
Every application starts from the records, controls and working practices already used by the responsible teams, then proves those rules against real operational work before wider release.
Honesty is a technical requirement
Where no approved method exists for a figure, the application declines it and says why. The same standard applies to what is written, claimed and committed to.
If your discipline is relevant, you can still contact us when no vacancy is listed.
There is no automated recruitment pipeline behind this page. A general career enquiry is reviewed by a person and answered against current or expected requirements.