Business Intelligence Data Analyst
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose. Do not repeat job title as heading (already shown). Do not put Job ID/requisition numbers as headings. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Preserve all substantive info.
We need sections: About the role (maybe heading "About the role") with paragraph(s). Then Responsibilities (list). Then Required Qualifications (list). Then Preferred Qualifications (list). Then Pay (since posting states typical base salary range). Then Benefits (since posting lists benefits). Possibly Schedule? Not present. So we omit Schedule.
We must not create sections with filler like "commensurate with experience". Pay section: we have salary range. Provide that.
Benefits: list from "What We Offer" section. Need to capture all benefits listed: Competitive base salary (but that's already pay), Performance-based annual bonus eligibility, 401(k) retirement savings plan, Tuition reimbursement for eligible education programs, Health & Wellness: Comprehensive medical, dental, and vision coverage with access to leading providers, Mental health resources and employee wellness support programs, Company-paid life and disability insurance, Time Away & Work-Life Balance: Paid time off (PTO) and company-paid holidays, Parental leave and family care support programs, Growth & Purpose: Structured training programs and on-the-job learning opportunities, Matching gifts and volunteer programs to support causes you care about. Also note "These benefits are available to eligible employees and are designed to grow with you as your career evolves. Full benefits and eligibility varies by work location." Might include that as prose.
We need to avoid duplication: "Competitive base salary" appears also in Pay section; we could still include in benefits but maybe avoid duplication? The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should keep it, but could be in both sections; but duplication is okay? They said remove duplicated lines. That refers to duplicated lines in the posting. The posting has "Competitive base salary" both in Pay and Benefits. It's duplicated in the source; we should remove duplicated lines. So we should include it only once, perhaps in Pay section, and not repeat in Benefits. But we need to preserve all substantive info; if we remove duplicate, we still have the info (in Pay). That's fine.
Thus Benefits section will list other benefits excluding base salary.
Now we need to format.
Structure:
About the role
... paragraph(s) from About The Role.
Then Responsibilities:
Responsibilities
- ... each bullet from Key Responsibilities.
Required Qualifications:
Required Qualifications
- ... each bullet.
Preferred Qualifications:
Preferred Qualifications
- ... each bullet.
Pay:
Pay
The typical base salary for this position is expected to be between $60,750 and $81,000 annually. Final base salary will be determined individually based on experience, skills, knowledge, education, and/or certifications.
Benefits:
Benefits
- Performance-based annual bonus eligibility
- 401(k) retirement savings plan
- Tuition reimbursement for eligible education programs
- Comprehensive medical, dental, and vision coverage with access to leading providers
- Mental health resources and employee wellness support programs
- 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 to support causes you care about
These benefits are available to eligible employees and are designed to grow with you as your career evolves. Full benefits and eligibility varies by work location.
We need to ensure we didn't include any boilerplate like EEO, etc. Also removed "About ZT Systems" and "What We Offer" headings? We used Benefits section to capture the substance. The "About ZT Systems" paragraph is descriptive about company culture; is that substantive? It might be considered boilerplate? It's not EEO/legal; it's about company values. Should we keep? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About ZT Systems" paragraph is not boilerplate; it's about company culture. Should we include? Possibly as part of About the role? But we already have About the role section. Could add another paragraph after About the role describing company. However the instruction: Prefer a few substantive sections over many thin ones. Could incorporate that into About the role paragraph. But we already have About the role paragraph from the initial "About The Role". We could add another paragraph describing ZT Systems culture as part of About the role or maybe a separate section like "About the company". But they said use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They didn't list "About the company". So better to incorporate that description into About the role paragraph.
Thus About the role paragraph should include both the role description and the company description? The original had "About The Role" then a paragraph about role, then later "About ZT Systems" paragraph about company. We can combine them into one or two paragraphs under About the role heading. That's acceptable.
We must not repeat job title as heading. Already fine.
Now ensure we didn't include any "Requirements" heading separate from Qualifications; we have Required Qualifications and Preferred Qualifications. That's fine.
Check for any duplicated lines: We removed duplicate base salary from benefits.
Check for any leftover boilerplate: We removed EEO paragraph, "Please be aware that certain positions may require..." etc. Also removed "Learn more about our benefits here." (that's application instruction? maybe not but it's a link; we can drop). Also removed "ZT Group Int’l. is an Equal Opportunity Employer..." etc.
Now produce HTML fragment.
Let's craft the About the role paragraph(s):
Original About The Role paragraph: "We are seeking an entry-level Business Intelligence Data Engineer (T1) to join our BI team. In this role, you will help build and maintain data pipelines that move information from manufacturing and business systems into reporting tools. You will assist in tracking end-to-end data lineage, supporting data validation checks, and maintaining documentation for SOX compliance. This role serves as a functional connector between IT and internal business teams to support reliable reporting across the company."
Then later About ZT Systems paragraph: "At ZT Systems, a Sanmina Company, you’ll get to do work you are proud of alongside smart, passionate people. Every day, there are opportunities to collaborate with the best in the industry to design, build, and deliver impactful solutions to world-class customers. Along the way, you will gain hands-on experience in a fast-paced environment that’s challenging, rewarding, and career-defining. A culture built around our values we work hard and think fast. We view challenges as opportunities—to do better, push harder, and be faster than we were the day before. When we fail, we learn from it and move on together. And when we succeed, we use the momentum to go even further. We create value with everything we do, building the foundation of today—and transforming the future of tomorrow. Join ZT Systems and help us build technology infrastructure that connects the world."
We can combine into two paragraphs under About the role.
Now Responsibilities bullets: list each from "Key Responsibilities". Let's extract:
- Design, build, and maintain data pipelines that move and transform data from source systems (e.g., ERP, MES, supply chain, finance) into reporting-ready datasets.
- Document and maintain data lineage from source systems through transformations to dashboards and reports.
- Ensure the accuracy, consistency, and usability of key business metrics, including validation checks and reconciliation.
- Build and maintain SOX-compliant data processes, including change management, access controls, audit trails, and documentation.
- Work closely with IT, Finance, Operations, Supply Chain, and other departments to understand business processes and translate them into reliable data solutions.
- Act as a bridge between technical and business teams, clarifying data definitions and resolving data quality issues.
- Manage work through Jira and follow version-control best practices in Git.
Now Required Qualifications bullets:
- Bachelor's degree in Computer Science, Information Systems, Engineering, or a related field, or equivalent experience.
- 1-2 years of experience in data engineering, BI, or a related role.
- Proficiency in writing foundational Python scripts and using pandas for data manipulation.
- Strong baseline SQL skills (joining tables, writing aggregations, subqueries, and standard transformations).
- Familiarity with version control using Git and task tracking via Jira.
- Understanding of basic data modeling concepts, data lineage, and data quality assurance methods.
- Strong written and verbal communication skills with an eagerness to collaborate across business functions.
Preferred Qualifications bullets:
- Familiarity with manufacturing, supply chain, or inventory accounting workflows.
- Exposure to ERP environments (e.g., SAP, Oracle, Microsoft Dynamics).
- Hands-on experience with visualization tools such as Power BI or Tableau.
- General awareness of SOX compliance, internal controls, or audit preparation requirements.
Now Pay paragraph: as above.
Benefits list: we enumerated.
Now ensure we didn't include any "Skills" section; we have qualifications covering skills.
Now output HTML.
Check for any stray text like "ZT Systems, a Sanmina Company, assesses market data to ensure a competitive compensation package is created for all our employees." That's part of Pay section? Actually that sentence appears before salary range. We should incorporate that into Pay paragraph maybe. The sentence: "ZT Systems, a Sanmina Company, assesses market data to ensure a competitive compensation package is created for all our employees. The typical base salary for this position is expected to be between $60,750 and $81,000 annually. If hired, the final base salary will be determined on an individual basis taking into consideration experience, skills, knowledge, education, and/or certifications. Base salary is just one component of ZT Systems total rewards philosophy. We take pride in offering a wide range of benefits and perks that appeal to the variety of needs across our diverse employee base. Other rewards may include bonus, paid time off, 401(k) retirement savings plan, tuition reimbursement, wellbeing resources, and more."
We already captured base salary range and mention of bonus, PTO, 401k, tuition reimbursement, wellbeing resources etc. Some of those are in benefits list. The sentence about base salary being one component and wide range of benefits is somewhat covered by benefits list. We can incorporate a short sentence in Pay section: "ZT Systems assesses market data to ensure a competitive compensation package; base salary is one component of its total rewards philosophy." Then benefits list covers rest.
We should not duplicate content already in benefits. So we can include that sentence in Pay paragraph.
Thus Pay paragraph: "ZT Systems, a Sanmina Company, assesses market data to ensure a competitive compensation package is created for all employees. The typical base salary for this position is expected to be between $60,750 and $81,000 annually. Final base salary will be determined individually based on experience, skills, knowledge, education, and/or certifications. Base salary is one component of ZT Systems
for prose. Do not repeat job title as heading (already shown). Do not put Job ID/requisition numbers as headings. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Preserve all substantive info. We need sections: About the role (maybe heading "About the role") with paragraph(s). Then Responsibilities (list). Then Required Qualifications (list). Then Preferred Qualifications (list). Then Pay (since posting states typical base salary range). Then Benefits (since posting lists benefits). Possibly Schedule? Not present. So we omit Schedule. We must not create sections with filler like "commensurate with experience". Pay section: we have salary range. Provide that. Benefits: list from "What We Offer" section. Need to capture all benefits listed: Competitive base salary (but that's already pay), Performance-based annual bonus eligibility, 401(k) retirement savings plan, Tuition reimbursement for eligible education programs, Health & Wellness: Comprehensive medical, dental, and vision coverage with access to leading providers, Mental health resources and employee wellness support programs, Company-paid life and disability insurance, Time Away & Work-Life Balance: Paid time off (PTO) and company-paid holidays, Parental leave and family care support programs, Growth & Purpose: Structured training programs and on-the-job learning opportunities, Matching gifts and volunteer programs to support causes you care about. Also note "These benefits are available to eligible employees and are designed to grow with you as your career evolves. Full benefits and eligibility varies by work location." Might include that as prose. We need to avoid duplication: "Competitive base salary" appears also in Pay section; we could still include in benefits but maybe avoid duplication? The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should keep it, but could be in both sections; but duplication is okay? They said remove duplicated lines. That refers to duplicated lines in the posting. The posting has "Competitive base salary" both in Pay and Benefits. It's duplicated in the source; we should remove duplicated lines. So we should include it only once, perhaps in Pay section, and not repeat in Benefits. But we need to preserve all substantive info; if we remove duplicate, we still have the info (in Pay). That's fine. Thus Benefits section will list other benefits excluding base salary. Now we need to format. Structure:
About the role
... paragraph(s) from About The Role.
Then Responsibilities:Responsibilities
- ... each bullet from Key Responsibilities.
Required Qualifications
- ... each bullet.
Preferred Qualifications
- ... each bullet.
Pay
The typical base salary for this position is expected to be between $60,750 and $81,000 annually. Final base salary will be determined individually based on experience, skills, knowledge, education, and/or certifications.
Benefits:Benefits
- Performance-based annual bonus eligibility
- 401(k) retirement savings plan
- Tuition reimbursement for eligible education programs
- Comprehensive medical, dental, and vision coverage with access to leading providers
- Mental health resources and employee wellness support programs
- 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 to support causes you care about
These benefits are available to eligible employees and are designed to grow with you as your career evolves. Full benefits and eligibility varies by work location.
We need to ensure we didn't include any boilerplate like EEO, etc. Also removed "About ZT Systems" and "What We Offer" headings? We used Benefits section to capture the substance. The "About ZT Systems" paragraph is descriptive about company culture; is that substantive? It might be considered boilerplate? It's not EEO/legal; it's about company values. Should we keep? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About ZT Systems" paragraph is not boilerplate; it's about company culture. Should we include? Possibly as part of About the role? But we already have About the role section. Could add another paragraph after About the role describing company. However the instruction: Prefer a few substantive sections over many thin ones. Could incorporate that into About the role paragraph. But we already have About the role paragraph from the initial "About The Role". We could add another paragraph describing ZT Systems culture as part of About the role or maybe a separate section like "About the company". But they said use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They didn't list "About the company". So better to incorporate that description into About the role paragraph. Thus About the role paragraph should include both the role description and the company description? The original had "About The Role" then a paragraph about role, then later "About ZT Systems" paragraph about company. We can combine them into one or two paragraphs under About the role heading. That's acceptable. We must not repeat job title as heading. Already fine. Now ensure we didn't include any "Requirements" heading separate from Qualifications; we have Required Qualifications and Preferred Qualifications. That's fine. Check for any duplicated lines: We removed duplicate base salary from benefits. Check for any leftover boilerplate: We removed EEO paragraph, "Please be aware that certain positions may require..." etc. Also removed "Learn more about our benefits here." (that's application instruction? maybe not but it's a link; we can drop). Also removed "ZT Group Int’l. is an Equal Opportunity Employer..." etc. Now produce HTML fragment. Let's craft the About the role paragraph(s): Original About The Role paragraph: "We are seeking an entry-level Business Intelligence Data Engineer (T1) to join our BI team. In this role, you will help build and maintain data pipelines that move information from manufacturing and business systems into reporting tools. You will assist in tracking end-to-end data lineage, supporting data validation checks, and maintaining documentation for SOX compliance. This role serves as a functional connector between IT and internal business teams to support reliable reporting across the company." Then later About ZT Systems paragraph: "At ZT Systems, a Sanmina Company, you’ll get to do work you are proud of alongside smart, passionate people. Every day, there are opportunities to collaborate with the best in the industry to design, build, and deliver impactful solutions to world-class customers. Along the way, you will gain hands-on experience in a fast-paced environment that’s challenging, rewarding, and career-defining. A culture built around our values we work hard and think fast. We view challenges as opportunities—to do better, push harder, and be faster than we were the day before. When we fail, we learn from it and move on together. And when we succeed, we use the momentum to go even further. We create value with everything we do, building the foundation of today—and transforming the future of tomorrow. Join ZT Systems and help us build technology infrastructure that connects the world." We can combine into two paragraphs under About the role. Now Responsibilities bullets: list each from "Key Responsibilities". Let's extract: - Design, build, and maintain data pipelines that move and transform data from source systems (e.g., ERP, MES, supply chain, finance) into reporting-ready datasets. - Document and maintain data lineage from source systems through transformations to dashboards and reports. - Ensure the accuracy, consistency, and usability of key business metrics, including validation checks and reconciliation. - Build and maintain SOX-compliant data processes, including change management, access controls, audit trails, and documentation. - Work closely with IT, Finance, Operations, Supply Chain, and other departments to understand business processes and translate them into reliable data solutions. - Act as a bridge between technical and business teams, clarifying data definitions and resolving data quality issues. - Manage work through Jira and follow version-control best practices in Git. Now Required Qualifications bullets: - Bachelor's degree in Computer Science, Information Systems, Engineering, or a related field, or equivalent experience. - 1-2 years of experience in data engineering, BI, or a related role. - Proficiency in writing foundational Python scripts and using pandas for data manipulation. - Strong baseline SQL skills (joining tables, writing aggregations, subqueries, and standard transformations). - Familiarity with version control using Git and task tracking via Jira. - Understanding of basic data modeling concepts, data lineage, and data quality assurance methods. - Strong written and verbal communication skills with an eagerness to collaborate across business functions. Preferred Qualifications bullets: - Familiarity with manufacturing, supply chain, or inventory accounting workflows. - Exposure to ERP environments (e.g., SAP, Oracle, Microsoft Dynamics). - Hands-on experience with visualization tools such as Power BI or Tableau. - General awareness of SOX compliance, internal controls, or audit preparation requirements. Now Pay paragraph: as above. Benefits list: we enumerated. Now ensure we didn't include any "Skills" section; we have qualifications covering skills. Now output HTML. Check for any stray text like "ZT Systems, a Sanmina Company, assesses market data to ensure a competitive compensation package is created for all our employees." That's part of Pay section? Actually that sentence appears before salary range. We should incorporate that into Pay paragraph maybe. The sentence: "ZT Systems, a Sanmina Company, assesses market data to ensure a competitive compensation package is created for all our employees. The typical base salary for this position is expected to be between $60,750 and $81,000 annually. If hired, the final base salary will be determined on an individual basis taking into consideration experience, skills, knowledge, education, and/or certifications. Base salary is just one component of ZT Systems total rewards philosophy. We take pride in offering a wide range of benefits and perks that appeal to the variety of needs across our diverse employee base. Other rewards may include bonus, paid time off, 401(k) retirement savings plan, tuition reimbursement, wellbeing resources, and more." We already captured base salary range and mention of bonus, PTO, 401k, tuition reimbursement, wellbeing resources etc. Some of those are in benefits list. The sentence about base salary being one component and wide range of benefits is somewhat covered by benefits list. We can incorporate a short sentence in Pay section: "ZT Systems assesses market data to ensure a competitive compensation package; base salary is one component of its total rewards philosophy." Then benefits list covers rest. We should not duplicate content already in benefits. So we can include that sentence in Pay paragraph. Thus Pay paragraph: "ZT Systems, a Sanmina Company, assesses market data to ensure a competitive compensation package is created for all employees. The typical base salary for this position is expected to be between $60,750 and $81,000 annually. Final base salary will be determined individually based on experience, skills, knowledge, education, and/or certifications. Base salary is one component of ZT Systems