AV Sales Engineer

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID etc. Remove boilerplate. We need to parse the posting. Sections present: - About DataVox (maybe "About the role"? Actually "About DataVox" is about company. Could map to "About the role"? The instruction says 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. Likely we should create sections: About the role (maybe description of role), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only those with real content. Let's extract: Role description: "Join DataVox and Help Design the Future of Workplace Technology DataVox is seeking an experienced AV Sales Engineer to partner with our Account Managers in designing and presenting innovative Audio Visual and Unified Communications solutions for corporate clients throughout Texas. This is a highly visible, customer-facing role where you'll combine technical expertise with consultative sales support to help clients transform their collaboration, communication, and presentation environments. If you enjoy working with cutting-edge AV technology, collaborating with customers, and designing solutions that solve real business challenges, we'd love to hear from you." That's about the role. About DataVox: maybe could be part of About the role? But we can include as part of About the role or maybe separate? The instruction only lists those headings; we could put company info under About the role. Responsibilities: list under "What You'll Do" and "Key Responsibilities". We'll extract bullet points. Requirements: maybe "What We're Looking For" includes Required Qualifications. That's qualifications. Also maybe "Required Qualifications" is qualifications. Also "Preferred Qualifications" could be skills? Actually they are qualifications. We'll separate Required Qualifications as Requirements? Or Qualifications? The headings include Requirements and Qualifications separate. Usually Requirements = mandatory, Qualifications = preferred? But we can decide: Requirements = Required Qualifications; Qualifications = Preferred Qualifications? Or Skills = specific skills? Let's map: - Requirements: Required Qualifications (mandatory) - Qualifications: Preferred Qualifications (maybe also certifications) - Skills: maybe list of specific skills like proficiency with Microsoft Office, etc. But those are also in Required Qualifications. Could combine. Better to follow typical job posting: Responsibilities, Requirements (education/experience), Qualifications (preferred), Skills (technical skills), Benefits, Pay, Schedule. We have data: Responsibilities: list of duties. Requirements (mandatory): Bachelor's degree or equivalent professional experience; 2+ years of AV system design or AV engineering experience; Experience supporting consultative technology sales environments; Strong customer-facing communication and presentation skills; Experience creating budgets, BOMs, estimates, and technical proposals; Experience responding to RFPs and competitive bid requests; Understanding of the AV project lifecycle from discovery through deployment; Ability to interpret architectural, construction, and engineering drawings; Experience estimating labor and project costs; Strong organizational skills and attention to detail; Self-motivated team player with excellent written and verbal communication abilities; Proficiency with Microsoft Office Suite, including Excel and Outlook. Qualifications (preferred): AVIXA CTS certification; CTS-D and/or CTS-I certifications; Experience with D-Tools; Experience with Digital Signage solutions; Manufacturer certifications from: Crestron, Extron, Q-SYS, AMX, Biamp, Shure, Audinate; Experience with: Microsoft Teams Rooms, Zoom Rooms, Cisco Collaboration Solutions, Enterprise AV and UC technologies; Knowledge of AV control systems and automation platforms. Skills: maybe we could list technical skills like AV system design, etc. But many are already in qualifications. Could create a Skills section for things like "Proficiency with Microsoft Office Suite" etc. But that is already in Requirements. Might be redundant. Perhaps we can omit Skills if content overlaps; but we need to include only sections with real specific content not duplicated. Could still include Skills for things like "Proficiency with Microsoft Office Suite, including Excel and Outlook" and "Strong customer-facing communication and presentation skills" etc. However those are also in Requirements. Might be okay to have both but risk duplication. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication, but better to avoid redundancy. We could put all mandatory under Requirements, and preferred under Qualifications, and maybe Skills not needed. But we need to include a section only when posting has real specific content for it. If we omit Skills, that's fine. Benefits: list under "What We Offer". Include bullet points. Pay: Not mentioned explicitly (no salary). So we should NOT include Pay section. Schedule: Not mentioned explicitly (maybe travel requirements). Travel requirements could be considered Schedule? But schedule usually refers to work hours, shift, etc. Not present. Travel requirements could be under a separate heading but not in allowed list. Could we put travel under Schedule? The instruction says include Schedule section only if posting actually states them. The posting does mention travel requirements: "Primarily local travel within a two-hour radius of Houston... Approximately 90% of travel is local by vehicle... Occasional overnight travel and air travel may be required... Valid Texas driver's license required... Personal vehicle required (mileage reimbursed at current IRS rates)". That's not exactly schedule but could be considered travel schedule. However the allowed headings include Schedule. Should we create a Schedule section with travel details? The instruction: "Prefer a few substantive sections over many thin ones." If we include Schedule, we need to put travel details there. It's substantive. I'd include Schedule. But we also have Physical Requirements section (not in allowed headings). Could we fold into Schedule? Probably not. Physical Requirements is not allowed heading; we could drop it or incorporate into something else? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." Physical Requirements is not minor metadata; it's a substantive section but not in allowed headings. Should we drop it? The instruction says to use headings only from the list; we can omit sections not in list. So we can drop Physical Requirements (or maybe incorporate into Responsibilities? Not appropriate). Better to drop it as it's not allowed heading. However we must preserve ALL substantive information; dropping it would lose info. But we could embed it into a

under maybe Responsibilities or Requirements? The instruction says fold minor metadata into a short

or drop it. Physical Requirements is not minor metadata; it's a section. But we don't have a heading for it. Could we treat it as part of Responsibilities? Not really. Could we create a

without heading? The instruction says output only HTML fragment; we can include

paragraphs anywhere. So we could add a paragraph about physical requirements without a heading. That would preserve info. That seems acceptable. Similarly, "Why DataVox?" could be folded into About the role or maybe a paragraph. We must remove boilerplate: EEO line at end. Now craft HTML. Structure:

About the role

...

Responsibilities

• ...
...

Requirements

• ...
...

Qualifications

• ...
...

Benefits

• ...
...

Schedule

... travel details ...

Optionally add a paragraph for physical requirements and Why DataVox? maybe under About the role or as separate

without heading. We need to ensure we don't repeat job title. Let's extract precise text. About the role paragraph: combine the introductory sentences. "Join DataVox and Help Design the Future of Workplace Technology DataVox is seeking an experienced AV Sales Engineer to partner with our Account Managers in designing and presenting innovative Audio Visual and Unified Communications solutions for corporate clients throughout Texas. This is a highly visible, customer-facing role where you'll combine technical expertise with consultative sales support to help clients transform their collaboration, communication, and presentation environments. If you enjoy working with cutting-edge AV technology, collaborating with customers, and designing solutions that solve real business challenges, we'd love to hear from you." We could split into two sentences but fine. About DataVox description: "First, let us tell you more about DataVox. DataVox has been serving the Texas Triangle area for over 30 years with our advanced technology solutions. We specialize in Audio Visual Solutions, Data Center & Network Technologies, Network Security, IT Support Services, Network Cabling, Phone Systems & Physical Security. We are committed to being the best technology partner and ensuring the highest level of expertise and quality service by employing people like you. Our success is built on delivering exceptional service, deep technical expertise, and long-term customer relationships." We could add that as part of About the role paragraph or separate

. Probably better to include as part of About the role. Thus About the role will have two paragraphs: one about role, one about company. Now Responsibilities list: from "What You'll Do" and "Key Responsibilities". Let's list each bullet: - Partner with Account Managers during client discovery meetings, presentations, and site assessments - Develop AV system designs, budgets, bills of materials (BOMs), scopes of work, and technical proposals - Present technical recommendations and solution concepts to customers, consultants, and stakeholders - Design conferencing, collaboration, presentation, control, and integrated AV systems - Support proposal development and responses to RFPs and bid opportunities - Identify project risks, scope gaps, and value-engineering opportunities - Provide technical guidance related to audio, video, control, and collaboration technologies - Collaborate with customers and internal teams to establish project objectives, schedules, and expectations - Lead project handoffs to Operations and Project Management teams - Work closely with manufacturers, vendors, engineers, and installation teams - Stay current on emerging AV, Unified Communications, and workplace technology trends - Deliver an exceptional customer experience throughout the sales process Now Requirements (mandatory) list: - Bachelor's degree or equivalent professional experience - 2+ years of Audio Visual system design or AV engineering experience - Experience supporting consultative technology sales environments - Strong customer-facing communication and presentation skills - Experience creating budgets, BOMs, estimates, and technical proposals - Experience responding to RFPs and competitive bid requests - Understanding of the AV project lifecycle from discovery through deployment - Ability to interpret architectural, construction, and engineering drawings - Experience estimating labor and project costs - Strong organizational skills and attention to detail - Self-motivated team player with excellent written and verbal communication abilities - Proficiency with Microsoft Office Suite, including Excel and Outlook Now Qualifications (preferred) list: - AVIXA CTS certification - CTS-D and/or CTS-I certifications - Experience with D-Tools - Experience with Digital Signage solutions - Manufacturer certifications from: Crestron, Extron, Q-SYS, AMX, Biamp, Shure, Audinate - Experience with: Microsoft Teams Rooms, Zoom Rooms, Cisco Collaboration Solutions, Enterprise AV and UC technologies - Knowledge of AV control systems and automation platforms We could split manufacturer certifications into separate bullets but okay. Now Benefits list: - Competitive salary - Medical, dental, and vision insurance - Company-paid life insurance - Company-paid long-term disability coverage - 401(k) and Roth 401(k) with company match - Sponsored 529 College Savings Plan - Professional development and certification reimbursement - Employee Assistance Program (EAP) - Paid vacation and sick time - Paid company holidays - Health and wellness initiatives - Mileage reimbursement - Phone reimbursement - Employee engagement clubs and activities - Team-building and