Auto Loans Collections Specialist
for headings. Use - for any list of duties/requirements/benefits. Use
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate etc. Preserve all substantive info. 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 parse the posting.
Key sections:
- About the Role: description after "About the Role:" includes responsibilities? Actually "About the Role: As an Auto Collections Specialist you will be responsible for managing and resolving mid-stage delinquent auto loan accounts..." That's a description.
- Starting Pay: $22.00/Hour
- What You'll Do: list of duties (bulleted). That's responsibilities.
- What We Look For: list of requirements (experience, skills). That's qualifications/requirements.
- Nice to Have: optional nice-to-have (maybe skills). Could be under Skills or Qualifications.
- What We Offer You: list of benefits (benefits). That's benefits.
- Environmental & Working Conditions: description of work environment (maybe schedule? Not schedule). Could be under "Work Environment" but not requested. We can maybe include under "Benefits"? No. The requested sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can combine some.
We need to decide which sections to include based on content.
We have:
- About the Role: we have a paragraph.
- Responsibilities: we have "What You'll Do" list.
- Requirements: we have "What We Look For" list (required qualifications). Could be Requirements.
- Qualifications: maybe same as Requirements? Could split but we should avoid thin sections. Perhaps combine Requirements and Qualifications into one? But we need to follow instruction: include a section only when posting has real specific content for it. We can have both if content distinct. "What We Look For" includes required experience, skills. "Nice to Have" includes additional preferred qualifications. Could treat "What We Look For" as Requirements, and "Nice to Have" as Qualifications or Skills. But we also have Skills section maybe separate.
We have also "Starting Pay" => Pay.
We have benefits list => Benefits.
We have schedule? Not mentioned explicitly. No schedule info. So we should NOT include Schedule section because no specific content.
We have also "Environmental & Working Conditions" description; could be under "Work Environment" but not requested. Could we put under "About the role"? Probably not. Could we include under "Benefits"? No. Could we create a section like "Work Environment"? Not in requested list, so we should omit because we only output sections from the list? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can use those headings, but not required to use all. It says "include a section ONLY when the posting has real, specific content for it". So we can omit sections not present.
Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay.
We need to decide content for each.
About the role: paragraph from "About the Role:" sentence.
Responsibilities: list from "What You'll Do:" bullet points.
Requirements: list from "What We Look For:" required items.
Qualifications: maybe we can put "Nice to Have:" as Qualifications (preferred qualifications). Or we could treat "Nice to Have:" as Skills? But we already have Skills section maybe for specific skills like bilingual, CRM proficiency etc. However those are already in requirements. Let's parse:
"What We Look For:" includes:
- 1+ years of collections experience (auto finance preferred)
- Experience working delinquent accounts in the 60+ DPD range
- Strong negotiation and customer communication skills
- Ability to handle difficult conversations professionally and confidently
- Working knowledge of FDCPA and consumer protection regulations
- Strong time management and organizational skills
- Ability to thrive in a fast-paced, metrics-driven environment
- Proficiency with CRM and collection systems
- Bilingual (Spanish) required
That's a mix of experience and skills.
"Nice to Have:" includes:
- Auto finance or secured lending collections experience
- Experience with repossession prevention and reinstatement
- Familiarity with skip tracing and advanced contact strategies
These are additional preferred experience/skills.
Thus we could have:
- Requirements: the required items list.
- Qualifications: the nice-to-have list (preferred qualifications).
- Skills: maybe we could extract specific skills like negotiation, communication, CRM proficiency, bilingual, time management, etc. But that would duplicate. Better to keep Requirements and Qualifications as above, and maybe omit Skills section to avoid thin sections. However we have a Skills heading in the list; we could include if we have specific skill content not covered elsewhere. But we already covered skills in Requirements. Could we create a Skills section for "Bilingual (Spanish) required" and "Proficiency with CRM and collection systems"? But those are already in Requirements. To avoid duplication, maybe we just not include Skills section.
But the instruction says "Prefer a few substantive sections over many thin ones." So we can combine Requirements and Qualifications into one section maybe called "Requirements & Qualifications". But the headings are fixed examples; we could still use "Requirements" and put both required and nice-to-have under it, labeling? But we need to preserve all substantive info; we can include both under Requirements with subheadings? Not allowed to add extra headings beyond h3? We could use
to differentiate. But better to have two sections: Requirements and Qualifications.
Thus we will have:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
Benefits
- ...
...
Pay
Starting Pay: $22.00/Hour
We should not include Schedule.
Now we need to strip boilerplate: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "For California residents: ..." and "Environmental & Working Conditions" etc. Also remove "We are an equal opportunity employer..." etc. Also remove "Upgrade does not accept unsolicited resumes..." etc. Also remove "English is required for all positions..." etc.
We need to preserve all substantive information: that includes the description about company, mission, stats, culture, awards? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. However earlier they said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company overview paragraph at start is substantive? It describes the company, mission, stats, culture, awards. That is substantive info about the company, not boilerplate. Should we keep it? The sections we are outputting are about the role etc. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we must include a company overview section. But we could include it under "About the role"? Actually "About the role" is specific to the role, not company overview. The company overview could be considered part of "About the role"? Not really. But we could include a separate section like "About Upgrade"? Not in the list of headings. The instruction says we can use those headings as examples; maybe we can also use other headings? It 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 an exhaustive list. However later: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could add a section for "About Upgrade" if we want, but it's not in the examples. Safer to stick to the given headings. The company overview may be considered part of "About the role"? Not exactly. But we could incorporate some of that into About the role paragraph? The About the role currently is just the role description. We could expand it to include company overview? That would be adding info not originally under About the role heading but still substantive. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep the company overview somewhere. If we don't have a heading for it, we could put it as a
before the first heading? The instruction says output ONLY the HTML fragment — no /, no markdown code fences. It doesn't forbid having stray paragraphs before headings. So we could include a
with company overview before the first heading. That would preserve it.
Thus we will output:
Upgrade helps customers move in the right direction with affordable and responsible financial products. Since 2017, we’ve helped over 7.5 million customers access over $42 billion in consumer credit. With a relentless focus on improving our customers' financial well-being, we build products that put more money in their pocket and support their journey toward a better financial future. We’re backed by some of the most prominent technology investors and were most recently valued at $7.3B. We’re consistently recognized for our collaborative and inclusive culture. Most recently, we were named one of the World’s Top Fintech Companies by CNBC, Best Places to Work by Built In, Best Places to Work by the San Francisco Business Times, America’s Greatest Workplaces by Newsweek, Best Startup Employer by Forbes, and Healthiest Employers by Phoenix Business Journal.
Then the sections.
Now we need to extract the exact text for each bullet.
Let's copy the relevant parts.
About the Role paragraph: "As an Auto Collections Specialist you will be responsible for managing and resolving mid-stage delinquent auto loan accounts that are for 60–89 days past due; through effective customer engagement, negotiation, and loss-mitigation strategies. This role focuses on curing delinquency, preventing charge-off and repossession, and maintaining strong compliance with all federal, state, and company regulations. Requires strong negotiation skills, critical thinking, urgency, and the ability to build rapport while driving results in a fast-paced, performance-driven environment."
We need to keep that as a .
Now Responsibilities: "What You'll Do:" list:
- Manage a daily queue of auto loan accounts that are 60–89 days past due.
- Contact customers via outbound and inbound calls to resolve delinquency.
- Negotiate payment arrangements, settlements, and reinstatement options.
- Identify root causes of delinquency and recommend appropriate loss-mitigation solutions.
- Educate customers on account status, contract terms, and available resolution options.
- Drive timely payments and account cures to reduce delinquency and prevent repossession.
- Accurately document all account activity, call notes, and customer commitments.
- Maintain full compliance with FDCPA, CFPB, state regulations, and company policies.
- Meet or exceed daily, weekly, and monthly performance goals (RPC, PTP, dollars collected, cure rate, etc.).
- Escalate high-risk or complex accounts appropriately (hardship, fraud indicators, disputes, complaints, etc.).
- Partner with servicing, titles, insurance, and repossession teams as needed.
We need to keep each as
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate etc. Preserve all substantive info. 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 parse the posting. Key sections: - About the Role: description after "About the Role:" includes responsibilities? Actually "About the Role: As an Auto Collections Specialist you will be responsible for managing and resolving mid-stage delinquent auto loan accounts..." That's a description. - Starting Pay: $22.00/Hour - What You'll Do: list of duties (bulleted). That's responsibilities. - What We Look For: list of requirements (experience, skills). That's qualifications/requirements. - Nice to Have: optional nice-to-have (maybe skills). Could be under Skills or Qualifications. - What We Offer You: list of benefits (benefits). That's benefits. - Environmental & Working Conditions: description of work environment (maybe schedule? Not schedule). Could be under "Work Environment" but not requested. We can maybe include under "Benefits"? No. The requested sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can combine some. We need to decide which sections to include based on content. We have: - About the Role: we have a paragraph. - Responsibilities: we have "What You'll Do" list. - Requirements: we have "What We Look For" list (required qualifications). Could be Requirements. - Qualifications: maybe same as Requirements? Could split but we should avoid thin sections. Perhaps combine Requirements and Qualifications into one? But we need to follow instruction: include a section only when posting has real specific content for it. We can have both if content distinct. "What We Look For" includes required experience, skills. "Nice to Have" includes additional preferred qualifications. Could treat "What We Look For" as Requirements, and "Nice to Have" as Qualifications or Skills. But we also have Skills section maybe separate. We have also "Starting Pay" => Pay. We have benefits list => Benefits. We have schedule? Not mentioned explicitly. No schedule info. So we should NOT include Schedule section because no specific content. We have also "Environmental & Working Conditions" description; could be under "Work Environment" but not requested. Could we put under "About the role"? Probably not. Could we include under "Benefits"? No. Could we create a section like "Work Environment"? Not in requested list, so we should omit because we only output sections from the list? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can use those headings, but not required to use all. It says "include a section ONLY when the posting has real, specific content for it". So we can omit sections not present. Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We need to decide content for each. About the role: paragraph from "About the Role:" sentence. Responsibilities: list from "What You'll Do:" bullet points. Requirements: list from "What We Look For:" required items. Qualifications: maybe we can put "Nice to Have:" as Qualifications (preferred qualifications). Or we could treat "Nice to Have:" as Skills? But we already have Skills section maybe for specific skills like bilingual, CRM proficiency etc. However those are already in requirements. Let's parse: "What We Look For:" includes: - 1+ years of collections experience (auto finance preferred) - Experience working delinquent accounts in the 60+ DPD range - Strong negotiation and customer communication skills - Ability to handle difficult conversations professionally and confidently - Working knowledge of FDCPA and consumer protection regulations - Strong time management and organizational skills - Ability to thrive in a fast-paced, metrics-driven environment - Proficiency with CRM and collection systems - Bilingual (Spanish) required That's a mix of experience and skills. "Nice to Have:" includes: - Auto finance or secured lending collections experience - Experience with repossession prevention and reinstatement - Familiarity with skip tracing and advanced contact strategies These are additional preferred experience/skills. Thus we could have: - Requirements: the required items list. - Qualifications: the nice-to-have list (preferred qualifications). - Skills: maybe we could extract specific skills like negotiation, communication, CRM proficiency, bilingual, time management, etc. But that would duplicate. Better to keep Requirements and Qualifications as above, and maybe omit Skills section to avoid thin sections. However we have a Skills heading in the list; we could include if we have specific skill content not covered elsewhere. But we already covered skills in Requirements. Could we create a Skills section for "Bilingual (Spanish) required" and "Proficiency with CRM and collection systems"? But those are already in Requirements. To avoid duplication, maybe we just not include Skills section. But the instruction says "Prefer a few substantive sections over many thin ones." So we can combine Requirements and Qualifications into one section maybe called "Requirements & Qualifications". But the headings are fixed examples; we could still use "Requirements" and put both required and nice-to-have under it, labeling? But we need to preserve all substantive info; we can include both under Requirements with subheadings? Not allowed to add extra headings beyond h3? We could use
to differentiate. But better to have two sections: Requirements and Qualifications. Thus we will have:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Benefits
- ... ...
Pay
Starting Pay: $22.00/Hour
We should not include Schedule. Now we need to strip boilerplate: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "For California residents: ..." and "Environmental & Working Conditions" etc. Also remove "We are an equal opportunity employer..." etc. Also remove "Upgrade does not accept unsolicited resumes..." etc. Also remove "English is required for all positions..." etc. We need to preserve all substantive information: that includes the description about company, mission, stats, culture, awards? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. However earlier they said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company overview paragraph at start is substantive? It describes the company, mission, stats, culture, awards. That is substantive info about the company, not boilerplate. Should we keep it? The sections we are outputting are about the role etc. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we must include a company overview section. But we could include it under "About the role"? Actually "About the role" is specific to the role, not company overview. The company overview could be considered part of "About the role"? Not really. But we could include a separate section like "About Upgrade"? Not in the list of headings. The instruction says we can use those headings as examples; maybe we can also use other headings? It 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 an exhaustive list. However later: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could add a section for "About Upgrade" if we want, but it's not in the examples. Safer to stick to the given headings. The company overview may be considered part of "About the role"? Not exactly. But we could incorporate some of that into About the role paragraph? The About the role currently is just the role description. We could expand it to include company overview? That would be adding info not originally under About the role heading but still substantive. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep the company overview somewhere. If we don't have a heading for it, we could put it as a
before the first heading? The instruction says output ONLY the HTML fragment — no /, no markdown code fences. It doesn't forbid having stray paragraphs before headings. So we could include a
with company overview before the first heading. That would preserve it. Thus we will output:
Upgrade helps customers move in the right direction with affordable and responsible financial products. Since 2017, we’ve helped over 7.5 million customers access over $42 billion in consumer credit. With a relentless focus on improving our customers' financial well-being, we build products that put more money in their pocket and support their journey toward a better financial future. We’re backed by some of the most prominent technology investors and were most recently valued at $7.3B. We’re consistently recognized for our collaborative and inclusive culture. Most recently, we were named one of the World’s Top Fintech Companies by CNBC, Best Places to Work by Built In, Best Places to Work by the San Francisco Business Times, America’s Greatest Workplaces by Newsweek, Best Startup Employer by Forbes, and Healthiest Employers by Phoenix Business Journal.
Then the sections. Now we need to extract the exact text for each bullet. Let's copy the relevant parts. About the Role paragraph: "As an Auto Collections Specialist you will be responsible for managing and resolving mid-stage delinquent auto loan accounts that are for 60–89 days past due; through effective customer engagement, negotiation, and loss-mitigation strategies. This role focuses on curing delinquency, preventing charge-off and repossession, and maintaining strong compliance with all federal, state, and company regulations. Requires strong negotiation skills, critical thinking, urgency, and the ability to build rapport while driving results in a fast-paced, performance-driven environment." We need to keep that as a. Now Responsibilities: "What You'll Do:" list: - Manage a daily queue of auto loan accounts that are 60–89 days past due. - Contact customers via outbound and inbound calls to resolve delinquency. - Negotiate payment arrangements, settlements, and reinstatement options. - Identify root causes of delinquency and recommend appropriate loss-mitigation solutions. - Educate customers on account status, contract terms, and available resolution options. - Drive timely payments and account cures to reduce delinquency and prevent repossession. - Accurately document all account activity, call notes, and customer commitments. - Maintain full compliance with FDCPA, CFPB, state regulations, and company policies. - Meet or exceed daily, weekly, and monthly performance goals (RPC, PTP, dollars collected, cure rate, etc.). - Escalate high-risk or complex accounts appropriately (hardship, fraud indicators, disputes, complaints, etc.). - Partner with servicing, titles, insurance, and repossession teams as needed. We need to keep each as