Assistant Director of Admissions
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we can only use those headings if content exists. The instructions: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should map content to these headings. Likely we need sections: About the role (position summary), Responsibilities, Requirements (minimum qualifications), Qualifications (preferred qualifications?), Skills (maybe proficiency), Benefits (maybe not explicit), Pay (salary range), Schedule (work location/hybrid). We must not create sections with filler like "commensurate with experience" etc. Pay section only if posting actually states salary range - yes it does: "Anticipated Hiring Range: $58,000 – $65,000, commensurate with education and experience." That's specific enough; we can include Pay section with that range. Schedule: posting mentions "full-time in-person position", "may require some weekend and evening work", "eligible for a hybrid work schedule". That's specific enough for Schedule section. Benefits: posting mentions "This is an exempt-level, benefited position. Learn more about UVA benefits." Not specific benefits listed; but we could include Benefits section with generic statement? The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. For Benefits, the posting says "benefited position" but doesn't list specifics. That might be considered filler? It's not a specific benefit; it's just stating it's benefited. Might be considered too vague. Safer to omit Benefits section. However we could include a short p: "This is an exempt-level, benefited position." That's not filler? It's a statement. Might be okay. But the instruction: "never emit a heading followed by filler/placeholder text (e.g., 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "benefited position" is not exactly filler. I'd include Benefits section with that sentence.
Now we need to preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, scam warning, application instructions, etc. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should exclude sections like "How To Apply", "Application Timeline", "Additional Requirements", "Reference Check Process", "Contact", "About UVA And The Community", etc. Those are likely considered boilerplate or application instructions. However some content like "About UVA And The Community" might be considered not boilerplate but still maybe we should exclude as it's not core to role? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About UVA And The Community" is not exactly those, but could be considered extra info not required. However we must preserve ALL substantive information; does that include that? It's about the community, maybe substantive but not required for job? The instruction says to remove application instructions. That section is not instructions but informational. However the list of headings we can use is limited; we might not have a heading for that. Could we include it under About the role? Possibly combine. But better to follow the instruction: only include sections when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The "About UVA And The Community" is specific content; we could include it under About the role? But About the role heading is for role description; we could add a paragraph about UVA community there. However the instruction says "About the role" is a section heading we can use. So we could put the position summary plus maybe UVA community info under About the role. That seems okay.
We must not repeat the job title as a heading. So no heading for "Assistant Director of Admissions and Enrollment Management". Good.
We need to output only HTML fragment, no /, no markdown fences.
We'll structure:
About the role
About the role
Position summary paragraph(s).
Responsibilities
- ...
Requirements
Minimum qualifications: Bachelor's degree; at least three years of experience in admissions or related field or a total of eight years of experience in lieu of degree.
Qualifications
Preferred qualifications: Proficiency with admission systems (Slate, Salesforce), university SIS (PeopleSoft), survey tools (Qualtrics); proficiency in Excel and MS Office 365; demonstrated experience managing multiple projects, meeting deadlines; experience developing reports, analyzing data to identify trends; ability to take initiative, execute high-quality work, attention to detail, follow through; thrive in fast-paced team-oriented innovative environments; strong aptitude to learn and communicate Data Science curriculum and educational trends.
Maybe also include Skills? But we already covered skills in Qualifications. Could also have Skills section for proficiency with Slate etc. But we can keep Qualifications.Pay
Anticipated hiring range: $58,000 – $65,000, commensurate with education and experience.
Schedule
Full-time in-person position at the School of Data Science, University of Virginia, Charlottesville, VA; may require weekend and evening work; eligible for hybrid work schedule after training and supervisor approval.
Optionally Benefits:Benefits
This is an exempt-level, benefited position.
We must ensure we don't include filler like "commensurate with experience" in Pay? That's part of the salary range statement; it's okay. We must not include duplicated lines. Ensure we capture all substantive info from posting: Let's extract. Position Summary paragraph: "The University of Virginia’s School of Data Science (SDS) seeks a passionate, motivated, and team-oriented professional to join its admission team as an Assistant Director of Admissions and Enrollment Management. The Assistant Director will advance the School’s undergraduate and graduate enrollment goals, focusing on recruitment, conversion, yield, and enrollment planning. In collaboration with the Director of Admissions and Recruiting and School leadership, this role analyzes enrollment data and trends, develops reports and forecasting tools, and recommends strategies to improve enrollment outcomes. The position manages key admissions operations, including application review processes, decision releases, communications, applicant portal content, and fellowship administration, while continually improving the applicant and reviewer experience. The Assistant Director also advises prospective and admitted students, supports recruitment and yield activities, and helps ensure a seamless transition from admission to enrollment and academic operations." That's the summary. Responsibilities bullet list: from posting: - Collect, evaluate, and interpret recruitment and enrollment data to provide strategic insights, process and operational improvements based on enrollment management trends. - Design and develop enrollment reports and queries within Slate to support recruitment, funnel management and enrollment forecasting. - Coordinate decision release processes and transition from Admissions to the Academic Operations Team. - Manage the awarding, tracking, and reporting of graduate fellowships - Represent the School at virtual and in-person recruitment and yield events, deliver presentations, and advise prospective and admitted students throughout the admissions and enrollment process. - Supervise Graduate Student Admissions Ambassadors and Interns We should keep exactly as given. Minimum Qualifications: Education: Bachelor's degree. Experience: At least three years of experience in admissions or related field or a total of eight years of experience in lieu of degree. Preferred Qualifications: list: - Proficiency with admission systems or customer success platforms (e.g., Slate, Salesforce), university student information systems (e.g., PeopleSoft, SIS), and/or survey tools (e.g., Qualtrics) - Proficiency in Excel and MS Office 365 suit (typo: suit -> suite) - Demonstrated experience with managing multiple ongoing projects and meeting competing deadlines with accuracy - Demonstrated experience with developing reports, analyzing and interpreting data to identify trends. - The successful candidate will demonstrate the ability to take initiative, execute high-quality work using sound judgment and discretion. They will have a proven track record of exceptional attention to detail and the ability to follow through on commitments. - The candidate will thrive in fast-paced, team-oriented, and innovative environments. - They will have a strong aptitude to learn and communicate Data Science curriculum and educational trends. We can combine into paragraph(s) or list. Use- for any list of duties/requirements/benefits. So for Preferred Qualifications we should use a list.
Similarly for Minimum Qualifications maybe list.
Physical Demands: "This is primarily a sedentary job involving extensive use of desktop computers. The job requires occasional travel for recruiting activities and or/to attend meetings and programs." This could go under Schedule? Or maybe a separate section but we don't have a heading for Physical Demands. Could incorporate into Schedule or a note. Since we only have limited headings, we could add a
under Schedule about physical demands? But Schedule heading is for schedule info; physical demands is separate. However we could add a
after Schedule? But we must only use headings from list; we could add a
without heading? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use
for section headings (e.g...). Likely they expect only those headings. So we should map physical demands to Schedule? Not ideal but maybe we can include a short sentence in Schedule about occasional travel. Or we could add a
without heading? Probably better to incorporate into Schedule: mention occasional travel. Also "Position Type & Work Location" includes: exempt-level, benefited position; restricted position dependent on funding; full-time in-person; may require weekend/evening work; eligible for hybrid schedule. We covered some. We should not include "Learn more about UVA benefits." That's a link; we can drop. We should not include "Application Timeline", "Additional Requirements", "How To Apply", "Reference Check Process", "Contact", "About UVA And The Community", EEO, etc. Now produce HTML. Let's craft:
About the role
The University of Virginia’s School of Data Science (SDS) seeks a passionate, motivated, and team-oriented professional to join its admission team as an Assistant Director of Admissions and Enrollment Management. The Assistant Director will advance the School’s undergraduate and graduate enrollment goals, focusing on recruitment, conversion, yield, and enrollment planning. In collaboration with the Director of Admissions and Recruiting and School leadership, this role analyzes enrollment data and trends, develops reports and forecasting tools, and recommends strategies to improve enrollment outcomes. The position manages key admissions operations, including application review processes, decision releases, communications, applicant portal content, and fellowship administration, while continually improving the applicant and reviewer experience. The Assistant Director also advises prospective and admitted students, supports recruitment and yield activities, and helps ensure a seamless transition from admission to enrollment and academic operations.
Responsibilities
- Collect, evaluate, and interpret recruitment and enrollment data to provide strategic insights, process and operational improvements based on enrollment management trends.