Advance Practice Provider
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 (the page already shows it)
- Do NOT put Job ID/requisition numbers as headings
- Fold minor metadata into short
or drop
- Preserve ALL substantive information
- Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, 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 parse the content:
The posting starts with "About the Company" - this is a section. It has prose about MyCare Medical.
Then "About the Role" with "Why Join Our Team:" and a list of bullet points (100% Outpatient care, On call services..., Competitive Salary..., Full Benefits Offered, Annual Performance Bonus..., Negotiable Relocation..., Malpractice Insurance..., Full support...). This is a list of benefits/perks. Could be under "Benefits" or "About the role". The rule says use headings like "Benefits" if present. The posting has "Full Benefits Offered" as a bullet point, but also a separate "Pay range and compensation package" section later. There's also "Responsibilities" section with bullet points.
"Qualifications" section with bullet points (some duplicated: "Certification through the American Academy of Nurse Practitioners (AANP) OR American Nurses Credentialing Center (ANCC)" appears twice). Also "Ideal Candidate, with a minimum of two years of experience as Nurse Practitioner", "Bilingual English Spanish speaking preferred", etc.
"Required Skills" section with bullet points.
"Preferred Skills" section with bullet points.
"Pay range and compensation package" section with prose about salary range $140,000-$145,000 (note: earlier it said $14,000-$145,000 but that's likely a typo; the later section says $140,000-$145,000). Also annual performance bonus up to 15%.
"Equal Opportunity Statement" - boilerplate, remove.
Also note: The posting has "Responsibilities" section with bullet points: Monday-Friday schedule, rotating on-call, eClinical Works, focus on continuity of care, integrated team-based care, prioritizing preventative care, comfortable managing adult-aged patient population.
Now, I need to decide on headings. The rules suggest using standard headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But only include if real content.
Let's map:
- About the Company: could be "About the company" or "About the role"? The rule says "About the role" as heading. But there is "About the Company" and "About the Role". I think we should include "About the company" as a section? The rule says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid "About the company". But the rule also says "Do NOT repeat the job title as a heading (the page already shows it)". The job title is not given in the text, but the user says "the page already shows it". So we can include "About the company" as a heading.
But the rule: "Prefer a few substantive sections over many thin ones." So maybe combine "About the Company" and "About the Role" into one "About the role" section? However, they are distinct. The posting has both. I'll keep both as separate sections.
But the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't list "About the company". But it's an example list. I think it's okay to include "About the company" as a heading.
Now, "Why Join Our Team" is a subsection under "About the Role". Could be a list under "About the role" heading.
The "Responsibilities" section is clear.
"Qualifications" section.
"Required Skills" and "Preferred Skills" could be combined under "Skills" heading with two sublists? Or separate headings? The rule says "Skills" as a heading. Could have "Required Skills" and "Preferred Skills" as subheadings? But the rule says use for section headings. Could use ? Not specified. Better to have one "Skills" heading with two sublists labeled "Required" and "Preferred". But the rule says use - for any list. Could do:
Skills
Required
...
Preferred
...
But the rule only mentions for section headings. It doesn't forbid . However, to keep it simple, maybe make two separate headings: "Required Skills" and "Preferred Skills". But the example list includes "Skills" as a heading. I'll combine under "Skills" with two lists.
Similarly, "Benefits" section: The "Why Join Our Team" list includes benefits: 100% Outpatient care, On call services, Competitive Salary, Full Benefits Offered, Annual Performance Bonus, Negotiable Relocation & Sign-On Bonuses, Malpractice Insurance Coverage, Full support. That's a benefits list. Also there is a separate "Pay range and compensation package" section. So we can have "Benefits" and "Pay" sections.
The "Pay range and compensation package" section has specific numbers: base salary $140,000-$145,000, annual performance bonus up to 15%. That's substantive.
The "Schedule" is mentioned in Responsibilities: Monday-Friday 8am-5pm, rotating on-call. Could be a "Schedule" section. But the rule says never create Schedule section unless posting actually states them. It does state schedule. So include.
Now, duplicate lines: The certification line appears twice. Should preserve but not duplicate? The rule says "Preserve ALL substantive information; do NOT invent or summarize away detail." But duplicated lines are likely a copy-paste error. Should we include both? Probably include once. But the rule says "Remove duplicated lines". So remove duplicate.
Also, the salary range earlier says $14,000-$145,000 (typo). The later section says $140,000-$145,000. We should use the correct one from the Pay section. The earlier one is likely a mistake. We'll use the Pay section.
Now, let's structure:
1. About the Company (prose)
2. About the Role (with "Why Join Our Team" list) - maybe combine into "About the role" heading with prose and list.
3. Responsibilities (list)
4. Qualifications (list)
5. Skills (with Required and Preferred sublists)
6. Benefits (list from Why Join Our Team? But those are already in About the Role. Might be redundant. The "Why Join Our Team" is essentially benefits. Could move that list to Benefits section. But the posting has it under About the Role. I'll keep it under About the Role as a list, and also have a Benefits section? That would duplicate. Better to have a Benefits section with that list, and About the Role can have a brief intro. However, the rule says "Prefer a few substantive sections over many thin ones." So maybe combine.
Let's think: The posting has "About the Role" with "Why Join Our Team:" and bullet points. That's essentially the benefits/perks. Then later there is "Pay range and compensation package". So we can have:
- About the Company
- About the Role (with a brief paragraph and then a list of why join/benefits)
- Responsibilities
- Qualifications
- Skills (Required and Preferred)
- Pay
- Schedule (maybe)
But the schedule is in Responsibilities. Could extract schedule into its own section.
The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states benefits in the Why Join list, states pay in Pay section, states schedule in Responsibilities. So we can create those sections.
But we must not have filler. So we need to decide.
I'll create:
About the Company
...
About the Role
...
(maybe a short intro)
... (Why Join Our Team list)
Responsibilities
...
Qualifications
...
Skills
Required
...
Preferred
...
Pay
...
Schedule
Monday–Friday, 8:00 AM – 5:00 PM; rotating on-call schedule.
But the schedule is also in Responsibilities. Could keep in Responsibilities and not create separate Schedule section. The rule says "never create Schedule section unless the posting actually states them." It does state them, but it's already in Responsibilities. Creating a separate Schedule section might be thin. I'll include schedule in Responsibilities list and not create separate section.
Similarly, Benefits are in Why Join list. Could create Benefits section with that list, but then About the Role would be thin. I'll keep Why Join list under About the Role.
Now, the "Full Benefits Offered" bullet point is vague. The list includes specific benefits: Competitive Salary, Annual Quality Bonus, Negotiable Relocation & Sign-On Bonuses, Malpractice Insurance Coverage, Full support. That's substantive.
Now, the "Equal Opportunity Statement" is boilerplate, remove.
Also, the "Certification through the American Academy of Nurse Practitioners (AANP) OR American Nurses Credentialing Center (ANCC)" appears twice. I'll include once.
The "Certification through the American Academy of Nurse Practitioners (AANP) OR American Nurses Credentialing Center (ANCC) program, focusing on adult medicine" and "Certification through an accredited PA certification program focusing on adult medicine" are separate? Actually the first line says "Certification through the American Academy of Nurse Practitioners (AANP) OR American Nurses Credentialing Center (ANCC)" and second line says "Certification through the American Academy of Nurse Practitioners (AANP) OR American Nurses Credentialing Center (ANCC) program, focusing on adult medicine". Might be duplicate. I'll combine.
Also "Currently licensed as an Acute, Adult/Gerontological or Family Nurse Pract
for prose - Do NOT repeat job title as heading (the page already shows it) - Do NOT put Job ID/requisition numbers as headings - Fold minor metadata into short
or drop - Preserve ALL substantive information - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, 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 parse the content: The posting starts with "About the Company" - this is a section. It has prose about MyCare Medical. Then "About the Role" with "Why Join Our Team:" and a list of bullet points (100% Outpatient care, On call services..., Competitive Salary..., Full Benefits Offered, Annual Performance Bonus..., Negotiable Relocation..., Malpractice Insurance..., Full support...). This is a list of benefits/perks. Could be under "Benefits" or "About the role". The rule says use headings like "Benefits" if present. The posting has "Full Benefits Offered" as a bullet point, but also a separate "Pay range and compensation package" section later. There's also "Responsibilities" section with bullet points. "Qualifications" section with bullet points (some duplicated: "Certification through the American Academy of Nurse Practitioners (AANP) OR American Nurses Credentialing Center (ANCC)" appears twice). Also "Ideal Candidate, with a minimum of two years of experience as Nurse Practitioner", "Bilingual English Spanish speaking preferred", etc. "Required Skills" section with bullet points. "Preferred Skills" section with bullet points. "Pay range and compensation package" section with prose about salary range $140,000-$145,000 (note: earlier it said $14,000-$145,000 but that's likely a typo; the later section says $140,000-$145,000). Also annual performance bonus up to 15%. "Equal Opportunity Statement" - boilerplate, remove. Also note: The posting has "Responsibilities" section with bullet points: Monday-Friday schedule, rotating on-call, eClinical Works, focus on continuity of care, integrated team-based care, prioritizing preventative care, comfortable managing adult-aged patient population. Now, I need to decide on headings. The rules suggest using standard headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But only include if real content. Let's map: - About the Company: could be "About the company" or "About the role"? The rule says "About the role" as heading. But there is "About the Company" and "About the Role". I think we should include "About the company" as a section? The rule says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid "About the company". But the rule also says "Do NOT repeat the job title as a heading (the page already shows it)". The job title is not given in the text, but the user says "the page already shows it". So we can include "About the company" as a heading.
But the rule: "Prefer a few substantive sections over many thin ones." So maybe combine "About the Company" and "About the Role" into one "About the role" section? However, they are distinct. The posting has both. I'll keep both as separate sections.
But the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't list "About the company". But it's an example list. I think it's okay to include "About the company" as a heading.
Now, "Why Join Our Team" is a subsection under "About the Role". Could be a list under "About the role" heading.
The "Responsibilities" section is clear.
"Qualifications" section.
"Required Skills" and "Preferred Skills" could be combined under "Skills" heading with two sublists? Or separate headings? The rule says "Skills" as a heading. Could have "Required Skills" and "Preferred Skills" as subheadings? But the rule says use for section headings. Could use ? Not specified. Better to have one "Skills" heading with two sublists labeled "Required" and "Preferred". But the rule says use - for any list. Could do:
Skills
Required
...
Preferred
...
But the rule only mentions for section headings. It doesn't forbid . However, to keep it simple, maybe make two separate headings: "Required Skills" and "Preferred Skills". But the example list includes "Skills" as a heading. I'll combine under "Skills" with two lists.
Similarly, "Benefits" section: The "Why Join Our Team" list includes benefits: 100% Outpatient care, On call services, Competitive Salary, Full Benefits Offered, Annual Performance Bonus, Negotiable Relocation & Sign-On Bonuses, Malpractice Insurance Coverage, Full support. That's a benefits list. Also there is a separate "Pay range and compensation package" section. So we can have "Benefits" and "Pay" sections.
The "Pay range and compensation package" section has specific numbers: base salary $140,000-$145,000, annual performance bonus up to 15%. That's substantive.
The "Schedule" is mentioned in Responsibilities: Monday-Friday 8am-5pm, rotating on-call. Could be a "Schedule" section. But the rule says never create Schedule section unless posting actually states them. It does state schedule. So include.
Now, duplicate lines: The certification line appears twice. Should preserve but not duplicate? The rule says "Preserve ALL substantive information; do NOT invent or summarize away detail." But duplicated lines are likely a copy-paste error. Should we include both? Probably include once. But the rule says "Remove duplicated lines". So remove duplicate.
Also, the salary range earlier says $14,000-$145,000 (typo). The later section says $140,000-$145,000. We should use the correct one from the Pay section. The earlier one is likely a mistake. We'll use the Pay section.
Now, let's structure:
1. About the Company (prose)
2. About the Role (with "Why Join Our Team" list) - maybe combine into "About the role" heading with prose and list.
3. Responsibilities (list)
4. Qualifications (list)
5. Skills (with Required and Preferred sublists)
6. Benefits (list from Why Join Our Team? But those are already in About the Role. Might be redundant. The "Why Join Our Team" is essentially benefits. Could move that list to Benefits section. But the posting has it under About the Role. I'll keep it under About the Role as a list, and also have a Benefits section? That would duplicate. Better to have a Benefits section with that list, and About the Role can have a brief intro. However, the rule says "Prefer a few substantive sections over many thin ones." So maybe combine.
Let's think: The posting has "About the Role" with "Why Join Our Team:" and bullet points. That's essentially the benefits/perks. Then later there is "Pay range and compensation package". So we can have:
- About the Company
- About the Role (with a brief paragraph and then a list of why join/benefits)
- Responsibilities
- Qualifications
- Skills (Required and Preferred)
- Pay
- Schedule (maybe)
But the schedule is in Responsibilities. Could extract schedule into its own section.
The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states benefits in the Why Join list, states pay in Pay section, states schedule in Responsibilities. So we can create those sections.
But we must not have filler. So we need to decide.
I'll create:
About the Company
...
About the Role
...
(maybe a short intro)
... (Why Join Our Team list)
Responsibilities
...
Qualifications
...
Skills
Required
...
Preferred
...
Pay
...
Schedule
Monday–Friday, 8:00 AM – 5:00 PM; rotating on-call schedule.
But the schedule is also in Responsibilities. Could keep in Responsibilities and not create separate Schedule section. The rule says "never create Schedule section unless the posting actually states them." It does state them, but it's already in Responsibilities. Creating a separate Schedule section might be thin. I'll include schedule in Responsibilities list and not create separate section.
Similarly, Benefits are in Why Join list. Could create Benefits section with that list, but then About the Role would be thin. I'll keep Why Join list under About the Role.
Now, the "Full Benefits Offered" bullet point is vague. The list includes specific benefits: Competitive Salary, Annual Quality Bonus, Negotiable Relocation & Sign-On Bonuses, Malpractice Insurance Coverage, Full support. That's substantive.
Now, the "Equal Opportunity Statement" is boilerplate, remove.
Also, the "Certification through the American Academy of Nurse Practitioners (AANP) OR American Nurses Credentialing Center (ANCC)" appears twice. I'll include once.
The "Certification through the American Academy of Nurse Practitioners (AANP) OR American Nurses Credentialing Center (ANCC) program, focusing on adult medicine" and "Certification through an accredited PA certification program focusing on adult medicine" are separate? Actually the first line says "Certification through the American Academy of Nurse Practitioners (AANP) OR American Nurses Credentialing Center (ANCC)" and second line says "Certification through the American Academy of Nurse Practitioners (AANP) OR American Nurses Credentialing Center (ANCC) program, focusing on adult medicine". Might be duplicate. I'll combine.
Also "Currently licensed as an Acute, Adult/Gerontological or Family Nurse Pract
for section headings. Could use ? Not specified. Better to have one "Skills" heading with two sublists labeled "Required" and "Preferred". But the rule says use - for any list. Could do:
Skills
Required
...
Preferred
...
But the rule only mentions for section headings. It doesn't forbid . However, to keep it simple, maybe make two separate headings: "Required Skills" and "Preferred Skills". But the example list includes "Skills" as a heading. I'll combine under "Skills" with two lists.
Similarly, "Benefits" section: The "Why Join Our Team" list includes benefits: 100% Outpatient care, On call services, Competitive Salary, Full Benefits Offered, Annual Performance Bonus, Negotiable Relocation & Sign-On Bonuses, Malpractice Insurance Coverage, Full support. That's a benefits list. Also there is a separate "Pay range and compensation package" section. So we can have "Benefits" and "Pay" sections.
The "Pay range and compensation package" section has specific numbers: base salary $140,000-$145,000, annual performance bonus up to 15%. That's substantive.
The "Schedule" is mentioned in Responsibilities: Monday-Friday 8am-5pm, rotating on-call. Could be a "Schedule" section. But the rule says never create Schedule section unless posting actually states them. It does state schedule. So include.
Now, duplicate lines: The certification line appears twice. Should preserve but not duplicate? The rule says "Preserve ALL substantive information; do NOT invent or summarize away detail." But duplicated lines are likely a copy-paste error. Should we include both? Probably include once. But the rule says "Remove duplicated lines". So remove duplicate.
Also, the salary range earlier says $14,000-$145,000 (typo). The later section says $140,000-$145,000. We should use the correct one from the Pay section. The earlier one is likely a mistake. We'll use the Pay section.
Now, let's structure:
1. About the Company (prose)
2. About the Role (with "Why Join Our Team" list) - maybe combine into "About the role" heading with prose and list.
3. Responsibilities (list)
4. Qualifications (list)
5. Skills (with Required and Preferred sublists)
6. Benefits (list from Why Join Our Team? But those are already in About the Role. Might be redundant. The "Why Join Our Team" is essentially benefits. Could move that list to Benefits section. But the posting has it under About the Role. I'll keep it under About the Role as a list, and also have a Benefits section? That would duplicate. Better to have a Benefits section with that list, and About the Role can have a brief intro. However, the rule says "Prefer a few substantive sections over many thin ones." So maybe combine.
Let's think: The posting has "About the Role" with "Why Join Our Team:" and bullet points. That's essentially the benefits/perks. Then later there is "Pay range and compensation package". So we can have:
- About the Company
- About the Role (with a brief paragraph and then a list of why join/benefits)
- Responsibilities
- Qualifications
- Skills (Required and Preferred)
- Pay
- Schedule (maybe)
But the schedule is in Responsibilities. Could extract schedule into its own section.
The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states benefits in the Why Join list, states pay in Pay section, states schedule in Responsibilities. So we can create those sections.
But we must not have filler. So we need to decide.
I'll create:
About the Company
...
About the Role
...
(maybe a short intro)
... (Why Join Our Team list)
Responsibilities
...
Qualifications
...
Skills
Required
...
Preferred
...
Pay
...
Schedule
Monday–Friday, 8:00 AM – 5:00 PM; rotating on-call schedule.
But the schedule is also in Responsibilities. Could keep in Responsibilities and not create separate Schedule section. The rule says "never create Schedule section unless the posting actually states them." It does state them, but it's already in Responsibilities. Creating a separate Schedule section might be thin. I'll include schedule in Responsibilities list and not create separate section.
Similarly, Benefits are in Why Join list. Could create Benefits section with that list, but then About the Role would be thin. I'll keep Why Join list under About the Role.
Now, the "Full Benefits Offered" bullet point is vague. The list includes specific benefits: Competitive Salary, Annual Quality Bonus, Negotiable Relocation & Sign-On Bonuses, Malpractice Insurance Coverage, Full support. That's substantive.
Now, the "Equal Opportunity Statement" is boilerplate, remove.
Also, the "Certification through the American Academy of Nurse Practitioners (AANP) OR American Nurses Credentialing Center (ANCC)" appears twice. I'll include once.
The "Certification through the American Academy of Nurse Practitioners (AANP) OR American Nurses Credentialing Center (ANCC) program, focusing on adult medicine" and "Certification through an accredited PA certification program focusing on adult medicine" are separate? Actually the first line says "Certification through the American Academy of Nurse Practitioners (AANP) OR American Nurses Credentialing Center (ANCC)" and second line says "Certification through the American Academy of Nurse Practitioners (AANP) OR American Nurses Credentialing Center (ANCC) program, focusing on adult medicine". Might be duplicate. I'll combine.
Also "Currently licensed as an Acute, Adult/Gerontological or Family Nurse Pract
- for any list. Could do:
Skills
Required
- ...
Preferred
- ...
for section headings. It doesn't forbid
. However, to keep it simple, maybe make two separate
headings: "Required Skills" and "Preferred Skills". But the example list includes "Skills" as a heading. I'll combine under "Skills" with two lists. Similarly, "Benefits" section: The "Why Join Our Team" list includes benefits: 100% Outpatient care, On call services, Competitive Salary, Full Benefits Offered, Annual Performance Bonus, Negotiable Relocation & Sign-On Bonuses, Malpractice Insurance Coverage, Full support. That's a benefits list. Also there is a separate "Pay range and compensation package" section. So we can have "Benefits" and "Pay" sections. The "Pay range and compensation package" section has specific numbers: base salary $140,000-$145,000, annual performance bonus up to 15%. That's substantive. The "Schedule" is mentioned in Responsibilities: Monday-Friday 8am-5pm, rotating on-call. Could be a "Schedule" section. But the rule says never create Schedule section unless posting actually states them. It does state schedule. So include. Now, duplicate lines: The certification line appears twice. Should preserve but not duplicate? The rule says "Preserve ALL substantive information; do NOT invent or summarize away detail." But duplicated lines are likely a copy-paste error. Should we include both? Probably include once. But the rule says "Remove duplicated lines". So remove duplicate. Also, the salary range earlier says $14,000-$145,000 (typo). The later section says $140,000-$145,000. We should use the correct one from the Pay section. The earlier one is likely a mistake. We'll use the Pay section. Now, let's structure: 1. About the Company (prose) 2. About the Role (with "Why Join Our Team" list) - maybe combine into "About the role" heading with prose and list. 3. Responsibilities (list) 4. Qualifications (list) 5. Skills (with Required and Preferred sublists) 6. Benefits (list from Why Join Our Team? But those are already in About the Role. Might be redundant. The "Why Join Our Team" is essentially benefits. Could move that list to Benefits section. But the posting has it under About the Role. I'll keep it under About the Role as a list, and also have a Benefits section? That would duplicate. Better to have a Benefits section with that list, and About the Role can have a brief intro. However, the rule says "Prefer a few substantive sections over many thin ones." So maybe combine. Let's think: The posting has "About the Role" with "Why Join Our Team:" and bullet points. That's essentially the benefits/perks. Then later there is "Pay range and compensation package". So we can have: - About the Company - About the Role (with a brief paragraph and then a list of why join/benefits) - Responsibilities - Qualifications - Skills (Required and Preferred) - Pay - Schedule (maybe) But the schedule is in Responsibilities. Could extract schedule into its own section. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states benefits in the Why Join list, states pay in Pay section, states schedule in Responsibilities. So we can create those sections. But we must not have filler. So we need to decide. I'll create:
About the Company
...
About the Role
...
(maybe a short intro)- ... (Why Join Our Team list)
Responsibilities
- ...
Qualifications
- ...
Skills
Required
- ...
Preferred
- ...
Pay
...
Schedule
Monday–Friday, 8:00 AM – 5:00 PM; rotating on-call schedule.
But the schedule is also in Responsibilities. Could keep in Responsibilities and not create separate Schedule section. The rule says "never create Schedule section unless the posting actually states them." It does state them, but it's already in Responsibilities. Creating a separate Schedule section might be thin. I'll include schedule in Responsibilities list and not create separate section. Similarly, Benefits are in Why Join list. Could create Benefits section with that list, but then About the Role would be thin. I'll keep Why Join list under About the Role. Now, the "Full Benefits Offered" bullet point is vague. The list includes specific benefits: Competitive Salary, Annual Quality Bonus, Negotiable Relocation & Sign-On Bonuses, Malpractice Insurance Coverage, Full support. That's substantive. Now, the "Equal Opportunity Statement" is boilerplate, remove. Also, the "Certification through the American Academy of Nurse Practitioners (AANP) OR American Nurses Credentialing Center (ANCC)" appears twice. I'll include once. The "Certification through the American Academy of Nurse Practitioners (AANP) OR American Nurses Credentialing Center (ANCC) program, focusing on adult medicine" and "Certification through an accredited PA certification program focusing on adult medicine" are separate? Actually the first line says "Certification through the American Academy of Nurse Practitioners (AANP) OR American Nurses Credentialing Center (ANCC)" and second line says "Certification through the American Academy of Nurse Practitioners (AANP) OR American Nurses Credentialing Center (ANCC) program, focusing on adult medicine". Might be duplicate. I'll combine. Also "Currently licensed as an Acute, Adult/Gerontological or Family Nurse Pract