Pipeline Developer — Editorial & Post-Production ( Contract)

About the Role

We are seeking two experienced Editorial Pipeline Developers to join our post-production team on a focused, time-critical engagement. These roles are immediately available. You will be working at the heart of a complex, live feature film production pipeline to solve real problems affecting editorial, VFX, and delivery workflows across multiple departments.

We are seeking two experienced Editorial Pipeline Developers to join our post-production team on a focused, time-critical engagement. These roles are immediately available. You will be working at the heart of a complex, live feature film production pipeline to solve real problems affecting editorial, VFX, and delivery workflows across multiple departments.

We are seeking two experienced Editorial Pipeline Developers to join our post-production team on a focused, time-critical engagement. These roles are immediately available. You will be working at the heart of a complex, live feature film production pipeline to solve real problems affecting editorial, VFX, and delivery workflows across multiple departments.

This is a focused engagement across three phases:

This is a focused engagement across three phases:

Phase 1 — Immediate rollout of existing tooling to resolve active pipeline bottlenecks.

Phase 1 — Immediate rollout of existing tooling to resolve active pipeline bottlenecks.

Phase 1 — Immediate rollout of existing tooling to resolve active pipeline bottlenecks.

Phase 2 — Improvements, integrations, and automation across downstream departments.

Phase 2 — Improvements, integrations, and automation across downstream departments.

Phase 2 — Improvements, integrations, and automation across downstream departments.

Phase 3 — Structured handover to the internal Dneg pipeline team for long-term support

Phase 3 — Structured handover to the internal Dneg pipeline team for long-term support

Phase 3 — Structured handover to the internal Dneg pipeline team for long-term support

The Problem You Will Solve

The Problem You Will Solve

The creative editorial cut is live and multiple editorial systems are currently operating in series.

The creative editorial cut is live and multiple editorial systems are currently operating in series.

Key objectives include:

Key objectives include:

Method to reconcile clip names, timecodes, and associated technical assets (HDRI, chrome ball, lens grid, Unreal post-viz scene, camera solve) to the correct take

Method to reconcile clip names, timecodes, and associated technical assets (HDRI, chrome ball, lens grid, Unreal post-viz scene, camera solve) to the correct take

Method to reconcile clip names, timecodes, and associated technical assets (HDRI, chrome ball, lens grid, Unreal post-viz scene, camera solve) to the correct take

Method to diff and produce change order reports

Method to diff and produce change order reports

Method to diff and produce change order reports

Inability to automatically reconcile cut versions or auto-conform to new editorial passes

Inability to automatically reconcile cut versions or auto-conform to new editorial passes

Inability to automatically reconcile cut versions or auto-conform to new editorial passes

Editorial tools to connect and export / import cut change propagation across: Adobe Premiere (Lipsync), DaVinci Resolve, FMP, ShotGrid, Google Sheets, Foundry Hiero, and Baselight.

Editorial tools to connect and export / import cut change propagation across: Adobe Premiere (Lipsync), DaVinci Resolve, FMP, ShotGrid, Google Sheets, Foundry Hiero, and Baselight.

Editorial tools to connect and export / import cut change propagation across: Adobe Premiere (Lipsync), DaVinci Resolve, FMP, ShotGrid, Google Sheets, Foundry Hiero, and Baselight.

The immediate strategic response is to point all editorial tools at ShotGrid as the central hub, enabling instant broadcast of cut changes and elimination of manual steps. A proven diffing toolset already exists (built prior to the current engagement) and will be forked and extended — the incoming developer will take primary ownership of its integration and development.

The immediate strategic response is to point all editorial tools at ShotGrid as the central hub, enabling instant broadcast of cut changes and elimination of manual steps. A proven diffing toolset already exists (built prior to the current engagement) and will be forked and extended — the incoming developer will take primary ownership of its integration and development.

The immediate strategic response is to point all editorial tools at ShotGrid as the central hub, enabling instant broadcast of cut changes and elimination of manual steps. A proven diffing toolset already exists (built prior to the current engagement) and will be forked and extended — the incoming developer will take primary ownership of its integration and development.

Key Responsibilities

Key Responsibilities

Phase 1: Immediate Deployment

Phase 1: Immediate Deployment

Take ownership of the existing editorial diff toolset and deploy it as-is across the production pipeline

Take ownership of the existing editorial diff toolset and deploy it as-is across the production pipeline

Take ownership of the existing editorial diff toolset and deploy it as-is across the production pipeline

Integrate all editorial tools with ShotGrid as the central source of truth

Integrate all editorial tools with ShotGrid as the central source of truth

Integrate all editorial tools with ShotGrid as the central source of truth

Establish automated cut change propagation to eliminate manual upload delays

Establish automated cut change propagation to eliminate manual upload delays

Establish automated cut change propagation to eliminate manual upload delays

Work with the originating developer during a structured knowledge transfer period