Medical Billing Supervisor
for each section heading, - for lists,
for prose.
We must not include boilerplate like About TEKsystems, equal opportunity, etc.
We must not include Application Deadline, Job Type & Location? Actually Job Type & Location could be considered part of role? But we already have location in responsibilities? Not needed. Could include location in About the role? But we already have location in Job Type & Location: "Contract to Hire position based out of Towson, MD." That's substantive. Should we include it? It's not covered elsewhere. Could be part of About the role or Responsibilities? Might be better to include a short paragraph under About the role: "This is a Contract to Hire position based out of Towson, MD." Or we could create a separate section? Not allowed headings besides those. Could fold into About the role.
Similarly, Workplace Type hybrid could be folded into About the role or Responsibilities.
We need to preserve all substantive info. So we need to include location, contract type, hybrid.
Let's craft About the role paragraph: "Oversee a team of 10 and the daily activities of billing and accounts receivable staff. Focused on timely and accurate claim processing, follow-up, and collections. Manage team, performance, time off requests, and billing questions around both facility & professional billing. This is a Contract to Hire position based out of Towson, MD, with a hybrid workplace arrangement."
That covers overview, responsibilities, location, contract type, hybrid.
Now Responsibilities: maybe we can list specific duties: Oversee team, daily activities, claim processing, follow-up, collections, manage team performance, time off requests, billing Qs facility & professional. But we already covered many in About the role. To avoid duplication, we could keep About the role as overview and Responsibilities as a list of duties.
Let's define:
About the role: brief overview (maybe 2 sentences). Responsibilities: bullet list.
Requirements: bullet list of experience/education.
Qualifications: maybe bullet list of knowledge/skills? But we have Skills section for skills. Qualifications could be degree plus experience? But we already have Requirements for experience/education. Qualifications could be "Ability to directly assist reps with job tasks", "Behavioral/mental health building is a PLUS". Hmm.
Better to combine Requirements and Qualifications into one section? But we need to follow headings if content exists. Could treat Requirements as the experience/education, Qualifications as the "PLUS" items? But that seems thin.
Given instruction to prefer few substantive sections over many thin ones, we could merge Requirements and Qualifications into a single section called "Requirements" (or "Qualifications") and omit the other. Which heading is more appropriate? The posting includes "Additional Skills & Qualifications". So we could use "Qualifications" heading for that content. And we could treat "Requirements" as maybe not needed if we put everything under Qualifications. But we need to decide.
We have also Skills section separate.
Thus we could have:
- About the role (overview)
- Responsibilities (duties)
- Qualifications (education, experience, plus)
- Skills (specific skills)
- Benefits
- Pay
That's 6 sections.
We must not include Requirements if we merge into Qualifications.
Now we need to extract content for Qualifications:
From text: "Associate’s or Bachelor’s degree would be a PLUS but not a must", "3+ years of progressively responsible experience in healthcare billing, collections, RCM", "At least 2+ years as either a team lead/supervisor etc over a team", "Strong in medical billing/collections with the ability to directly assist reps with job tasks", "Behavioral/mental health building is a PLUS, but not a must".
Also maybe "Skills medical billing, supervisor, IDK, Hospital billing, behavioral health" but that's for Skills.
Now Skills: list: medical billing, supervisor, Hospital billing, behavioral health. IDK maybe we keep as "IDK". We'll include.
Now Benefits: list as given.
Pay: pay range.
Now we need to format.
We must not include any extra text outside HTML.
Let's craft HTML:
About the role
Oversee a team of 10 and
for prose. We must not include boilerplate like About TEKsystems, equal opportunity, etc. We must not include Application Deadline, Job Type & Location? Actually Job Type & Location could be considered part of role? But we already have location in responsibilities? Not needed. Could include location in About the role? But we already have location in Job Type & Location: "Contract to Hire position based out of Towson, MD." That's substantive. Should we include it? It's not covered elsewhere. Could be part of About the role or Responsibilities? Might be better to include a short paragraph under About the role: "This is a Contract to Hire position based out of Towson, MD." Or we could create a separate section? Not allowed headings besides those. Could fold into About the role. Similarly, Workplace Type hybrid could be folded into About the role or Responsibilities. We need to preserve all substantive info. So we need to include location, contract type, hybrid. Let's craft About the role paragraph: "Oversee a team of 10 and the daily activities of billing and accounts receivable staff. Focused on timely and accurate claim processing, follow-up, and collections. Manage team, performance, time off requests, and billing questions around both facility & professional billing. This is a Contract to Hire position based out of Towson, MD, with a hybrid workplace arrangement." That covers overview, responsibilities, location, contract type, hybrid. Now Responsibilities: maybe we can list specific duties: Oversee team, daily activities, claim processing, follow-up, collections, manage team performance, time off requests, billing Qs facility & professional. But we already covered many in About the role. To avoid duplication, we could keep About the role as overview and Responsibilities as a list of duties. Let's define: About the role: brief overview (maybe 2 sentences). Responsibilities: bullet list. Requirements: bullet list of experience/education. Qualifications: maybe bullet list of knowledge/skills? But we have Skills section for skills. Qualifications could be degree plus experience? But we already have Requirements for experience/education. Qualifications could be "Ability to directly assist reps with job tasks", "Behavioral/mental health building is a PLUS". Hmm. Better to combine Requirements and Qualifications into one section? But we need to follow headings if content exists. Could treat Requirements as the experience/education, Qualifications as the "PLUS" items? But that seems thin. Given instruction to prefer few substantive sections over many thin ones, we could merge Requirements and Qualifications into a single section called "Requirements" (or "Qualifications") and omit the other. Which heading is more appropriate? The posting includes "Additional Skills & Qualifications". So we could use "Qualifications" heading for that content. And we could treat "Requirements" as maybe not needed if we put everything under Qualifications. But we need to decide. We have also Skills section separate. Thus we could have: - About the role (overview) - Responsibilities (duties) - Qualifications (education, experience, plus) - Skills (specific skills) - Benefits - Pay That's 6 sections. We must not include Requirements if we merge into Qualifications. Now we need to extract content for Qualifications: From text: "Associate’s or Bachelor’s degree would be a PLUS but not a must", "3+ years of progressively responsible experience in healthcare billing, collections, RCM", "At least 2+ years as either a team lead/supervisor etc over a team", "Strong in medical billing/collections with the ability to directly assist reps with job tasks", "Behavioral/mental health building is a PLUS, but not a must". Also maybe "Skills medical billing, supervisor, IDK, Hospital billing, behavioral health" but that's for Skills. Now Skills: list: medical billing, supervisor, Hospital billing, behavioral health. IDK maybe we keep as "IDK". We'll include. Now Benefits: list as given. Pay: pay range. Now we need to format. We must not include any extra text outside HTML. Let's craft HTML:
About the role
Oversee a team of 10 and