Security Officer

We need to output HTML fragment with sections: About the role? Actually we need headings for sections present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if content exists. Must not repeat job title. Must not include boilerplate like EEO, etc. Must preserve all substantive info. We need to parse the posting. Content: - Intro: "Wake Robin is seeking a full-time Security Officer to join our community! Security is different at Wake Robin. We’re like a small town where everyone knows and helps each other. Our version of security means helping our senior residents and our staff feel safe and secure - easy to do on our 136-acre campus. Some days it includes welcoming a new resident to their home to teach them about our medical alert system and another day may be running a fire drill or updating settings on one of our security systems. Occasionally, you’ll also support the broader team by responding to situations like assisting a resident who has taken a fall, lending a hand to ensure walkways are safe, or assisting maintenance in an emergency like a water leak or minor maintenance issue. While no two days are the same, the one constant is our commitment to customer service. This is a very vibrant community looking for someone who enjoys variety in their job and wants to be a part of something larger than themselves." That's about the role / description. Could be "About the role" or maybe "Responsibilities". We'll decide. Then "Schedule Sunday-Tuesday 7am-7pm, Wednesday 7am-11am" Then "Duties Include" list: - Providing safety and security measures for residents and staff - Addressing emergency or comfort concerns of residents - Responding to and assessing situations involving the physical plant - Ensuring that all buildings are secured according to appropriate schedules - Helping screen visitors and service providers - Utilizing computer-based technology Then "Skills/Experience" list: - Background in Security or as a first responder - High-level of problem-solving skills and adaptability - Positive interactions with general public, preferably with senior population - Fire/safety alarm systems in a residential or health care setting - Collaboration with multiple teams, both internal and external - Team centered approach - Outstanding communication skills Then "Pay" paragraph: "The pay range for this position is $21.75-$26.54 (Starting salary is determined based on candidate's experience, education, and relevant skills as well as internal equity considerations.)" Then "Due to our vulnerable resident population the COVID vaccine is highly recommended but not required." This is maybe a note; but it's not a section; we could include as a short paragraph under maybe "Additional Information"? But we shouldn't create sections unless content. Could include as a paragraph under maybe "About the role"? But it's not about role. Could include as a separate short paragraph after Pay? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." This is metadata about vaccine recommendation; we could fold into a short

after Pay or maybe under a generic "Additional Info". But we shouldn't create a heading unless there's real specific content. Could just include as a

after Pay without heading. Then "About Wake Robin" paragraph(s). That's about the organization; could be "About Wake Robin" heading? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It didn't list "About the company". But we could treat "About Wake Robin" as maybe "About the role"? Actually "About the role" is for role description; "About Wake Robin" is about the organization. The instruction didn't forbid other headings, but said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gave examples but not exclusive. However they said "Prefer a few substantive sections over many thin ones." So we could combine the organizational description into maybe "About the role" or maybe we could add a section "About Wake Robin". But they didn't list that as example; but it's not prohibited. However they said "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the expected headings. It might be safer to stick to those headings only. So we need to map content to those headings. We have: - About the role: could include the introductory paragraph describing the role and community, plus maybe the "About Wake Robin" paragraph? But that is about the organization, not role. However we could incorporate it under About the role as context. - Responsibilities: the Duties Include list. - Requirements: maybe the Skills/Experience list? Or we could split: Requirements = background, problem-solving, etc. Qualifications maybe similar. But we need to avoid thin sections. Could combine Requirements and Qualifications into one? But they said use headings for those if content exists. We have content for Skills/Experience; we could put that under Skills heading. Then we could have Requirements maybe empty? Better to not create empty headings. So we could use Skills heading for the list. Then we could have Requirements maybe not needed. Or we could treat the list as Requirements and Skills combined under Skills. - Benefits: we have a list of benefits. - Pay: we have pay range. - Schedule: we have schedule. Thus we can have sections: About the role, Responsibilities, Skills, Benefits, Pay, Schedule. We need to ensure we include all substantive info. Let's extract each. About the role: combine the introductory paragraph(s) and maybe the About Wake Robin paragraph(s). Let's gather: Intro: "Wake Robin is seeking a full-time Security Officer to join our community! Security is different at Wake Robin. We’re like a small town where everyone knows and helps each other. Our version of security means helping our senior residents and our staff feel safe and secure - easy to do on our 136-acre campus. Some days it includes welcoming a new resident to their home to teach them about our medical alert system and another day may be running a fire drill or updating settings on one of our security systems. Occasionally, you’ll also support the broader team by responding to situations like assisting a resident who has taken a fall, lending a hand to ensure walkways are safe, or assisting maintenance in an emergency like a water leak or minor maintenance issue. While no two days are the same, the one constant is our commitment to customer service. This is a very vibrant community looking for someone who enjoys variety in their job and wants to be a part of something larger than themselves." About Wake Robin: "The foundation of our success as a Life Plan Community is the mutual respect among staff and between residents and staff. Staff share a belief in the dignity and worth of each resident and each other. As employees, we do more than just work here — we uphold Wake Robin’s commitment to these values; the relationship between staff and residents is the hallmark of this community. At Wake Robin, we want to support you in your career growth. We offer flexible scheduling for those wishing to return to school and loan forgiveness programs, great benefits, a pristine working environment, and an opportunity to build strong relationships with staff and residents in a dynamic community setting. At Wake Robin, community is critical; we stand by this, starting with the first phone call with you!" We could merge these into About the role section. Responsibilities: the Duties Include list. Skills: the Skills/Experience list. Benefits: the Benefits list. Pay: the Pay paragraph. Schedule: the Schedule line. Also we have the vaccine recommendation line; we could include as a short paragraph after Pay maybe under a generic note, but we could also fold into Pay section as a note? It's not pay. Could add a short

