Software QA Engineer
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not include filler like "commensurate with experience". Not present.
We must not include boilerplate like EEO, legal, etc. Remove those paragraphs.
We must not include application instructions.
We must not include duplicated lines.
We need to preserve all substantive information.
Let's extract substantive content:
About the role paragraph:
"ZT Systems, a wholly owned subsidiary of Sanmina, is seeking an experienced Software QA Engineer to support the development and validation of enterprise storage management solutions in partnership with Viking Enterprise Solutions, another Sanmina company. Viking Enterprise Solutions delivers storage array systems and infrastructure solutions that enable customers to build flexible, scalable, and resilient storage, public cloud, and private cloud environments. In this role, you will be responsible for end-to-end validation of storage management applications and solutions. The successful candidate will join a team focused on designing, maintaining, and validating software for advanced storage array systems, leveraging a combination of open-source and third-party technologies to deliver high-quality, reliable products to customers."
That's about the role.
Responsibilities (Key Accountabilities & Skills Required) list:
- Experience with developing Software test plan per product feature requirement
- Experience with Software QA processes and methodologies
- Working knowledge of CI/CD test automation pipelines
- Working knowledge in JIRA Confluence toolsets
- Project Management experiences such as schedule, risk management
- Experience with assisting field team on debug analysis, customer issue recreate activities.
- Working knowledge of Server/Storage and Networking infrastructures
- Collaborate with other team members on shared items of work and communicate effectively in a team-oriented environment to ensure end to end delivery of features
- Experience with web services API integration.
- Experience with Python, JavaScript, Shell script and other software languages
Also later: "We are seeking a team player who enjoys technical challenges within a fast-paced environment, applies sound judgment in successful task planning and execution, meets deadlines, and communicates the highest standards of professionalism in his/her work habits." Could be part of responsibilities or qualifications. We'll treat as responsibilities.
Qualifications/Education:
Essential:
- Bachelor's degree in Computer Science or related field, or demonstrated experience
- 5+ years of software development or Storage Software QA experience
- Experience working with a team and collaborating in a remote work scenario
- Experience utilizing Agile development and QA methodologies
- A record of successful delivery of software applications as an individual QA engineer in a team environment
- Understanding of the software development and quality assurance program cycle
- Problem-solving skills - methodical approach
- Communication skills both verbal and written
- Ability to communicate and work with customers and end users
- Experience in Python, JavaScript, Shell script and other software languages
Desirable:
- Familiar with data storage technologies (S3 Object, Block Devices, NFS and SMB File Systems).
- Familiarity with developing and testing software in a Linux environment
Skills: Might be overlapping with qualifications. But we can have a Skills section summarizing technical skills: Python, JavaScript, Shell script, web services API integration, JIRA Confluence, CI/CD, Server/Storage/Networking, etc. However we must avoid duplication. Perhaps we can combine skills into Qualifications and Responsibilities; but the instruction says we can have Skills section if there is real specific content. The posting includes "Skills and knowledge: Essential" and "Skills and knowledge: Desirable". That's essentially qualifications. There's also a separate "Skills" heading? Not exactly. The posting includes "Skills and knowledge: Essential" and "Skills and knowledge: Desirable". So we could treat that as Qualifications. There's no separate Skills section beyond that. However we could still create a Skills section for technical skills like Python, JavaScript, Shell script, web services API integration, etc. But that would duplicate content from qualifications. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine qualifications and skills into one Qualifications section. But we also have Responsibilities separate.
We need to decide sections: About the role, Responsibilities, Qualifications, Benefits, Pay. Possibly also Skills if distinct.
Let's see if there is any distinct Skills list besides qualifications: The "Key Accountabilities & Skills Required" includes skills. But that's more responsibilities. So we could have Responsibilities and Qualifications.
Benefits: The posting includes "We take pride in offering a wide range of benefits and perks..." then later "What We Offer" with detailed benefits: Competitive base salary, Performance-based annual bonus eligibility, 401(k) retirement savings plan, Tuition reimbursement, Comprehensive medical, dental, vision coverage, Mental health resources, Company-paid life and disability insurance, Paid time off (PTO) and company-paid holidays, Parental leave and family care support programs, Structured training programs and on-the-job learning opportunities, Matching gifts and volunteer programs.
Also "Other rewards may include bonus, paid time off, 401k, tuition reimbursement, wellbeing resources, and more."
Thus we have benefits content.
Pay: salary range $105,000-$154,000 per year.
Schedule: none.
Thus output sections: About the role (
About the role
), Responsibilities (Responsibilities
), Qualifications (Qualifications
), Benefits (Benefits
), Pay (Pay
).
We must not include empty sections.
Now we need to format content.
For About the role: use with the paragraph(s). Could be two paragraphs? We have one paragraph. We'll keep as
.
For Responsibilities: we need a
- list. Include each bullet.
We need to ensure we include all responsibilities from Key Accountabilities & Skills Required plus the team player statement.
Let's list them:
- Developing Software test plan per product feature requirement
- Software QA processes and methodologies
- CI/CD test automation pipelines
- JIRA Confluence toolsets
- Project Management experiences such as schedule, risk management
- Assisting field team on debug analysis, customer issue recreate activities
- Working knowledge of Server/Storage and Networking infrastructures
- Collaborate with other team members on shared items of work and communicate effectively in a team-oriented environment to ensure end to end delivery of features
- Experience with web services API integration.
- Experience with Python, JavaScript, Shell script and other software languages
- Team player who enjoys technical challenges within a fast-paced environment, applies sound judgment in successful task planning and execution, meets deadlines, and communicates the highest standards of professionalism in his/her work habits.
We could combine some.
Now Qualifications: essential and desirable.
We'll make two sub-lists? Could just list all as bullet points, marking essential vs desirable? But we need to preserve all info. Could separate into Essential and Desirable subheadings? But we cannot add extra headings beyond
for sections; we could use
to introduce essential and desirable. Or we could just list all as bullet points with note. The instruction: Use
- for any list of duties/requirements/benefits. So we can have a list for qualifications. We'll include all essential and desirable items as bullet points.
List essential:
- Bachelor's degree in Computer Science or related field, or demonstrated experience
- 5+ years of software development or Storage Software QA experience
- Experience working with a team and collaborating in a remote work scenario
- Experience utilizing Agile development and QA methodologies
- A record of successful delivery of software applications as an individual QA engineer in a team environment
- Understanding of the software development and quality assurance program cycle
- Problem-solving skills - methodical approach
- Communication skills both verbal and written
- Ability to communicate and work with customers and end users
- Experience in Python, JavaScript, Shell script and other software languages
Desirable:
- Familiar with data storage technologies (S3 Object, Block Devices, NFS and SMB File Systems)
- Familiarity with developing and testing software in a Linux environment
Now Benefits: list.
From "What We Offer" and earlier:
- Competitive base salary (but we have Pay section separate; maybe we mention base salary in Pay only; but benefits section could still mention other benefits). However we should not duplicate. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we put base salary in Pay section, we should not also repeat it in Benefits. But the benefits section includes "Competitive base salary" as part of total rewards. We could still include it but that would duplicate. Better to keep Pay section for salary range, and Benefits section for other benefits: performance-based annual bonus eligibility, 401(k) retirement savings plan, tuition reimbursement, comprehensive medical/dental/vision coverage, mental health resources, company-paid life and disability insurance, paid time off (PTO) and company-paid holidays, parental leave and family care support programs, structured training programs and on-the-job learning opportunities, matching gifts and volunteer programs, wellbeing resources.
Also "Other rewards may include bonus, paid time off, 401k, tuition reimbursement, wellbeing resources, and more." Already covered.
Thus Benefits list.
Pay: salary range $105,000-$154,000 per year. Also note that final base salary determined individually based on experience, skills, etc. Also mention base salary is one component of total rewards. We'll include that.
Now we need to ensure we don't include boilerplate like EEO, legal, etc. Remove those paragraphs.
Now produce HTML.
We'll start with
About the role
...
Then Responsibilities
...
Then Qualifications
...
Then Benefits
...
Then Pay
...
Make sure no extra whitespace? It's fine.
Now craft the content precisely.
About the role paragraph: combine the two sentences? We'll keep as one paragraph.
Paragraph: "ZT Systems, a wholly owned subsidiary of Sanmina, is seeking an experienced Software QA Engineer to support the development and validation of enterprise storage management solutions in partnership with Viking Enterprise Solutions, another Sanmina company. Viking Enterprise Solutions delivers storage array systems and infrastructure solutions that enable customers to build flexible, scalable, and resilient storage, public cloud, and private cloud environments. In this role, you will be responsible for end-to
for prose. We must not include filler like "commensurate with experience". Not present. We must not include boilerplate like EEO, legal, etc. Remove those paragraphs. We must not include application instructions. We must not include duplicated lines. We need to preserve all substantive information. Let's extract substantive content: About the role paragraph: "ZT Systems, a wholly owned subsidiary of Sanmina, is seeking an experienced Software QA Engineer to support the development and validation of enterprise storage management solutions in partnership with Viking Enterprise Solutions, another Sanmina company. Viking Enterprise Solutions delivers storage array systems and infrastructure solutions that enable customers to build flexible, scalable, and resilient storage, public cloud, and private cloud environments. In this role, you will be responsible for end-to-end validation of storage management applications and solutions. The successful candidate will join a team focused on designing, maintaining, and validating software for advanced storage array systems, leveraging a combination of open-source and third-party technologies to deliver high-quality, reliable products to customers." That's about the role. Responsibilities (Key Accountabilities & Skills Required) list: - Experience with developing Software test plan per product feature requirement - Experience with Software QA processes and methodologies - Working knowledge of CI/CD test automation pipelines - Working knowledge in JIRA Confluence toolsets - Project Management experiences such as schedule, risk management - Experience with assisting field team on debug analysis, customer issue recreate activities. - Working knowledge of Server/Storage and Networking infrastructures - Collaborate with other team members on shared items of work and communicate effectively in a team-oriented environment to ensure end to end delivery of features - Experience with web services API integration. - Experience with Python, JavaScript, Shell script and other software languages Also later: "We are seeking a team player who enjoys technical challenges within a fast-paced environment, applies sound judgment in successful task planning and execution, meets deadlines, and communicates the highest standards of professionalism in his/her work habits." Could be part of responsibilities or qualifications. We'll treat as responsibilities. Qualifications/Education: Essential: - Bachelor's degree in Computer Science or related field, or demonstrated experience - 5+ years of software development or Storage Software QA experience - Experience working with a team and collaborating in a remote work scenario - Experience utilizing Agile development and QA methodologies - A record of successful delivery of software applications as an individual QA engineer in a team environment - Understanding of the software development and quality assurance program cycle - Problem-solving skills - methodical approach - Communication skills both verbal and written - Ability to communicate and work with customers and end users - Experience in Python, JavaScript, Shell script and other software languages Desirable: - Familiar with data storage technologies (S3 Object, Block Devices, NFS and SMB File Systems). - Familiarity with developing and testing software in a Linux environment Skills: Might be overlapping with qualifications. But we can have a Skills section summarizing technical skills: Python, JavaScript, Shell script, web services API integration, JIRA Confluence, CI/CD, Server/Storage/Networking, etc. However we must avoid duplication. Perhaps we can combine skills into Qualifications and Responsibilities; but the instruction says we can have Skills section if there is real specific content. The posting includes "Skills and knowledge: Essential" and "Skills and knowledge: Desirable". That's essentially qualifications. There's also a separate "Skills" heading? Not exactly. The posting includes "Skills and knowledge: Essential" and "Skills and knowledge: Desirable". So we could treat that as Qualifications. There's no separate Skills section beyond that. However we could still create a Skills section for technical skills like Python, JavaScript, Shell script, web services API integration, etc. But that would duplicate content from qualifications. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine qualifications and skills into one Qualifications section. But we also have Responsibilities separate. We need to decide sections: About the role, Responsibilities, Qualifications, Benefits, Pay. Possibly also Skills if distinct. Let's see if there is any distinct Skills list besides qualifications: The "Key Accountabilities & Skills Required" includes skills. But that's more responsibilities. So we could have Responsibilities and Qualifications. Benefits: The posting includes "We take pride in offering a wide range of benefits and perks..." then later "What We Offer" with detailed benefits: Competitive base salary, Performance-based annual bonus eligibility, 401(k) retirement savings plan, Tuition reimbursement, Comprehensive medical, dental, vision coverage, Mental health resources, Company-paid life and disability insurance, Paid time off (PTO) and company-paid holidays, Parental leave and family care support programs, Structured training programs and on-the-job learning opportunities, Matching gifts and volunteer programs. Also "Other rewards may include bonus, paid time off, 401k, tuition reimbursement, wellbeing resources, and more." Thus we have benefits content. Pay: salary range $105,000-$154,000 per year. Schedule: none. Thus output sections: About the role (
About the role
), Responsibilities (Responsibilities
), Qualifications (Qualifications
), Benefits (Benefits
), Pay (Pay
). We must not include empty sections. Now we need to format content. For About the role: usewith the paragraph(s). Could be two paragraphs? We have one paragraph. We'll keep as
. For Responsibilities: we need a
- list. Include each bullet.
We need to ensure we include all responsibilities from Key Accountabilities & Skills Required plus the team player statement.
Let's list them:
- Developing Software test plan per product feature requirement
- Software QA processes and methodologies
- CI/CD test automation pipelines
- JIRA Confluence toolsets
- Project Management experiences such as schedule, risk management
- Assisting field team on debug analysis, customer issue recreate activities
- Working knowledge of Server/Storage and Networking infrastructures
- Collaborate with other team members on shared items of work and communicate effectively in a team-oriented environment to ensure end to end delivery of features
- Experience with web services API integration.
- Experience with Python, JavaScript, Shell script and other software languages
- Team player who enjoys technical challenges within a fast-paced environment, applies sound judgment in successful task planning and execution, meets deadlines, and communicates the highest standards of professionalism in his/her work habits.
We could combine some.
Now Qualifications: essential and desirable.
We'll make two sub-lists? Could just list all as bullet points, marking essential vs desirable? But we need to preserve all info. Could separate into Essential and Desirable subheadings? But we cannot add extra headings beyond
for sections; we could use
to introduce essential and desirable. Or we could just list all as bullet points with note. The instruction: Use
- for any list of duties/requirements/benefits. So we can have a list for qualifications. We'll include all essential and desirable items as bullet points.
List essential:
- Bachelor's degree in Computer Science or related field, or demonstrated experience
- 5+ years of software development or Storage Software QA experience
- Experience working with a team and collaborating in a remote work scenario
- Experience utilizing Agile development and QA methodologies
- A record of successful delivery of software applications as an individual QA engineer in a team environment
- Understanding of the software development and quality assurance program cycle
- Problem-solving skills - methodical approach
- Communication skills both verbal and written
- Ability to communicate and work with customers and end users
- Experience in Python, JavaScript, Shell script and other software languages
Desirable:
- Familiar with data storage technologies (S3 Object, Block Devices, NFS and SMB File Systems)
- Familiarity with developing and testing software in a Linux environment
Now Benefits: list.
From "What We Offer" and earlier:
- Competitive base salary (but we have Pay section separate; maybe we mention base salary in Pay only; but benefits section could still mention other benefits). However we should not duplicate. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we put base salary in Pay section, we should not also repeat it in Benefits. But the benefits section includes "Competitive base salary" as part of total rewards. We could still include it but that would duplicate. Better to keep Pay section for salary range, and Benefits section for other benefits: performance-based annual bonus eligibility, 401(k) retirement savings plan, tuition reimbursement, comprehensive medical/dental/vision coverage, mental health resources, company-paid life and disability insurance, paid time off (PTO) and company-paid holidays, parental leave and family care support programs, structured training programs and on-the-job learning opportunities, matching gifts and volunteer programs, wellbeing resources.
Also "Other rewards may include bonus, paid time off, 401k, tuition reimbursement, wellbeing resources, and more." Already covered.
Thus Benefits list.
Pay: salary range $105,000-$154,000 per year. Also note that final base salary determined individually based on experience, skills, etc. Also mention base salary is one component of total rewards. We'll include that.
Now we need to ensure we don't include boilerplate like EEO, legal, etc. Remove those paragraphs.
Now produce HTML.
We'll start with
About the role
...
ThenResponsibilities
- ...
Qualifications
- ...
Benefits
- ...
Pay
...
Make sure no extra whitespace? It's fine. Now craft the content precisely. About the role paragraph: combine the two sentences? We'll keep as one paragraph. Paragraph: "ZT Systems, a wholly owned subsidiary of Sanmina, is seeking an experienced Software QA Engineer to support the development and validation of enterprise storage management solutions in partnership with Viking Enterprise Solutions, another Sanmina company. Viking Enterprise Solutions delivers storage array systems and infrastructure solutions that enable customers to build flexible, scalable, and resilient storage, public cloud, and private cloud environments. In this role, you will be responsible for end-to
- for any list of duties/requirements/benefits. So we can have a list for qualifications. We'll include all essential and desirable items as bullet points.
List essential:
- Bachelor's degree in Computer Science or related field, or demonstrated experience
- 5+ years of software development or Storage Software QA experience
- Experience working with a team and collaborating in a remote work scenario
- Experience utilizing Agile development and QA methodologies
- A record of successful delivery of software applications as an individual QA engineer in a team environment
- Understanding of the software development and quality assurance program cycle
- Problem-solving skills - methodical approach
- Communication skills both verbal and written
- Ability to communicate and work with customers and end users
- Experience in Python, JavaScript, Shell script and other software languages
Desirable:
- Familiar with data storage technologies (S3 Object, Block Devices, NFS and SMB File Systems)
- Familiarity with developing and testing software in a Linux environment
Now Benefits: list.
From "What We Offer" and earlier:
- Competitive base salary (but we have Pay section separate; maybe we mention base salary in Pay only; but benefits section could still mention other benefits). However we should not duplicate. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we put base salary in Pay section, we should not also repeat it in Benefits. But the benefits section includes "Competitive base salary" as part of total rewards. We could still include it but that would duplicate. Better to keep Pay section for salary range, and Benefits section for other benefits: performance-based annual bonus eligibility, 401(k) retirement savings plan, tuition reimbursement, comprehensive medical/dental/vision coverage, mental health resources, company-paid life and disability insurance, paid time off (PTO) and company-paid holidays, parental leave and family care support programs, structured training programs and on-the-job learning opportunities, matching gifts and volunteer programs, wellbeing resources.
Also "Other rewards may include bonus, paid time off, 401k, tuition reimbursement, wellbeing resources, and more." Already covered.
Thus Benefits list.
Pay: salary range $105,000-$154,000 per year. Also note that final base salary determined individually based on experience, skills, etc. Also mention base salary is one component of total rewards. We'll include that.
Now we need to ensure we don't include boilerplate like EEO, legal, etc. Remove those paragraphs.
Now produce HTML.
We'll start with