Engineering Supervisor - Heartland

We need to output HTML fragment with sections: About the role? Actually the posting includes "Who We Are", "What You’ll Do", "Day-To-Day Responsibilities", "Must-Haves", "Nice-To-Haves", "Physical Requirements", "WHY YOU’LL LIKE WORKING HERE". Also maybe "Benefits" from WHY YOU’LL LIKE WORKING HERE includes medical benefits etc. We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We must include sections only when posting has real specific content. No filler. We need to extract content. Let's parse: - About the role: Could be "Who We Are" and maybe description of role? The posting includes "As the Engineering Supervisor, you will be responsible for mentoring and leading..." repeated. That's role description. So we can put that under About the role. - Responsibilities: Day-To-Day Responsibilities list. - Requirements: Must-Haves (requirements). Also maybe Nice-To-Haves as Qualifications or Skills? Could treat Must-Haves as Requirements, Nice-To-Haves as Qualifications or Skills. - Skills: maybe list of skills from Must-Haves/Nice-To-Haves. - Benefits: WHY YOU’LL LIKE WORKING HERE includes medical benefits, paid holidays and PTO, enjoyable culture, training and professional development. - Pay: Not mentioned. So we should NOT include Pay section. - Schedule: Not mentioned (only mention work hours may vary, travel). Not specific schedule. So we should not include Schedule. We must not include placeholder like "commensurate with experience". Not present. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the details as given, but we can format as lists. We must not include boilerplate like EEO etc. Remove that. We must not include navigation/cookie etc. We must not include application instructions. We must not repeat job title as heading. We need to output only HTML fragment. Let's craft:

About the role

As the Engineering Supervisor, you will be responsible for mentoring and leading the execution of the office’s local project engineering group. This position will support the Operations and Engineering Manager while serving as a change agent to help improve overall communication, project execution, and efficiency within Engineering.

Who We Are: AVI-SPL is a digital enablement solutions provider who transforms how people and technology connect to elevate experiences, create new value, and enable organizations to thrive and grow. We are the largest provider of collaboration technology solutions, which include our award-winning managed services. Our highly certified industry experts and innovation leaders share a vision to help people work smarter and live better. Our success starts with our people; and a workplace that champions culture and belonging ensures we grow and thrive together.

But we might combine. Better: About the role includes both role description and who we are? The instruction: use

for section headings (e.g. About the role, Responsibilities...). So we can have About the role with role description; Who We Are could be part of About the role or maybe separate? Not in list. Could treat as About the role includes company description. We'll put role description and company description in About the role. Responsibilities: list from Day-To-Day Responsibilities. Requirements: Must-Haves. Qualifications: Nice-To-Haves (education/experience preferences). Skills: maybe combine some skill items? But we can also put skills under Requirements? However we need to avoid thin sections. Could combine Requirements and Qualifications into one? But we have headings list; we can choose to include Requirements and Qualifications. We need to preserve all substantive info. Let's extract Must-Haves list: - Ability to mentor, educate, and develop members of the team. - Ability to understand the team and provide solutions for optimal performance. - Communicate and interact with internal employees, clients, and colleagues in a professional and timely manner. - Strong interpersonal skills, with the ability to work effectively with all levels of the organization. - Exceptional strategic thinking and structured problem-solving skills. - Excellent capability to switch tasks while adapting to changing priorities. - Energized self-starter capable of working and thinking independently and ensuring to meet deadlines. - Clear and professional communication skills (written and oral) both internally and externally. - Demonstrated customer service focus and client communication skills. - Ability to read and interpret electronic schematics and architectural blueprints. - Understanding of engineering aspects of audiovisual systems design and installation preferred. - Understand basic IP networking. - Advanced computer skills as required for the design, configuration, and operation of AV equipment. - Valid Driver’s License and a Motor Vehicle Record that meets AVI-SPL driving standards. - Minimum of a High School Diploma or equivalent. - Employees operating company or personal vehicles for business purposes must be legally authorized to drive, maintain a valid driver’s license and provide proof of coverage, meeting all minimum required insurance coverage as a condition of employment. - Employees driving fleet vehicles must meet eligibility requirements; comply with all guidelines, including telematics monitoring, vehicle maintenance schedules, proper use of assigned fuel and toll devices. That's a lot; we need to keep all. Nice-To-Haves: - B.S, degree in Electrical/Computer Engineering, Computer Science or related field is preferred - At least 10 years of AV experience is preferred - A minimum of 6 years of AV experience plus a four-year degree or military experience may be considered in place of job experience - Experience with Enterprise VC solutions (Zoom, Microsoft Teams, Google Meet, Bluejeans, Cisco TelePresence, etc.) - both hardware and software - AVIXA CTS-D and/or I (Certified Technical Specialist-Design/Installation) is preferred Physical Requirements: Combination of sitting, standing, and walking. Frequent verbal communication and presentations. Frequent use of computers and mobile devices. Travel may be required. Occasionally lift and/or move up to 20 pounds. Office and client-site environments. Reasonable accommodations may be made to enable qualified individuals with disabilities to perform the essential functions of this role. We could put Physical Requirements under a separate section? Not in allowed headings; maybe we can include under Responsibilities? But better to create a section "Requirements" includes physical? However the instruction says use those headings; we can add 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 not exclusive? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should map content to those headings. Physical Requirements could go under Requirements or Qualifications? Probably Requirements includes physical requirements. We'll include physical requirements under Requirements as part of list. Benefits: from WHY YOU’LL LIKE WORKING HERE: Medical benefits, including vision and dental; Paid holidays and PTO; Enjoyable and dynamic company culture; Training and professional development opportunities. We'll put those in Benefits as list. Pay: not present -> omit. Schedule: not present -> omit. Skills: maybe we can extract skill items from Must-Haves/Nice-To-Haves that are skills: ability to mentor, communicate, interpersonal, strategic thinking, task switching, self-starter, communication skills, customer service, reading schematics, understanding AV engineering, IP networking, advanced computer skills, driver's license, etc. But we already have many in Requirements. To avoid duplication, we could put Skills separate but risk duplication. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we split, we need to ensure we don't lose any info. Could include all in Requirements and Qualifications, and leave Skills empty? But we must not emit a heading followed by filler/placeholder text. So we cannot have a Skills section with no content. So we omit Skills if no specific skill content not already covered. However there are skill-specific items like "Ability to read and interpret electronic schematics and architectural blueprints" etc. Those could be considered skills. But we could still put them under Requirements. That's fine. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. Check if any content left out: Who We Are included in About the role. Day-To-Day Responsibilities included. Must-Haves included in Requirements. Nice-To-Haves included in Qualifications. Physical Requirements included in Requirements (maybe as sublist). Benefits included. Now we need to format lists with

