Lead Compositor - ILM London
Core
Provide creative and technical guidance for assigned shots, ensuring uniformity in finished work and maintaining overall quality (look, color balance) for shots and sequences.
Role type
Lead Compositor (VFX)
Builds
Visual effects shots and sequences for film productions
Domain
Film & Entertainment / 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 actual deliverable: production ML models is wrong, it should be production ML models? No. The deliverable for a compositor is shots/sequences. The schema options are: production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work. None fit perfectly. 'product features' is closest for creative assets, but 'client delivery' or 'infrastructure' are also off. Let's look at the options again. Actually, for VFX compositors, the output is shots. The schema options are limited. I will map 'shots and sequences' to the closest available or leave blank if none fit well? The instruction says 'one of: ...'. I must choose one. 'product features' is often used for creative assets in some taxonomies, but 'client delivery' implies service. Let's re-read the schema options. None are perfect. However, 'product features' is the standard fallback for creative content in this specific schema when 'shots' isn't an option. Wait, looking at the schema again: 'production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work'. A compositor creates shots. This is a mismatch. I will select 'product features' as the closest proxy for creative assets, or perhaps 'client delivery' if viewed as a service. Let's stick to the most logical: 'product features' (creative output).
