Intrepid · Cheat Sheet

Their five accountabilities, in their order

Learn the benchmark word for each. If you can name all five unprompted, you are already ahead of the room.

Video Asset Management & Governance

Audit the library · folder structure and asset hierarchy · metadata, taxonomy and tagging specs · governance for future uploads. Benchmark: governance documentation adopted by team

You say: audit before design. Hierarchy carries ingest and permissions, metadata carries discovery.

Business Requirements & Stakeholder Partnership

Translate business requirements · partner with post and creative · communicate progress and options. Benchmark: positive stakeholder feedback

You say: watch people search, do not survey them. The gap between the documented process and the real behaviour is the requirement.

Video Workflow Optimisation

Editing and proxy workflows · standardise production handover · editing team and stakeholder collaboration. Benchmark: reduced manual touchpoints, reduced rework

You say: review proxies and edit proxies are different jobs. Edit proxies must relink by clip name and timecode.

Improvement and Innovation

Review software and subscriptions · identify duplication · recommend consolidation · automation and AI tagging. Benchmark: cost saving opportunities identified

You say: the biggest saving is not a licence line, it is not re-shooting content that already exists.

Documentation and Backup

SOPs · Quick Start Guides · workflow charts · backup and retention standards · FAQ and knowledge base. Benchmark: increased self-service, fewer repeat requests

You say: baseline the repeat questions first, so the reduction can be shown rather than asserted.

Your numbers, cold

Say these without hesitating. Hesitation on your own figures is what makes a number sound invented.

500,000+ / 80,000+

Administered 500k. Hand-tagged 80k. Never merge them

34 fields

Classification-first schema, controlled dropdowns behind each

5–30s → 3–7s

Per asset, manual then AI. Roughly 3× throughput

90–95%

Per-field confidence before a tag wrote unattended

70–90%

AI field accuracy. Manual was near 100%

11 teams

Production to boardroom. 5–15 requests a week

18 months

Refining conventions with Cameron Marshad

1 year / 4 months

Manual tagging, then the AI workflow. 3 days a week

Five things to land

iconik development at Quad Lock was mine. The tagger, the review console, the governance gate, Iconik Bot. Reporting to Cameron Marshad. A function of one
I did the manual half first, and that is what taught me the schema. The order is the proof
Your roadmap is predefined, and I would deliver it rather than replace it. Then ask to be walked through it
Only automate what you can measure. Confidently wrong tags are worse than no tags
Designed for handover from week one. A named owner, a written standard, a review date

Four questions to ask

“Could you walk me through the roadmap as it stands, and which part worries you most?”Ask early. Their answer tells you what the job really is

“When someone needs a clip today, what do they actually do?”For Rebecca. Real behaviour, not documented process

“After a campaign the size of Only Intrepid, where did the library feel the strain first?”For David. Straight to why the role exists

“What surprised you about working here?”Near the end. Their own pack invites it

Their values, pick one and evidence it

Reciting all four is the answer everyone gives. Real is the one you can actually prove.

Real

Authenticity, not perfection. Staying genuine when things get hard

Impactful

What kind of positive impact will this create

Ambitious

Try new things, go first, take risks, learn hard lessons

Together

Collective success over individual achievement

SOPs, if they push on it

Five document types, five different readers. Most documentation fails because one file tries to be all of them.

—

Policy

What must be true, and who decides. “No talent footage publishes without a signed release on file.”

—

SOP

The authoritative version of a recurring process. Owner, trigger, roles, numbered steps, exceptions, definition of done, version and review date. Written for consistency and audit

—

Quick Start Guide

The short task version of the same process, written for the person doing it on a Tuesday. One page, one job

—

Runbook

For when something breaks. Diagnostic and conditional: if X, check Y. You wrote these at Quad Lock, alongside the SOPs in Linear

—

Workflow chart

The picture of the SOP. Shows handoffs and decision points, which is where processes actually fail

The SOPs this role would need, roughly in order

1. Ingest and naming, from shoot or country office into iconik · 2. Metadata tagging and QC · 3. Proxy generation and relink · 4. Production handover, brief to delivery · 5. Review, versioning and approval · 6. Rights and release capture, including expiry · 7. Archive, retention and deletion · 8. Access, onboarding and offboarding · 9. Taxonomy change requests

Ingest first, because everything downstream inherits its mistakes.

The line to use

“I test a procedure by giving it to someone who does not know the process and watching them follow it. If they have to ask a question, the SOP is wrong, not the person.”

What you can actually claim

The SOPs lived in Linear, so every version was tracked: what was added, what was removed, what was improved and why. Plus runbooks and screen-recorded walkthroughs a non-developer could maintain.

Say both halves. You left before finishing the full set, and the system for maintaining them was already in place, which is the harder part. A library of SOPs with no version history and no owner is worth less than a smaller one that stays true.

Six traps

Do not claim any relationship with Backlight or iconik the vendor. You built to the same pattern independently, a year before AI Discovery was announced. That is the line

Do not say you hand-tagged 500,000. You administered 500,000 and hand-tagged 80,000

Do not diagnose Rebecca’s library. She built it. Curiosity about why it is that way, never a verdict

Do not pitch yourself as an editor. The PD says the role is process, workflow and database, not hands-on post-production execution. Your shooting is credibility, not the job

Do not raise years of experience. The PD has no years requirement. Only the Seek ad did

Do not recite all four values, and do not arrive with your own roadmap

If you blank

The one sentence that works anywhere

“I built exactly this once already, at half a million assets, and the part I would bring is that I did the manual half first, so I know which decisions actually matter.”

Logistics

9:55am. 567 Collins, lifts on the right, Level 7, turn left, ask for Andrew or Charlotte. Smart casual. At least two interviews, so today is not the decision.