Sr. Manager, System Test and Validation
Qcells North America · Santa Clara, CA · 1 mo ago
On-siteQuality AssuranceFull-time
We need to output HTML fragment with sections only if content present. Use for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content.
The posting includes: description (position description) which is about the role. Then Responsibilities list. Then Required Qualifications (list). Then Preferred Qualifications (list). Then Physical, Mental & Environmental Demands (maybe not needed as a section; we could include under Requirements? But we have headings: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide where to put each.
We have "Required Qualifications" and "Preferred Qualifications". Could combine into Qualifications section with subpoints? But we must not invent headings not listed. We can use "Qualifications" heading and include both required and preferred as list items, maybe differentiate? But we must preserve all substantive info. Could split into two sub-sections? Not allowed because only headings from list. Could put Required Qualifications under "Requirements" heading, and Preferred Qualifications under "Qualifications" heading. Or vice versa. The spec: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role (from position description), Responsibilities, Requirements (maybe required qualifications), Qualifications (maybe preferred qualifications), Skills (maybe list of skills like Python, etc). Benefits, Pay, Schedule only if present. Pay is present: salary range mentioned. So we need a Pay section with that info. Schedule? Not mentioned besides travel up to 20% expected. That's not schedule. Could treat travel as schedule? Not exactly. Probably no schedule section. Benefits? Not mentioned besides maybe none. So omit Benefits.
We need to extract substantive info: About the role: The position description paragraph(s). Responsibilities: bullet list. Requirements: required qualifications list. Qualifications: preferred qualifications list. Skills: maybe list of specific skills like Python, HIL, etc. Could extract from required qualifications: proficiency in Python, experience with hardware/software test automation, HIL, IoT communications, data acquisition, databases, command-and-control, analyzing large datasets, etc. Could put those under Skills.
We must not repeat job title. No Job ID. Remove boilerplate like EEO, privacy, etc. Also remove Physical, Mental & Environmental Demands? That is substantive but not fitting headings; maybe we could include under Requirements? But it's about physical demands. Could we include under Requirements? Might be okay but it's not typical. However we must preserve ALL substantive information. If we omit it, we lose info. We could include it under a heading not in list? Not allowed. Could we incorporate into Requirements as a list? Possibly but it's not a qualification. Could we add a section "Requirements" and include both qualifications and physical demands? The spec says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid adding other content under those headings. So we can put physical demands under Requirements as a list.
Similarly, we could put "Travel of up to 20% is expected" maybe under Responsibilities or About the role? Could be under Responsibilities? Not exactly. Could be under About the role as a note. We'll include in About the role paragraph.
Pay section: include salary range text.
Now craft HTML.
Structure:
.
Requirements: Required Qualifications list:
- B.S. in Electrical Engineering, Mechanical Engineering, Physics, Computer Engineering, or a related technical field; M.S. preferred.
- 5–10+ years of technical experience in energy storage systems, solar inverters, distributed energy resources, solar products, microgrids, power conversion systems, or other complex grid-connected/off-grid energy systems.
- Demonstrated experience with end-to-end product and system-level testing of complex hardware, firmware, and software systems.
- Strong understanding of system integration, functional validation, performance testing, and product-level verification.
- Experience developing test plans and validation strategies based on product requirements, user stories, and user acceptance criteria.
- Experience working across hardware, firmware, software, systems engineering, and product development organizations.
- Experience with hardware and software test automation methodologies and best practices.
- Knowledge of hardware-in-the-loop (HIL) testing principles and system simulation environments.
- Experience with IoT communications, data acquisition, databases, and command-and-control systems used in energy or connected products.
- Experience testing applications, user interfaces, or software tools that interact with connected hardware products.
- Proficiency in Python or a comparable scripting/programming language used for automation, testing, or data analysis.
- Experience analyzing large datasets and using data to identify trends, performance issues, and system-level anomalies.
- Demonstrated leadership experience guiding multidisciplinary engineering teams, projects, or technical programs.
- Strong analytical, troubleshooting, and root-cause problem-solving capabilities.
- Ability to communicate complex technical concepts clearly to engineering teams, cross-functional partners, and executive leadership.
- Proven ability to manage multiple priorities and projects in a fast-paced product development environment.
- Strong decision-making, organizational, and cross-functional collaboration skills.
- Ability to work effectively with global and multinational teams across different functions, cultures, and time zones.
Physical demands list:
- Mobility: Standing 20% of time, Sitting 70% of time, Walking 10% of time
- Strength: Pulling up to 10 Pounds, Pushing up to 10 Pounds, Carrying up to 10 Pounds, Lifting up to 10 Pounds
- Dexterity(F = Frequently, O = Occasionally, N = Never): Typing F, Handling F, Reaching F
- Agility(F = Frequently, O = Occasionally, N = Never): Turning F, Twisting F, Bending O, Crouching O, Balancing N, Climbing N, Crawling N, Kneeling N
We could format as list items.
Qualifications: Preferred Qualifications list:
- Experience leading or managing multidisciplinary engineering or system test teams.
- Experience with team budgeting, resource planning, and technical program forecasting.
- Experience designing, expanding, or managing engineering laboratory infrastructure.
- Hands-on laboratory and outdoor product testing experience.
- Experience with regulatory compliance, certification, and safety testing for solar, ESS, inverter, or related energy products.
- Experience testing integrated systems with third-party hardware, software, or energy products.
- Field engineering, applications engineering, deployment, or customer-facing technical experience.
- Experience working with installers, O&M providers, field service organizations, or other end users to incorporate field requirements into product testing.
- Experience taking complex hardware/software products from early development through validation, commercialization, and deployment.
- Experience working in a startup, high-growth, or rapidly evolving engineering environment.
- Experience working within a global organization and collaborating with multinational engineering teams.
- Experience working effectively with colleagues whose primary language may differ from your own.
Skills: we can extract specific skills from required qualifications: Python, hardware/software test automation, HIL testing, IoT communications, data acquisition, databases, command-and-control, analyzing large datasets, etc. Also maybe "test plans", "validation strategies". But we can list:
- Proficiency in Python or comparable scripting/programming language for automation, testing, data analysis.
- Experience with hardware and software test automation methodologies and best practices.
- Knowledge of hardware-in-the-loop (HIL) testing principles and system simulation environments.
- Experience with IoT communications, data acquisition, databases, and command-and-control systems.
- Experience testing applications, user interfaces, or software tools that interact with connected hardware.
- Experience analyzing large datasets to identify trends, performance issues, and system-level anomalies.
- Experience developing test plans and validation strategies based on product requirements, user stories, acceptance criteria.
- Experience working across hardware, firmware, software, systems engineering, and product development organizations.
- Strong understanding of system integration, functional validation, performance testing, product-level verification.
- Demonstrated leadership experience guiding multidisciplinary engineering teams.
- Strong analytical, troubleshooting, root-cause problem-solving.
- Ability to communicate complex technical concepts clearly.
- Ability to manage multiple priorities in fast-paced environment.
- Strong decision-making, organizational, cross-functional collaboration.
- Ability to work with global/multinational teams.
But we must not invent info; we can list those as skills.
Pay section: The salary range text:
"The salary range is required by the California Pay Transparency Act and may differ depending on the location of those candidates hired nationwide. Actual compensation is influenced by a wide array of factors including but not limited to, skill set, education, licenses and certifications, essential job duties and requirements, and the necessary experience relative to the job’s minimum qualifications. This target salary range is for CA positions only and should not be interpreted as an offer of compensation."
We'll put that in
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content.
The posting includes: description (position description) which is about the role. Then Responsibilities list. Then Required Qualifications (list). Then Preferred Qualifications (list). Then Physical, Mental & Environmental Demands (maybe not needed as a section; we could include under Requirements? But we have headings: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide where to put each.
We have "Required Qualifications" and "Preferred Qualifications". Could combine into Qualifications section with subpoints? But we must not invent headings not listed. We can use "Qualifications" heading and include both required and preferred as list items, maybe differentiate? But we must preserve all substantive info. Could split into two sub-sections? Not allowed because only headings from list. Could put Required Qualifications under "Requirements" heading, and Preferred Qualifications under "Qualifications" heading. Or vice versa. The spec: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role (from position description), Responsibilities, Requirements (maybe required qualifications), Qualifications (maybe preferred qualifications), Skills (maybe list of skills like Python, etc). Benefits, Pay, Schedule only if present. Pay is present: salary range mentioned. So we need a Pay section with that info. Schedule? Not mentioned besides travel up to 20% expected. That's not schedule. Could treat travel as schedule? Not exactly. Probably no schedule section. Benefits? Not mentioned besides maybe none. So omit Benefits.
We need to extract substantive info: About the role: The position description paragraph(s). Responsibilities: bullet list. Requirements: required qualifications list. Qualifications: preferred qualifications list. Skills: maybe list of specific skills like Python, HIL, etc. Could extract from required qualifications: proficiency in Python, experience with hardware/software test automation, HIL, IoT communications, data acquisition, databases, command-and-control, analyzing large datasets, etc. Could put those under Skills.
We must not repeat job title. No Job ID. Remove boilerplate like EEO, privacy, etc. Also remove Physical, Mental & Environmental Demands? That is substantive but not fitting headings; maybe we could include under Requirements? But it's about physical demands. Could we include under Requirements? Might be okay but it's not typical. However we must preserve ALL substantive information. If we omit it, we lose info. We could include it under a heading not in list? Not allowed. Could we incorporate into Requirements as a list? Possibly but it's not a qualification. Could we add a section "Requirements" and include both qualifications and physical demands? The spec says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid adding other content under those headings. So we can put physical demands under Requirements as a list.
Similarly, we could put "Travel of up to 20% is expected" maybe under Responsibilities or About the role? Could be under Responsibilities? Not exactly. Could be under About the role as a note. We'll include in About the role paragraph.
Pay section: include salary range text.
Now craft HTML.
Structure:
About the role
... (combined description paragraphs)
Responsibilities
- ... each responsibility line
Requirements
- ... required qualifications items
- ... physical demands items (maybe as subitems? but we can just list)
Qualifications
- ... preferred qualifications items
Skills
- ... skills extracted
Pay
... salary range text
We must not include empty sections. Now extract content. About the role: The description includes: "POSITION DESCRIPTION: The System Integration and Architecture Team is seeking an experienced technical leader to serve as Sr. Manager, System Test and Validation and lead Qcells’ System Test team. This role will own the end-to-end system validation strategy for Qcells’ current and next-generation energy products, including AC modules, inverters, energy storage systems (ESS), energy management platforms, and integrated software solutions for the North American market. The Sr. Manager will lead a multidisciplinary team of hardware, systems, and software engineers and will be responsible for developing scalable test methodologies, expanding laboratory capabilities, and increasing test automation. Working closely with Product Management, Development, QA, Deployment, and external test partners, this leader will ensure Qcells products meet functional, performance, reliability, and user requirements from early development through product release. This position reports to the Head of the System Integration and Architecture Team and is based at the Qcells R&D Center in Santa Clara, CA. Travel of up to 20% is expected to Qcells offices and test facilities." We'll put that in. Responsibilities list: each line starting with a verb. Let's copy them: - Define, document, and execute comprehensive end-to-end system test and validation strategies for current and next-generation Qcells products. - Lead and develop a multidisciplinary team of hardware, systems, and software engineers focused on system testing and validation. - Establish test plans, procedures, reporting standards, and records management processes that support product development and release. - Collaborate with hardware, firmware, software, systems, and QA teams to define and execute system-level test requirements. - Partner with Product Management to develop objective Alpha test plans based on user acceptance criteria, product requirements, and customer needs. - Collaborate with Deployment teams to define and execute Beta test programs and incorporate field feedback into validation strategies. - Lead the expansion of test laboratory capabilities in Santa Clara and other Qcells laboratory facilities. - Identify and implement opportunities to increase hardware and software test automation, including hardware-in-the-loop (HIL) testing. - Develop scalable and repeatable test processes that improve coverage, efficiency, reliability, and speed of product validation. - Collaborate with external laboratories, certification bodies, and third-party testing partners as required. - Stay current on industry testing standards, regulatory requirements, technologies, and validation methodologies. - Provide technical leadership across complex system-level issues, root-cause investigations, and cross-functional problem solving. - Foster a team culture centered on accountability, collaboration, innovation, technical excellence, and continuous learning. We'll put each as
. Now ensure we don't include boilerplate like privacy, EEO, etc. We removed. Now produce HTML fragment.