Lead Architect - Unified Communications & Collaboration (UC&C)

We need to output HTML fragment with sections: About the role? The posting includes a lot of intro about company, but we should not repeat job title. We need to include sections only when there is real specific content. The posting includes: Work location, Job Summary, Key Tasks & Responsibilities, Skills And Minimum Experience Required, Preferred Skills And Experience, Travel Requirements, Pay range, Benefits mention. Also maybe "About the role" not present; we can use "Job Summary" as heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to those headings. We have: - Job Summary: could be "About the role" or "Job Summary". Use "About the role" heading. - Key Tasks & Responsibilities: heading "Responsibilities". - Skills And Minimum Experience Required: heading "Requirements" or "Qualifications". Use "Requirements". - Preferred Skills And Experience: could be "Qualifications" or "Skills". Since we already used Requirements, we could use "Preferred Qualifications" but not in list. Maybe use "Skills" for both required and preferred? But we need separate sections only if content. Could combine? Better: "Requirements" for minimum, "Preferred Qualifications" not in list but we could use "Skills" for preferred? The instruction says use those example headings but not strict; we can use others? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should stick to those. So we can have:

About the role

(Job Summary)

Responsibilities

(Key Tasks & Responsibilities)

Requirements

(Skills And Minimum Experience Required)

Skills

(Preferred Skills And Experience) maybe.

Pay

(salary range)

Benefits

(benefits description)

Schedule

