Contract Coordinator
WPS—A health solutions company · North Carolina, United States · 1 mo ago
RemoteRemoteAdministrative$23–$25/hrFull-time
We need to produce HTML fragment with sections: About the role (maybe Role Snapshot?), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use for headings. Use
for headings. Use - for any list of duties/requirements/benefits. Use
for prose. Do NOT repeat job title as heading (the page already shows it). Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones.
We need to extract substantive info from the posting.
Let's parse:
Role Snapshot: description: "The Contract Coordinator is accountable to maintain and strengthen WPS provider networks by managing existing provider contracts and prospecting and proposing new contracts based on adequacy needs and financial considerations. The role serves as a liaison between WPS and the provider community."
That's a prose description. Could be "About the role" or "Role Snapshot". Use heading
About the role
maybe.
Hourly Rate of Pay $23.00-25.00/hourly -> Pay section.
Work Location: list of states remote work allowed. That's location info; could be part of Schedule? Not exactly. Could be part of "Work Location" but not a required heading. We could include under "Schedule" maybe? Actually schedule is work hours: 8am-5pm Central Time, Monday-Friday. So schedule section.
Remote Work Requirements: high speed cable or fiber internet, minimum 10 Mbps downstream and at least 1 Mbps upstream. That's a requirement; could be part of Requirements or Qualifications.
Minimum Qualifications: Associate degree in Business, Marketing, Healthcare Administration, or related field OR equivalent post high school education and/or work-related experience. Two (2) or more years of customer service experience related to the health insurance industry to include provider contracting, provider relations or healthcare administration. Strong analytical skills with ability to prepare and interpret reports (e.g. network analysis, RFP support). Excellent written and verbal communication skills. Strong organizational and time management skills with proven attention to detail.
That's qualifications and skills.
Benefits: list: Remote work options available; Performance bonus and/or merit increase opportunities; 401(k) with a 100% match for the first 3% of your salary and a 50% match for the next 2% of your salary (100% vested immediately); Competitive paid time off; Health insurance, dental insurance, and telehealth services start DAY 1; Professional and Leadership Development Programs; Review additional benefits: (link). So we have benefits.
Who We Are: description of company. Could be "About the company" but not required heading; maybe we can include under "About the role"? But we have "About the role" already. Could add a separate section "About WPS" but not in prescribed headings list. The headings list includes: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those.
Responsibilities: The role snapshot includes responsibilities: maintain and strengthen WPS provider networks by managing existing provider contracts and prospecting and proposing new contracts based on adequacy needs and financial considerations; serve as liaison between WPS and provider community. Could be responsibilities.
Requirements: maybe remote work requirements? Or minimum qualifications? The distinction: Requirements could be mandatory items like education, experience, remote work internet. Qualifications could be preferred? But we have both. We'll decide: Requirements: education and experience (minimum qualifications). Skills: analytical, communication, organizational, time management, attention to detail. Qualifications maybe same as requirements? Actually they listed "Minimum Qualifications". So we can put that under Requirements. Then Skills under Skills.
Pay: hourly rate.
Schedule: work hours.
Benefits: list.
We need to avoid filler like "commensurate with experience", etc. Not present.
We need to remove duplicated lines, boilerplate like "Sign up for Job Alerts FOLLOW US! Instagram LinkedIn Facebook WPS Health Blog". Also "Review additional benefits: (https://...)" maybe we keep as link? It's part of benefits but could be considered boilerplate? It's a link to additional benefits; we could keep as part of benefits list but maybe it's okay. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link to additional benefits is not exactly boilerplate but could be considered navigation? It's a link to benefits page; maybe we keep it as part of benefits.
We also need to not include "Who We Are" and "Culture Drives Our Success" sections unless we map them to headings. They are not in headings list; we could omit them as they are not required. But we must preserve ALL substantive information; do NOT invent or summarize away detail. If we omit "Who We Are" and culture, we lose substantive info about the company. However the instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It does not require us to include all possible headings; we can choose to include only those that have content. But we must preserve ALL substantive information; we cannot discard substantive info. So we need to include that info somewhere, perhaps under "About the role" or another heading like "About the company". But the allowed headings list includes "About the role". Could we put company info under "About the role"? That might be odd but permissible? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we could also use other headings? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections; but we could also add other headings if needed? The instruction: "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." So we should create sections only for those headings that have content. It doesn't forbid other headings, but the examples given are those. Likely they expect us to use those headings only. So we need to fit all substantive info into those sections.
We can put company description under "About the role" maybe as a brief description of the organization. But "About the role" is about the role, not company. However we could stretch: "About the role" could include both role and company context. Might be acceptable.
Alternatively we could add a section "About the company" but not in list; risk of being considered not following instruction. Safer to stick to given headings.
Thus we will produce sections: About the role (includes role snapshot and company overview), Responsibilities, Requirements, Skills, Benefits, Pay, Schedule.
We need to decide what goes where.
About the role: Could include role snapshot and company overview (Who We Are, Culture). But we need to avoid filler. We'll write a concise paragraph combining.
Responsibilities: managing existing provider contracts, prospecting and proposing new contracts based on adequacy needs and financial considerations, serving as liaison between WPS and provider community.
Requirements: Associate degree in Business, Marketing, Healthcare Administration, or related field OR equivalent post high school education and/or work-related experience; Two (2) or more years of customer service experience related to the health insurance industry to include provider contracting, provider relations or healthcare administration; Remote work requirements: high speed cable or fiber internet, minimum of 10 Mbps downstream and at least 1 Mbps upstream internet connection.
Skills: Strong analytical skills with ability to prepare and interpret reports (e.g. network analysis, RFP support); Excellent written and verbal communication skills; Strong organizational and time management skills with proven attention to detail.
Benefits: Remote work options available; Performance bonus and/or merit increase opportunities; 401(k) with a 100% match for the first 3% of your salary and a 50% match for the next 2% of your salary (100% vested immediately); Competitive paid time off; Health insurance, dental insurance, and telehealth services start DAY 1; Professional and Leadership Development Programs; Additional benefits details available at https://www.wpshealthsolutions.com/careers/
Pay: Hourly Rate of Pay $23.00-25.00/hourly
Schedule: Work hours 8am-5pm Central Time, Monday-Friday; Remote work allowed in approved states: Colorado, Florida, Georgia, Illinois, Indiana, Iowa, Michigan, Minnesota, Missouri, Nebraska, New Jersey, North Carolina, Ohio, South Carolina, Texas, Virginia, Wisconsin
We need to ensure we don't repeat info. Remote work options appear both in Benefits and Schedule; but we can mention remote work eligibility in Schedule (list of states) and remote work options in Benefits (just mention remote work options available). That's okay.
We must not include duplicated lines. Ensure we don't repeat same sentence.
Now produce HTML fragment: use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
Thus:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Skills
- ...
...
Benefits
- ...
...
Pay
Hourly Rate of Pay $23.00-25.00/hourly
Schedule
Work hours 8am-5pm Central Time, Monday‑Friday. Remote work permitted in the following approved states: Colorado, Florida, Georgia, Illinois, Indiana, Iowa, Michigan, Minnesota, Missouri, Nebraska, New Jersey, North Carolina, Ohio, South Carolina, Texas, Virginia, Wisconsin.
We need to ensure we don't include any extra text like "Work Location". Already covered.
Check for any leftover boilerplate: "Review additional benefits: (https://...)" we turned into a link inside benefits list item.
We need to ensure we didn't include "Sign up for Job Alerts FOLLOW US! Instagram LinkedIn Facebook WPS Health Blog". Not included.
Now produce final HTML.
Check that we didn't create any empty sections. All have content.
Let's craft the prose for About the role: combine role snapshot and company overview.
Role snapshot: "The Contract Coordinator is accountable to maintain and strengthen WPS provider networks by managing existing provider contracts and prospecting and proposing new contracts based on adequacy needs and financial considerations. The role serves as a liaison between WPS and the provider community."
Company overview: "WPS, a health solutions company, is a leading not-for-profit health insurer and federal government contractor headquartered in Madison, Wisconsin. WPS offers health insurance plans for individuals, families, seniors and group health plans for small to large businesses. We process claims and provide customer support for beneficiaries of the Medicare program and manage benefits for millions of active-duty and retired military personnel across the U.S. and abroad. WPS has been making healthcare easier for the people we serve for nearly 80 years. Proud to be military and veteran ready
for prose. Do NOT repeat job title as heading (the page already shows it). Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to extract substantive info from the posting. Let's parse: Role Snapshot: description: "The Contract Coordinator is accountable to maintain and strengthen WPS provider networks by managing existing provider contracts and prospecting and proposing new contracts based on adequacy needs and financial considerations. The role serves as a liaison between WPS and the provider community." That's a prose description. Could be "About the role" or "Role Snapshot". Use heading
About the role
maybe. Hourly Rate of Pay $23.00-25.00/hourly -> Pay section. Work Location: list of states remote work allowed. That's location info; could be part of Schedule? Not exactly. Could be part of "Work Location" but not a required heading. We could include under "Schedule" maybe? Actually schedule is work hours: 8am-5pm Central Time, Monday-Friday. So schedule section. Remote Work Requirements: high speed cable or fiber internet, minimum 10 Mbps downstream and at least 1 Mbps upstream. That's a requirement; could be part of Requirements or Qualifications. Minimum Qualifications: Associate degree in Business, Marketing, Healthcare Administration, or related field OR equivalent post high school education and/or work-related experience. Two (2) or more years of customer service experience related to the health insurance industry to include provider contracting, provider relations or healthcare administration. Strong analytical skills with ability to prepare and interpret reports (e.g. network analysis, RFP support). Excellent written and verbal communication skills. Strong organizational and time management skills with proven attention to detail. That's qualifications and skills. Benefits: list: Remote work options available; Performance bonus and/or merit increase opportunities; 401(k) with a 100% match for the first 3% of your salary and a 50% match for the next 2% of your salary (100% vested immediately); Competitive paid time off; Health insurance, dental insurance, and telehealth services start DAY 1; Professional and Leadership Development Programs; Review additional benefits: (link). So we have benefits. Who We Are: description of company. Could be "About the company" but not required heading; maybe we can include under "About the role"? But we have "About the role" already. Could add a separate section "About WPS" but not in prescribed headings list. The headings list includes: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those. Responsibilities: The role snapshot includes responsibilities: maintain and strengthen WPS provider networks by managing existing provider contracts and prospecting and proposing new contracts based on adequacy needs and financial considerations; serve as liaison between WPS and provider community. Could be responsibilities. Requirements: maybe remote work requirements? Or minimum qualifications? The distinction: Requirements could be mandatory items like education, experience, remote work internet. Qualifications could be preferred? But we have both. We'll decide: Requirements: education and experience (minimum qualifications). Skills: analytical, communication, organizational, time management, attention to detail. Qualifications maybe same as requirements? Actually they listed "Minimum Qualifications". So we can put that under Requirements. Then Skills under Skills. Pay: hourly rate. Schedule: work hours. Benefits: list. We need to avoid filler like "commensurate with experience", etc. Not present. We need to remove duplicated lines, boilerplate like "Sign up for Job Alerts FOLLOW US! Instagram LinkedIn Facebook WPS Health Blog". Also "Review additional benefits: (https://...)" maybe we keep as link? It's part of benefits but could be considered boilerplate? It's a link to additional benefits; we could keep as part of benefits list but maybe it's okay. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link to additional benefits is not exactly boilerplate but could be considered navigation? It's a link to benefits page; maybe we keep it as part of benefits. We also need to not include "Who We Are" and "Culture Drives Our Success" sections unless we map them to headings. They are not in headings list; we could omit them as they are not required. But we must preserve ALL substantive information; do NOT invent or summarize away detail. If we omit "Who We Are" and culture, we lose substantive info about the company. However the instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It does not require us to include all possible headings; we can choose to include only those that have content. But we must preserve ALL substantive information; we cannot discard substantive info. So we need to include that info somewhere, perhaps under "About the role" or another heading like "About the company". But the allowed headings list includes "About the role". Could we put company info under "About the role"? That might be odd but permissible? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we could also use other headings? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections; but we could also add other headings if needed? The instruction: "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." So we should create sections only for those headings that have content. It doesn't forbid other headings, but the examples given are those. Likely they expect us to use those headings only. So we need to fit all substantive info into those sections.
We can put company description under "About the role" maybe as a brief description of the organization. But "About the role" is about the role, not company. However we could stretch: "About the role" could include both role and company context. Might be acceptable.
Alternatively we could add a section "About the company" but not in list; risk of being considered not following instruction. Safer to stick to given headings.
Thus we will produce sections: About the role (includes role snapshot and company overview), Responsibilities, Requirements, Skills, Benefits, Pay, Schedule.
We need to decide what goes where.
About the role: Could include role snapshot and company overview (Who We Are, Culture). But we need to avoid filler. We'll write a concise paragraph combining.
Responsibilities: managing existing provider contracts, prospecting and proposing new contracts based on adequacy needs and financial considerations, serving as liaison between WPS and provider community.
Requirements: Associate degree in Business, Marketing, Healthcare Administration, or related field OR equivalent post high school education and/or work-related experience; Two (2) or more years of customer service experience related to the health insurance industry to include provider contracting, provider relations or healthcare administration; Remote work requirements: high speed cable or fiber internet, minimum of 10 Mbps downstream and at least 1 Mbps upstream internet connection.
Skills: Strong analytical skills with ability to prepare and interpret reports (e.g. network analysis, RFP support); Excellent written and verbal communication skills; Strong organizational and time management skills with proven attention to detail.
Benefits: Remote work options available; Performance bonus and/or merit increase opportunities; 401(k) with a 100% match for the first 3% of your salary and a 50% match for the next 2% of your salary (100% vested immediately); Competitive paid time off; Health insurance, dental insurance, and telehealth services start DAY 1; Professional and Leadership Development Programs; Additional benefits details available at https://www.wpshealthsolutions.com/careers/
Pay: Hourly Rate of Pay $23.00-25.00/hourly
Schedule: Work hours 8am-5pm Central Time, Monday-Friday; Remote work allowed in approved states: Colorado, Florida, Georgia, Illinois, Indiana, Iowa, Michigan, Minnesota, Missouri, Nebraska, New Jersey, North Carolina, Ohio, South Carolina, Texas, Virginia, Wisconsin
We need to ensure we don't repeat info. Remote work options appear both in Benefits and Schedule; but we can mention remote work eligibility in Schedule (list of states) and remote work options in Benefits (just mention remote work options available). That's okay.
We must not include duplicated lines. Ensure we don't repeat same sentence.
Now produce HTML fragment: use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
Thus:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Skills
- ...
...
Benefits
- ...
...
Pay
Hourly Rate of Pay $23.00-25.00/hourly
Schedule
Work hours 8am-5pm Central Time, Monday‑Friday. Remote work permitted in the following approved states: Colorado, Florida, Georgia, Illinois, Indiana, Iowa, Michigan, Minnesota, Missouri, Nebraska, New Jersey, North Carolina, Ohio, South Carolina, Texas, Virginia, Wisconsin.
We need to ensure we don't include any extra text like "Work Location". Already covered.
Check for any leftover boilerplate: "Review additional benefits: (https://...)" we turned into a link inside benefits list item.
We need to ensure we didn't include "Sign up for Job Alerts FOLLOW US! Instagram LinkedIn Facebook WPS Health Blog". Not included.
Now produce final HTML.
Check that we didn't create any empty sections. All have content.
Let's craft the prose for About the role: combine role snapshot and company overview.
Role snapshot: "The Contract Coordinator is accountable to maintain and strengthen WPS provider networks by managing existing provider contracts and prospecting and proposing new contracts based on adequacy needs and financial considerations. The role serves as a liaison between WPS and the provider community."
Company overview: "WPS, a health solutions company, is a leading not-for-profit health insurer and federal government contractor headquartered in Madison, Wisconsin. WPS offers health insurance plans for individuals, families, seniors and group health plans for small to large businesses. We process claims and provide customer support for beneficiaries of the Medicare program and manage benefits for millions of active-duty and retired military personnel across the U.S. and abroad. WPS has been making healthcare easier for the people we serve for nearly 80 years. Proud to be military and veteran ready
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
Thus:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Skills
- ...
...
Benefits
- ...
...
Pay
Hourly Rate of Pay $23.00-25.00/hourly
Schedule
Work hours 8am-5pm Central Time, Monday‑Friday. Remote work permitted in the following approved states: Colorado, Florida, Georgia, Illinois, Indiana, Iowa, Michigan, Minnesota, Missouri, Nebraska, New Jersey, North Carolina, Ohio, South Carolina, Texas, Virginia, Wisconsin.
We need to ensure we don't include any extra text like "Work Location". Already covered.
Check for any leftover boilerplate: "Review additional benefits: (https://...)" we turned into a link inside benefits list item.
We need to ensure we didn't include "Sign up for Job Alerts FOLLOW US! Instagram LinkedIn Facebook WPS Health Blog". Not included.
Now produce final HTML.
Check that we didn't create any empty sections. All have content.
Let's craft the prose for About the role: combine role snapshot and company overview.
Role snapshot: "The Contract Coordinator is accountable to maintain and strengthen WPS provider networks by managing existing provider contracts and prospecting and proposing new contracts based on adequacy needs and financial considerations. The role serves as a liaison between WPS and the provider community."
Company overview: "WPS, a health solutions company, is a leading not-for-profit health insurer and federal government contractor headquartered in Madison, Wisconsin. WPS offers health insurance plans for individuals, families, seniors and group health plans for small to large businesses. We process claims and provide customer support for beneficiaries of the Medicare program and manage benefits for millions of active-duty and retired military personnel across the U.S. and abroad. WPS has been making healthcare easier for the people we serve for nearly 80 years. Proud to be military and veteran ready
for prose. Thus:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Benefits
- ... ...
Pay
Hourly Rate of Pay $23.00-25.00/hourly
Schedule
Work hours 8am-5pm Central Time, Monday‑Friday. Remote work permitted in the following approved states: Colorado, Florida, Georgia, Illinois, Indiana, Iowa, Michigan, Minnesota, Missouri, Nebraska, New Jersey, North Carolina, Ohio, South Carolina, Texas, Virginia, Wisconsin.
We need to ensure we don't include any extra text like "Work Location". Already covered. Check for any leftover boilerplate: "Review additional benefits: (https://...)" we turned into a link inside benefits list item. We need to ensure we didn't include "Sign up for Job Alerts FOLLOW US! Instagram LinkedIn Facebook WPS Health Blog". Not included. Now produce final HTML. Check that we didn't create any empty sections. All have content. Let's craft the prose for About the role: combine role snapshot and company overview. Role snapshot: "The Contract Coordinator is accountable to maintain and strengthen WPS provider networks by managing existing provider contracts and prospecting and proposing new contracts based on adequacy needs and financial considerations. The role serves as a liaison between WPS and the provider community." Company overview: "WPS, a health solutions company, is a leading not-for-profit health insurer and federal government contractor headquartered in Madison, Wisconsin. WPS offers health insurance plans for individuals, families, seniors and group health plans for small to large businesses. We process claims and provide customer support for beneficiaries of the Medicare program and manage benefits for millions of active-duty and retired military personnel across the U.S. and abroad. WPS has been making healthcare easier for the people we serve for nearly 80 years. Proud to be military and veteran ready