Senior Director of Residence Life
Core
Lead the Office of Residence Life and Dining to create safe, supportive, and inclusive living-learning environments that foster student development, academic success, and community engagement.
Role type
Senior Director of Residence Life and Dining
Builds
Comprehensive residence life and dining programs, living-learning communities, and residential curriculum
Domain
Higher Education / Student Affairs / Campus Operations
Deliverable
production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work -> physical/clinical work (Note: This is a correction. The deliverable is actually 'product features' in the sense of program design, but the prompt options are rigid. Let's re-evaluate based on the options: 'production ML models', 'product features', 'dashboards & analysis', 'research', 'client delivery', 'infrastructure', 'physical/clinical work'. None fit perfectly. However, 'product features' is often used for software. This is a physical/operational role. The closest semantic match for 'design and implementation of a comprehensive program' among the limited list is often mapped to 'product features' in these schemas if 'program design' isn't an option, OR 'infrastructure' if referring to building the department structure. However, looking at the list again, none are ideal. Let's look at the 'Deliverable' definition in the prompt: 'one of: ...'. I must choose one. The role designs programs and manages facilities. 'Infrastructure' usually means IT/Cloud. 'Physical/clinical work' implies hands-on care. 'Product features' implies software. This is a trick. Let's look at the responsibilities: 'design and implementation of a comprehensive residence life and dining program'. This is creating a 'product' (the student experience). I will select 'product features' as the closest abstraction for 'program design' in this constrained schema, or perhaps 'infrastructure' for the departmental structure. Actually, standard interpretation for non-tech roles in these specific schemas often defaults to 'product features' for 'program design' or 'client delivery' for service. Let's stick to the most literal: they build the 'program'. I will use 'product features' as a proxy for 'program design' as it's the only 'creation' option besides research/infrastructure which don't fit well. Wait, let's re-read the options. Maybe I should check if I can omit? 'Omit a label entirely when nothing is stated'. But the prompt says 'Deliverable: <one of: ...>'. It implies a choice is mandatory if the field exists. I will choose 'product features' as the design of the living-learning environment is the 'product'.