Technical Director, Brendle Recital Hall
Core
Oversee technical execution of theatrical events and campus venue operations, managing lighting, sound, and audiovisual elements for productions in Wait Chapel, Brendle Hall, and other campus spaces.
Role type
Technical Director (Theatrical/Event Production)
Builds
Live theatrical productions, campus events, and venue technical setups
Domain
Higher Education / Theatrical Production / Audiovisual Engineering
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' is not applicable. Correcting:
Deliverable
production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work. Wait, the instruction says 'one of: ...'. The role produces live events. None of the standard options fit perfectly except perhaps 'client delivery' if viewed as service, but 'physical/clinical work' is for hands-on. Let's look at the options again: 'production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work'. This is a tricky mapping. The role builds 'events'. 'Client delivery' is the closest fit for service-based event execution. However, 'infrastructure' fits the AV setup. Let's stick to the most accurate description of the output. The output is the event itself. 'Client delivery' is often used for service roles. Let's use 'client delivery' as it represents the delivery of the event service to the audience/client.
