Success Advisor
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We need to parse the posting.
Key info:
- Position Title: Academic Advisor II (Working Title Success Advisor). Not to repeat as heading.
- Overview: "Access and Success is focused on promoting Montana State University’s commitment to making education accessible to all students and bringing students into supportive environments that set them up for success. We aim to break down barriers to access, promote personal and academic success, and cultivate leadership potential. Our commitment is to ensure that every individual from any background has the resources, opportunities, and support needed to thrive and contribute meaningfully to a diverse and dynamic campus community. As part of a multi-faceted and results oriented team, a Success Advisor is responsible for conducting intervention/advising meetings with students. Advisors are responsible for connecting with students identified as benefiting from additional support or those who seek out services for time management, test taking skills and learning strategies."
That's prose.
- Duties and Responsibilities: includes bullet-like sentences. We can make a - list.
List items:
- Conduct one-on-one and group appointments with students, reviewing appropriate learning strategies for students referred to them via referrals through the Navigate/Early Alert program, Residence Life, MSU 101, CARE team, as well as self-referral by students who know they need help with pursuing their degree.
- Assist students with decoding important information, navigating university resources, developing ideas and tactics (such as time-management, learning strategies, and goal-setting) to help students receive the full benefit of their education.
- Provide student-facing assistance and education on learning management via workshops, strategy clinics, hosting classroom lectures, assisting with the US 103 Learning Strategies course, and group appointments.
- Connect students with learning management instruction and support to enhance retention and degree completion in a variety of settings.
- Possibly also: "Reporting to the Senior Access Officer, this position is housed within the Division of Student Success, as part of the dynamic Access and Success team committed to advancing equitable student outcomes and enhancing student persistence and graduation." That's more overview.
But we can include that in About the role.
- Required Qualifications – Experience, Education, Knowledge & Skills: list.
List items:
- Bachelor’s degree in relevant field, or a combination of education and/or experience from which comparable skills are acquired.
- Experience in student advising at the post-secondary level or experience with career/professional coaching.
- Demonstrated experience in program delivery and with a high degree of professionalism.
- Demonstrated technical competence using personal computers and various software such as word processing, spreadsheets, presentation software & relational databases with a willingness to learn additional department and MSU specific software and programs.
- Demonstrated experience working in a fast-paced office setting.
- Ability to troubleshoot problems and have candid conversations.
- Preferred Qualifications – Experience, Education, Knowledge & Skills: list.
List items:
- Master’s Degree, or combination of education and/or applicable experience equivalent to a master’s degree.
- Experience facilitating and instructing small group workshops and classes.
- Knowledge of trends in higher education, Human Resources, the economy and/or workforce development trends.
- Demonstrated experience with teaching and learning pedagogy.
- Experience facilitating and instructing small group workshops and classes. (duplicate? but keep as is.)
- Possess knowledge of the higher education system and related services.
- The Successful Candidate Will Possess a desire to work with college students.
- Have a proven ability to work independently and in a team environment.
- Possess sound decision-making skills.
- Possess an enthusiastic approach and a high level of integrity.
- Be experienced managing and maintaining confidential information.
- Excellence with technology, demonstrated experience, and comfort using new digital apps and online platforms to support student learning and information management.
- Possess the ability to troubleshoot problems and have candid conversations.
- Be dedicated to (maybe incomplete) but we have "Be dedicated to Have the ability to represent the office in a professional manner and serving and effectively communicating with individuals from all backgrounds." Actually text: "Be dedicated to Have the ability to represent the office in a professional manner and serving and effectively communicating with individuals from all backgrounds." Might be garbled. We'll keep as is.
- Have a strong desire to help students create their MSU experience with intentionality.
- Be committed to utilizing engaging pedagogy that involves students in the learning process.
- Possess a willingness and desire to engage in learning themselves.
- Possess the ability to troubleshoot problems and have candid conversations.
- Have the ability to relate to, mentor, inspire and develop rapport with students from all backgrounds.
- Have excellent written and oral communication skills.
- Have a proven ability to take initiative, work independently and in a team environment.
- Have effective interpersonal skills including the ability to collaborate successfully with mentors and staff.
- Possess sound decision-making skills.
- Possess an enthusiastic approach and a high level of integrity.
- Be experienced managing and maintaining confidential information.
- Have the ability to represent the office in a professional manner.
We can combine duplicates but we need to preserve all substantive info, not invent or summarize away detail. Duplicates are okay but we should not remove substantive info. However we can keep them as separate list items; duplicates are okay.
- Position Special Requirements/Additional Information: includes schedule info.
- "Maintain a fixed weekly schedule with flexibility to occasionally host events and interact with students during evenings and weekends."
- "This position is on a academic year 10 month working schedule."
- "The weekly schedule can be set between 30 and 40 hours a week."
- Also earlier: "Salary $24.55 per hour, commensurate with experience, education, and qualifications" (Pay). Also "Benefits Eligible Eligible" (Benefits). Also "FTE .75 - 1.0". Also "Contract Type Classified Hourly". Also "Appointment Type Classified Contract Term Academic Year". Also "FLSA Non-Exempt". Also "Union Affiliation FOCUS-MFPE". Also "Position Number 4N6207". Also "Department Access & Success Division Division of Student Success". Also "If other, specify From date If other, specify End date". Not needed.
We need to include Pay section only if posting states it. Yes: Salary $24.55 per hour, commensurate with experience, education, and qualifications. That's specific. So we include Pay
Pay
with Salary $24.55 per hour, commensurate with experience, education, and qualifications.
Benefits: "Benefits Eligible Eligible". That's not specific detail; it's just "Eligible". Might be considered not specific? 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, it says "Benefits Eligible Eligible". That's stating eligible, but it's vague. However it's stating that benefits are eligible. Might be considered substantive? It says "Benefits Eligible Eligible". Could be interpreted as "Benefits Eligible". It's not a placeholder like "not specified". It's stating eligible. I'd include Benefits section with Benefits eligible.
maybe.
Schedule: The posting states: "Maintain a fixed weekly schedule with flexibility to occasionally host events and interact with students during evenings and weekends. This position is on a academic year 10 month working schedule. The weekly schedule can be set between 30 and 40 hours a week." Also earlier: "Contract Term Academic Year". So we have schedule specifics. So include Schedule Schedule
with - ... maybe combine into
or list.
We should not repeat job title as heading. No Job ID/requisition numbers as headings; we can fold minor metadata into a short
or drop it. We could include a
for Position Number, Department, etc. But we need to preserve ALL substantive information. So we need to include Position Number, Department, Division, Appointment Type, Contract Term, FTE, Union Affiliation, FLSA, etc. However those are minor metadata; we could put them in a
under an "About the role" section or separate "Position Details". But we must not use headings for them unless they match allowed headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can put them in a
under About the role or maybe a separate
before sections.
We need to decide sections: About the role (overview), Responsibilities (duties), Requirements (maybe required qualifications), Qualifications (maybe preferred?), Skills (maybe combine). But we have both Required Qualifications and Preferred Qualifications and also "The Successful Candidate Will Possess" list (skills/attributes). Could split: Requirements = Required Qualifications; Qualifications = Preferred Qualifications; Skills = The Successful Candidate Will Possess list. Or we could combine Required and Preferred into Qualifications. But we need to follow instruction: use headings for those categories if content exists. We'll create sections:
- About the role (
About the role
) with overview prose.
- Responsibilities (Responsibilities
) with list of duties.
- Requirements (Requirements
) with list of required qualifications.
- Qualifications (Qualifications
) with list of preferred qualifications.
- Skills (Skills
) with list of successful candidate attributes.
- Pay (Pay
) with salary.
- Benefits (Benefits
) with eligibility.
- Schedule (Schedule
) with schedule details.
We must avoid filler like "commensurate with experience" in Pay? Actually that's part of salary description; it's okay.
We must not include sections with only filler. All have content.
Now we need to output only HTML fragment, no /, no markdown.
We'll produce:
About the role
...overview...
Responsibilities
- ...
...
Similarly for others.
We need to ensure we preserve all substantive info from the posting. Let's extract all substantive info.
Overview: The paragraph about Access and Success mission and role.
Also the sentence: "Reporting to the Senior Access Officer, this position is housed within the Division of Student Success, as part of the dynamic Access and Success team committed to advancing equitable student outcomes and enhancing student persistence and graduation." That's also overview.
We'll combine.
Responsibilities list: we have four bullet items from Duties and Responsibilities. Also maybe "Conduct one-on-one and group appointments..." etc. Also maybe "Assist students with decoding important information..." etc. Also "Provide student-facing assistance and education on learning management via workshops, strategy clinics, hosting classroom lectures, assisting with the US 103 Learning Strategies course, and group appointments." Also "Connect students with learning management instruction and support to enhance retention and degree completion in a variety of settings."
Also maybe "As part of a multi-faceted and results oriented team, a Success Advisor is responsible for conducting intervention/advising meetings with students." That's more overview but could be duty. We'll include in responsibilities as a bullet.
Also "Advisors are responsible for connecting with students identified as benefiting from additional support or those who seek out services for time management, test taking skills and learning strategies." That's also duty.
We'll include those.
Now Required Qualifications list: we have six items.
Preferred Qualifications list: we have many items, some duplicates. We'll list each distinct item but preserve all. Might be long but okay.
Successful Candidate Will Possess list: many items, some duplicates with preferred. We'll list them as given.
Pay: Sal
Pay
withSalary $24.55 per hour, commensurate with experience, education, and qualifications.
Benefits: "Benefits Eligible Eligible". That's not specific detail; it's just "Eligible". Might be considered not specific? 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, it says "Benefits Eligible Eligible". That's stating eligible, but it's vague. However it's stating that benefits are eligible. Might be considered substantive? It says "Benefits Eligible Eligible". Could be interpreted as "Benefits Eligible". It's not a placeholder like "not specified". It's stating eligible. I'd include Benefits section withBenefits eligible.
maybe. Schedule: The posting states: "Maintain a fixed weekly schedule with flexibility to occasionally host events and interact with students during evenings and weekends. This position is on a academic year 10 month working schedule. The weekly schedule can be set between 30 and 40 hours a week." Also earlier: "Contract Term Academic Year". So we have schedule specifics. So include ScheduleSchedule
with- ... maybe combine into
or list. We should not repeat job title as heading. No Job ID/requisition numbers as headings; we can fold minor metadata into a short
or drop it. We could include a
for Position Number, Department, etc. But we need to preserve ALL substantive information. So we need to include Position Number, Department, Division, Appointment Type, Contract Term, FTE, Union Affiliation, FLSA, etc. However those are minor metadata; we could put them in a
under an "About the role" section or separate "Position Details". But we must not use headings for them unless they match allowed headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can put them in a
under About the role or maybe a separate
before sections. We need to decide sections: About the role (overview), Responsibilities (duties), Requirements (maybe required qualifications), Qualifications (maybe preferred?), Skills (maybe combine). But we have both Required Qualifications and Preferred Qualifications and also "The Successful Candidate Will Possess" list (skills/attributes). Could split: Requirements = Required Qualifications; Qualifications = Preferred Qualifications; Skills = The Successful Candidate Will Possess list. Or we could combine Required and Preferred into Qualifications. But we need to follow instruction: use headings for those categories if content exists. We'll create sections: - About the role (
About the role
) with overview prose. - Responsibilities (Responsibilities
) with list of duties. - Requirements (Requirements
) with list of required qualifications. - Qualifications (Qualifications
) with list of preferred qualifications. - Skills (Skills
) with list of successful candidate attributes. - Pay (Pay
) with salary. - Benefits (Benefits
) with eligibility. - Schedule (Schedule
) with schedule details. We must avoid filler like "commensurate with experience" in Pay? Actually that's part of salary description; it's okay. We must not include sections with only filler. All have content. Now we need to output only HTML fragment, no /, no markdown. We'll produce:About the role
...overview...
Responsibilities
- ... ...