(Travel Requirements? Actually schedule maybe travel %). Could treat travel as schedule. We also have Work location: could be included in About the role paragraph. We must not include boilerplate like EEO, legal, etc. We must preserve all substantive information. So we need to include details: work location (anywhere in US, includes travel). Job Summary paragraph. Responsibilities list (bullet points). Requirements list (bullet points). Preferred skills list (bullet points). Pay range. Benefits list (health care, dental, vision, 401K, commissions/incentive compensation). Travel Requirements (1-20%). Also mention that QSC is owned by Acuity Inc., location etc? That's maybe not substantive for role; but it's part of company description. Might be considered boilerplate? It's generic company info; but it's part of the posting. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company overview might be considered boilerplate but it's substantive? It's describing the company; maybe we can keep a brief summary in About the role? However we should not repeat job title. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the company overview? It's not directly about the role but it's part of posting. Might be considered substantive. However the sections we output are limited to role-specific sections; we could include a brief paragraph under About the role that includes the company overview? The About the role section could contain the job summary plus maybe company description. But we must not invent. We'll include the job summary paragraph as given, and maybe also include work location. We need to ensure we don't include duplicated lines. We'll extract. Let's parse the posting: Company overview paragraphs (first big block) about QSC, Q-SYS, Atrius, Distech Controls, Acuity Intelligent Spaces, mission, etc. That's likely boilerplate but it's about the company. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It doesn't explicitly say to remove company overview. However typical job postings include that; but they said "Preserve ALL substantive information". The company overview is substantive about the employer. I'd keep it maybe as a short paragraph under About the role? But the heading "About the role" is for role, not company. Could add a separate section "About the company"? Not in allowed headings. Might be better to include it in About the role paragraph as context. But we must not include duplicated lines. The company overview appears only once. We'll include a paragraph under About the role that contains the company overview? Might be too long. However the instruction: "Prefer a few substantive sections over many thin ones." So we could have About the role containing both company overview and job summary. That's okay. Let's extract the job summary paragraph: "We are looking for a Lead Architect to serve as a key engineering leader for our Unified Communications & Collaboration hardware and software portfolio, spanning Audio, Video, and Control domains. This is a senior role for someone who has spent their career at the intersection of conferencing platforms (Microsoft Teams, Zoom) and the hardware/software products certified to run on them. You will define system architectures, contribute to hardware and software requirements, and act as the technical authority guiding our engineering and product teams through the fast-changing landscape of Unified Communications platforms. You'll be equally comfortable in a whiteboard architecture review, a certification lab, and a conversation with product management about tradeoffs and roadmap. Your technical expertise will be required to lead teams through UC certification efforts and help define broader solution-level test strategies. This role has no formal direct reports but is expected to influence, mentor, and guide engineers across the organization." Now responsibilities list: bullet points under "Key Tasks & Responsibilities (Essential Functions)". We'll extract each line: - Stay ahead of the ecosystem: Continuously track Microsoft Teams and Zoom platform, hardware, and certification specifications, translating changes into actionable impacts on our hardware and software roadmaps. - Define system architecture: Lead the specification and design of end-to-end system architectures across Audio, Video, and Control subsystems for products built for interoperability with UC platforms. - Determine requirements: Establish and document hardware and software requirements that satisfy Teams/Zoom certification programs, customer needs, and internal product goals. - Partner with product management: Provide technical input into product management decisions, helping shape feature tradeoffs, roadmap sequencing, and platform investment priorities. - Champion the customer voice with engineering: Develop a working understanding of the customer base and market landscape; partner with, and advocate for, product management by translating customer requirements and use-cases into terms the development team and engineering leadership can act on. - Certification clarity and leadership: Provide clear guidance to engineering and QA on certification test requirements; when needed, formally own and lead Teams and Zoom certification submissions and lab engagements from planning through sign-off. - Consult on product development: Act as a trusted technical consultant to design and engineering teams across the product portfolio, reviewing architecture and design decisions for compliance, performance, and manufacturability. - Cross-domain ownership: Provide architectural guidance across Audio and Video subsystems as primary areas of depth, with working knowledge of Control system integration (serial, IP-based, and third-party control ecosystems). - Platform integration: Guide integration efforts for Windows-based platforms (Windows IoT / Windows for Teams Rooms) and Android-based platforms under Microsoft's Device Ecosystem Platform (MDEP), ensuring compliance with OEM certification requirements. - Solution-level testing: Periodically help define broader solution and system-level test plans that go beyond individual certification requirements. Now Requirements (Skills And Minimum Experience Required) list: - 10+ years of relevant industry experience in audio/video/collaboration hardware and software development. - Direct prior experience at a company that designed, built, and certified Teams and/or Zoom conferencing devices (e.g., cameras, speakerphones, room systems, docking/USB peripherals, or similar collaboration endpoints). - Deep, current knowledge of Microsoft Teams and Zoom device certification programs, hardware specifications, and platform requirements. - Strong architectural background across Audio and Video signal chains, including: Video: USB Video Class (UVC), HDMI/HDCP, camera ISP pipelines, video codecs Audio: USB Audio Class (UAC), DSP and acoustic echo cancellation (AEC)/noise suppression, Bluetooth audio Networking/streaming: SIP, RTP/RTCP, PoE Working knowledge of Control system integration (RS-232/IP control, third-party control system ecosystems). - Hands-on familiarity with Windows platform integration (Windows IoT / Windows for Teams Rooms) and Android platform integration under Microsoft's Device Ecosystem Platform (MDEP). - Demonstrated experience defining hardware and software requirements from certification specifications. - Proven ability to operate as a technical consultant/advisor across engineering, QA, and product management functions. - Excellent written and verbal communication skills, with experience presenting architecture and technical tradeoffs to both engineering and business stakeholders. - BS in Electrical Engineering, Computer Engineering, Computer Science, or related field, or equivalent practical experience. Now Preferred Skills And Experience list: - Direct experience leading or participating in formal Teams and/or Zoom certification lab engagements. - Familiarity with embedded Linux platforms in collaboration endpoints. - Experience with broader UC solution testing beyond individual device certification (multi-device, room-scale, or interoperability testing). - Experience mentoring engineers or acting as a technical lead without formal management authority. - Familiarity with USB-IF, HDMI Forum, and Bluetooth SIG specifications relevant to AV peripherals. Travel Requirements: "Travel Requirements 1-20% QSC." Actually line: "Travel Requirements 1-20% QSC." Probably means travel 1-20%. Pay: "The range for this position is $150,000 to $270,000. Placement within this range may vary, depending on the applicant’s experience and geographic location." Benefits: "Acuity offers generous benefits including health care, dental coverage, vision plans, 401K benefits, and commissions/incentive compensation depending on role. For a list of our benefits, click here ." We should include benefits as list. Now we need to output HTML fragment only, no markdown. We'll structure:

About the role

Company overview paragraph? We'll include a brief summary: maybe combine company overview and job summary. But we must not invent. We'll include the company overview as a paragraph before job summary? Could be two paragraphs. Let's include company overview as a paragraph, then job summary as another paragraph. Company overview: The first big block up to "Visit us at www.acuityinc.com . #QSYS". We'll extract that as a paragraph (maybe multiple sentences). We'll keep it as is. Then job summary paragraph. Then responsibilities

• ... etc. Then requirements
  • ... Then skills
    • ... (preferred) Then pay

      The range for this position is $150,000 to $270,000. Placement within this range may vary, depending on the applicant’s experience and geographic location.

      Then benefits
      • health care
      • dental coverage
      • vision plans
      • 401K benefits
      • commissions/incentive compensation depending on role
      Then schedule

      Travel required: 1-20%.

      (or Travel Requirements) We must not include duplicated lines like "QSC. is owned by Acuity Inc., which is located in the United States." That's in the later part after Travel Requirements. That's maybe redundant with company overview; we can omit as duplicated? It's a sentence: "QSC. is owned by Acuity Inc., which is located in the United States." That's not in company overview earlier? The overview mentioned Atrius, Distech Controls and QSC are part of the Acuity Int