Design Engineer

We need to output HTML fragment with sections only if real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. Must preserve all substantive info. Remove boilerplate like EEO, etc. Also remove duplicated lines. Must not create sections with placeholder text. We need to parse the posting. Content: - Intro: "The Design Engineer transforms customer needs into actionable solutions through system design and detailed documentation. You will work closely with sales team members, including Account Managers, to understand client requirements, identify potential risks and communicate with stakeholders." - "Who We Are" paragraph about AVI-SPL. - "What You’ll Do" repeats intro and then details: presenting solutions, explaining designs, creating design packages, problem solving, ownership, etc. - Then "Day-To-Day Responsibilities" with bullet-like sentences. - Then "Must-Haves" with list of requirements. - Then "Nice-To-Haves". - Then "Physical Requirements". - Then "WHY YOU’LL LIKE WORKING HERE" with benefits: Medical benefits, including vision and dental; Paid holidays and PTO; Enjoyable and dynamic company culture; Training and professional development opportunities. - Then "More About Us" EEO etc which we should remove. We need to produce sections: About the role (maybe combine Who We Are and What You’ll Do?), Responsibilities (Day-To-Day Responsibilities), Requirements (Must-Haves?), Qualifications (maybe Nice-To-Haves?), Skills (maybe core competencies?), Benefits (WHY YOU’LL LIKE WORKING HERE). Pay and Schedule not present, so omit. We must not create sections with filler. So only include sections where we have substantive content. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve all substantive information, not invent or summarize away detail. So we need to keep details like bullet points. We need to avoid repeating duplicated lines (the intro appears twice). We should include it once. We need to format responsibilities as list items. Let's extract substantive content: About the role / Who We Are: Could be combined as "About the role" maybe includes description of role and company. The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role heading, containing prose about role and company. Responsibilities: list of duties from Day-To-Day Responsibilities and maybe also from What You’ll Do (presenting solutions, etc). We'll combine. Requirements: Must-Haves (minimum high school diploma, core competencies, technical expertise, certifications, driver's license). Could be split into Requirements and Qualifications? But we have both headings available. We could put Must-Haves under Requirements, and Nice-To-Haves under Qualifications. Or we could put all under Requirements. But we have both headings; we can use both if we have content. The instruction: Prefer a few substantive sections over many thin ones. But we can still use both if they have substantive content. Let's split: Requirements = Must-Haves (mandatory). Qualifications = Nice-To-Haves (preferred). Skills: maybe core competencies and technical expertise? But those are already in Must-Haves. Could combine Skills section for core competencies and technical expertise? However Must-Haves already includes core competencies and technical expertise. Might be redundant. Better to follow typical structure: About the role, Responsibilities, Requirements (including Must-Haves), Qualifications (Nice-To-Haves), Benefits. Skills maybe not needed if covered. But we have to use headings only if we have real content. We could omit Skills if we don't have distinct content beyond what's in Requirements. But we have core competencies and skills listed; they could go under Skills. However Must-Haves includes them. To avoid duplication, we could put core competencies and skills under Skills, and technical expertise under Requirements? But that splits. Simplify: Use About the role, Responsibilities, Requirements (covering Must-Haves), Qualifications (Nice-To-Haves), Benefits. Omit Skills. Check if any content for Pay or Schedule: none, so omit. Now we need to format lists. Let's extract Must-Haves items: - Minimum of a high school diploma or equivalent. - Core Competencies and Skills: - Strong problem-solving skills and the ability to identify and address risks effectively. - Customer-focused mindset with a commitment to delivering solutions that exceed expectations - Effective Stakeholder Communication: Experience conveying technical concepts to both technical and non-technical audiences, including clients, project managers, and field teams. - Detail-Oriented: knows the difference between “good enough” and “perfect” and strives for accuracy in work. - Experience working in cross-functional teams, including sales, project managers, and vendors. - Ability to meet deadlines and manage priorities independently in a fast-paced environment. - Self-directed learning habits to stay current with emerging AV technologies, industry standards, and best practices through ongoing education or certifications. - Technical Expertise and Knowledge: - Proficiency in design and configuration of AV systems, including software tools and standards. - A working understanding of IP networking, including topologies, AVoIP, and network design architecture. - Familiarity with AV/IT industry standards such as AVIXA, ANSI/TIA, or other relevant guidelines. - Familiarity with tools such as CAD (e.g., AutoCAD, Bluebeam Revu) - Familiarity with common infrastructure requirements, including power, data, and conduit, and how they integrate into AV systems. - Two (2) or more relevant audio/DSP certifications (Biamp, Q-SYS, BSS, Extron, Shure, etc.) - Valid driver’s license and a motor vehicle record meeting company standards. 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. We need to preserve all that. Could be a list. Nice-To-Haves: - Three (3) years of experience in audiovisual system design or integration. - Formal education in Electronics, Engineering, or a related field preferred. - AVIXIA General CTS (Certified Technical Specialist) is preferred. - Experience with Enterprise VC solutions (Zoom, Microsoft Teams, Google Meet, Cisco Webex/Telepresence)-both hardware and software. - Field Knowledge: Prior exposure to on-site project work, including installation oversight or field troubleshooting to bridge design and implementation. 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 include Physical Requirements under Requirements or as separate section? Not in headings list. Could be part of Requirements. But we have no heading for Physical Requirements. Could incorporate into Requirements as a list item. Benefits: Medical benefits, including vision and dental; Paid holidays and PTO; Enjoyable and dynamic company culture; Training and professional development opportunities. Now About the role: combine intro and Who We Are. Intro: "The Design Engineer transforms customer needs into actionable solutions through system design and detailed documentation. You will work closely with sales team members, including Account Managers, to understand client requirements, identify potential risks and communicate with stakeholders." 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." We can combine into a paragraph. Responsibilities: from What You’ll Do and Day-To-Day Responsibilities. What You’ll Do: after intro repeats, then: "This role involves presenting solutions and explaining complex technical designs in a simple way that helps customers clearly see how the solutions meet their needs. By creating accurate, comprehensive design packages, you ensure the project team has the details needed for successful execution. Strong problem-solving skills that balance addressing customer desires and satisfaction with internal business needs are essential. The Design Engineer takes ownership and responsibility for accuracy and feasibility of designs ensuring successful project execution through collaboration and support." Day-To-Day Responsibilities bullet points: - Pre-Sales Design and Proposal Efforts - Collaborate with Account Managers to understand customer requirements and translate them into functional system designs. - Participate in client discussions to explain design concepts and demonstrate how proposed systems meet their needs. - Provide labor estimates and material requirements to support the sales proposal creation. - Develop and maintain comprehensive design standards packages tailored for large and repeat customer accounts. - Design Responsibilities - Develop detailed system documentation, including a bill of materials, conceptual block diagrams, infrastructure plans, and scopes of work. - Determine infrastructure requirements, such as power, data, and conduit, during pre-sales efforts and coordinate with general contractors. - Assess project risks and account for site conditions, scheduling requirements, and dependencies in the design. - Review pre-construction documentation to ensure clarity and alignment with project objectives. - Coordinate with vendors, architects, consultants and contractors to align designs with project constraints during design development. - Project Responsibilities - Support project teams during implementation and provide technical input as the “design authority” as needed. - Perform additional tasks, responsibilities, and projects as needed to support the team and organization, ensuring flexibility in adapting to evolving priorities and objectives. We need to preserve all. We'll make a flat list of responsibilities (maybe grouped). Use

  • for each duty. Now we need to avoid duplication: The intro appears twice; we will include once. Now produce HTML. Structure:

    About the role

    ... combined intro and who we are ...

    Responsibilities

    • ... each duty ...

    Requirements

    • Minimum of a high school diploma or equivalent.
    • Core Competencies and Skills: ... maybe we need to keep as sub-items? Could embed as separate
      inside? But instruction: Use
      • for any list of duties/requirements/benefits. It doesn't forbid nested lists. We can keep flat but preserve the bullet points. Could treat each bullet as separate
      • . For core competencies list, we could have each as separate
      • . Similarly technical expertise. Thus Requirements list will include many items: high school diploma, each core competency, each technical expertise item, driver's license etc. We need to keep the phrasing exactly as in posting? Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the exact wording. Let's extract each bullet exactly. Core Competencies and Skills bullets: - Strong problem-solving skills and the ability to identify and address risks effectively. - Customer-focused mindset with a commitment to delivering solutions that exceed expectations - Effective Stakeholder Communication: Experience conveying technical concepts to both technical and non-technical audiences, including clients, project managers, and field teams. - Detail-Oriented: knows the difference between “good enough” and “perfect” and strives for accuracy in work. - Experience working in cross-functional teams, including sales, project managers, and vendors. - Ability to meet deadlines and manage priorities independently in a fast-paced environment. - Self-directed learning habits to stay current with emerging AV technologies, industry standards, and best practices through ongoing education or certifications.