Office & Admin Specialist Int

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if 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, contact info? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove sections like "How To Apply", "Contact", "About Corrections Dept", "Benefits" maybe we keep if substantive. Benefits section is present: we have a Benefits paragraph with details. Should keep that as Benefits section. Pay: we have Salary Range: $21.12 - $28.01 / hourly; $44,098 - $58,484 / annually. That's specific, so include Pay section. Schedule: we have Work Shift/Work Hours: Day Shift/7:00 am to 3:30 pm; Days of Work: Monday - Friday; Travel Required: No. Also Telework Eligible: No. So schedule info present. Include Schedule section. About the role: we have description of work: "The work you'll do is more than just a job..." and description of responsibilities. We'll put that under About the role. Responsibilities: we have bullet-like sentences: "This position is responsible for an administrative area, under limited supervision, providing a wide range of technical, administrative support, and work duties necessary for the functioning of a complex Mental Health, Department at Minnesota Correctional Facility – Rush City (RC). Position also requires administrative support to the Release Planner. This position oversees and is responsible for ensuring necessary data collection and data management of clinical information related to Mental Health, thereby supporting and facilitating the work of clinical services. Management of this data is necessary to facilitate the program staff and DOC in information flow, program evaluation and management, and the DOC in making decisions related to budget, policy and legislative initiatives. This position oversees legal documents, so significant care is exercised in order to mitigate risk for the department, as well as to ensure best clinical outcomes. This position assists the management staff in providing direction to the Behavioral Health team." We can put those as