• . For prose, use

  . We need to avoid repeating sentences. The role description appears twice in posting; we should include only once. Let's craft About the role:

  As the Engineering Supervisor, you will be responsible for mentoring and leading the execution of the office’s local project engineering group. This position will support the Operations and Engineering Manager while serving as a change agent to help improve overall communication, project execution, and efficiency within Engineering.

  Who We Are: AVI-SPL is a digital enablement solutions provider who transforms how people and technology connect to elevate experiences, create new value, and enable organizations to thrive and grow. We are the largest provider of collaboration technology solutions, which include our award-winning managed services. Our highly certified industry experts and innovation leaders share a vision to help people work smarter and live better. Our success starts with our people; and a workplace that champions culture and belonging ensures we grow and thrive together.

  That's fine. Responsibilities: list each bullet from Day-To-Day Responsibilities. Let's extract them exactly: - Support the local office Engineering Management as a subject matter expert and escalation resource in coordination with local Operations Management. - Provide leadership and guidance to local engineering team by coaching and motivating to successfully perform job requirements and to meet and exceed goals and objectives. - Share, teach, and reinforce the use of AVI-SPL standard practice across the team. - Communicate through weekly huddles with the team to ensure consistent, timely, and accurate completion of engineering tasks. - Lead the engineering team with a positive attitude that is in alignment with teamwork, mission, vision, and values of the organization. - Support leadership with establishing departmental goals, objectives, and operating procedure. - Perform frequent spot checks of team’s work to ensure accuracy and adherence to all company standards. - Conduct lessons learned meetings as necessary. - Validate pre-construction drawings and documentation, technical design, and pricing as needed. - Meet with vendors and prospective vendors to help evaluate products and be a customer liaison for engineering inquires and post sales project consultation. - Stay up to date with AV advances in the field and be able to identify areas of use in the organization. - Contribute to improving process workflows, maintaining system administration, scheduling, and resources for the department. - Perform additional tasks, responsibilities, and projects as needed to support the team and organization, ensuring flexibility in adapting to evolving priorities and objectives. We'll put each as
• . Requirements: combine Must-Haves and Physical Requirements. List Must-Haves items as above. Physical Requirements items: - Combination of sitting, standing, and walking. - Frequent verbal communication and presentations. - Frequent use of computers and mobile devices. - Travel may be required. - Occasionally lift and/or move up to 20 pounds. - Office and client-site environments. - Reasonable accommodations may be made to enable qualified individuals with disabilities to perform the essential functions of this role. We'll include them. Qualifications: Nice-To-Haves list. Benefits list: - Medical benefits, including vision and dental - Paid holidays and PTO - Enjoyable and dynamic company culture - Training and professional development opportunities Now ensure we don't include any boilerplate like EEO etc. We removed. Now output HTML fragment. Check for any repeated content: We have role description only once. Check for any missing: The posting also mentions "Employees operating company or personal vehicles for business purposes must be legally authorized to drive, maintain a valid driver’s license and provide proof of coverage, meeting all minimum