Personal Care Attendant- West SATX
` for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use `- ` for lists of duties/requirements/benefits
- Use `
` for prose
- Do NOT repeat job title as heading (already shown)
- Do NOT put Job ID / requisition numbers as headings - fold minor metadata into short `
` or drop it
- Preserve ALL substantive information; do NOT invent or summarize away detail
- Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
- IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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
- Prefer a few substantive sections over many thin ones
- Output ONLY the HTML fragment — no `/`, no markdown code fences
2. **Analyze the Input Text:**
Let me parse the job posting:
- "Pride PHC is Seeking a Caregiver in West San Antonio, TX Zip Code: 78245"
- "Monday - Saturday 9am-4pm"
- "Starting Pay Rate: $12.20"
- "Are you looking for a rewarding job with the opportunity to make a difference in the daily life of a client whose life has been changed due to age or illness?"
- "Looking for Supplemental income with flexible scheduling?"
- "We are looking for a compassionate Attendant with the dedication and professionalism it takes to work for Pride PHC"
- "Now offering affordable benefits for our Part Time employees!"
- "Choice Of One Or All Medical plansDental planVision planShort-term DisabilityLife/AD&D Insurance Benefits"
- "Flexible scheduling weekly payEmployee recognition PPE provided"
- "A Few Daily Tasks May Include"
- "Preparing/cleaning up after a meal"
- "Assist clients with activities of daily living"
- "Ambulatory Care"
- "Basic home chores (sweeping, mopping, dusting)"
- "Laundry"
- "Requirements"
- "Be at least 18 years of age"
- "Ability to lift 50 LBS"
- "This is more than a job—it is meaningful work that fits your life. Choose Pride PHC Services and take the next step with confidence."
I need to map this to the requested sections, using `
` for headings, `- ` for lists, `
` for prose. I must NOT create sections without real content. I must preserve all substantive info. I must remove boilerplate, duplicated lines, application instructions. The job title is already shown, so I shouldn't repeat it as a heading. I need to figure out reasonable section names that match the content, using the allowed examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
Let's categorize the content:
- Location/Zip/Schedule: "Pride PHC is Seeking a Caregiver in West San Antonio, TX Zip Code: 78245 Monday - Saturday 9am-4pm" -> This is location/schedule/pay metadata. I can fold into a `
` or use Schedule/Pay sections if content is specific. The rules say: "never create Pay/Schedule/Benefits sections unless the posting actually states them" and "never emit a heading followed by filler/placeholder text". The posting states "Starting Pay Rate: $12.20" and "Monday - Saturday 9am-4pm". So I can have Pay and Schedule sections with actual content. But the rule also says: "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid Pay/Schedule sections if content exists. It says "Prefer a few substantive sections over many thin ones." and "include a section ONLY when the posting has real, specific content for it". So I can have Pay and Schedule sections since they have specific info.
- Pay: "$12.20" starting pay rate.
- Schedule: "Monday - Saturday 9am-4pm"
- Benefits: "Now offering affordable benefits for our Part Time employees! Choice Of One Or All Medical plansDental planVision planShort-term DisabilityLife/AD&D Insurance Benefits" -> This is a benefits list. I should make a Benefits section.
- Responsibilities/Daily Tasks: "A Few Daily Tasks May Include Preparing/cleaning up after a meal Assist clients with activities of daily living Ambulatory Care Basic home chores (sweeping, mopping, dusting) Laundry" -> Responsibilities section.
- Requirements: "Be at least 18 years of age Ability to lift 50 LBS" -> Requirements section. Could also be Qualifications. The rules mention "Requirements" and "Qualifications" as examples. I'll use "Requirements" since that's what the heading says in the posting. Or I could combine. I'll stick to "Requirements" as a heading, or maybe "Qualifications". The posting says "Requirements" explicitly. I'll use `
Requirements
`.
- About the role/Prose: "Are you looking for a rewarding job with the opportunity to make a difference in the daily life of a client whose life has been changed due to age or illness? Looking for Supplemental income with flexible scheduling? We are looking for a compassionate Attendant with the dedication and professionalism it takes to work for Pride PHC" -> This is prose. I can put it in a `` under "About the role" or similar. But I need to check if "About the role" section has real content. Yes, this prose describes the role and what they're looking for. I'll create an "About the role" section with a `
`.
Let's map carefully, ensuring each section has real content, no placeholders.
Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
I need to decide which to include. The posting has:
- Pay: $12.20
- Schedule: Mon-Sat 9am-4pm
- Benefits: medical, dental, vision, short-term disability, life/ADD insurance, flexible scheduling, weekly pay, employee recognition, PPE provided
- Responsibilities: daily tasks listed
- Requirements: 18+, lift 50 lbs
- Prose/About: the introductory questions/description
I should NOT create a "Skills" section if there's no specific skills content, or I can fold it. The posting doesn't really list specific skills, just tasks and requirements. I'll skip Skills or maybe include it under Requirements. The rule: "include a section ONLY when the posting has real, specific content for it". So I'll only include sections where there's actual content.
Let's list potential sections and their content:
- About the role: The introductory prose about rewarding job, making a difference, supplemental income, compassionate attendant. I'll put it in a `
`.
- Responsibilities: The daily tasks list.
- Requirements: 18+, lift 50 lbs.
- Benefits: The benefits list.
- Pay: $12.20 starting pay.
- Schedule: Mon-Sat 9am-4pm.
That's 6 sections. I could also fold location/zip into a `
` or maybe not have a separate section. The zip and location could be part of a `
` at the top, or folded into Schedule/Pay. The rule: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So I can put the location/zip/schedule/pay info in a `
` at the start, or use Schedule and Pay sections since they have specific content. I think it's better to have Schedule and Pay sections with the actual values, and maybe a `
` for location if needed. But the rule also says "Prefer a few substantive sections over many thin ones." Having 6 sections might be okay if each has substantial content. But I need to be careful not to create thin sections.
Let's re-read: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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." So I can create Pay/Schedule/Benefits since they are stated. But I should ensure they're not thin. Pay: "$12.20" is specific. Schedule: "Monday - Saturday 9am-4pm" is specific. Benefits: list is specific.
However, the rule also says: "Prefer a few substantive sections over many thin ones." So maybe I should combine some. For example, I could put Pay and Schedule in a single `
` at the top, or have separate sections. I think having separate sections is fine as long as they have content. But I need to check if the posting actually has a "Skills" section. It doesn't explicitly, just tasks and requirements. I'll skip Skills.
Let's structure:
Maybe start with a `
` for location/intro metadata, then sections for About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. But that's 6 headings. I could merge Pay and Schedule into one `
` or keep them separate. I'll keep them separate since they have distinct content, but I'll make sure each section's content is substantive.
Actually, re-reading the input: "Monday - Saturday 9am-4pm Starting Pay Rate: $12.20" is at the top. I could put that in a `
` at the top, then sections. But the rules say I can use headings for Pay and Schedule. I'll use `
Pay
` and `Schedule
` with the specific values. But wait: the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It doesn't forbid them, it just says don't create them if not stated. They are stated.
Let's think about the "About the role" section. The prose is: "Are you looking for a rewarding job with the opportunity to make a difference in the daily life of a client whose life has been changed due to age or illness? Looking for Supplemental income with flexible scheduling? We are looking for a compassionate Attendant with the dedication and professionalism it takes to work for Pride PHC". That's good content for About the role.
"Responsibilities": "A Few Daily Tasks May Include Preparing/cleaning up after a meal Assist clients with activities of daily living Ambulatory Care Basic home chores (sweeping, mopping, dusting) Laundry" -> I'll make a list.
"Requirements": "Be at least 18 years of age Ability to lift 50 LBS" -> list.
"Benefits": "Now offering affordable benefits for our Part Time employees! Choice Of One Or All Medical plansDental planVision planShort-term DisabilityLife/AD&D Insurance Benefits" -> list. Also "
` for prose - Do NOT repeat job title as heading (already shown) - Do NOT put Job ID / requisition numbers as headings - fold minor metadata into short `
` or drop it - Preserve ALL substantive information; do NOT invent or summarize away detail - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions - IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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 - Prefer a few substantive sections over many thin ones - Output ONLY the HTML fragment — no `/`, no markdown code fences 2. **Analyze the Input Text:** Let me parse the job posting: - "Pride PHC is Seeking a Caregiver in West San Antonio, TX Zip Code: 78245" - "Monday - Saturday 9am-4pm" - "Starting Pay Rate: $12.20" - "Are you looking for a rewarding job with the opportunity to make a difference in the daily life of a client whose life has been changed due to age or illness?" - "Looking for Supplemental income with flexible scheduling?" - "We are looking for a compassionate Attendant with the dedication and professionalism it takes to work for Pride PHC" - "Now offering affordable benefits for our Part Time employees!" - "Choice Of One Or All Medical plansDental planVision planShort-term DisabilityLife/AD&D Insurance Benefits" - "Flexible scheduling weekly payEmployee recognition PPE provided" - "A Few Daily Tasks May Include" - "Preparing/cleaning up after a meal" - "Assist clients with activities of daily living" - "Ambulatory Care" - "Basic home chores (sweeping, mopping, dusting)" - "Laundry" - "Requirements" - "Be at least 18 years of age" - "Ability to lift 50 LBS" - "This is more than a job—it is meaningful work that fits your life. Choose Pride PHC Services and take the next step with confidence." I need to map this to the requested sections, using `
` for headings, `- ` for lists, `
` for prose. I must NOT create sections without real content. I must preserve all substantive info. I must remove boilerplate, duplicated lines, application instructions. The job title is already shown, so I shouldn't repeat it as a heading. I need to figure out reasonable section names that match the content, using the allowed examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
Let's categorize the content:
- Location/Zip/Schedule: "Pride PHC is Seeking a Caregiver in West San Antonio, TX Zip Code: 78245 Monday - Saturday 9am-4pm" -> This is location/schedule/pay metadata. I can fold into a `
` or use Schedule/Pay sections if content is specific. The rules say: "never create Pay/Schedule/Benefits sections unless the posting actually states them" and "never emit a heading followed by filler/placeholder text". The posting states "Starting Pay Rate: $12.20" and "Monday - Saturday 9am-4pm". So I can have Pay and Schedule sections with actual content. But the rule also says: "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid Pay/Schedule sections if content exists. It says "Prefer a few substantive sections over many thin ones." and "include a section ONLY when the posting has real, specific content for it". So I can have Pay and Schedule sections since they have specific info.
- Pay: "$12.20" starting pay rate.
- Schedule: "Monday - Saturday 9am-4pm"
- Benefits: "Now offering affordable benefits for our Part Time employees! Choice Of One Or All Medical plansDental planVision planShort-term DisabilityLife/AD&D Insurance Benefits" -> This is a benefits list. I should make a Benefits section.
- Responsibilities/Daily Tasks: "A Few Daily Tasks May Include Preparing/cleaning up after a meal Assist clients with activities of daily living Ambulatory Care Basic home chores (sweeping, mopping, dusting) Laundry" -> Responsibilities section.
- Requirements: "Be at least 18 years of age Ability to lift 50 LBS" -> Requirements section. Could also be Qualifications. The rules mention "Requirements" and "Qualifications" as examples. I'll use "Requirements" since that's what the heading says in the posting. Or I could combine. I'll stick to "Requirements" as a heading, or maybe "Qualifications". The posting says "Requirements" explicitly. I'll use `
Requirements
`.
- About the role/Prose: "Are you looking for a rewarding job with the opportunity to make a difference in the daily life of a client whose life has been changed due to age or illness? Looking for Supplemental income with flexible scheduling? We are looking for a compassionate Attendant with the dedication and professionalism it takes to work for Pride PHC" -> This is prose. I can put it in a `` under "About the role" or similar. But I need to check if "About the role" section has real content. Yes, this prose describes the role and what they're looking for. I'll create an "About the role" section with a `
`.
Let's map carefully, ensuring each section has real content, no placeholders.
Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
I need to decide which to include. The posting has:
- Pay: $12.20
- Schedule: Mon-Sat 9am-4pm
- Benefits: medical, dental, vision, short-term disability, life/ADD insurance, flexible scheduling, weekly pay, employee recognition, PPE provided
- Responsibilities: daily tasks listed
- Requirements: 18+, lift 50 lbs
- Prose/About: the introductory questions/description
I should NOT create a "Skills" section if there's no specific skills content, or I can fold it. The posting doesn't really list specific skills, just tasks and requirements. I'll skip Skills or maybe include it under Requirements. The rule: "include a section ONLY when the posting has real, specific content for it". So I'll only include sections where there's actual content.
Let's list potential sections and their content:
- About the role: The introductory prose about rewarding job, making a difference, supplemental income, compassionate attendant. I'll put it in a `
`.
- Responsibilities: The daily tasks list.
- Requirements: 18+, lift 50 lbs.
- Benefits: The benefits list.
- Pay: $12.20 starting pay.
- Schedule: Mon-Sat 9am-4pm.
That's 6 sections. I could also fold location/zip into a `
` or maybe not have a separate section. The zip and location could be part of a `
` at the top, or folded into Schedule/Pay. The rule: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So I can put the location/zip/schedule/pay info in a `
` at the start, or use Schedule and Pay sections since they have specific content. I think it's better to have Schedule and Pay sections with the actual values, and maybe a `
` for location if needed. But the rule also says "Prefer a few substantive sections over many thin ones." Having 6 sections might be okay if each has substantial content. But I need to be careful not to create thin sections.
Let's re-read: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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." So I can create Pay/Schedule/Benefits since they are stated. But I should ensure they're not thin. Pay: "$12.20" is specific. Schedule: "Monday - Saturday 9am-4pm" is specific. Benefits: list is specific.
However, the rule also says: "Prefer a few substantive sections over many thin ones." So maybe I should combine some. For example, I could put Pay and Schedule in a single `
` at the top, or have separate sections. I think having separate sections is fine as long as they have content. But I need to check if the posting actually has a "Skills" section. It doesn't explicitly, just tasks and requirements. I'll skip Skills.
Let's structure:
Maybe start with a `
` for location/intro metadata, then sections for About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. But that's 6 headings. I could merge Pay and Schedule into one `
` or keep them separate. I'll keep them separate since they have distinct content, but I'll make sure each section's content is substantive.
Actually, re-reading the input: "Monday - Saturday 9am-4pm Starting Pay Rate: $12.20" is at the top. I could put that in a `
` at the top, then sections. But the rules say I can use headings for Pay and Schedule. I'll use `
Pay
` and `Schedule
` with the specific values. But wait: the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It doesn't forbid them, it just says don't create them if not stated. They are stated.
Let's think about the "About the role" section. The prose is: "Are you looking for a rewarding job with the opportunity to make a difference in the daily life of a client whose life has been changed due to age or illness? Looking for Supplemental income with flexible scheduling? We are looking for a compassionate Attendant with the dedication and professionalism it takes to work for Pride PHC". That's good content for About the role.
"Responsibilities": "A Few Daily Tasks May Include Preparing/cleaning up after a meal Assist clients with activities of daily living Ambulatory Care Basic home chores (sweeping, mopping, dusting) Laundry" -> I'll make a list.
"Requirements": "Be at least 18 years of age Ability to lift 50 LBS" -> list.
"Benefits": "Now offering affordable benefits for our Part Time employees! Choice Of One Or All Medical plansDental planVision planShort-term DisabilityLife/AD&D Insurance Benefits" -> list. Also "
` for prose. I must NOT create sections without real content. I must preserve all substantive info. I must remove boilerplate, duplicated lines, application instructions. The job title is already shown, so I shouldn't repeat it as a heading. I need to figure out reasonable section names that match the content, using the allowed examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Let's categorize the content: - Location/Zip/Schedule: "Pride PHC is Seeking a Caregiver in West San Antonio, TX Zip Code: 78245 Monday - Saturday 9am-4pm" -> This is location/schedule/pay metadata. I can fold into a `
` or use Schedule/Pay sections if content is specific. The rules say: "never create Pay/Schedule/Benefits sections unless the posting actually states them" and "never emit a heading followed by filler/placeholder text". The posting states "Starting Pay Rate: $12.20" and "Monday - Saturday 9am-4pm". So I can have Pay and Schedule sections with actual content. But the rule also says: "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid Pay/Schedule sections if content exists. It says "Prefer a few substantive sections over many thin ones." and "include a section ONLY when the posting has real, specific content for it". So I can have Pay and Schedule sections since they have specific info. - Pay: "$12.20" starting pay rate. - Schedule: "Monday - Saturday 9am-4pm" - Benefits: "Now offering affordable benefits for our Part Time employees! Choice Of One Or All Medical plansDental planVision planShort-term DisabilityLife/AD&D Insurance Benefits" -> This is a benefits list. I should make a Benefits section. - Responsibilities/Daily Tasks: "A Few Daily Tasks May Include Preparing/cleaning up after a meal Assist clients with activities of daily living Ambulatory Care Basic home chores (sweeping, mopping, dusting) Laundry" -> Responsibilities section. - Requirements: "Be at least 18 years of age Ability to lift 50 LBS" -> Requirements section. Could also be Qualifications. The rules mention "Requirements" and "Qualifications" as examples. I'll use "Requirements" since that's what the heading says in the posting. Or I could combine. I'll stick to "Requirements" as a heading, or maybe "Qualifications". The posting says "Requirements" explicitly. I'll use `
Requirements
`. - About the role/Prose: "Are you looking for a rewarding job with the opportunity to make a difference in the daily life of a client whose life has been changed due to age or illness? Looking for Supplemental income with flexible scheduling? We are looking for a compassionate Attendant with the dedication and professionalism it takes to work for Pride PHC" -> This is prose. I can put it in a `` under "About the role" or similar. But I need to check if "About the role" section has real content. Yes, this prose describes the role and what they're looking for. I'll create an "About the role" section with a `
`. Let's map carefully, ensuring each section has real content, no placeholders. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I need to decide which to include. The posting has: - Pay: $12.20 - Schedule: Mon-Sat 9am-4pm - Benefits: medical, dental, vision, short-term disability, life/ADD insurance, flexible scheduling, weekly pay, employee recognition, PPE provided - Responsibilities: daily tasks listed - Requirements: 18+, lift 50 lbs - Prose/About: the introductory questions/description I should NOT create a "Skills" section if there's no specific skills content, or I can fold it. The posting doesn't really list specific skills, just tasks and requirements. I'll skip Skills or maybe include it under Requirements. The rule: "include a section ONLY when the posting has real, specific content for it". So I'll only include sections where there's actual content. Let's list potential sections and their content: - About the role: The introductory prose about rewarding job, making a difference, supplemental income, compassionate attendant. I'll put it in a `
`. - Responsibilities: The daily tasks list. - Requirements: 18+, lift 50 lbs. - Benefits: The benefits list. - Pay: $12.20 starting pay. - Schedule: Mon-Sat 9am-4pm. That's 6 sections. I could also fold location/zip into a `
` or maybe not have a separate section. The zip and location could be part of a `
` at the top, or folded into Schedule/Pay. The rule: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So I can put the location/zip/schedule/pay info in a `
` at the start, or use Schedule and Pay sections since they have specific content. I think it's better to have Schedule and Pay sections with the actual values, and maybe a `
` for location if needed. But the rule also says "Prefer a few substantive sections over many thin ones." Having 6 sections might be okay if each has substantial content. But I need to be careful not to create thin sections. Let's re-read: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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." So I can create Pay/Schedule/Benefits since they are stated. But I should ensure they're not thin. Pay: "$12.20" is specific. Schedule: "Monday - Saturday 9am-4pm" is specific. Benefits: list is specific. However, the rule also says: "Prefer a few substantive sections over many thin ones." So maybe I should combine some. For example, I could put Pay and Schedule in a single `
` at the top, or have separate sections. I think having separate sections is fine as long as they have content. But I need to check if the posting actually has a "Skills" section. It doesn't explicitly, just tasks and requirements. I'll skip Skills. Let's structure: Maybe start with a `
` for location/intro metadata, then sections for About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. But that's 6 headings. I could merge Pay and Schedule into one `
` or keep them separate. I'll keep them separate since they have distinct content, but I'll make sure each section's content is substantive. Actually, re-reading the input: "Monday - Saturday 9am-4pm Starting Pay Rate: $12.20" is at the top. I could put that in a `
` at the top, then sections. But the rules say I can use headings for Pay and Schedule. I'll use `