after Pay but before Benefits? Or after Schedule? Probably after Pay as a note. Since it's minor metadata, we can fold into a short

without heading. We must not include boilerplate like EEO, etc. The posting ends with "Wake Robin is proud to be a smoke free environment. Wake Robin believes in supporting a livable wage for all Vermonters. Wake Robin is an Equal Opportunity Employer." That's boilerplate; we should remove. Now construct HTML. We'll output:

About the role

...combined text...

Responsibilities

• ...
...

Skills

• ...
...

Benefits

• ...
...

Pay

The pay range for this position is $21.75-$26.54 (Starting salary is determined based on candidate's experience, education, and relevant skills as well as internal equity considerations.)

Due to our vulnerable resident population the COVID vaccine is highly recommended but not required.

Schedule

Schedule Sunday-Tuesday 7am-7pm, Wednesday 7am-11am

Make sure to preserve all details exactly. Check Benefits list: The posting includes: "Staff members work together with humor and an appreciation for diversity. For many, the biggest benefit of working here is coming to know Wake Robin’s residents and having the time and support to do good work on their behalf. Other important benefits include: Health Benefits: Medical, dental, and vision coverage Company paid short - term disability, long-term disability , and life insurance Flexible spending plan 403b retirement plan with company match of 50% up to a calendar year maximum of $6,000 Com petitive paid time o ff Continuing education support Financial assistance with car maintenance and repairs P ersonal loan assistance to help with emergency and unplanned needs Up to $200 f itness reimbursement annually Up to $100 reimbursement for vision expenses annually Incentives for commuting with your coworkers Free, on-site consul ting on housing, finances, transportation, daycare, and legal servi ces Use of community facilities including hiking trails, library, aquatic and fitness centers On-site meals for purchase, made from scratch with local ingredients Refer a Friend bonus - up to $1,500 per employee referral Wake Robin is proud to be a smoke free environment." We need to preserve all substantive info; but we should remove boilerplate like "Wake Robin is proud to be a smoke free environment." That's maybe considered boilerplate? It's a policy statement; but it's not EEO etc. Might be okay to keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". Smoke free environment is not exactly those categories; it's a workplace policy. Might be okay to keep. However it's near the end after benefits; but we could include as a benefit? It's a policy. Might be okay to keep as a separate sentence in benefits section. But we need to ensure we don't include the Equal Opportunity Employer line (we will remove). Also remove "Wake Robin believes in supporting a livable wage for all Vermonters." That's also a statement; not EEO but could be considered boilerplate? It's a value statement. Might be okay to keep? The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. This is not exactly those. But it's a generic statement; maybe we can keep. However to be safe, we could keep it as part of About the role? It's about the organization. But it's near the end after benefits. I'd consider it as part of About Wake Robin description; we already have that. So we could incorporate that sentence into About the role section. Thus we will include the livable wage sentence in About the role. Now we need to ensure we don't duplicate content. Let's craft About the role paragraph(s): Paragraph 1: "Wake Robin is seeking a full