Use recruitment evidence to distinguish editorial capacity from operational ownership. A content team can be capable of maintaining reviews without being responsible for integration security, supplier permissions or launch testing.
The following is a proposed operating model for publishers, not a description of how every observed employer works.
| Workstream | Suggested accountable owner | Evidence or deliverable to require |
|---|---|---|
| Demo slot licensing and embedding rights | Founder or commercial lead, with counsel reviewing unresolved issues | Permission register covering domains, territories, embedding method, asset reuse, duration and termination |
| Catalogue freshness and metadata | Catalogue/content operations lead, supported by a data specialist | Stable game identifiers, provenance, release dates, version distinctions, update history and exceptions |
| API or iframe integration | Engineering lead | Documented launch flow, server-side credential handling where required, synchronisation jobs, logging and rollback plan |
| Mobile embeds and launch reliability | Product owner, with QA execution | Reproducible device/browser tests, launch outcomes, failure evidence and fallback behaviour |
| Playable reviews and editorial accuracy | Content lead | Evidence that the described game and the embedded version correspond; documented handling of uncertain metadata |
| Renewal and supplier continuity | Product or commercial owner | Supplier dependency map, notice requirements, replacement options and an exit plan |
What should a catalogue or release-operations person actually own?
EveryMatrix’s release role provides a concrete example of coordination across vendor roadmaps, calendars, assets and product updates. The transferable lesson is that obtaining a game record is only one part of maintaining a useful catalogue. (everymatrix.teamtailor.com)
For a publisher, the recommended adaptation is a single release queue in which each proposed title has:
- A named editorial purpose.
- A source and stable identifier.
- A recorded permission status.
- A territorial availability statement, with unknowns preserved.
- A launch-test result or an explicit “not tested” label.
- A person responsible for resolving missing evidence.
This is a suggested workflow, not a claim that the advertised EveryMatrix role includes publisher-specific rights checks.
What should an integration or QA person be able to demonstrate?
EveryMatrix’s integration advert covers the delivery lifecycle, while its QA advert distinguishes test design, automation, exploratory testing and release visibility. Those are different responsibilities, even when a small publisher assigns them to one person. (everymatrix.teamtailor.com)
For a demo slot integration performance audit, use an evidence-based acceptance exercise rather than a tool-name checklist:
- Reproduce one successful launch and one failure under declared conditions.
- Separate loading the publisher page from confirming that the game is usable.
- Record the browser, device, location, consent state and timestamp.
- Explain what the test cannot observe or establish.
- Produce a ticket another developer can reproduce.
- Demonstrate the fallback when a title is unavailable.
These are recommended assessment criteria. They do not imply that any reviewed employer uses this exact exercise.
What does a data-engineering hire mean for catalogue procurement?
Gentoo’s advert explicitly includes external-source integration, data quality, monitoring and documentation. The inference is capability investment, not confirmed expenditure on catalogue APIs. (careers.gentoomedia.com)
Before purchasing a metadata service, ask the proposed owner to define matching rules, provenance requirements, update frequency and how uncertain records will be handled. For a usable catalogue comparison, unknown permission and untested availability should remain separate from missing metadata.