General Manager

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate like EEO, legal, etc. Must preserve all substantive info. We need to parse the posting. Content: - Intro: "Collision General Manager Classic Collision was established in 1983 in Atlanta, Georgia with one single goal: To offer quality service to its customers with integrity and honesty. Be a part of a rapidly growing company whose mission is to put safety, quality, integrity, and heart into every vehicle we repair and customer we serve. Classic Collision offers competitive pay, benefits, and career advancement opportunities. Please come and join our team! Why Choose Classic Collision? Paid Weekly Continuous Training Supportive Team Culture Company match 401K Medical/Dental/Vision Paid Time Off – 6 Paid Holiday Rewarding Work" That's about company and benefits. So we can have an "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content. We have responsibilities: "The General Manager is responsible for the overall operations and financial results of their assigned store including but not limited to operations, internal and external development, business relationships, and profitability. The General Manager is expected to mentor to all direct reports while leading the team effectively and efficiently. Essential Responsibilities Actively lead center level performance though: key metrics, quality, individual skill levels and culture Communicate and manage the change process Stay abreast of current vehicle repair procedures and technologies Manage and hold all staff accountable for shop performance though Recipe Book execution. Ensure customer satisfaction by coaching staff and resolve customer concerns as required Recruit, interview and hire new staff as required Train new hires regarding company policy and procedures Promote safe, clean working conditions Promote, develop and act as a liaison with area insurance contacts and other referral points Contact all claims managers and dealer accounts every month Participate in external marketing and team building activities as requested Other duties may be assigned as necessary" We have skills/requirements: "Skills/Requirements Minimum of five years collision repair / auto body management experience REQUIRED Proven leadership and track record of employee development Ability to read and understand financial P&L statements required ICAR Platinum certification preferred Ability to travel up to 25% Must have valid a driver's license and be eligible for insurance coverage Working knowledge of CCC One estimating platform and management system Advanced skills in Microsoft Office, including Word, Excel, Outlook and PPT. Ability to read and interpret documents such as repair procedures, safety rules, operating and maintenance instructions, and procedure manuals Ability to write routine reports and correspondence Ability to speak effectively before groups of customers or employees of organization" Also there is a note: "Critical features of this position are described under the heading. They may be subject to change at any time due to reasonable accommodations or managements’ rights to reassign duties and responsibilities of this job at any time." That's filler, maybe ignore. Physical demands etc: maybe not needed as a section; but we could include under Requirements? But we have no specific heading for Physical Demands. The instruction says only include sections when posting has real specific content. Physical demands is specific content; but we don't have a heading for it in the allowed list. We could possibly put under Requirements or Qualifications? But better to omit if not matching allowed headings. The instruction says use those headings for section headings. It doesn't forbid 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, but likely they want only those. Safer to stick to those. We have benefits info: "Paid Weekly Continuous Training Supportive Team Culture Company match 401K Medical/Dental/Vision Paid Time Off – 6 Paid Holiday Rewarding Work". Also earlier: "Classic Collision offers competitive pay, benefits, and career advancement opportunities." So we have benefits. Pay: "competitive pay" but not specific amount. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "competitive pay" but that's vague. However it's still stating pay exists. Might be considered stating them? It says "competitive pay" which is not a specific number but still mentions pay. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "competitive pay". So we could include a Pay section with that phrase. However they also said "Prefer a few substantive sections over many thin ones." Might be better to incorporate pay into Benefits or About the role. But we have a Benefits section already; we could include pay there. But they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." Since they state competitive pay, we could include Pay section with that line. But we also have benefits; we could combine? The instruction says use those headings; we can include Pay and Benefits separate if content exists. Schedule: not mentioned. So omit Schedule. Qualifications: maybe we have ICAR Platinum certification preferred, driver's license, etc. Could be under Qualifications. Requirements: maybe years experience, leadership, etc. Skills: maybe technical skills. We need to avoid duplication. Let's structure:

About the role

: intro about company and mission? Could be about the role: "The General Manager is responsible for the overall operations..." but that's responsibilities. Actually About the role could be a brief summary: "Be a part of a rapidly growing company whose mission is to put safety, quality, integrity, and heart into every vehicle we repair and customer we serve." plus maybe "Classic Collision offers competitive pay, benefits, and career advancement opportunities." That seems appropriate.

Responsibilities

: list of essential responsibilities.

Requirements

