Assistant/Associate Professor - Finance & Faculty Director of the Charles Schwab Foundation Center for Financial Wellness
University of Wisconsin-Green Bay · Green Bay, WI · 1 mo ago
EducationFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invented summary. Remove boilerplate like EEO, legal, application instructions, etc. Must not include sections with placeholder like "commensurate with experience" etc. Pay: The posting says "Competitive compensation commensurate with qualifications and experience." That's vague; we should not include Pay section because it's not specific. Benefits: there is a Benefit Details section with specifics: health insurance options, dental, vision, life insurance, AD&D, Flexible Spending, Health Savings Accounts, Wisconsin Retirement System, supplemental retirement savings programs, paid leave, holidays, personal holiday, sick leave, parental leave, vacation days. That's specific, so include Benefits section.
Schedule: Not mentioned explicitly; maybe "academic year, tenure-track appointment" but not schedule details like full-time/part-time. Could infer but not explicit. Probably no Schedule section.
Pay: not specific, so omit.
Skills: maybe not explicit list; but there are qualifications like CFP certification, leadership experience, etc. Could treat as Requirements/Qualifications. The instruction: Use headings for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections to include based on content.
We have About the role: could be introductory paragraph describing role. Could include that.
Responsibilities: there is "Key Job Responsibilities" with Faculty Responsibilities and Faculty Director Responsibilities. So include Responsibilities.
Requirements: maybe "Required Qualifications" section. Could be Requirements.
Qualifications: maybe "Required Qualifications" again? Might duplicate. Could treat Requirements as required qualifications, and Qualifications as preferred? But posting only has Required Qualifications. Could split into Requirements (mandatory) and Qualifications (preferred) but we don't have preferred. Might just include Requirements and omit Qualifications if no distinct content. However instruction: include a section ONLY when posting has real, specific content for it. So if we have only Required Qualifications, we could put that under Requirements. Qualifications could be omitted.
Skills: maybe not explicit separate list; but could be derived from Required Qualifications (leadership experience, relationship building, fundraising). Might be considered Skills. But we need to avoid thin sections. Could combine into Requirements.
Better: Include About the role, Responsibilities, Requirements (which includes Required Qualifications), Benefits. Possibly also Skills if we can extract explicit skill list: "Evidence of a commitment to quality teaching", "ongoing record of scholarship", "CFP certification, or ability to sit for CFP Board’s CFP® Certification Examination", "Evidence of engagement in institutional, community, and professional endeavors", "Demonstrated leadership experience...", "Experience developing or implementing strategic initiatives.", "Demonstrated ability to build productive relationships with external partners and advisory groups.", "Experience supporting fundraising, donor engagement, grants, sponsorships, or other resource-development activities.", "A record of academic, professional, or industry leadership appropriate for appointment as Faculty Director." Those are qualifications/requirements, not skills per se. Could treat as Requirements.
Thus sections: About the role, Responsibilities, Requirements, Benefits.
We must not include Pay or Schedule.
Now need to preserve all substantive information. Must not omit details like start date, department, etc. Those could go in About the role or maybe a separate meta but we shouldn't create headings for Job ID etc. Could include start date, department in About the role paragraph.
We must remove boilerplate: "Current Employees and Students: If you are currently employed or enrolled as a student at any of the Universities of Wisconsin, log in to Workday to apply through the internal application process." That's application instruction; remove. Also "How To Apply", "Application Deadline", "Contact Information", "The Successful Candidate" (some of that may be substantive? It includes expected behavior, but could be considered part of About the role? Might be considered boilerplate? It's about expected behavior; could keep as part of About the role? It's not exactly boilerplate but it's about candidate expectations. Might be considered part of role description. However instruction says remove application instructions, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines. "The Successful Candidate" section includes expectations; could be considered part of role description. Might keep but maybe it's generic. Safer to keep as part of About the role? Might be okay.
But we must preserve ALL substantive information. So we need to include details like start date August 23, 2027, Department Accounting & Finance, Position is academic year, tenure-track appointment, etc. Also mention that courses taught both face-to-face and online, etc. Also mention that position is exempt from FLSA overtime. Also mention that pre-employment education check, criminal conviction investigation, etc. Those are conditions of appointment; could be part of Requirements or About the role.
We need to be careful not to include boilerplate like "In compliance with the Wisconsin Fair Employment Act, the university does not discriminate on the basis of arrest or conviction record." That's EEO; remove.
Also remove "Benefit Details" heading? We'll keep Benefits section with content.
We must not include markdown fences.
Now craft HTML.
Structure:
About the role
... paragraphs ...
Responsibilities
- ... each responsibility ...
Requirements
- ... each requirement ...
Benefits
- ... each benefit ...