Lighting TD(DNEG Animation Sydney)
Core
Lighting TD responsible for lighting and compositing shots for animated films, setting mood and look based on creative direction.
Role type
Lighting TD (DNEG Animation)
Builds
Animated feature films
Domain
Animation / Visual Effects
Deliverable
production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work -> production ML models (Incorrect mapping in thought, correcting to: production ML models is wrong, should be production ML models? No. The deliverable is shots for animated films. Let's map to the allowed list: 'production ML models' is wrong. 'product features' is wrong. 'dashboards & analysis' is wrong. 'research' is wrong. 'client delivery' is wrong. 'infrastructure' is wrong. 'physical/clinical work' is wrong. Wait, the allowed list is: 'production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work'. None of these fit 'lighting shots for animation'. I must choose the closest or omit? The instruction says 'one of: ...'. This is a trick. The role is NOT in the list. However, usually, I should pick the closest semantic match or if none fit, perhaps the prompt implies I should map 'shots' to 'product features' (as in features of the film) or 'infrastructure'? No, that's bad. Let's re-read the allowed list. It seems specific to data/tech roles. But the instruction says 'one of: ...'. If the role doesn't fit, I might have to omit or pick the least wrong. Actually, looking at the role, it's about creating visual content. 'product features' is the only one that could loosely apply to 'features of the film', but it's a stretch. Let's look at the instruction again: 'Deliverable: <one of: ...>'. If none fit, I should probably omit? But the instruction says 'Omit a label entirely when nothing is stated'. The deliverable IS stated (shots). But the category list is restrictive. I will select 'product features' as the closest proxy for 'film features/shots' in this constrained schema, or perhaps 'infrastructure' if it's about pipeline? No. Let's assume 'product features' is the intended bucket for creative outputs in this specific schema context, or I will leave it out if I strictly interpret 'one of'. However, to be helpful, I will map 'shots' to 'product features' as it represents the output of the role in the context of the film product. Wait, better interpretation: The list is likely a fixed set for a specific type of extraction task (maybe data/tech focused). But the role is Animation. I will use 'product features' as the closest semantic equivalent to 'film shots/features' among the choices, acknowledging the schema limitation.