: Minimum of five years collision repair / auto body management experience REQUIRED; Proven leadership and track record of employee development; Ability to read and understand financial P&L statements required; Must have valid driver's license and be eligible for insurance coverage; Ability to travel up to 25%; Working knowledge of CCC One estimating platform and management system; Advanced skills in Microsoft Office, including Word, Excel, Outlook and PPT.; Ability to read and interpret documents such as repair procedures, safety rules, operating and maintenance instructions, and procedure manuals; Ability to write routine reports and correspondence; Ability to speak effectively before groups of customers or employees of organization.

Qualifications

: ICAR Platinum certification preferred; maybe also "Proven leadership..." but that's already in Requirements. Could put certification here.

Skills

: maybe overlapping; but we could put technical skills here: CCC One, Microsoft Office, etc. But we already put many in Requirements. To avoid duplication, we could separate: Requirements = experience, leadership, travel, license; Qualifications = certifications; Skills = technical abilities (CCC One, MS Office, reading/interpreting docs, writing reports, speaking). However the posting lumps them together under Skills/Requirements. We need to decide. Better to follow the posting: they have a "Skills/Requirements" heading. We could map that to either Requirements or Skills. Since we have both headings allowed, we could split: Requirements = experience, leadership, travel, license; Skills = technical abilities (CCC One, MS Office, reading docs, writing reports, speaking). Qualifications = certifications (ICAR Platinum preferred). That seems reasonable. Benefits: list: Paid Weekly, Continuous Training, Supportive Team Culture, Company match 401K, Medical/Dental/Vision, Paid Time Off – 6 Paid Holiday, Rewarding Work. Also "competitive pay" maybe in Pay section. Pay: "competitive pay". Could also mention career advancement opportunities but that's more about benefits. We'll create Pay section with "Competitive pay (specific amount not disclosed)". But we must not invent or summarize away detail. We cannot add "specific amount not disclosed" because that's not in posting. We must preserve ALL substantive information; do NOT invent or summarize away detail. So we can only put exactly what is stated: "competitive pay". That's it. So Pay section will have

Competitive pay

. Benefits section will have list. Now ensure we don't include boilerplate like EEO, legal, etc. Remove those paragraphs. Also remove "Note Critical features..." etc. Also remove "Physical Demands & Work Environment" and "Behaviors/Competencies" etc because they are not in allowed headings; but we could maybe incorporate into Requirements? But better to omit as they are not requested headings. However we must preserve ALL substantive information. If we omit those, we are losing substantive info (physical demands, behaviors). The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we cannot drop them unless we can fit them into allowed headings. We could incorporate them under Requirements or Qualifications? But they are not exactly requirements; they are physical demands and behaviors/competencies. Could we create a section for "Physical Demands" or "Behaviors"? Not in allowed list but maybe we can still use

for those if they are substantive? 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, but likely they expect only those headings. However the instruction also says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid other headings, but the examples given are those. To be safe, we could create additional headings for Physical Demands and Behaviors/Competencies, but they'd be non-standard. Might be considered violating the instruction to use those headings. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This could be interpreted as you must use those headings for sections; you can also use other headings? The phrase "e.g." indicates examples, not exhaustive list. So we could use other headings if needed. However they also say "Prefer a few substantive sections over many thin ones." So maybe better to incorporate those details into existing sections like Requirements or Qualifications. Physical demands: "Frequently required to stand..." etc. Could be under Requirements as "Physical demands: frequently required to stand, walk, occasionally sit, use hands and fingers, climb, balance, bend, stoop, kneel or crawl, continually talk or hear, lift/push weights up to 50 pounds." That's substantive. Behaviors/Competencies: list of integrity, respect, accountability, customer service, innovation, teamwork. Could be under Requirements or Qualifications as "Expected behaviors/competencies: integrity, respect, accountability, customer service, innovation, teamwork." We can incorporate them. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We'll omit Schedule. Now we need to ensure we don't repeat content. Let's draft About the role: Paragraph: "Classic Collision was established in 1983 in Atlanta, Georgia with one single goal: To offer quality service to its customers with integrity and honesty. Be a part of a rapidly growing company whose mission is to put safety, quality, integrity, and heart into every vehicle we repair and customer we serve. Classic Collision offers competitive pay, benefits, and career advancement opportunities." That's fine. Responsibilities: list bullet points. We need to capture all responsibilities from the posting. Let's extract: - Actively lead center level performance though: key metrics, quality, individual skill levels and culture - Communicate and