Circular economy
Hire Traceability Engineers
Engineers who build supply chain evidence on open standards, so a claim can be checked rather than trusted.
A traceability engineer builds tamper-evident supply chain data systems using open standards: EPCIS 2.0 event capture, W3C Verifiable Credentials and decentralised identifiers. Hire one when provenance claims must be independently verifiable rather than merely asserted. Expect $95 to $170 per hour.
What this role actually does
Most supply chain traceability is a database with a nice interface. It records what a supplier said. It does not let a downstream party verify that claim independently, and it does not survive the supplier changing systems. That is adequate for internal visibility and inadequate the moment a regulator, customer or auditor needs evidence.
Verifiable traceability changes the trust model. Supply chain events are captured in EPCIS 2.0, an open GS1 standard for recording what happened, when, where and why. Claims are issued as W3C Verifiable Credentials, cryptographically signed by the party making them, so any recipient can check the signature without contacting the issuer. Identity is anchored in decentralised identifiers rather than a single vendor's account system.
Core skills to look for
- EPCIS 2.0 capture and query interfaces, including the JSON-LD binding
- GS1 identification: GTIN, SSCC, GLN and Digital Link resolution
- W3C Verifiable Credentials: issuance, presentation and verification flows
- Decentralised identifiers and key management that survives staff turnover
- Selective disclosure so suppliers can prove a claim without exposing commercial data
- Interoperability testing against partner implementations, not just your own
- Pragmatic judgement about when a distributed ledger is genuinely needed
When you need to hire this role
- A regulation or customer requires evidence of origin rather than an assertion
- Supply chain claims must be verifiable by parties who do not trust your database
- You need to prove chain of custody across companies that use different systems
- Suppliers will not share commercial detail but must still prove compliance
- A previous blockchain traceability project delivered no verifiable outcome
How to assess candidates for this role
Ask when a ledger is unnecessary
Strong candidates say most of the time, and can explain why signed credentials plus standard APIs usually suffice. Reflexive blockchain advocacy is a warning sign.
Probe EPCIS modelling
Ask them to model a transformation event, such as several inputs becoming one output batch. This exposes real familiarity with the standard quickly.
Test selective disclosure
Ask how a supplier proves compliance without revealing its own supplier. Look for concrete cryptographic or credential-level mechanisms.
Check interoperability discipline
Ask how they validated against another organisation's implementation. Systems that were only ever tested internally usually fail on first contact.
Typical rate bands
| Level | Experience | Typical rate | What they own |
|---|---|---|---|
| Mid-level | 4-6 years | $95-125/hr | Implements event capture and credential issuance within a defined design |
| Senior | 7-10 years | $125-155/hr | Owns the traceability data model, identity and verification architecture |
| Staff / Principal | 11+ years | $155-170/hr | Designs multi-party traceability platforms and governance |
Frequently asked questions
What is EPCIS 2.0?
EPCIS 2.0 is a GS1 standard for recording supply chain events — what object, at what time, at what location, and for what business purpose. Version 2.0 added a JSON and JSON-LD binding plus a REST API, which makes it far easier to implement than earlier XML-based versions.
Do we need blockchain for traceability?
Usually not. Most requirements are met by signed Verifiable Credentials and standard APIs, which give tamper-evidence and independent verification without the operational cost of a distributed ledger. A ledger is justified when no party can be trusted to host shared state.
What are Verifiable Credentials in a supply chain context?
They are cryptographically signed claims — a certification, test result or origin statement — issued by a specific party. Any recipient can verify the signature offline, so the claim can be checked without trusting or contacting the system that stored it.
How much does a traceability engineer cost?
Typical vetted contract rates are $95 to $125 per hour at mid-level, $125 to $155 at senior and $155 to $170 for staff and principal. The premium reflects how few engineers have combined standards knowledge and shipped implementations.
How does traceability relate to the Digital Product Passport?
Traceability supplies much of the evidence a passport presents. EPCIS events establish chain of custody, and Verifiable Credentials let a passport carry claims that a recycler or authority can check independently rather than take on trust.