UC&C Support Engineer
About the role
with paragraph(s). Then "Key Tasks & Responsibilities (Essential Functions)" list: we can put underResponsibilities
with- items.
Then "Skills And Minimum Experience Required" includes many bullet-like sentences. Could be under
Requirements
orQualifications
orSkills
. We need to decide. The posting includes "Skills And Minimum Experience Required". That could be split: Requirements (education, experience) and Skills (technical). But we can combine into one section maybe "Requirements". However we have separate headings allowed: Requirements, Qualifications, Skills. We should avoid thin sections. Perhaps we can put education/experience under Requirements, and technical skills under Skills. But we need to see if there is enough content. Let's extract: Education: Bachelors or advanced degree in computer science, electrical engineering or similar discipline. CTS, CTS-D or similar Avixa technical certification desired. Experience: Minimum 5 years experience in-depth troubleshooting of USB, HID PTZ Cameras and UC&C systems protocols, USB, AV automation, and AV related AI. Minimum 3 years experience in-depth troubleshooting of Q-SYS or similar Linux-based AV systems. Minimum 2 years experience with Atlassian collaborative tools, such as Confluence and Jira. Other: The UC&C Support Engineer will operate with a high degree of independence, keeping in mind that collaboration with other parts of the organization will be the key to success. Excellent verbal and written communications skills. Proven experience in supporting UC&C systems including Microsoft Teams, Zoom and other collaboration tools. Strong troubleshooting and problem-solving skilles (typo). Ability to work independently and as part of a team. Excellent software and hardware troubleshooting skills. Strong understanding of and experience in audiovisual systems design, technical support and troubleshooting QSC. We could split: Requirements (education + years experience) and Skills (communication, troubleshooting, teamwork, etc). But we also have "Skills And Minimum Experience Required" heading originally. Might be okay to have a single section "Requirements" covering both. Pay: The range for this position is $66,500.00 to $143,600.00. 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 . Schedule: Not mentioned. Work location: This position may be based anywhere in the United States and includes travel as part of the responsibilities. That's location, not schedule. No schedule info. Thus we have sections: About the role (Job Summary), Responsibilities (Key Tasks & Responsibilities), Requirements (education/experience), Skills (maybe we can combine with Requirements but we need to decide). Could also have a "Qualifications" section for education/certifications. But we have limited distinct content. We could do: - About the role (Job Summary) - Responsibilities (Key Tasks & Responsibilities) - Requirements (Education & Experience) - Skills (Technical & Soft skills) - Benefits - Pay We need to avoid thin sections: each should have substantive content. Let's extract responsibilities list: From "Key Tasks & Responsibilities (Essential Functions)" we have sentences: - Advanced support of Q-SYS clients and systems, provide efficient and effective response and resolution to a variety of incidents and service requests, identify and solve critical problems and prevent them from reoccurring via root cause analysis and automation, diagnosing and differentiating hardware issues from software issues - Report ongoing software bugs from the field and test environments via collaborative software reporting tools (Jira), communicate the technical support team and customer requirements effectively with software developers and hardware quality to help prioritize changes that add value to our business - Provide project status updates for management, internal stakeholders (e.g. sales), and customers, communicate progress on issues and makes modifications as needed. Ensure that all issues/tickets are addressed properly and all records are maintained in Q-SYS’s CRM system (SalesForce), bug reports (Jira), and knowledge base (Helpjuice) - Provide on-site support to clients and end-users, focusing on troubleshooting and diagnosing technical issues. Ensure client systems are updated and optimized to meet the operational requirements outlined in the scope of work We can break each sentence into - .
Now Skills: we have list of skills: Excellent verbal and written communications skills, Proven experience in supporting UC&C systems including Microsoft Teams, Zoom and other collaboration tools, Strong troubleshooting and problem-solving skills, Ability to work independently and as part of a team, Excellent software and hardware troubleshooting skills, Strong understanding of and experience in audiovisual systems design, technical support and troubleshooting.
Also maybe "CTS, CTS-D or similar Avixa technical certification desired." could be under Requirements or Skills. We'll put certification under Requirements.
Now Benefits: list: health care, dental coverage, vision plans, 401K benefits, commissions/incentive compensation depending on role.
Pay: range $66,500.00 to $143,600.00.
Now About the role: we have Job Summary paragraph: "UC&C Support Engineer - The UC&C Subject Matter Expert serves as the primary technical authority for Unified Communications & Collaboration solutions, with a specialized focus on RoomSuite Simplified Collaboration Spaces and related collaboration technologies. This role provides advanced product support, troubleshooting expertise, operational readiness, and technical leadership across a broad portfolio that includes Teams integration, USB and HID peripherals, PTZ cameras, microphones, touch panels, RoomSuite Collaboration Spaces, Windows-based management systems, cloud services, and data communication technologies. The UC&C Suppoty Engineer will act as the technical bridge between Engineering, Product Management, Support teams, strategic partners, and customers. The UC&C Support Engineer is responsible for diagnosing and resolving complex customer issues, defining and reproducing software defects, validating customer reported problems and testing software fixes in partnership with development teams. Key responsibilities include assisting in delivering technical training, establishing troubleshooting methodologies and support best practices, validating release readiness, and identifying opportunities to improve product supportability. The UC&C Support Engineer collaborates closely with engineering teams to enhance diagnostic capabilities, improve system visibility, and develop tools that streamline troubleshooting and issue resolution. The role also drives operational excellence for RoomSuite Simplified Collaboration Spaces, helping define support policies, customer recovery procedures, firmware and software management practices, and deployment standards. The ideal candidate combines deep technical expertise in UC&C technologies with strong communication, collaboration, and problem-solving skills. By enabling teams through training, documentation, escalation leadership, and continuous improvement initiatives, the SME ensures that UC&C and RoomSuite Collaboration Spaces solutions are scalable, supportable, and deliver an exceptional customer experience while fostering a culture of teamwork, accountability, and innovation."
We need to fix typo "Suppoty". We'll keep as is? Probably keep original text but we could correct? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should not correct typos? It's part of the posting. We should keep as is. However "Suppoty" is likely a typo but it's part of the text. We'll keep it.
Now produce HTML.
We must not include or . Just fragment.
We'll produce:
About the role
...
Responsibilities
- ... ...
Requirements
- Bachelors or advanced degree in computer science, electrical engineering or similar discipline.
- CTS, CTS-D or similar Avixa technical certification desired.
- Minimum 5 years experience in-depth troubleshooting of USB, HID PTZ Cameras and UC&C systems protocols, USB, AV automation, and AV related AI.
- Minimum 3 years experience in-depth troubleshooting of Q-SYS or similar Linux-based AV systems.
- Minimum 2 years experience with Atlassian collaborative tools, such as Confluence and Jira.
Skills
- Excellent verbal and written communications skills.
- Proven experience in supporting UC&C systems including Microsoft Teams, Zoom and other collaboration tools.
- Strong troubleshooting and problem-solving skills.
- Ability to work independently and as part of a team.
- Excellent software and hardware troubleshooting skills.
- Strong understanding of and experience in audiovisual systems design, technical support and troubleshooting.
Benefits
- Health care
- Dental coverage
- Vision plans
- 401K benefits
- Commissions/incentive compensation depending on role
Pay
The range for this position is $66,500.00 to $143,600.00. Placement within this range may vary, depending on the applicant’s experience and geographic location.
We should not include Schedule section. Check for any duplicated lines: we have not included boilerplate. Make sure we didn't include any navigation/legal/EEO etc. We omitted the work location sentence; maybe we could include it under About the role? It's not a heading but could be part of About the role paragraph? The instruction: do not repeat job title as heading, but we can include location info in a paragraph. However we have not included location anywhere. Should we preserve all substantive information? The work location is substantive: "This position may be based anywhere in the United States and includes travel as part of the responsibilities." We should include that somewhere. Could add a paragraph under About the role after the summary, or a separate section like "Work Location" but we don't have a heading for that; we could add aunder About the role. Thus modify About the role paragraph to include that sentence at end. Let's craft About the role paragraph: combine the Job Summary and location. We'll produce one
containing the summary plus location sentence. Now check for any other substantive info: "QSC is creating exceptional, people-centric experiences..." that's company description; maybe not needed for role but could be part of About the role? The instruction: preserve ALL substantive information; do not invent or summarize away detail. The company description is substantive but maybe not required for the role? However it's part of the posting. Should we include? The instruction says preserve ALL substantive information; but also we should not create sections with filler. We could include a brief paragraph under About the role that includes company overview. However the job posting already includes that at top; it's not directly about the role but it's part of the posting. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should include that company description somewhere. Could add a
under About the role before the summary. Thus About the role section could have multiple paragraphs: first company overview, then job summary, then location. Let's extract company overview paragraph: "QSC is creating exceptional, people-centric experiences with the perfect balance of technology and creativity. Q-SYS, our innovative full stack audio, video and control platform, unifies data, devices and a cloud-first architecture, empowering organizations to deliver transformative AV