Student Success Coordinator
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We must include sections only when posting has real, specific content. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. Must not include Pay/Schedule/Benefits sections unless posting actually states them. The posting includes Salary: "$21.00 per hour, commensurate with experience, education, and qualifications." That's pay info. It says "commensurate with experience..." which is a phrase we should avoid as filler? The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". So we cannot have a Pay section if the content is just that phrase? But the posting does give a specific hourly rate: $21.00 per hour, plus "commensurate with experience, education, and qualifications." That's still some filler but includes a concrete number. The instruction says never emit a heading followed by filler/placeholder text. Does "$21.00 per hour, commensurate with experience..." count as filler? It's partially filler but includes a concrete number. Might be okay to include Pay section with that sentence. However they said "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". That suggests if the only content is that phrase, we should not create the section. But we have also a concrete number. Might be okay. Safer to include Pay section with the salary line. Schedule: Not specified. No schedule info given. So we should not create Schedule section. Benefits: The posting mentions "Benefits Eligible Eligible". It says "Benefits Eligible Eligible". That's a bit weird: "Benefits Eligible Eligible". Probably means benefits eligible. So we have some benefits info: "Benefits Eligible". That's not specific details but indicates eligibility. The instruction: never create Benefits section unless posting actually states them. It does state "Benefits Eligible". That's a statement, albeit vague. Should we include Benefits section? It says "Benefits Eligible". That's not detailed but it's a statement. Might be okay to include Benefits section with that line. However they said prefer a few substantive sections over many thin ones. Benefits Eligible is thin. Might be better to omit Benefits section because it's not substantive detail. But we need to preserve ALL substantive information. "Benefits Eligible" is substantive? It's a yes/no. Could be considered metadata. Might be okay to include in a short paragraph under a generic section? But we only have defined headings. Could we put it under a
without a heading? The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. We can include paragraphs and lists. We could include a
for Benefits Eligible without a heading? But they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So if we want to mention benefits, we should use Benefits
. But if it's thin, maybe we omit. The instruction: "Prefer a few substantive sections over many thin ones." So we could omit Benefits.
Pay: we have salary info. Could include Pay section.
We need sections: About the role (maybe from Brief Position Overview), Responsibilities (Duties and Responsibilities), Requirements (Required Qualifications), Qualifications (maybe Preferred Qualifications?), Skills (maybe from Required Qualifications includes skills). But we need to avoid duplication. Let's map:
- About the role: could use Brief Position Overview paragraph.
- Responsibilities: Duties and Responsibilities section (multiple bullet points). We'll need to convert each duty into
About the role
) with paragraph from Brief Position Overview. - Responsibilities (Responsibilities
) with- of duties.
- Requirements (
- Serves as a welcoming and trusted departmental resource for undergraduate and graduate students, helping students navigate departmental and university processes, identify appropriate resources, and resolve academic and administrative questions.
- Coordinates undergraduate and graduate student processes from entry through graduation, working closely with faculty advisors, the Department Head, College advising staff, the Graduate School, Registrar’s Office, and other university partners.
- Supports faculty advising by assigning faculty advisors, helping students and faculty navigate advising systems and processes, and coordinating approved substitutions, exceptions, and other academic actions.
- Serves as the primary departmental coordinator for graduate admissions, helping prospective students and faculty navigate the process from application and admission through funding commitments and graduate appointment/hiring.
- Tracks important student milestones, requirements, and deadlines and proactively communicates with students, faculty, and department leadership when action is needed.
- Coordinates graduate program processes including annual student evaluations, programs of study, committees, examinations and defenses, graduation requirements, and related Graduate School processes.
- Responds to student questions in person, by phone, and electronically and connects students with appropriate faculty, College, or University resources when issues require additional expertise.
- Helps create a connected student community within Plant Sciences and Plant Pathology.
- Develops and coordinates student-focused activities and events, including graduate student welcome activities, graduation celebrations, recruitment events, lectures, and other opportunities that strengthen student engagement and connection with the department.
- Collaborates with students, faculty, and department leadership to identify and develop new opportunities to improve the undergraduate and graduate student experience.
- Represents the department at selected recruitment events,
Requirements
) with- of experience/education bullet.
- Skills (
Skills
) with- of demonstrated abilities.
- Qualifications (
Qualifications
) with- of preferred qualifications.
- Pay (
Pay
) withsalary line. We must not include Benefits or Schedule. Check for any other info: "Appointment Type Classified Contract Term Fiscal Year Semester If other, specify From date If other, specify End date FLSA Non-Exempt Union Affiliation FOCUS-MFPE FTE 0.5 - 1.0 Benefits Eligible Eligible". This is metadata like appointment type, contract term, FTE, FLSA, union, FTE, benefits eligible. Should we include? The instruction: remove minor metadata into a short
or drop it. We could include a short paragraph for metadata like "Appointment Type: Classified; Contract Term: Fiscal Year Semester; FTE: 0.5–1.0; FLSA: Non-Exempt; Union Affiliation: FOCUS-MFPE; Benefits Eligible." But that's metadata. Could be included as a short
under maybe a generic section? But we have no heading for metadata. Could just include a
at the end? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include a short
for metadata. However we must not repeat job title as heading. So we can add a
containing that metadata. But we also have "Position Number 4M1875 Department Plant Sciences Division College of Agriculture/MAES". That's also metadata. Could fold into same
. We need to preserve ALL substantive information. Metadata like position number, department, division, college, appointment type, contract term, FTE, FLSA, union, benefits eligible are substantive? They are details about the position. The instruction says fold minor metadata into a short
or drop it. So we can include them in a short paragraph. Thus final HTML:
About the role
The Student Success Coordinator helps students navigate academic and administrative processes from recruitment through graduation; coordinates undergraduate and graduate program activities; supports recruitment, retention, and student engagement; and helps develop new initiatives that strengthen our academic programs and student community. The position also provides essential administrative coordination that keeps student programs running effectively. We are looking for someone who enjoys working directly with students and faculty, takes ownership of projects and follows them through to completion, communicates proactively, and can manage multiple priorities and deadlines. The successful candidate will have opportunities not only to coordinate established processes, but also to bring forward ideas and work collaboratively to improve how we recruit, support, engage, and celebrate our students. The work varies throughout the academic year and includes periods with multiple overlapping deadlines and time-sensitive student needs. At other times, the coordinator will have opportunities to develop projects and improvements that strengthen departmental programs, processes, communications, and student experiences.