Co-op City Tire & Auto - Automotive General Manager

We need to output HTML fragment with sections: About the role? Actually the posting includes "WHO WE ARE", "Our Mission", "Our Core Values", "JOB DESCRIPTION", "WHAT MAKES THIS ROLE UNIQUE", "RESPONSIBILITIES", "REQUIREMENTS", "WHAT SUCCESS LOOKS LIKE", "BENEFITS". Also there is "HOW TO APPLY" and disclaimer which we should remove (application instructions). Also we should not repeat job title as heading. Use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. Remove boilerplate, navigation, EEO, etc. Also remove "Link to apply listed at the bottom..." and "HOW TO APPLY" and disclaimer. We need to preserve all substantive information. So we need to include sections: About the company (WHO WE ARE, mission, core values). Could be combined under "About the role"? Actually we can have sections: About the Company (or About the role). The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings based on content. We have "WHO WE ARE" (company description). Could map to "About the role" or "About the company". Probably "About the role" is fine. Then "WHAT MAKES THIS ROLE UNIQUE" could be part of About the role or separate. Could be "Role Overview". But we should follow given examples; we can create headings like "About the role", "Responsibilities", "Requirements", "Benefits". Also we have "WHAT SUCCESS LOOKS LIKE" maybe could be under "Expectations" but not in list; we could include as a separate section like "Success Milestones". However instruction: Prefer a few substantive sections over many thin ones. So we could combine "WHAT SUCCESS LOOKS LIKE" into "Requirements" or "Responsibilities"? It's more about outcomes; maybe we can include as a separate section "Success Milestones". But that adds a thin section. Could incorporate into "Responsibilities" as bullet points? Might be okay to keep as separate if substantive. It's fairly detailed with timelines. Could be its own section "Success Milestones". That's okay. We also have "Compensation" under BENEFITS. So we need Benefits section with compensation details, PTO, holidays, professional development. We also have Pay? Not separate; compensation is in Benefits. We need to ensure we don't include placeholder text like "commensurate with experience". Not present. We need to remove duplicated lines. Ensure we don't include application instructions. Let's extract content. WHO WE ARE: "Co-op City Tire & Auto is a Bronx landmark. We operate an 8,800 square foot facility with 11 service bays on a corridor that carries roughly 35,000 vehicles past our door every day. We have built a reputation over decades as the shop this neighborhood trusts with its cars, and we now have the infrastructure, the location, and the demand to become something considerably larger than a neighborhood tire shop.Our mission: To provide superior customer service every driver in the Bronx, giving each customer dealership-quality service without the dealership runaround." Then repeated mission line: "Our Mission: To provide superior customer service to every driver in the Bronx, giving each customer dealership-quality service without the dealership runaround." Then core values list. We should combine and avoid duplication. Our Core Values: Honesty: Tell the story as it needs to be told. Straight answers. We tell customers what their car actually needs, and what it does not. Respect and Integrity: Doing the right thing and what's best for our customers, and treating their vehicle like it's our own. Transparency: Communicating openly and honestly with our customers. If our culture and mission does not resonate with you, please do not bother applying. We can keep that as prose. JOB DESCRIPTION paragraph: "The Co-op City Tire & Auto team is looking for a results-driven and systems-minded Automotive General Manager with a proven track record in automotive service, fleet, or multi-bay shop operations. The application code word is EMPOWER. The Automotive General Manager owns the day-to-day execution of the business and builds the infrastructure that lets a busy shop run like a well-managed dealership rather than a series of reactions to whoever walks through the door.The Automotive General Manager is a highly skilled strategic thinker who anticipates and solves problems in a self-directed way. They empower and build a team around them to move fast while holding quality and culture steady.This role leads Co-op City Tire & Auto through a chapter of significant growth. You will work in close partnership with the owner to take a business that has already earned its demand and give it the systems, the reporting, and the accountability structure to capture that demand at scale.This is a full-time, on-site W2 position. Because this is a critical role within the business, candidates go through a rigorous four-part application process." We should remove "The application code word is EMPOWER."? It's substantive? Might be considered metadata but maybe keep? It's not a heading. It's a detail; we can keep in prose. WHAT MAKES THIS ROLE UNIQUE: paragraphs. RESPONSIBILITIES: bullet list under headings: Systems & Financial Infrastructure, Service Execution & Revenue Growth, Team Leadership & Accountability, Owner Partnership. Each has sub-bullets. We need to output

  • for any list of duties/requirements/benefits. So we can have a
    with
    • each responsibility group? Or we could nest? Probably simplest: each responsibility as
    • containing the description (maybe with internal
      ?). But instruction: Use
      • for any list of duties/requirements/benefits. So we can make a top-level
        where each
        • is a responsibility area, and inside we can have further detail as prose or nested lists? Not specified. We'll keep simple: each responsibility as
        • with the description (including sub-bullets maybe as separate sentences). Could also break sub-bullets into separate
        • but then we lose grouping. I'd keep each responsibility as
        • with the description (including sub-bullets as separate sentences). That satisfies. REQUIREMENTS: includes Experience Requirements (Non-Negotiable) bullet list, Core Competencies bullet list, Critical Soft Skills bullet list, Technical Requirements bullet list, Mindset & Cultural Fit prose. We need to output as list. We should not repeat "Experience Requirements (Non-Negotiable)" as heading inside list? Could keep as prose before list. We'll output a
          with each requirement area as
          • maybe with internal detail. WHAT SUCCESS LOOKS LIKE: timeline bullet points. Could be a
            with each timeframe as
            • . BENEFITS: compensation, role type, PTO, holidays, professional development. We'll output as
              . We must not include Pay or Schedule sections unless present. Not present. Now produce HTML fragment. Let's craft. Start with

              About the role

              then

              containing WHO WE ARE, mission, core values combined. Then

              What makes this role unique

              ... Then

              Responsibilities

              with
              • each. Then

                Requirements

                with
                • each. Then

                  Success milestones

                  with
                  • each. Then

                    Benefits

                    with
                    • each. Make sure to preserve all details. Let's extract details precisely. WHO WE ARE combined: "Co-op City Tire & Auto is a Bronx landmark. We operate an 8,800 square foot facility with 11 service bays on a corridor that carries roughly 35,000 vehicles past our door every day. We have built a reputation over decades as the shop this neighborhood trusts with its cars, and we now have the infrastructure, the location, and the demand to become something considerably larger than a neighborhood tire shop. Our mission: To provide superior customer service to every driver in the Bronx, giving each customer dealership-quality service without the dealership runaround. Our Core Values: Honesty: Tell the story as it needs to be told. Straight answers. We tell customers what their car actually needs, and what it does not. Respect and Integrity: Doing the right thing and what's best for our customers, and treating their vehicle like it's our own. Transparency: Communicating openly and honestly with our customers. If our culture and mission does not resonate with you, please do not bother applying." We can keep as paragraph. JOB DESCRIPTION paragraph (maybe incorporate into About the role? But we have separate "What makes this role unique". We'll keep JOB DESCRIPTION as part of About the role? Actually the instruction: use headings for sections like About the role, Responsibilities, etc. The JOB DESCRIPTION is generic description; we could include it under About the role as well. But we already have About the role with WHO WE ARE. Might be better to have About the role include both WHO WE ARE and JOB DESCRIPTION. However we also have "WHAT MAKES THIS ROLE UNIQUE" separate. Let's put About the role: includes WHO ARE, mission, values, and the job description paragraph (the looking for...). That seems reasonable. Thus About the role

                      will contain all that. Then What makes this role unique

                      . Now Responsibilities: need to capture bullet points. Let's list each responsibility area with its subpoints. Systems & Financial Infrastructure: - Integrate shop management and accounting systems, eliminating duplicate entry - Manage the external accounting partner, ensuring reconciliation and accurate financials - Build dashboards for revenue, margin, and bay productivity - Implement inventory and parts-return controls to prevent losses Service Execution & Revenue Growth: - Drive digital vehicle inspection adoption across all 11 bays - Build standardized preventative maintenance packages - Create workflows that increase average repair order without pressuring customers - Improve equipment and processes to increase profitable bay output Team Leadership & Accountability: - Define front office and service floor roles, ownership, and standards - Recruit, train, and retain a stable service team - Manage performance through visible scorecards and clear expectations - Lead direct performance conversations while building trust with long-tenured staff Owner Partnership: - Translate owner growth goals into clear initiatives and milestones - Permanently remove administrative and low-value work from the owner - Provide concise reporting that enables data-driven leadership - Push back when requests conflict with strategic priorities We'll put each as

                    • with the subpoints maybe as separate sentences or using
                      inside? To keep simple, we can separate with semicolons or line breaks using
                      . But HTML fragment can include
                      . Probably okay. We'll do:
                      • Systems & Financial Infrastructure: Integrate shop management and accounting systems, eliminating duplicate entry; manage the external accounting partner, ensuring reconciliation and accurate financials; build dashboards for revenue, margin, and bay productivity; implement inventory and parts-return controls to prevent losses.
                      etc. Now Requirements. Experience Requirements (Non-Negotiable): - Operations experience in automotive service, dealership fixed operations, fleet maintenance, or similar multi-bay environments - Experience integrating shop management and accounting systems; Protractor and QuickBooks strongly preferred - Financial workflow experience across AP, reconciliation, inventory, and vendors - Proven success leading service teams through measurable process change - Experience implementing digital inspections or similar service-recommendation processes Core Competencies: - Systems integration ability. You can map how information should move between platforms and get the integration finished - Financial stewardship. You read a profit and loss statement, find what does not belong, and fix it at the source