• items. Requirements: Minimum Qualifications list: Data entry skills..., Typing/keyboarding..., Word processing..., Spreadsheet software..., English language..., Communication and customer service skills... We'll put as list. Preferred Qualifications: Experience working with offender records, Associates degree or higher, Experience using COMS, MNCIS and/or BCA, Experience working in a correctional setting, Knowledge of the Minnesota Data Practices Act. Could be under Qualifications or Skills? The instruction: Use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have both minimum and preferred qualifications. Could put minimum under Requirements, preferred under Qualifications. Skills maybe we can extract from qualifications? But we already have skills listed in minimum qualifications (data entry, typing, word processing, spreadsheet, English language, communication). Those could go under Skills. However we need to avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. We could combine Requirements and Qualifications into one? But headings are prescribed; we should use them if we have content. We have content for Requirements (minimum qualifications). We have content for Qualifications (preferred qualifications). We have content for Skills (maybe we can list the specific skill types). However the minimum qualifications already list skills; we could treat those as Skills section and Requirements as something else? But the minimum qualifications are essentially requirements. Could treat Requirements as the list of minimum qualifications, and Skills as maybe the specific skill categories (data entry, typing, etc.) but that duplicates. Better to follow: Requirements = minimum qualifications; Qualifications = preferred qualifications; Skills maybe we can omit if no distinct content beyond those. But we need to avoid empty headings. So we should not include Skills if we don't have distinct content beyond what's already covered. However the minimum qualifications are skills; but they are also requirements. Could we put them under Skills and not Requirements? But then we lose the concept of requirements. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's examples, not mandatory to use all. We should include a section only when posting has real, specific content for it. So we need to decide what constitutes Requirements vs Qualifications vs Skills. The posting has "Minimum Qualifications" and "Preferred Qualifications". So we can map Minimum Qualifications -> Requirements, Preferred Qualifications -> Qualifications. Skills maybe not separately listed; we could omit Skills section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Check if we have content for each: - About the role: we have introductory paragraph about work and agency commitment. Yes. - Responsibilities: we have the paragraph describing duties; we can turn into list. - Requirements: Minimum Qualifications list. - Qualifications: Preferred Qualifications list. - Benefits: we have a paragraph describing benefits; we can turn into list. - Pay: Salary Range. - Schedule: Work Shift/Work Hours, Days of Work, Telework Eligible, Travel Required. We must not include fluff like "commensurate with experience". Not present. We must remove boilerplate: EEO, equal opportunity, etc. Also remove "Post has been extended." maybe keep? It's substantive? It's just a note; but it's not boilerplate. Could keep in About the role? Might be considered metadata. Safer to keep it as a sentence in About the role? It says "Post has been extended." Could be considered a note; but it's not boilerplate. We'll keep it maybe as a short sentence in About the role. Also remove "Designated in Connect 700 Program for Applicants with Disabilities: Yes". That's metadata; could be included in About the role or maybe as a note. But it's not boilerplate; it's specific info about eligibility. Could be included in About the role or maybe as a separate section? Not in headings list. Could fold into About the role as a sentence. Also remove "Who May Apply: All qualified applicants", "Date Posted", "Closing Date", "Job ID", etc. Those are metadata; we should drop them per instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can drop them entirely or put in a short p at top? Probably drop. We need to preserve all substantive information. The metadata like date posted, closing date, job id, location, telework eligible, full/part time, regular/temporary, hiring agency, division, etc. Some of those are substantive (location, work shift, schedule). We already captured schedule. Location: Rush City. Could be included in About the role or maybe as a short p. The instruction: fold minor metadata into a short

  or drop it. Location is minor? Might be considered minor but could be kept as a short p before sections. However they said "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can include a short p at top with location and maybe other minor metadata like agency, division, etc. But we must not repeat job title as heading. The page already shows it. So we can start with a

  containing location and maybe agency. But we also need to preserve all substantive information; location is substantive. We'll include a short p: "

  Location: Rush City, MN. Agency: Minnesota Department of Corrections, Corrections-Rush City-AFSCME, Division/Unit: Minn Corr Facl - Rush City / RC Psychological Services Dir.

  " That seems okay. Also we have "Classified Status: Classified", "Bargaining Unit/Union: 206 - Clerical/AFSCME", "FLSA Status: Nonexempt". Those are minor metadata; could be included in that short p or dropped. We'll include them in the short p. We must not include application instructions, contact info, etc. So remove "How To Apply", "Contact", "If you have questions about this position, contact Shelley Rojesky..." etc. Also remove "To receive consideration as a Connect 700 Program applicant..." etc. Also remove "About Corrections Dept" section (the promotional paragraph). That's boilerplate? It's about the agency; could be considered substantive but maybe it's boilerplate. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Corrections Dept" is not exactly those but could be considered promotional boilerplate. Safer to drop it. Also remove "EQUAL OPPORTUNITY EMPLOYERS" etc. Also remove "Applicants With Disabilities" etc. Also remove "Resources that provide support..." etc under Benefits? Actually Benefits section includes a list of benefits; we need to keep that. The Benefits paragraph includes many items; we should keep that as list. Now we need to format. We'll output:

  Location: Rush City, MN. Agency: Minnesota Department of Corrections, Corrections-Rush City-AFSCME, Division/Unit: Minn Corr Facl - Rush City / RC Psychological Services Dir. Classified Status: Classified, Bargaining Unit: 206 - Clerical/AFSCME, FLSA Status: Nonexempt.

  Then

  About the role

  with paragraph(s). Include the introductory paragraph: "The work you'll do is more than just a job. At the State of Minnesota, employees play a critical role in developing policies, providing essential services, and working to improve the well-being and quality of life for all Minnesotans. The State of Minnesota is committed to equity and inclusion, and invests in employees by providing benefits, support resources, and training and development opportunities. Post has been extended. This position is responsible for an administrative area, under limited supervision, providing a wide range of technical, administrative support, and work duties necessary for the functioning of a complex Mental Health, Department at Minnesota Correctional Facility – Rush City (RC). Position also requires administrative support to the Release Planner. This position oversees and is responsible for ensuring necessary data collection and data management of clinical information related to Mental Health, thereby supporting and facilitating the work of clinical services. Management of this data is necessary to facilitate the program staff and DOC in information flow, program evaluation and management, and the DOC in making decisions related to budget, policy and legislative initiatives. This position oversees legal documents, so significant care is exercised in order to mitigate risk for the department, as well as to ensure best clinical outcomes. This position assists the management staff in providing direction to the Behavioral Health team." That's a bit long but okay. But we also have Responsibilities section separate; we might split duties into Responsibilities list and keep About the role more generic. However the instruction: "Prefer a few substantive sections over many thin ones." We could combine About the role and Responsibilities into one? But we have headings for both; we can keep both if they have distinct content. The About the role could be the introductory paragraph about agency and role significance; Responsibilities could be the list of specific duties. That seems fine. Thus About the role paragraph: maybe just the first two sentences about work and agency commitment plus "Post has been extended." Not include the duties. Then Responsibilities list will contain the duties. Let's extract: About the role: "The work you'll do is more than just a job. At the State of Minnesota, employees play a critical role in developing policies, providing essential services, and working to improve the well-being and quality of life for all Minnesotans. The State of Minnesota is committed to equity and inclusion, and invests in employees by providing benefits, support resources, and training and development opportunities. Post has been extended." That seems good. Respons