Finance Operations Coordinator
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map content to these headings where appropriate. The instructions: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. 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. Output ONLY the HTML fragment — no /, no markdown code fences.
Thus we need to decide which sections to include based on content.
We have:
- Who We Are (company overview) - could be "About the role"? Actually "About the role" is typical heading for role overview. But we have "Role Overview". Could map to "About the role". Or we could keep "Role Overview" as heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those standard ones. Probably we should map content to those standard headings where appropriate.
Thus:
- About the role: could include "Role Overview" and maybe "Who We Are"? But "Who We Are" is about company, not role. Might be better as a separate section like "About CarGurus"? Not in list. But we could still include a heading like "About CarGurus"? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, but to follow the pattern. Probably safer to stick to those headings. However we need to preserve all substantive information. If we omit "Who We Are" and "What We Do", we lose info. But maybe we can incorporate that into "About the role" as a brief company description. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine company overview into "About the role". That seems acceptable.
Thus sections:
- About the role: includes Who We Are, What We Do, Role Overview.
- Responsibilities: What You'll Do (list of duties).
- Requirements/Qualifications: What You'll Bring (experience, education, skills). Could split into Requirements and Qualifications but we can combine.
- Skills: maybe list specific skills (Excel, CRM/ERP, communication). Could be part of Requirements.
- Pay: Position Pay Range.
- Benefits: Working at CarGurus (benefits description).
We should not include Schedule (not mentioned). So omit.
We need to use - for any list of duties/requirements/benefits. So for responsibilities, we need a list. For requirements/qualifications, also list. For benefits, also list.
We need to preserve all substantive information, not invent or summarize away detail. So we need to keep details like "Respond to incoming cases and phone calls related to billing, payments, and account inquiries." etc.
We need to remove boilerplate: EEO, etc. At the end there is EEO statement and accommodation request. Remove that.
Also remove "CarGurus may require in-person interviews..." etc. That's application instructions? It's about interview process. Might be considered application instructions? The instruction says remove application instructions. So we should remove that paragraph about in-person interviews and travel expenses.
Also remove "We welcome all CarGurus strives to be a place..." etc. That's EEO boilerplate. Remove.
Thus final HTML will have sections:
About the role
... combined company overview and role overview ...
Responsibilities
- ...
...
Requirements
- ...
...
Maybe also Skills
but we can incorporate into Requirements.
Pay
Position Pay Range $43,000—$54,000 USD
Benefits
- ...
...
We need to ensure we don't create empty sections.
Now let's extract content.
Who We Are:
"At CarGurus (NASDAQ: CARG), our mission is to give people the power to reach their destination. We started as a small team of developers determined to bring trust and transparency to car shopping. Since then, our history of innovation and go-to-market acceleration has driven industry-leading growth. In fact, we’re the largest and fastest-growing automotive marketplace, and we’ve been profitable for over 15 years."
What We Do:
"The market is evolving, and we are too, moving the entire automotive journey online and guiding our customers through every step. That includes everything from the sale of an old car to the financing, purchase, and delivery of a new one. Today, tens of millions of consumers visit CarGurus.com each month, and ~30,000 dealerships use our products. But they're not the only ones who love CarGurus—our employees do, too. We have a people-first culture that fosters kindness, collaboration, and innovation, and empowers our Gurus with tools to fuel their career growth. Disrupting a trillion-dollar industry requires fresh and diverse perspectives. Come join us for the ride!"
Role Overview:
"We’re looking for a detail-oriented and motivated Finance Operations Coordinator. This role is ideal for someone eager to learn, thrive in a fast-paced environment, and make an immediate impact by supporting billing, payments, and customer account maintenance. You’ll be part of the front line for our Finance Operations team, working directly with customers and cross-functional partners to ensure accuracy, timeliness, and excellent customer experience."
Combine these into About the role paragraph(s). Could be multiple tags.
Now Responsibilities (What You'll Do):
List:
- Respond to incoming cases and phone calls related to billing, payments, and account inquiries.
- Ensure timely and accurate resolutions while meeting individual and team KPIs.
- Create credits and maintain customer account balances while adhering to internal approval policies.
- Support cross-functional teams including Sales, Sales Operations, and Collections to resolve customer issues and improve processes.
- Maintain and update customer master data in our financial systems to ensure integrity and consistency.
- Identify trends or recurring issues and communicate them to leadership for continuous improvement.
- Perform additional administrative or operational tasks as needed to support the Finance Operations team.
Note: The original had no bullet points but sentences separated by periods. We'll make list.
Now Requirements (What You'll Bring):
- 1–3 years of experience in AR, Billing, or Customer Support.
- Bachelor’s degree in business, Finance, Accounting, or related field preferred.
- Strong attention to detail with the ability to work quickly and accurately under pressure.
- Excellent written and verbal communication skills for customer-facing interactions.
- Comfortable managing high volumes of work while maintaining accuracy.
- Eager to learn new systems and processes; self-motivated with a strong work ethic.
- Proficiency with Microsoft Excel and familiarity with CRM or ERP systems (e.g., Salesforce, Zuora, NetSuite) a plus.
We could also include "Bachelor’s degree ... preferred" as a requirement.
Now Benefits (Working at CarGurus):
List:
- Equity for all employees, both when they start and as they continue to grow with us.
- Career development and corporate giving programs.
- Employee resource groups (ERGs) and communities.
- Flexible hybrid model.
- Robust time off policies.
- Thoughtful perks like daily free lunch, a new car discount, meditation and fitness apps, commuting cost coverage, and more.
We need to preserve all substantive information. The paragraph: "Working at CarGurus We reward our Gurus’ curiosity and passion with best-in-class benefits and compensation, including equity for all employees, both when they start and as they continue to grow with us. Our career development and corporate giving programs, as well as our employee resource groups (ERGs) and communities, help people build connections while making an impact in personally meaningful ways. A flexible hybrid model and robust time off policies encourage work-life balance and individual well-being. Thoughtful perks like daily free lunch, a new car discount, meditation and fitness apps, commuting cost coverage, and more help our people create space for what matters most in their personal and professional lives."
We'll turn into list items.
Pay: "Position Pay Range $43,000—$54,000 USD". Also note about OTE etc. The posting includes: "The displayed range represents the expected annual base salary / On-Target Earnings (OTE) for this position. On-Target Earnings (OTE) is inclusive of base salary and on-target commission earnings, which applies exclusively to sales roles. Individual pay within this range is determined by work location and other factors such as job-related skills, experience, and relevant education or training. This annual base salary forms part of a comprehensive Total Rewards Package. In addition to benefits, this role may qualify for discretionary bonuses/incentives and Restricted Stock Units (RSUs)."
We need to preserve all substantive information. So we should include that explanation as well, not just the range. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay range and details. So we should include a Pay section with that info. Could be a
containing the range and explanation.
Thus Pay section:
Pay
The displayed range represents the expected annual base salary / On-Target Earnings (OTE) for this position. On-Target Earnings (OTE) is inclusive of base salary and on-target commission earnings, which applies exclusively to sales roles. Individual pay within this range is determined by work location and other factors such as job-related skills, experience, and relevant education or training. This annual base salary forms part of a comprehensive Total Rewards Package. In addition to benefits, this role may qualify for discretionary bonuses/incentives and Restricted Stock Units (RSUs). Position Pay Range $43,000—$54,000 USD
We need to avoid duplication; but it's fine.
Now ensure we removed boilerplate: EEO statement, accommodation request, in-person interview paragraph, etc.
Check for any duplicated lines: none.
Now output HTML fragment.
We'll structure:
About the role
...
...
...
Responsibilities
- ...
...
Requirements
- ...
...
Pay
...
Benefits
- ...
...
We could also add Skills section but not needed.
Make sure no extra whitespace at start
- for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. 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. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to decide which sections to include based on content. We have: - Who We Are (company overview) - could be "About the role"? Actually "About the role" is typical heading for role overview. But we have "Role Overview". Could map to "About the role". Or we could keep "Role Overview" as heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those standard ones. Probably we should map content to those standard headings where appropriate. Thus: - About the role: could include "Role Overview" and maybe "Who We Are"? But "Who We Are" is about company, not role. Might be better as a separate section like "About CarGurus"? Not in list. But we could still include a heading like "About CarGurus"? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, but to follow the pattern. Probably safer to stick to those headings. However we need to preserve all substantive information. If we omit "Who We Are" and "What We Do", we lose info. But maybe we can incorporate that into "About the role" as a brief company description. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine company overview into "About the role". That seems acceptable. Thus sections: - About the role: includes Who We Are, What We Do, Role Overview. - Responsibilities: What You'll Do (list of duties). - Requirements/Qualifications: What You'll Bring (experience, education, skills). Could split into Requirements and Qualifications but we can combine. - Skills: maybe list specific skills (Excel, CRM/ERP, communication). Could be part of Requirements. - Pay: Position Pay Range. - Benefits: Working at CarGurus (benefits description). We should not include Schedule (not mentioned). So omit. We need to use
- for any list of duties/requirements/benefits. So for responsibilities, we need a list. For requirements/qualifications, also list. For benefits, also list.
We need to preserve all substantive information, not invent or summarize away detail. So we need to keep details like "Respond to incoming cases and phone calls related to billing, payments, and account inquiries." etc.
We need to remove boilerplate: EEO, etc. At the end there is EEO statement and accommodation request. Remove that.
Also remove "CarGurus may require in-person interviews..." etc. That's application instructions? It's about interview process. Might be considered application instructions? The instruction says remove application instructions. So we should remove that paragraph about in-person interviews and travel expenses.
Also remove "We welcome all CarGurus strives to be a place..." etc. That's EEO boilerplate. Remove.
Thus final HTML will have sections:
About the role
... combined company overview and role overview ...
Responsibilities
- ... ...
Requirements
- ... ...
Skills
but we can incorporate into Requirements.Pay
Position Pay Range $43,000—$54,000 USD
Benefits
- ... ...
tags. Now Responsibilities (What You'll Do): List: - Respond to incoming cases and phone calls related to billing, payments, and account inquiries. - Ensure timely and accurate resolutions while meeting individual and team KPIs. - Create credits and maintain customer account balances while adhering to internal approval policies. - Support cross-functional teams including Sales, Sales Operations, and Collections to resolve customer issues and improve processes. - Maintain and update customer master data in our financial systems to ensure integrity and consistency. - Identify trends or recurring issues and communicate them to leadership for continuous improvement. - Perform additional administrative or operational tasks as needed to support the Finance Operations team. Note: The original had no bullet points but sentences separated by periods. We'll make list. Now Requirements (What You'll Bring): - 1–3 years of experience in AR, Billing, or Customer Support. - Bachelor’s degree in business, Finance, Accounting, or related field preferred. - Strong attention to detail with the ability to work quickly and accurately under pressure. - Excellent written and verbal communication skills for customer-facing interactions. - Comfortable managing high volumes of work while maintaining accuracy. - Eager to learn new systems and processes; self-motivated with a strong work ethic. - Proficiency with Microsoft Excel and familiarity with CRM or ERP systems (e.g., Salesforce, Zuora, NetSuite) a plus. We could also include "Bachelor’s degree ... preferred" as a requirement. Now Benefits (Working at CarGurus): List: - Equity for all employees, both when they start and as they continue to grow with us. - Career development and corporate giving programs. - Employee resource groups (ERGs) and communities. - Flexible hybrid model. - Robust time off policies. - Thoughtful perks like daily free lunch, a new car discount, meditation and fitness apps, commuting cost coverage, and more. We need to preserve all substantive information. The paragraph: "Working at CarGurus We reward our Gurus’ curiosity and passion with best-in-class benefits and compensation, including equity for all employees, both when they start and as they continue to grow with us. Our career development and corporate giving programs, as well as our employee resource groups (ERGs) and communities, help people build connections while making an impact in personally meaningful ways. A flexible hybrid model and robust time off policies encourage work-life balance and individual well-being. Thoughtful perks like daily free lunch, a new car discount, meditation and fitness apps, commuting cost coverage, and more help our people create space for what matters most in their personal and professional lives." We'll turn into list items. Pay: "Position Pay Range $43,000—$54,000 USD". Also note about OTE etc. The posting includes: "The displayed range represents the expected annual base salary / On-Target Earnings (OTE) for this position. On-Target Earnings (OTE) is inclusive of base salary and on-target commission earnings, which applies exclusively to sales roles. Individual pay within this range is determined by work location and other factors such as job-related skills, experience, and relevant education or training. This annual base salary forms part of a comprehensive Total Rewards Package. In addition to benefits, this role may qualify for discretionary bonuses/incentives and Restricted Stock Units (RSUs)." We need to preserve all substantive information. So we should include that explanation as well, not just the range. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay range and details. So we should include a Pay section with that info. Could be a
containing the range and explanation. Thus Pay section:
Pay
The displayed range represents the expected annual base salary / On-Target Earnings (OTE) for this position. On-Target Earnings (OTE) is inclusive of base salary and on-target commission earnings, which applies exclusively to sales roles. Individual pay within this range is determined by work location and other factors such as job-related skills, experience, and relevant education or training. This annual base salary forms part of a comprehensive Total Rewards Package. In addition to benefits, this role may qualify for discretionary bonuses/incentives and Restricted Stock Units (RSUs). Position Pay Range $43,000—$54,000 USD
We need to avoid duplication; but it's fine. Now ensure we removed boilerplate: EEO statement, accommodation request, in-person interview paragraph, etc. Check for any duplicated lines: none. Now output HTML fragment. We'll structure:About the role
...
...
...
Responsibilities
- ... ...
Requirements
- ... ...
Pay
...
Benefits
- ... ...
- for any list of duties/requirements/benefits. So for responsibilities, we need a list. For requirements/qualifications, also list. For benefits, also list.
We need to preserve all substantive information, not invent or summarize away detail. So we need to keep details like "Respond to incoming cases and phone calls related to billing, payments, and account inquiries." etc.
We need to remove boilerplate: EEO, etc. At the end there is EEO statement and accommodation request. Remove that.
Also remove "CarGurus may require in-person interviews..." etc. That's application instructions? It's about interview process. Might be considered application instructions? The instruction says remove application instructions. So we should remove that paragraph about in-person interviews and travel expenses.
Also remove "We welcome all CarGurus strives to be a place..." etc. That's EEO boilerplate. Remove.
Thus final HTML will have sections: