Lien Resolution Team Lead
The Ward Law Group, PL · Hialeah, FL · 1 mo ago
OTHRFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes Company Description, Job Description (POSITION OVERVIEW, Key Responsibilities, Qualifications, LOCATION, Additional Information (Compensation & Benefits), etc). We must use for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must not repeat job title as heading. We must not put Job ID etc. We must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions). Also we must include a 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") and never create Pay/Schedule/Benefits sections unless posting actually states them.
We have content: Company Description (mission, values). That could be "About the role"? Actually "About the role" is generic; but we can use "About the Company" maybe? The instruction says use
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must not repeat job title as heading. We must not put Job ID etc. We must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions). Also we must include a 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") and never create Pay/Schedule/Benefits sections unless posting actually states them.
We have content: Company Description (mission, values). That could be "About the role"? Actually "About the role" is generic; but we can use "About the Company" maybe? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we can use those headings if appropriate. We need to map content to those headings.
We have:
- Company Description: could go under "About the role" or maybe "About the Company". But they said "About the role" as example; we can use that heading for company description? Might be okay.
- POSITION OVERVIEW: could be part of Responsibilities? Or we could treat as overview separate but not required heading. Could embed in Responsibilities.
- Key Responsibilities: definitely Responsibilities heading.
- Qualifications: Requirements heading (or Qualifications). They gave both Requirements and Qualifications as possible headings. We'll use "Requirements" for required qualifications, and maybe "Preferred Qualifications" could be under "Skills"? Or we could have a "Qualifications" heading for required and then a "Preferred Qualifications" maybe as part of Skills? But they said use headings like Skills, Benefits, Pay, Schedule. We could have a "Skills" section for preferred qualifications like bilingual, etc. But we need to avoid filler.
- LOCATION: could be Schedule? Actually location is not schedule. They didn't give a heading for location; maybe we can omit location section if not in list? But we need to preserve all substantive info. However instruction: "include a section ONLY when the posting has real, specific content for it". It didn't say we must include location; but we should preserve info. Could we put location under a generic heading like "About the role"? Not ideal. Maybe we can create a heading "Location" even though not in the list? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exhaustive list. So we can use other headings if needed, but better to stick to those examples. However location is not covered; maybe we can incorporate location into "About the role" or "Responsibilities"? Not ideal.
Alternatively we could treat location as part of "Schedule"? No.
Maybe we can omit location because it's not essential? But instruction says preserve ALL substantive information. So we need to include location somewhere.
We could add a heading "Location" as Location
. That seems reasonable; not prohibited.
Similarly, we have "Position Type: Full Time (8:30 AM - 5 PM EST)" which is schedule info. So we can create a Schedule section.
Compensation & Benefits: we have details; we can create Benefits section (and maybe Pay). They said never create Pay/Schedule/Benefits sections unless posting actually states them. We have benefits details, but compensation is only "Competitive salary commensurate with experience" which is placeholder; we should not create a Pay section because it's just "commensurate with experience" which is filler. So we should omit Pay section. Benefits we have concrete list: medical, dental & vision, hospital plans, 401(k), life insurance, disability, HSA & DCFSA, EAP, tuition assistance, paid time off and paid holidays. That's substantive. So we create Benefits section.
Schedule: we have "Position Type: Full Time (8:30 AM - 5 PM EST)". That's specific schedule. So we create Schedule section.
Now we need to remove boilerplate: EEO statement, immigration reform, unsolicited assistance from search firms, etc. Also remove duplicated lines, application instructions like "Apply today", "JOIN OUR TEAM", etc. Also remove "Additional Information" heading maybe.
We need to preserve all substantive info: company description, mission, values, position overview, key responsibilities, qualifications (required and preferred), location, position type (schedule), benefits.
We need to format using for section headings, - for any list of duties/requirements/benefits, and
for prose.
We must not repeat job title as heading. No job title given explicitly but we can ignore.
We must not put Job ID/requisition numbers as headings.
Now craft HTML.
Structure:
About the Company
maybe but they said About the role example. Could use About the role for company description? But we have position overview separate. Maybe better: About the Role
for position overview? Actually "About the role" could contain position overview. But we also have company description. Could combine? Might be confusing.
We could do:
About the Company
(prose)
Position Overview
(prose) but they didn't list that as example but it's okay.
But they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should try to map to those. However we have a lot of sections; we can use those exact headings where appropriate.
Let's map:
- About the role: could include company description and position overview? Might be okay.
- Responsibilities: key responsibilities.
- Requirements: required qualifications.
- Skills: preferred qualifications (bilingual, etc.) maybe also some skills like proficiency with software.
- Benefits: benefits list.
- Schedule: position type.
- Location: maybe we can put under About the role? Or we could add a Location heading.
But we need to avoid filler. Let's decide to use:
About the Company
(though not in list but okay). However to be safe, we could use About the role
and put company description + position overview there. But that mixes company description with role overview; still okay.
But we also need to include location; maybe we can add a short paragraph under About the role.
Alternatively we could create a heading Location
even if not in examples; I think it's acceptable.
Given the instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." indicates those are examples, not an exhaustive list. So we can use other headings.
Thus we can use:
About the Company
Position Overview
Responsibilities
Requirements
Skills
Benefits
Schedule
Location
But we might be creating many sections; they said "Prefer a few substantive sections over many thin ones." So we should combine where possible to avoid many thin sections.
We could combine About the Company and Position Overview into one About the Role
section containing both company description and position overview prose.
Then Responsibilities separate.
Then Requirements (required qualifications).
Then Skills (preferred qualifications and maybe software proficiency).
Then Benefits.
Then Schedule (position type).
Then Location (maybe we can incorporate location into Schedule or About the Role? Could add a short line under About the Role: "Located at 7900NW 154th Street, Suite 101 Miami Lakes, FL 33016." That's substantive.
Thus we have sections: About the Role, Responsibilities, Requirements, Skills, Benefits, Schedule.
That's six sections, reasonable.
Now we need to ensure we don't include filler like "Competitive salary commensurate with experience" in Benefits or Pay. We'll omit Pay section entirely.
Now we need to remove boilerplate: EEO, immigration, unsolicited assistance, etc. Also remove "JOIN OUR TEAM" and "Apply today". Also remove "Additional Information" heading.
Now we need to preserve all substantive info: Let's extract.
Company Description paragraph: "Join an Award-Winning Personal Injury Law Firm At The Ward Law Group, our mission is simple: Changing Lives. One Client at a Time Recognized as one of the Best Places to Work for consecutive years, we are committed to delivering exceptional legal representation while creating an environment where talented professionals can grow, lead, and make a meaningful impact every day. We believe our people are our greatest asset. We foster a collaborative, innovative, and high-accountability culture where every team member is empowered to make informed decisions, continuously improve, and deliver exceptional results for our clients. Every role contributes directly to helping injured individuals navigate one of the most challenging times in their lives while supporting the continued growth and success of our firm. Our Core Values Faith – We act with integrity, honesty, and purpose in everything we do. Accountability – We take ownership of our work, our commitments, and the results we deliver. Leadership – We lead by example, inspire others, embrace continuous improvement, and develop high-performing teams. Loyalty – We build lasting relationships through trust, respect, and dedication to our clients, teammates, and community. Service to Our Clients – We are committed to delivering compassionate, responsive, and exceptional service that maximizes every client's opportunity for success. Service to Our Teammates – We foster a culture of collaboration, respect, support, and shared success where every team member has the opportunity to grow and thrive. Service to Our Community – We believe in making a positive impact beyond the workplace by serving and strengthening the communities where we live and work. If you are passionate about helping injured clients, thrive in a fast-paced, results-driven environment, and are committed to delivering exceptional client service while continuously growing your career, we invite you to join The Ward Law Group and help us change lives—one client at a time."
We can condense but must preserve all substantive info; we can keep as prose.
Position Overview: "The Lien Resolution Team Lead runs the function that determines how much of every settlement actually reaches our clients. You will supervise a team of reductions and lien resolution specialists, personally handle the largest and most complex lien files, and own the metrics that measure our performance — aggregate reduction rate, net-to-client percentage, and time from settlement to disbursement. This is a negotiation role with a management layer on top. Every dollar your team takes off a medical balance, a hospital lien, or a health plan’s subrogation claim is a dollar that goes to an injured client instead. You will set the standard for how hard those negotiations are pushed, hold the team to it, and step in personally when a provider or plan will not move."
Key Responsibilities: list bullet points.
We need to convert each responsibility into
- .
Let's extract bullet points from the responsibilities paragraph:
- Post-settlement medical bill and liens (maybe heading). Actually the responsibilities start with "Post-settlement medical bill and liens" then a dash? The text: "Post-settlement medical bill and liens Lead the team. Supervise, train, and evaluate a team of reductions and lien
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exhaustive list. So we can use other headings if needed, but better to stick to those examples. However location is not covered; maybe we can incorporate location into "About the role" or "Responsibilities"? Not ideal.
Alternatively we could treat location as part of "Schedule"? No.
Maybe we can omit location because it's not essential? But instruction says preserve ALL substantive information. So we need to include location somewhere.
We could add a heading "Location" as Location
. That seems reasonable; not prohibited.
Similarly, we have "Position Type: Full Time (8:30 AM - 5 PM EST)" which is schedule info. So we can create a Schedule section.
Compensation & Benefits: we have details; we can create Benefits section (and maybe Pay). They said never create Pay/Schedule/Benefits sections unless posting actually states them. We have benefits details, but compensation is only "Competitive salary commensurate with experience" which is placeholder; we should not create a Pay section because it's just "commensurate with experience" which is filler. So we should omit Pay section. Benefits we have concrete list: medical, dental & vision, hospital plans, 401(k), life insurance, disability, HSA & DCFSA, EAP, tuition assistance, paid time off and paid holidays. That's substantive. So we create Benefits section.
Schedule: we have "Position Type: Full Time (8:30 AM - 5 PM EST)". That's specific schedule. So we create Schedule section.
Now we need to remove boilerplate: EEO statement, immigration reform, unsolicited assistance from search firms, etc. Also remove duplicated lines, application instructions like "Apply today", "JOIN OUR TEAM", etc. Also remove "Additional Information" heading maybe.
We need to preserve all substantive info: company description, mission, values, position overview, key responsibilities, qualifications (required and preferred), location, position type (schedule), benefits.
We need to format using for section headings, - for any list of duties/requirements/benefits, and
for prose.
We must not repeat job title as heading. No job title given explicitly but we can ignore.
We must not put Job ID/requisition numbers as headings.
Now craft HTML.
Structure:
About the Company
maybe but they said About the role example. Could use About the role for company description? But we have position overview separate. Maybe better: About the Role
for position overview? Actually "About the role" could contain position overview. But we also have company description. Could combine? Might be confusing.
We could do:
About the Company
(prose)
Position Overview
(prose) but they didn't list that as example but it's okay.
But they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should try to map to those. However we have a lot of sections; we can use those exact headings where appropriate.
Let's map:
- About the role: could include company description and position overview? Might be okay.
- Responsibilities: key responsibilities.
- Requirements: required qualifications.
- Skills: preferred qualifications (bilingual, etc.) maybe also some skills like proficiency with software.
- Benefits: benefits list.
- Schedule: position type.
- Location: maybe we can put under About the role? Or we could add a Location heading.
But we need to avoid filler. Let's decide to use:
About the Company
(though not in list but okay). However to be safe, we could use About the role
and put company description + position overview there. But that mixes company description with role overview; still okay.
But we also need to include location; maybe we can add a short paragraph under About the role.
Alternatively we could create a heading Location
even if not in examples; I think it's acceptable.
Given the instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." indicates those are examples, not an exhaustive list. So we can use other headings.
Thus we can use:
About the Company
Position Overview
Responsibilities
Requirements
Skills
Benefits
Schedule
Location
But we might be creating many sections; they said "Prefer a few substantive sections over many thin ones." So we should combine where possible to avoid many thin sections.
We could combine About the Company and Position Overview into one About the Role
section containing both company description and position overview prose.
Then Responsibilities separate.
Then Requirements (required qualifications).
Then Skills (preferred qualifications and maybe software proficiency).
Then Benefits.
Then Schedule (position type).
Then Location (maybe we can incorporate location into Schedule or About the Role? Could add a short line under About the Role: "Located at 7900NW 154th Street, Suite 101 Miami Lakes, FL 33016." That's substantive.
Thus we have sections: About the Role, Responsibilities, Requirements, Skills, Benefits, Schedule.
That's six sections, reasonable.
Now we need to ensure we don't include filler like "Competitive salary commensurate with experience" in Benefits or Pay. We'll omit Pay section entirely.
Now we need to remove boilerplate: EEO, immigration, unsolicited assistance, etc. Also remove "JOIN OUR TEAM" and "Apply today". Also remove "Additional Information" heading.
Now we need to preserve all substantive info: Let's extract.
Company Description paragraph: "Join an Award-Winning Personal Injury Law Firm At The Ward Law Group, our mission is simple: Changing Lives. One Client at a Time Recognized as one of the Best Places to Work for consecutive years, we are committed to delivering exceptional legal representation while creating an environment where talented professionals can grow, lead, and make a meaningful impact every day. We believe our people are our greatest asset. We foster a collaborative, innovative, and high-accountability culture where every team member is empowered to make informed decisions, continuously improve, and deliver exceptional results for our clients. Every role contributes directly to helping injured individuals navigate one of the most challenging times in their lives while supporting the continued growth and success of our firm. Our Core Values Faith – We act with integrity, honesty, and purpose in everything we do. Accountability – We take ownership of our work, our commitments, and the results we deliver. Leadership – We lead by example, inspire others, embrace continuous improvement, and develop high-performing teams. Loyalty – We build lasting relationships through trust, respect, and dedication to our clients, teammates, and community. Service to Our Clients – We are committed to delivering compassionate, responsive, and exceptional service that maximizes every client's opportunity for success. Service to Our Teammates – We foster a culture of collaboration, respect, support, and shared success where every team member has the opportunity to grow and thrive. Service to Our Community – We believe in making a positive impact beyond the workplace by serving and strengthening the communities where we live and work. If you are passionate about helping injured clients, thrive in a fast-paced, results-driven environment, and are committed to delivering exceptional client service while continuously growing your career, we invite you to join The Ward Law Group and help us change lives—one client at a time."
We can condense but must preserve all substantive info; we can keep as prose.
Position Overview: "The Lien Resolution Team Lead runs the function that determines how much of every settlement actually reaches our clients. You will supervise a team of reductions and lien resolution specialists, personally handle the largest and most complex lien files, and own the metrics that measure our performance — aggregate reduction rate, net-to-client percentage, and time from settlement to disbursement. This is a negotiation role with a management layer on top. Every dollar your team takes off a medical balance, a hospital lien, or a health plan’s subrogation claim is a dollar that goes to an injured client instead. You will set the standard for how hard those negotiations are pushed, hold the team to it, and step in personally when a provider or plan will not move."
Key Responsibilities: list bullet points.
We need to convert each responsibility into
- .
Let's extract bullet points from the responsibilities paragraph:
- Post-settlement medical bill and liens (maybe heading). Actually the responsibilities start with "Post-settlement medical bill and liens" then a dash? The text: "Post-settlement medical bill and liens Lead the team. Supervise, train, and evaluate a team of reductions and lien
- for any list of duties/requirements/benefits, and
for prose. We must not repeat job title as heading. No job title given explicitly but we can ignore. We must not put Job ID/requisition numbers as headings. Now craft HTML. Structure:
About the Company
maybe but they said About the role example. Could use About the role for company description? But we have position overview separate. Maybe better:About the Role
for position overview? Actually "About the role" could contain position overview. But we also have company description. Could combine? Might be confusing. We could do:About the Company
(prose)Position Overview
(prose) but they didn't list that as example but it's okay. But they said usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should try to map to those. However we have a lot of sections; we can use those exact headings where appropriate. Let's map: - About the role: could include company description and position overview? Might be okay. - Responsibilities: key responsibilities. - Requirements: required qualifications. - Skills: preferred qualifications (bilingual, etc.) maybe also some skills like proficiency with software. - Benefits: benefits list. - Schedule: position type. - Location: maybe we can put under About the role? Or we could add a Location heading. But we need to avoid filler. Let's decide to use:
About the Company
(though not in list but okay). However to be safe, we could useAbout the role
and put company description + position overview there. But that mixes company description with role overview; still okay. But we also need to include location; maybe we can add a short paragraph under About the role. Alternatively we could create a headingLocation
even if not in examples; I think it's acceptable. Given the instruction: "Usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." indicates those are examples, not an exhaustive list. So we can use other headings. Thus we can use:
About the Company
Position Overview
Responsibilities
Requirements
Skills
Benefits
Schedule
Location
But we might be creating many sections; they said "Prefer a few substantive sections over many thin ones." So we should combine where possible to avoid many thin sections. We could combine About the Company and Position Overview into oneAbout the Role
section containing both company description and position overview prose. Then Responsibilities separate. Then Requirements (required qualifications). Then Skills (preferred qualifications and maybe software proficiency). Then Benefits. Then Schedule (position type). Then Location (maybe we can incorporate location into Schedule or About the Role? Could add a short line under About the Role: "Located at 7900NW 154th Street, Suite 101 Miami Lakes, FL 33016." That's substantive. Thus we have sections: About the Role, Responsibilities, Requirements, Skills, Benefits, Schedule. That's six sections, reasonable. Now we need to ensure we don't include filler like "Competitive salary commensurate with experience" in Benefits or Pay. We'll omit Pay section entirely. Now we need to remove boilerplate: EEO, immigration, unsolicited assistance, etc. Also remove "JOIN OUR TEAM" and "Apply today". Also remove "Additional Information" heading. Now we need to preserve all substantive info: Let's extract. Company Description paragraph: "Join an Award-Winning Personal Injury Law Firm At The Ward Law Group, our mission is simple: Changing Lives. One Client at a Time Recognized as one of the Best Places to Work for consecutive years, we are committed to delivering exceptional legal representation while creating an environment where talented professionals can grow, lead, and make a meaningful impact every day. We believe our people are our greatest asset. We foster a collaborative, innovative, and high-accountability culture where every team member is empowered to make informed decisions, continuously improve, and deliver exceptional results for our clients. Every role contributes directly to helping injured individuals navigate one of the most challenging times in their lives while supporting the continued growth and success of our firm. Our Core Values Faith – We act with integrity, honesty, and purpose in everything we do. Accountability – We take ownership of our work, our commitments, and the results we deliver. Leadership – We lead by example, inspire others, embrace continuous improvement, and develop high-performing teams. Loyalty – We build lasting relationships through trust, respect, and dedication to our clients, teammates, and community. Service to Our Clients – We are committed to delivering compassionate, responsive, and exceptional service that maximizes every client's opportunity for success. Service to Our Teammates – We foster a culture of collaboration, respect, support, and shared success where every team member has the opportunity to grow and thrive. Service to Our Community – We believe in making a positive impact beyond the workplace by serving and strengthening the communities where we live and work. If you are passionate about helping injured clients, thrive in a fast-paced, results-driven environment, and are committed to delivering exceptional client service while continuously growing your career, we invite you to join The Ward Law Group and help us change lives—one client at a time." We can condense but must preserve all substantive info; we can keep as prose. Position Overview: "The Lien Resolution Team Lead runs the function that determines how much of every settlement actually reaches our clients. You will supervise a team of reductions and lien resolution specialists, personally handle the largest and most complex lien files, and own the metrics that measure our performance — aggregate reduction rate, net-to-client percentage, and time from settlement to disbursement. This is a negotiation role with a management layer on top. Every dollar your team takes off a medical balance, a hospital lien, or a health plan’s subrogation claim is a dollar that goes to an injured client instead. You will set the standard for how hard those negotiations are pushed, hold the team to it, and step in personally when a provider or plan will not move." Key Responsibilities: list bullet points. We need to convert each responsibility into - . Let's extract bullet points from the responsibilities paragraph: - Post-settlement medical bill and liens (maybe heading). Actually the responsibilities start with "Post-settlement medical bill and liens" then a dash? The text: "Post-settlement medical bill and liens Lead the team. Supervise, train, and evaluate a team of reductions and lien