Open Rank (Asst/Assoc/Prof)
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. 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. 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.
We need to decide which sections to include based on content.
Content includes:
- About the university (Get to Know Us!): description of Marshall University, mission, etc. Could be "About the role"? Actually "About the role" is generic; but we could use "About the role" to describe the position? However we have a description of the university, not the role. The instructions say we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings.
We have:
- Position Information: Banner Position Number, Position Title, Classification Title, Department. These are metadata; we should fold minor metadata into a short
or drop it. Probably we can include a short paragraph with position details (title, department, location, etc.) but not as headings.
- Job Description: includes responsibilities: teaching and curricular development within DPT program, primary need teaching gross anatomy, additional areas: diagnostic imaging, musculoskeletal pathology, physiology, foundational clinical skills. Teaching responsibilities may be adjusted. Faculty member will engage in independent and collaborative team teaching. Teaching and advising students, developing and sustaining active scholarly agenda, participating in service activities, contributing to curriculum development and program assessment, limited release time may be available to support clinical practice.
- Location: OTHR - Other Off-Campus Location.
- Salary Range: "Rank and salary are competitive and commensurate with academic preparation and experience." That's vague; we should NOT create Pay section unless posting actually states them. This is vague, not a specific number or range. According to instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Also never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should NOT include a Pay section.
- Benefits: The posting includes a lot about benefits: Work week 37.5 hrs, Winter break almost two weeks off, Holidays – 13 Paid Holidays, Annual and Sick Leave details, Health Insurance, Educational/Tuition Benefits, Retirement Plans, Life Insurance, Wellness Programs. That's substantive benefits info. So we should include a Benefits section with list.
- Qualifications: Required Qualifications (Education, license, terminal degree) and Experience (minimum five years clinical experience, gross anatomy experience, ability to contribute in team-teaching, strong communication). Preferred Qualifications (education, experience, scholarly productivity, ABPTS certification, APTA engagement). So we should have a Requirements or Qualifications section. The instructions list both Requirements and Qualifications as possible headings. We need to decide which to use. Could combine required and preferred under Qualifications? Or separate? Probably we can have a "Qualifications" section with subheadings? But we only allowed headings from list; we cannot add custom headings like "Required Qualifications". We could put all qualifications under a single Qualifications section, using
- for each item, maybe marking required vs preferred in text. Or we could have two sections: Requirements and Qualifications? But that might be thin. Better to have one Qualifications section containing both required and preferred, maybe with notes.
- Responsibilities: we have duties listed; we can put under Responsibilities.
- Skills: maybe not explicitly listed; we have strong communication and interpersonal skills, ability to contribute within collaborative team-teaching environment. Could be under Skills.
- About the role: we could use About the role to describe the position overview (the job description summary). Or we could use About the role for the university description? The instructions gave examples; we can choose.
We need to avoid duplication and boilerplate. Remove application instructions, supplemental questions, etc.
We need to preserve all substantive information. So we need to include all details from job description, qualifications, benefits, etc.
We must not include metadata like Banner Position Number, Position Title (already shown), Classification Title, Department? Might be considered minor metadata; we can fold into a short paragraph.
We must not include Job ID/requisition numbers as headings; we can drop them or put in a short p.
We must not include the "Open Date", "Close Date", "Posting Number", "Special Instructions", "Supplemental Questions", etc. Those are application instructions/boilerplate; drop.
We must not include the "Come Meet Marshall..." etc? That's part of university description; keep.
We must not include the "We are . . . Marshall!" incomplete; keep as is? It's part of description.
We must not include the "Marshall University Research Corporation (MURC) employees have different benefit options than those listed below." That's part of benefits description; keep.
We must not include the "Work week is 37.5 hrs." etc; that's benefits.
We must not include the "Employee Leave" heading inside benefits; we can incorporate.
We need to output only HTML fragment, no /, no markdown fences.
Let's structure:
Position: Open Rank (Asst/Assoc/Prof) Assistant Professor, Department of COHP-Physical Therapy - MU9540, Location: OTHR - Other Off-Campus Location.
Then sections:
About the role
... description of Marshall University and the position? Actually About the role could be a brief overview of the position: The School of Physical Therapy invites applications for a 12-month, full-time, tenure-track faculty position at the rank of Assistant, Associate, or Full Professor starting January 2027. The successful candidate will contribute to teaching and curricular development within the Doctor of Physical Therapy program. Primary need for teaching is in gross anatomy. Additional areas include diagnostic imaging, musculoskeletal pathology, physiology (medical and exercise), and foundational clinical skills. Teaching responsibilities may be adjusted based on program needs and candidate’s expertise. The faculty member will engage in both independent and collaborative team teaching, teaching and advising students, developing and sustaining an active scholarly agenda, participating in service activities, contributing to curriculum development and program assessment, with limited release time available to support clinical practice.
That captures responsibilities too; but we also need Responsibilities section maybe separate. However we could combine About the role and Responsibilities? The instruction says prefer a few substantive sections over many thin ones. So we could have About the role covering overview and responsibilities, and Qualifications covering requirements, and Benefits covering benefits. That's three sections.
We need to ensure we don't miss any substantive info: The university mission description (Get to Know Us!) is substantive; we could include that in About the role or maybe a separate section like "About Marshall University". But not in allowed headings. Could we put it under About the role? That might be stretching but okay. The instructions say use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings only. So we should stick to those.
Thus we need to fit university description somewhere; maybe under About the role we can include both university overview and role overview. That's acceptable.
Now responsibilities: we could include them in About the role as well, but maybe better to have a Responsibilities section for duties. However that would increase sections. But we can combine.
Qualifications: we need to list required and preferred.
Benefits: we need to list all benefits.
Let's decide to have three sections: About the role (includes university description and position overview), Qualifications (required and preferred), Benefits.
We must not create Pay or Schedule sections.
Now we need to format lists with - .
For Qualifications, we can separate required and preferred using maybe Required: etc inside
- or separate
for each? Could do - Required: ...
etc but that mixes. Better to have two sub-lists: maybe Required Qualifications
but not allowed. So we can just list all qualifications with notes.
We must preserve all specifics: Education: Earned degree in physical therapy (PT, MPT, or DPT). Current unrestricted PT license in a US jurisdiction, with eligibility for licensure in WV. Earned terminal academic degree (PhD, EdD, DSc, or equivalent) in a related discipline. Applicants holding a DPT degree with board certification through ABPTS will also be considered; however, candidates without a terminal academic degree will be expected to enroll in an approved academic doctoral program within one year of appointment.
Experience: Minimum of five years of full-time clinical experience (or equivalent part-time experience). Demonstrated experience in gross anatomy, including experience with human cadaveric dissection. Ability to contribute effectively within a collaborative team-teaching environment. Strong communication and interpersonal skills.
Preferred Qualifications: Education: Prior teaching experience in an entry-level DPT program. Evidence of scholarly productivity, including peer-reviewed publications and/or professional presentations. Preference for candidates who hold both a terminal academic degree and ABPTS board certification. Active engagement in the profession, including membership and participation in the American Physical Therapy Association (APTA).
We also have "Education" repeated; we can combine.
Now Benefits: details:
- Work week is 37.5 hrs.
- Great highlight in December: Marshall University employees receive almost two weeks off for Winter Break!
- Holidays – Employees receive 13 Paid Holidays
- Annual and Sick Leave – Classified Staff, Non-Classified Staff and 12-month Faculty earn up to 24 days of annual leave per year (max 360 hours) and up to 18 days of sick leave per year.
- Employee Leave (maybe redundant)
- Health Insurance – Marshall University offers health insurance through West Virginia Public Employees Insurance Agency (PEIA). There are seven (7) health benefit plans.
- Educational/Tuition Benefits – Marshall University provides tuition benefits to regular employees (after probationary period) and their dependent children.
- Retirement Plans – Marshall University offers retirement through Teachers Insurance and Annuity Association (TIAA). Full-time benefits eligible employees must participate in the mandated retirement plan (401(a)).
- Life Insurance – Basic term life insurance ($10,000) at no cost and may purchase optional life insurance coverage with pre-tax earnings.
- Wellness Programs – PEIA provides various care management programs and the Pathways to Wellness program.
- Also "We are . . . Marshall!" incomplete; ignore.
We should also include "Marshall University Research Corporation (MURC) employees have different benefit options than those listed below." That's a note.
We need to preserve all substantive info; we can include that note as a sentence.
for prose. 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. 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. We need to decide which sections to include based on content. Content includes: - About the university (Get to Know Us!): description of Marshall University, mission, etc. Could be "About the role"? Actually "About the role" is generic; but we could use "About the role" to describe the position? However we have a description of the university, not the role. The instructions say we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings. We have: - Position Information: Banner Position Number, Position Title, Classification Title, Department. These are metadata; we should fold minor metadata into a short
or drop it. Probably we can include a short paragraph with position details (title, department, location, etc.) but not as headings. - Job Description: includes responsibilities: teaching and curricular development within DPT program, primary need teaching gross anatomy, additional areas: diagnostic imaging, musculoskeletal pathology, physiology, foundational clinical skills. Teaching responsibilities may be adjusted. Faculty member will engage in independent and collaborative team teaching. Teaching and advising students, developing and sustaining active scholarly agenda, participating in service activities, contributing to curriculum development and program assessment, limited release time may be available to support clinical practice. - Location: OTHR - Other Off-Campus Location. - Salary Range: "Rank and salary are competitive and commensurate with academic preparation and experience." That's vague; we should NOT create Pay section unless posting actually states them. This is vague, not a specific number or range. According to instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Also never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should NOT include a Pay section. - Benefits: The posting includes a lot about benefits: Work week 37.5 hrs, Winter break almost two weeks off, Holidays – 13 Paid Holidays, Annual and Sick Leave details, Health Insurance, Educational/Tuition Benefits, Retirement Plans, Life Insurance, Wellness Programs. That's substantive benefits info. So we should include a Benefits section with list. - Qualifications: Required Qualifications (Education, license, terminal degree) and Experience (minimum five years clinical experience, gross anatomy experience, ability to contribute in team-teaching, strong communication). Preferred Qualifications (education, experience, scholarly productivity, ABPTS certification, APTA engagement). So we should have a Requirements or Qualifications section. The instructions list both Requirements and Qualifications as possible headings. We need to decide which to use. Could combine required and preferred under Qualifications? Or separate? Probably we can have a "Qualifications" section with subheadings? But we only allowed headings from list; we cannot add custom headings like "Required Qualifications". We could put all qualifications under a single Qualifications section, using
- for each item, maybe marking required vs preferred in text. Or we could have two sections: Requirements and Qualifications? But that might be thin. Better to have one Qualifications section containing both required and preferred, maybe with notes.
- Responsibilities: we have duties listed; we can put under Responsibilities.
- Skills: maybe not explicitly listed; we have strong communication and interpersonal skills, ability to contribute within collaborative team-teaching environment. Could be under Skills.
- About the role: we could use About the role to describe the position overview (the job description summary). Or we could use About the role for the university description? The instructions gave examples; we can choose.
We need to avoid duplication and boilerplate. Remove application instructions, supplemental questions, etc.
We need to preserve all substantive information. So we need to include all details from job description, qualifications, benefits, etc.
We must not include metadata like Banner Position Number, Position Title (already shown), Classification Title, Department? Might be considered minor metadata; we can fold into a short paragraph.
We must not include Job ID/requisition numbers as headings; we can drop them or put in a short p.
We must not include the "Open Date", "Close Date", "Posting Number", "Special Instructions", "Supplemental Questions", etc. Those are application instructions/boilerplate; drop.
We must not include the "Come Meet Marshall..." etc? That's part of university description; keep.
We must not include the "We are . . . Marshall!" incomplete; keep as is? It's part of description.
We must not include the "Marshall University Research Corporation (MURC) employees have different benefit options than those listed below." That's part of benefits description; keep.
We must not include the "Work week is 37.5 hrs." etc; that's benefits.
We must not include the "Employee Leave" heading inside benefits; we can incorporate.
We need to output only HTML fragment, no /, no markdown fences.
Let's structure:
Position: Open Rank (Asst/Assoc/Prof) Assistant Professor, Department of COHP-Physical Therapy - MU9540, Location: OTHR - Other Off-Campus Location.
Then sections:About the role
... description of Marshall University and the position? Actually About the role could be a brief overview of the position: The School of Physical Therapy invites applications for a 12-month, full-time, tenure-track faculty position at the rank of Assistant, Associate, or Full Professor starting January 2027. The successful candidate will contribute to teaching and curricular development within the Doctor of Physical Therapy program. Primary need for teaching is in gross anatomy. Additional areas include diagnostic imaging, musculoskeletal pathology, physiology (medical and exercise), and foundational clinical skills. Teaching responsibilities may be adjusted based on program needs and candidate’s expertise. The faculty member will engage in both independent and collaborative team teaching, teaching and advising students, developing and sustaining an active scholarly agenda, participating in service activities, contributing to curriculum development and program assessment, with limited release time available to support clinical practice.
That captures responsibilities too; but we also need Responsibilities section maybe separate. However we could combine About the role and Responsibilities? The instruction says prefer a few substantive sections over many thin ones. So we could have About the role covering overview and responsibilities, and Qualifications covering requirements, and Benefits covering benefits. That's three sections. We need to ensure we don't miss any substantive info: The university mission description (Get to Know Us!) is substantive; we could include that in About the role or maybe a separate section like "About Marshall University". But not in allowed headings. Could we put it under About the role? That might be stretching but okay. The instructions say usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings only. So we should stick to those. Thus we need to fit university description somewhere; maybe under About the role we can include both university overview and role overview. That's acceptable. Now responsibilities: we could include them in About the role as well, but maybe better to have a Responsibilities section for duties. However that would increase sections. But we can combine. Qualifications: we need to list required and preferred. Benefits: we need to list all benefits. Let's decide to have three sections: About the role (includes university description and position overview), Qualifications (required and preferred), Benefits. We must not create Pay or Schedule sections. Now we need to format lists with
- . For Qualifications, we can separate required and preferred using maybe Required: etc inside
- or separate
- for each? Could do
- Required: ... etc but that mixes. Better to have two sub-lists: maybe
Required Qualifications
but not allowed. So we can just list all qualifications with notes. We must preserve all specifics: Education: Earned degree in physical therapy (PT, MPT, or DPT). Current unrestricted PT license in a US jurisdiction, with eligibility for licensure in WV. Earned terminal academic degree (PhD, EdD, DSc, or equivalent) in a related discipline. Applicants holding a DPT degree with board certification through ABPTS will also be considered; however, candidates without a terminal academic degree will be expected to enroll in an approved academic doctoral program within one year of appointment. Experience: Minimum of five years of full-time clinical experience (or equivalent part-time experience). Demonstrated experience in gross anatomy, including experience with human cadaveric dissection. Ability to contribute effectively within a collaborative team-teaching environment. Strong communication and interpersonal skills. Preferred Qualifications: Education: Prior teaching experience in an entry-level DPT program. Evidence of scholarly productivity, including peer-reviewed publications and/or professional presentations. Preference for candidates who hold both a terminal academic degree and ABPTS board certification. Active engagement in the profession, including membership and participation in the American Physical Therapy Association (APTA). We also have "Education" repeated; we can combine. Now Benefits: details: - Work week is 37.5 hrs. - Great highlight in December: Marshall University employees receive almost two weeks off for Winter Break! - Holidays – Employees receive 13 Paid Holidays - Annual and Sick Leave – Classified Staff, Non-Classified Staff and 12-month Faculty earn up to 24 days of annual leave per year (max 360 hours) and up to 18 days of sick leave per year. - Employee Leave (maybe redundant) - Health Insurance – Marshall University offers health insurance through West Virginia Public Employees Insurance Agency (PEIA). There are seven (7) health benefit plans. - Educational/Tuition Benefits – Marshall University provides tuition benefits to regular employees (after probationary period) and their dependent children. - Retirement Plans – Marshall University offers retirement through Teachers Insurance and Annuity Association (TIAA). Full-time benefits eligible employees must participate in the mandated retirement plan (401(a)). - Life Insurance – Basic term life insurance ($10,000) at no cost and may purchase optional life insurance coverage with pre-tax earnings. - Wellness Programs – PEIA provides various care management programs and the Pathways to Wellness program. - Also "We are . . . Marshall!" incomplete; ignore. We should also include "Marshall University Research Corporation (MURC) employees have different benefit options than those listed below." That's a note. We need to preserve all substantive info; we can include that note as a sentence.