Design Engineer
AVI-SPL · Oklahoma City, OK · 4 wk ago
On-siteEngineeringFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the posting.
First, job title is "Design Engineer". Not to repeat as heading.
We need sections:
- About the role? The posting includes "Who We Are" and description. Could be "About the role" or "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map content accordingly.
We have:
- About the role: maybe a paragraph describing the role: "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." That's repeated later but we can include once.
- Responsibilities: includes "What You’ll Do" and "Day-To-Day Responsibilities". So we can list bullet points.
- Requirements: includes "Must-Haves" (minimum high school diploma, core competencies, technical expertise, etc.) Also "Nice-To-Haves" maybe part of qualifications? Could be under Requirements or Qualifications. The instruction says we can have Requirements and Qualifications separate. We'll decide: Requirements = Must-Haves (mandatory). Qualifications = Nice-To-Haves (preferred). Or we could combine. We'll follow typical: Requirements = mandatory, Qualifications = preferred.
- Skills: maybe we can extract from core competencies: problem-solving, stakeholder communication, detail-oriented, cross-functional teamwork, deadline management, self-directed learning, technical expertise (design/configuration AV systems, IP networking, standards, CAD tools, infrastructure, certifications, driver's license). Could be a separate Skills section.
- Benefits: includes "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". Also maybe more about culture. So we can include Benefits.
- Pay: not mentioned. So we should NOT include Pay section.
- Schedule: not mentioned specific schedule; only mention "Work hours may vary based on client requirements and may include travel". That's somewhat schedule info but not explicit. The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does mention work hours may vary, but not explicit schedule. Might be considered schedule info? It's vague. Safer to omit Schedule.
Now we need to output HTML fragment with
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the posting.
First, job title is "Design Engineer". Not to repeat as heading.
We need sections:
- About the role? The posting includes "Who We Are" and description. Could be "About the role" or "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map content accordingly.
We have:
- About the role: maybe a paragraph describing the role: "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." That's repeated later but we can include once.
- Responsibilities: includes "What You’ll Do" and "Day-To-Day Responsibilities". So we can list bullet points.
- Requirements: includes "Must-Haves" (minimum high school diploma, core competencies, technical expertise, etc.) Also "Nice-To-Haves" maybe part of qualifications? Could be under Requirements or Qualifications. The instruction says we can have Requirements and Qualifications separate. We'll decide: Requirements = Must-Haves (mandatory). Qualifications = Nice-To-Haves (preferred). Or we could combine. We'll follow typical: Requirements = mandatory, Qualifications = preferred.
- Skills: maybe we can extract from core competencies: problem-solving, stakeholder communication, detail-oriented, cross-functional teamwork, deadline management, self-directed learning, technical expertise (design/configuration AV systems, IP networking, standards, CAD tools, infrastructure, certifications, driver's license). Could be a separate Skills section.
- Benefits: includes "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". Also maybe more about culture. So we can include Benefits.
- Pay: not mentioned. So we should NOT include Pay section.
- Schedule: not mentioned specific schedule; only mention "Work hours may vary based on client requirements and may include travel". That's somewhat schedule info but not explicit. The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does mention work hours may vary, but not explicit schedule. Might be considered schedule info? It's vague. Safer to omit Schedule.
Now we need to output HTML fragment with headings and - for lists,
for prose.
We must preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not include boilerplate like EEO etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
We need to remove duplicated lines: The first sentence appears twice: "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." It appears at start and again under "What You’ll Do". We should include only once.
Also "Who We Are" paragraph about AVI-SPL. That's substantive.
We need to include "More About Us" maybe not needed as it's EEO boilerplate; but it includes "AVI-SPL is an Equal Opportunity/Affirmative Action Employer..." which is boilerplate to remove. Also "AVI-SPL reserves the right to alter work hours..." maybe not boilerplate but could be considered schedule? It's about work hours variation. Might be considered schedule info but it's generic. The instruction says never create Schedule section unless posting actually states them. It does state work hours may vary based on client requirements and may include travel. That's somewhat schedule. But we might still omit Schedule section because it's not a specific schedule (like shift times). Safer to omit.
Now we need to decide structure:
About the role
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.
Maybe also include a brief about company? Could be under About the role or separate About the company. But headings limited to list; we could use About the role for role description, and maybe include company description under same heading? Could add another paragraph.
Better: About the role
with two paragraphs: role description and company overview.
But we must not invent headings not in list; we can use About the role.
Now Responsibilities: need to list bullet points from "What You’ll Do" and "Day-To-Day Responsibilities". Let's extract distinct responsibilities:
- 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.
- 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.
- 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.
Also maybe "Presenting solutions and explaining complex technical designs in a simple way that helps customers clearly see how the solutions meet their needs." That's covered by participate in client discussions.
Also "By creating accurate, comprehensive design packages, you ensure the project team has the details needed for successful execution." That's covered by develop detailed system documentation.
Also "Strong problem-solving skills that balance addressing customer desires and satisfaction with internal business needs are essential." That's more a requirement.
Also "The Design Engineer takes ownership and responsibility for accuracy and feasibility of designs ensuring successful project execution through collaboration and support." Could be a responsibility.
We'll include that as a bullet: "Take ownership and responsibility for accuracy and feasibility of designs to ensure successful project execution through collaboration and support."
Now Requirements (Must-Haves): list:
- Minimum of a high school diploma or equivalent.
- 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 could break the technical expertise into sub-bullets.
Now Qualifications (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.
Now Skills: Could be overlapping with requirements; but we could create a Skills section summarizing core competencies: problem-solving, stakeholder communication, detail-oriented, cross-functional teamwork, deadline management, self-directed learning, technical expertise (design/configuration AV systems, IP networking, standards, CAD, infrastructure, certifications, driver's license). However that may duplicate. The instruction says prefer a few substantive sections over many thin ones. We could combine Requirements and Qualifications into one "Requirements" section, and maybe have Skills separate. But we need to follow headings list; we can include Skills if we have content.
We could decide to have:
- About the role
- Responsibilities
- Requirements (including both must-haves and nice-to-haves)
- Benefits
That's four sections. Skills could be omitted to avoid thin.
But we need to ensure we include all substantive info. If we put nice-to-haves under Requirements, it's okay.
Let's craft Requirements section with two subheadings? Not allowed; only headings. We could just list all items, maybe separate with paragraphs indicating "Must-Haves" and "Nice-To-Haves". But we cannot add extra headings not in list. We could use
to label them.
We'll do:
Requirements
Must-Haves:
...
Nice-To-Haves:
...
That's acceptable.
Now Benefits section:
Benefits
- Medical benefits, including vision and dental
- Paid holidays and PTO
- Enjoyable and dynamic company culture
- Training and professional development opportunities
We could also include "More About Us" but that's EEO boilerplate; remove.
Now we need to ensure we didn't include any boilerplate like EEO, etc. Remove the "More About Us" paragraph.
Also remove any duplicated lines: we already removed duplicate role description.
Now check for any other boilerplate: "AVI-SPL is an Equal Opportunity/Affirmative Action Employer..." etc. Remove.
Also "AVI-SPL reserves the right to alter work hours and work location as necessary. Work hours may vary based on client requirements and may include travel to various locations in support of the account." This is somewhat schedule info but we are not making Schedule section. Could we include it under Responsibilities or About the role? It's about work hours; maybe we could include a sentence in About the role or Benefits? But it's not a benefit. Could be included as a note under Responsibilities? Might be considered schedule info but not a heading. The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state work hours may vary; but we are not making a Schedule section, we are just including that info somewhere else. Is that allowed? The instruction says "never create Pay/Schedule/Benefits sections
- for lists,
for prose. We must preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not include boilerplate like EEO etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to remove duplicated lines: The first sentence appears twice: "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." It appears at start and again under "What You’ll Do". We should include only once. Also "Who We Are" paragraph about AVI-SPL. That's substantive. We need to include "More About Us" maybe not needed as it's EEO boilerplate; but it includes "AVI-SPL is an Equal Opportunity/Affirmative Action Employer..." which is boilerplate to remove. Also "AVI-SPL reserves the right to alter work hours..." maybe not boilerplate but could be considered schedule? It's about work hours variation. Might be considered schedule info but it's generic. The instruction says never create Schedule section unless posting actually states them. It does state work hours may vary based on client requirements and may include travel. That's somewhat schedule. But we might still omit Schedule section because it's not a specific schedule (like shift times). Safer to omit. Now we need to decide structure:
About the role
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.
Maybe also include a brief about company? Could be under About the role or separate About the company. But headings limited to list; we could use About the role for role description, and maybe include company description under same heading? Could add another paragraph. Better:About the role
with two paragraphs: role description and company overview. But we must not invent headings not in list; we can use About the role. Now Responsibilities: need to list bullet points from "What You’ll Do" and "Day-To-Day Responsibilities". Let's extract distinct responsibilities: - 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. - 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. - 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. Also maybe "Presenting solutions and explaining complex technical designs in a simple way that helps customers clearly see how the solutions meet their needs." That's covered by participate in client discussions. Also "By creating accurate, comprehensive design packages, you ensure the project team has the details needed for successful execution." That's covered by develop detailed system documentation. Also "Strong problem-solving skills that balance addressing customer desires and satisfaction with internal business needs are essential." That's more a requirement. Also "The Design Engineer takes ownership and responsibility for accuracy and feasibility of designs ensuring successful project execution through collaboration and support." Could be a responsibility. We'll include that as a bullet: "Take ownership and responsibility for accuracy and feasibility of designs to ensure successful project execution through collaboration and support." Now Requirements (Must-Haves): list: - Minimum of a high school diploma or equivalent. - 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 could break the technical expertise into sub-bullets. Now Qualifications (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. Now Skills: Could be overlapping with requirements; but we could create a Skills section summarizing core competencies: problem-solving, stakeholder communication, detail-oriented, cross-functional teamwork, deadline management, self-directed learning, technical expertise (design/configuration AV systems, IP networking, standards, CAD, infrastructure, certifications, driver's license). However that may duplicate. The instruction says prefer a few substantive sections over many thin ones. We could combine Requirements and Qualifications into one "Requirements" section, and maybe have Skills separate. But we need to follow headings list; we can include Skills if we have content. We could decide to have: - About the role - Responsibilities - Requirements (including both must-haves and nice-to-haves) - Benefits That's four sections. Skills could be omitted to avoid thin. But we need to ensure we include all substantive info. If we put nice-to-haves under Requirements, it's okay. Let's craft Requirements section with two subheadings? Not allowed; onlyheadings. We could just list all items, maybe separate with paragraphs indicating "Must-Haves" and "Nice-To-Haves". But we cannot add extra headings not in list. We could use
to label them. We'll do:
Requirements
Must-Haves:
- ...
Nice-To-Haves:
- ...
Benefits
- Medical benefits, including vision and dental
- Paid holidays and PTO
- Enjoyable and dynamic company culture
- Training and professional development opportunities