Certified Nurses Aide (CNA or STNA)

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. First, I need to identify the sections. The posting has: - An introductory paragraph (marketing fluff) - Shift differential and benefits list - Purpose - Working Conditions - Education and Experience - Specific Requirements - Primary Job Responsibilities - Essential Functions Rules: - Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use

• for lists,

  for prose - Do NOT repeat job title as heading (page already shows it) - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/scam-warning, duplicated lines, application instructions) - Include section ONLY when posting has real, specific content for it - Never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment, no /, no markdown code fences Now, let's map the content to appropriate sections. The introductory paragraph is marketing fluff, but it mentions competitive pay, flexible scheduling, great benefits, positive work environment. Then there's a list of benefits: Shift Differential, Brand new pay scale, Overtime Pay, Shift Differential (duplicate), Flexible scheduling, Paid Training, Paid Time Off, Health, Dental, Vision, Life and Disability Insurance, Flexible Health Care Savings Plans, 401K, Career Advancement Opportunities, Employee Assistance Program, Free Great Meals. We have a "Purpose" section - that's like "About the role". "Working Conditions" - could be part of "About the role" or separate. "Education and Experience" - that's "Qualifications" or "Requirements". "Specific Requirements" - also qualifications/requirements. "Primary Job Responsibilities" - that's "Responsibilities". "Essential Functions" - also responsibilities or requirements. We need to decide on section headings. The user suggested: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have benefits listed, so we can have a Benefits section. Pay is mentioned (shift differential, brand new pay scale, overtime pay). Schedule: flexible scheduling mentioned, but not detailed. Could include in Benefits or separate Schedule section? The rule says only create Pay/Schedule/Benefits sections if posting actually states them. It does state pay differentials and benefits. Schedule: "flexible scheduling" is mentioned, but not details. Might include in Benefits. We should not create a section for "Working Conditions" unless it's substantive. It is substantive: list of conditions. Could be part of "About the role" or separate. The user didn't list "Working Conditions" as a standard heading, but we can use it if it's a clear section. However, the rule says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." so we can use other headings if they fit. But we should prefer those standard ones. "Working Conditions" could be under "About the role". "Purpose" is essentially "About the role". "Education and Experience" and "Specific Requirements" are "Qualifications" or "Requirements". "Primary Job Responsibilities" and "Essential Functions" are "Responsibilities". Let's structure: 1. About the role (Purpose + Working Conditions) 2. Responsibilities (Primary Job Responsibilities + Essential Functions) 3. Qualifications (Education and Experience + Specific Requirements) 4. Benefits (the list of benefits) 5. Pay (shift differential, brand new pay scale, overtime pay) - but pay is part of benefits? The list includes "Brand new pay scale", "Overtime Pay", "Shift Differential". Could be a Pay section. However, the rule says never create Pay section unless posting actually states them. It does state pay differentials and pay scale. So we can have a Pay section. But the benefits list includes those. Might combine into Benefits? The user example includes both Pay and Benefits as separate. I'll separate: Pay for compensation details, Benefits for other benefits. But the posting lists them all together. Let's parse: "Offering Shift Differential: Weekdays after 3pm: $2.00 extra per hour, Weekends, all shifts: $4.00 extra per hour Brand new pay scale Overtime Pay Shift Differential Flexible scheduling Paid Training Paid Time Off Health, Dental, Vision, Life and Disability Insurance Flexible Health Care Savings Plans 401 K Career Advancement Opportunities Employee Assistance Program Free Great Meals" Some are pay-related (shift differential, brand new pay scale, overtime pay), some are benefits (health insurance, 401k, etc.), some are schedule (flexible scheduling). Could create three sections: Pay, Benefits, Schedule. But the rule says prefer few substantive sections over many thin ones. Schedule only has "flexible scheduling" - that's thin. Could include in Benefits. Pay has a few items. Benefits has many. I'll create a Benefits section that includes all, but maybe separate Pay because it's specific numbers. However, the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. But we can combine into one "Compensation & Benefits" section? The user example headings include Pay, Benefits, Schedule as separate. I'll follow the example: create Pay, Benefits, and maybe Schedule if there's enough. Schedule only has "flexible scheduling" - that's one line. Could be a bullet in Benefits. I'll include flexible scheduling in Benefits. Thus sections: - About the role - Responsibilities - Qualifications - Pay - Benefits But the user said "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So we can use "Qualifications" instead of "Requirements". The posting has "Education and Experience" and "Specific Requirements". That's qualifications. Now, we need to output HTML fragment. Let's write:

  About the role

  The CERTIFIED NURSES AIDE / CNA (STNA-State Tested Nursing Assistant) delivers routine daily assisted living services through interpersonal contact focused on maximizing residents’ individual capabilities in accordance with all laws, regulations and Century Park standards. Reports to Resident Care Director.

  Working Conditions

  • Attends and participates in continuing education programs
  • Works in department as well as throughout community
  • Subject to frequent interruptions
  • Involved with residents, associates, visitors, government agencies/personnel, etc. under all conditions and circumstances
  • Subject to hostile and emotionally upset residents, family members, etc.
  • Works beyond normal working hours, on weekends and holidays, and in other positions temporary as necessary
  • Subject to falls, burns from equipment, odors, etc. throughout the workday
  • Possible exposure to infectious waste, diseases, conditions, etc., including exposure to the AIDS and hepatitis B viruses
  But the rule says use

  for section headings. Should "Working Conditions" be

  or

  ? The rule says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid subheadings, but we should keep it flat. Could make "Working Conditions" a separate

  section. But the user said prefer few substantive sections. Working Conditions is substantive. Could be its own section. However, the example headings don't include Working Conditions. But we can include it as a section if it's real content. I'll make it a separate

  section. But then we have many sections: About the role, Working Conditions, Responsibilities, Qualifications, Pay, Benefits. That's okay. Alternatively, combine Working Conditions into About the role as a list. The rule says use

  • for any list of duties/requirements/benefits, and

    for prose. Working Conditions is a list. Could be a list under About the role. I'll do:

    About the role

    The CERTIFIED NURSES AIDE / CNA (STNA-State Tested Nursing Assistant) delivers routine daily assisted living services through interpersonal contact focused on maximizing residents’ individual capabilities in accordance with all laws, regulations and Century Park standards. Reports to Resident Care Director.

    Working Conditions

    ...
    But the rule says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings. It says "e.g." So we can use Working Conditions. Now Responsibilities: combine Primary Job Responsibilities and Essential Functions. They are both lists of duties. Could be one section "Responsibilities" with two sub-lists? But we should keep flat. Could have one list with all items. However, they are distinct categories. Could use

    Responsibilities

    and then two
    with maybe a heading for each? But we cannot use

    ? The rule doesn't forbid

    , but says use

    for section headings. We can use

    for subsections. But to keep simple, we can merge into one list. But the posting separates them. I'll keep them as two separate lists under Responsibilities, with a brief intro.

    Responsibilities

    Primary Job Responsibilities:

    • Assists residents with activities of daily living as designated in care plan (i.e., dressing, toileting, hair care, bathing)
    • Reads 24-hour log at beginning of shift
    ...

    Essential Functions:

    • Must be able to respond to call lights promptly
    • Must assist with evacuation of residents and supports residents in times of crisis (i.e., natural disaster).
    ...
    That's acceptable. Qualifications: Education and Experience and Specific Requirements.

    Qualifications

    Education and Experience

    • Must possess a high school diploma or equivalent
    • Must be a graduate of a State-approved CNA program
    • Must be currently certified/registered in applicable state. Must maintain an active certification in good standing throughout employment
    • One (1) year experience in senior services preferred
    • Must have CPR certification upon hire or obtain during Orientation. Certification must remain current during employment.

    Specific Requirements

    • Must have patience, tact, cheerful disposition, and enthusiasm as well as a willingness to handle difficult residents
    • Must possess the ability to make independent decisions when circumstances warrant such action
    • Must be knowledgeable of nursing aide practices and procedures as well as the laws, regulations, and guidelines governing nursing aide functions in an assisted living community
    • Must perform efficiently in all applicable competence areas
    • Maintains professional working relationships with all associates, vendors, etc.
    • Maintains confidentiality of all proprietary and/or confidential information
    • Displays integrity and professionalism by adhering to Century Parks’ Code of Ethics