Physical Therapist Assistant- $8,000 sign on bonus
for section headings, - for lists,
for prose.
I must not include boilerplate like application instructions, EEO, etc.
Let me extract substantive content:
1. About the role / Company: The description about Dignity/Select Medical, mission, core values, culture. This is substantive.
2. Responsibilities: Not explicitly listed as bullet points, but the "ideal team member" qualities and the questions give insight. However, the posting doesn't have a clear responsibilities list. I might need to infer from the description? The rules say preserve ALL substantive information. The posting describes the role indirectly. I could create a "Responsibilities" section with the qualities expected? But better to include the "ideal team member" and the questions as part of About the role or a separate "What we're looking for" section. The rules say use headings like Responsibilities, Requirements, Qualifications, Skills. I'll create a "Qualifications" or "Requirements" section for the required credentials and physical requirements. And maybe a "What we're looking for" for the ideal team member traits.
3. Requirements: Required Credentials and Physical Requirements are clear lists.
4. Benefits: The benefits package is listed with bullet points.
5. Pay: $30-38 hourly depending on experience.
6. Schedule: Full-Time 40 hours weekly.
7. Location: 10630 Dean Martin Drive Las Vegas, NV (Southern Highlands)
Also there's mention of Incentive: Student Debt Benefit Program and annual bonus plan.
And continuing education opportunities worth up to $15,580 each year.
I need to include only sections with real content.
Let me structure:
- About the role (company description, mission, values)
- Qualifications (or Requirements) - including Required Credentials and Physical Requirements
- Benefits
- Pay
- Schedule
- Location (maybe as a short paragraph)
But the rules say use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I should use those standard headings.
I'll create:
About the role
... company description ...
Responsibilities
- but there's no explicit responsibilities list. The posting says "Our ideal team member is..." and lists qualities. That's more about qualifications. The questions are about fit. I could put those under "Qualifications" or "What we're looking for". However, the rules say include a section ONLY when the posting has real, specific content for it. Since there's no explicit responsibilities, I might skip Responsibilities heading. But the posting does describe the role: "helping our patients get back to athletics, work, life..." That's more about the role. I'll include a brief paragraph under About the role.
Maybe I can have a "Qualifications" section for the ideal team member traits and required credentials.
Let me read the rules again: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So I can choose which headings to use.
I'll do:
- About the role
- Qualifications (including required credentials, physical requirements, and ideal traits)
- Benefits
- Pay
- Schedule
- Location (maybe as a short paragraph under About the role or separate)
But location is metadata; the rules say "fold minor metadata into a short
or drop it." I'll include location in a short paragraph at the top or under About the role.
Also, the posting mentions "Incentive: Student Debt Benefit Program and annual bonus plan" - that's part of benefits.
And "continuing education opportunities worth up to $15,580 each year" - also benefits.
Now, I need to output ONLY the HTML fragment.
Let me write the HTML.
First, a paragraph for location and schedule/pay? The rules say do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So I can put location, schedule, pay in a short paragraph? But Pay and Schedule are required headings if they have content. The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states them, so I should create sections for Pay and Schedule.
But the rules also say "Prefer a few substantive sections over many thin ones." So I could combine Schedule and Pay into one section? But the example headings include separate Pay and Schedule. I'll keep them separate.
I'll start with a short paragraph for location and maybe the incentive.
Then sections.
Let me draft:
Location: 10630 Dean Martin Drive, Las Vegas, NV (Southern Highlands). Full-time, 40 hours per week. Hourly pay range: $30–38, depending on experience. Incentives include a Student Debt Benefit Program and annual bonus plan.
About the role
At Dignity/Select Medical, we take pride in creating an exceptional patient experience, helping patients return to athletics, work, life, and the things they love. Our mission is to deliver an exceptional patient care experience that promotes healing and recovery in a compassionate environment. We are the nation’s leading physical therapy provider with 1,900 centers in 39 states, offering internal mobility and specialties such as aquatics, sports medicine, neuro, pelvic, concussion, hand therapy, and more.
Our culture is guided by five Core Values: Quality, Integrity, Accountability, Teamwork, and Innovation. We deliver superior quality, set high standards, treat others with respect, communicate honestly, achieve objectives, and embrace change with poise.
Qualifications
Required credentials
- Successful completion of educational requirements mandated for state licensure or eligibility for a license in Physical Therapy Assisting.
- Current state licensure or eligibility for licensure in the state of practice.
- Cardio-Pulmonary Resuscitation (CPR) certification required.
Physical requirements
- Ability to lift patients using biomedical techniques frequently throughout the work day/shift.
- Capable of easily lifting fifty (50) pounds of weight alone.
- Ability to walk, bend, stand, and reach constantly during a work day/shift.
- Visual acuity (near and distant) sufficient to maintain accurate records, recognize people, and understand written direction.
- Ability to speak and hear sufficiently to understand and give directions.
- Ability to push wheeled equipment throughout the facility.
- Fine motor skills adequate for scheduling and preparing patients, equipment, and supplies for treatment.
- Ability to participate in sustained activities for many hours in duration in accordance with state labor laws.
Ideal team member
- Adaptable and flexible: willing to adjust to accommodate colleagues and patients.
- Patient-centric: the patient always comes first; treat every patient with care.
- Exceptional communicator: proactive and empathetic communication.
- Detail-oriented: ensure all details are done correctly the first time.
- Team player: integral part of a clinical team.
Benefits
- Mentorship and orientation programs for successful transition.
- Unmatched CEU program with paid national certifications; continuing education opportunities worth up to $15,580 per year, including APTA-accredited Orthopedic Residency Program, weekend classes, online education, and formal weekly mentoring for new grads.
- Student Debt Benefit Program to alleviate financial pressure of student debt.
- Generous paid time off for work-life balance.
- Comprehensive health benefits packages.
- Company-matching 401(k) retirement plans.
- Specialty tracks nationwide (aquatics, sports medicine, neuro, pelvic, concussion, hand therapy, and more).
- Internal mobility across 1,900 centers in 39 states.
- Annual bonus plan.
Pay
Hourly range: $30–38, depending on years of experience.
Schedule
Full-time, 40 hours per week.
But note: The rules say "Do NOT repeat the job title as a heading (the page already shows it)". I didn't.
Also, "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." I removed the "To apply..." line.
Now, check for any filler: "commensurate with experience" is not used; we have specific range.
The "Incentive" line is included in benefits and pay paragraph.
The continuing education value is specific.
I used for subheadings within Qualifications. The rules didn't forbid subheadings, but they said use for section headings. Using is okay for subsections. But to be safe, maybe just use for main sections and use
or
for subsections. However, the rules didn't specify subheadings. I think it's fine.
But the rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other heading levels. But to be safe, I'll avoid and instead use or just list items with bold? But semantic HTML: maybe use for main sections only. I'll keep the subheadings as but maybe the user expects only . The instruction: "use for section headings". It doesn't say exclusively, but I'll assume they want only for top-level sections. I'll make the subheadings as
...
or just incorporate into list items.
Better to keep it simple: Use for each main section, and within Qualifications, use a list with categories as bold text in list items? But that might be messy.
I'll restructure Qualifications as a single list with grouped items, but that loses structure. Alternatively, I can have multiple sections: "Required Credentials", "Physical Requirements", "Ideal Team Member". But the example headings include "Requirements, Qualifications, Skills". I could use "Requirements" for required credentials and physical requirements, and "Qualifications" for ideal team member. But the posting has "Required Credentials" and "Physical Requirements" as separate headings. I'll follow the posting's structure but map to allowed headings.
The allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
I can use:
- About the role
- Requirements (for required credentials and physical requirements)
- Qualifications (for ideal team member traits)
- Benefits
- Pay
- Schedule
That seems good.
Let me adjust
for prose. I must not include boilerplate like application instructions, EEO, etc. Let me extract substantive content: 1. About the role / Company: The description about Dignity/Select Medical, mission, core values, culture. This is substantive. 2. Responsibilities: Not explicitly listed as bullet points, but the "ideal team member" qualities and the questions give insight. However, the posting doesn't have a clear responsibilities list. I might need to infer from the description? The rules say preserve ALL substantive information. The posting describes the role indirectly. I could create a "Responsibilities" section with the qualities expected? But better to include the "ideal team member" and the questions as part of About the role or a separate "What we're looking for" section. The rules say use headings like Responsibilities, Requirements, Qualifications, Skills. I'll create a "Qualifications" or "Requirements" section for the required credentials and physical requirements. And maybe a "What we're looking for" for the ideal team member traits. 3. Requirements: Required Credentials and Physical Requirements are clear lists. 4. Benefits: The benefits package is listed with bullet points. 5. Pay: $30-38 hourly depending on experience. 6. Schedule: Full-Time 40 hours weekly. 7. Location: 10630 Dean Martin Drive Las Vegas, NV (Southern Highlands) Also there's mention of Incentive: Student Debt Benefit Program and annual bonus plan. And continuing education opportunities worth up to $15,580 each year. I need to include only sections with real content. Let me structure: - About the role (company description, mission, values) - Qualifications (or Requirements) - including Required Credentials and Physical Requirements - Benefits - Pay - Schedule - Location (maybe as a short paragraph) But the rules say use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I should use those standard headings. I'll create:
About the role
... company description ...
Responsibilities
- but there's no explicit responsibilities list. The posting says "Our ideal team member is..." and lists qualities. That's more about qualifications. The questions are about fit. I could put those under "Qualifications" or "What we're looking for". However, the rules say include a section ONLY when the posting has real, specific content for it. Since there's no explicit responsibilities, I might skip Responsibilities heading. But the posting does describe the role: "helping our patients get back to athletics, work, life..." That's more about the role. I'll include a brief paragraph under About the role. Maybe I can have a "Qualifications" section for the ideal team member traits and required credentials. Let me read the rules again: "usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So I can choose which headings to use. I'll do: - About the role - Qualifications (including required credentials, physical requirements, and ideal traits) - Benefits - Pay - Schedule - Location (maybe as a short paragraph under About the role or separate) But location is metadata; the rules say "fold minor metadata into a short
or drop it." I'll include location in a short paragraph at the top or under About the role. Also, the posting mentions "Incentive: Student Debt Benefit Program and annual bonus plan" - that's part of benefits. And "continuing education opportunities worth up to $15,580 each year" - also benefits. Now, I need to output ONLY the HTML fragment. Let me write the HTML. First, a paragraph for location and schedule/pay? The rules say do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So I can put location, schedule, pay in a short paragraph? But Pay and Schedule are required headings if they have content. The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states them, so I should create sections for Pay and Schedule. But the rules also say "Prefer a few substantive sections over many thin ones." So I could combine Schedule and Pay into one section? But the example headings include separate Pay and Schedule. I'll keep them separate. I'll start with a short paragraph for location and maybe the incentive. Then sections. Let me draft:
Location: 10630 Dean Martin Drive, Las Vegas, NV (Southern Highlands). Full-time, 40 hours per week. Hourly pay range: $30–38, depending on experience. Incentives include a Student Debt Benefit Program and annual bonus plan.
About the role
At Dignity/Select Medical, we take pride in creating an exceptional patient experience, helping patients return to athletics, work, life, and the things they love. Our mission is to deliver an exceptional patient care experience that promotes healing and recovery in a compassionate environment. We are the nation’s leading physical therapy provider with 1,900 centers in 39 states, offering internal mobility and specialties such as aquatics, sports medicine, neuro, pelvic, concussion, hand therapy, and more.
Our culture is guided by five Core Values: Quality, Integrity, Accountability, Teamwork, and Innovation. We deliver superior quality, set high standards, treat others with respect, communicate honestly, achieve objectives, and embrace change with poise.
Qualifications
Required credentials
- Successful completion of educational requirements mandated for state licensure or eligibility for a license in Physical Therapy Assisting.
- Current state licensure or eligibility for licensure in the state of practice.
- Cardio-Pulmonary Resuscitation (CPR) certification required.
Physical requirements
- Ability to lift patients using biomedical techniques frequently throughout the work day/shift.
- Capable of easily lifting fifty (50) pounds of weight alone.
- Ability to walk, bend, stand, and reach constantly during a work day/shift.
- Visual acuity (near and distant) sufficient to maintain accurate records, recognize people, and understand written direction.
- Ability to speak and hear sufficiently to understand and give directions.
- Ability to push wheeled equipment throughout the facility.
- Fine motor skills adequate for scheduling and preparing patients, equipment, and supplies for treatment.
- Ability to participate in sustained activities for many hours in duration in accordance with state labor laws.
Ideal team member
- Adaptable and flexible: willing to adjust to accommodate colleagues and patients.
- Patient-centric: the patient always comes first; treat every patient with care.
- Exceptional communicator: proactive and empathetic communication.
- Detail-oriented: ensure all details are done correctly the first time.
- Team player: integral part of a clinical team.
Benefits
- Mentorship and orientation programs for successful transition.
- Unmatched CEU program with paid national certifications; continuing education opportunities worth up to $15,580 per year, including APTA-accredited Orthopedic Residency Program, weekend classes, online education, and formal weekly mentoring for new grads.
- Student Debt Benefit Program to alleviate financial pressure of student debt.
- Generous paid time off for work-life balance.
- Comprehensive health benefits packages.
- Company-matching 401(k) retirement plans.
- Specialty tracks nationwide (aquatics, sports medicine, neuro, pelvic, concussion, hand therapy, and more).
- Internal mobility across 1,900 centers in 39 states.
- Annual bonus plan.
Pay
Hourly range: $30–38, depending on years of experience.
Schedule
Full-time, 40 hours per week.
But note: The rules say "Do NOT repeat the job title as a heading (the page already shows it)". I didn't. Also, "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." I removed the "To apply..." line. Now, check for any filler: "commensurate with experience" is not used; we have specific range. The "Incentive" line is included in benefits and pay paragraph. The continuing education value is specific. I used for subheadings within Qualifications. The rules didn't forbid subheadings, but they said use for section headings. Using is okay for subsections. But to be safe, maybe just use for main sections and use
is okay for subsections. But to be safe, maybe just use for main sections and use
or
- for subsections. However, the rules didn't specify subheadings. I think it's fine.
But the rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other heading levels. But to be safe, I'll avoid and instead use or just list items with bold? But semantic HTML: maybe use for main sections only. I'll keep the subheadings as but maybe the user expects only . The instruction: "use for section headings". It doesn't say exclusively, but I'll assume they want only for top-level sections. I'll make the subheadings as
...
or just incorporate into list items.
Better to keep it simple: Use for each main section, and within Qualifications, use a list with categories as bold text in list items? But that might be messy.
I'll restructure Qualifications as a single list with grouped items, but that loses structure. Alternatively, I can have multiple sections: "Required Credentials", "Physical Requirements", "Ideal Team Member". But the example headings include "Requirements, Qualifications, Skills". I could use "Requirements" for required credentials and physical requirements, and "Qualifications" for ideal team member. But the posting has "Required Credentials" and "Physical Requirements" as separate headings. I'll follow the posting's structure but map to allowed headings.
The allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
I can use:
- About the role
- Requirements (for required credentials and physical requirements)
- Qualifications (for ideal team member traits)
- Benefits
- Pay
- Schedule
That seems good.
Let me adjust
for main sections only. I'll keep the subheadings as but maybe the user expects only . The instruction: "use for section headings". It doesn't say exclusively, but I'll assume they want only for top-level sections. I'll make the subheadings as
. The instruction: "use for section headings". It doesn't say exclusively, but I'll assume they want only for top-level sections. I'll make the subheadings as
for top-level sections. I'll make the subheadings as
...
or just incorporate into list items. Better to keep it simple: Use