AI/ML Engineer
About the role
with. Responsibilities: maybe we can extract duties: "develop scalable ML solutions, automate training and deployment workflows, and support production AI infrastructure." Also maybe "work closely with software engineers, data scientists, and platform engineers". That's more about collaboration. We'll put as
- .
Requirements: Minimum Requirements list: Bachelor's degree, 2–5+ years experience, Strong programming skills in Python including FastAPI, async, and production-grade code, Good understanding of ML fundamentals, Familiarity with ML frameworks such as PyTorch, TensorFlow, or scikit-learn, Experience working with Linux environments, Basic experience with Docker and containerized applications, Working knowledge of Kubernetes fundamentals (deployments, services, pods, jobs), Understanding of version control using Git, Strong problem-solving skills and ability to work in a collaborative engineering environment.
We'll put as
- .
Qualifications: Preferred Qualifications list: Familiarity with LLMs and prompt engineering, Experience building RAG pipelines end-to-end (chunking, embedding, retrieval, reranking), Experience with LLM serving frameworks such as vLLM or Ollama, Knowledge of vector databases such as Qdrant, Some frontend experience with TypeScript and Next.js, Experience with Orchestration tools such as Kubeflow, Kuberay etc.
We'll put as
- .
Skills: Might be overlapping; but we could separate technical skills vs soft skills? However we already have many skill-like items in Requirements and Qualifications. The instruction says prefer a few substantive sections over many thin ones. Could combine Requirements and Qualifications into one? But they ask to use headings for those specific ones if content exists. We have content for Requirements and Qualifications, so we should include both. Skills maybe we could include a summary of soft skills: "Strong problem-solving skills and ability to work in a collaborative engineering environment" but that's already in Requirements. Could still include Skills section with items like "Problem solving, collaboration, communication". But we risk duplication/inventing. Better to omit Skills if not distinct content. The instruction: "Prefer a few substantive sections over many thin ones." So we could omit Skills if it would be thin. However we have content for Skills maybe we can extract from the description: "Strong programming skills in Python including FastAPI, async, and production-grade code" etc. But those are already in Requirements. So we can skip Skills.
Benefits: we have content.
Pay: we have salary range.
Schedule: none, omit.
Thus final HTML:
About the role
...
Responsibilities
- ...
Requirements
- ...
Qualifications
- ...
Benefits
- ...
Pay
...
Make sure to not include any boilerplate like EEO, etc. Also remove duplicated lines. Ensure we preserve all substantive info. Let's extract benefits precisely as listed: From "Compensation & Financial Security Competitive base salaryPerformance-based annual bonus eligibility401(k) retirement savings planTuition 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 holidaysParental leave and family care support programs Growth & Purpose Structured training programs and on-the-job learning opportunitiesMatching gifts and volunteer programs to support causes you care about" We need to format as list items. Might need to split into sensible items: - Competitive base salary - 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 We'll output as- ... ...
. Now ensure we didn't include any boilerplate like "ZT Systems assesses market data to ensure a competitive compensation package is created for all our employees." That's part of Pay section? Actually that sentence is before salary range. It's substantive about compensation philosophy. Could include in Pay section as well. But we might incorporate it. The instruction: preserve ALL substantive information. So we should include that sentence too. Let's include in Pay section: "ZT Systems 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 $105,000 and $154,000 per year. If hired, the final base salary will be determined on an individual basis taking into consideration experience, skills, knowledge, education and/or certifications." Now Benefits: we also have sentence: "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, 401k, tuition reimbursement, wellbeing resources, and more." That's also substantive. Should we include that in Benefits section? Yes, we can include as introductory paragraph before list. But we must not repeat info. We'll include a
summarizing that, then the list. Now About the role: we have the paragraph. Also there is a line: "About ZT Systems 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." That's also substantive about company. Should we include that? It's under "About ZT Systems". Could be part of About the role or maybe a separate section but we only have defined headings. Could include in About the role as additional paragraph. The instruction: "About the role" heading for section headings (e.g. About the role, Responsibilities...). So we can put all descriptive content under About the role. That includes the initial role description and the company description. That's fine. Now Responsibilities: we have "You will work closely with software engineers, data scientists, and platform engineers to develop scalable ML solutions, automate training and deployment workflows, and support production AI infrastructure." That's the main responsibility. Could also include "help build, deploy, and operate AI applications." That's from first sentence. We'll include both. Now Requirements: we have list. Now Qualifications: we have list. Now Benefits: we have intro paragraph and list. Now Pay: we have paragraph. Now ensure we didn't include any boilerplate like "We are dedicated to building a diverse, inclusive, and authentic workplace, so if you’re excited about this opportunity but your experience doesn’t align perfectly with every qualification in the job description, we encourage you to apply anyway. You may be just the right candidate for this or other roles." That's encouraging to apply; it's somewhat boilerplate but it's substantive? It's generic encouragement. Might be considered boilerplate but it's not legal/EEO. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This encouragement to apply is not exactly legal; it's more motivational. Might be considered application instruction? It's encouraging to apply. Might be considered application instruction. Safer to remove it. Also remove "Learn more about our benefits here." That's a link instruction; remove. Also remove "Full benefits and eligibility varies by work location." That's generic but maybe substantive? It's about benefits variability. Could keep? It's not specific detail. Might be considered filler. Safer to remove. Also remove "ZT Group Int’l. is an Equal Opportunity Employer..." etc. That's EEO boilerplate; remove. Also remove
- .
Skills: Might be overlapping; but we could separate technical skills vs soft skills? However we already have many skill-like items in Requirements and Qualifications. The instruction says prefer a few substantive sections over many thin ones. Could combine Requirements and Qualifications into one? But they ask to use headings for those specific ones if content exists. We have content for Requirements and Qualifications, so we should include both. Skills maybe we could include a summary of soft skills: "Strong problem-solving skills and ability to work in a collaborative engineering environment" but that's already in Requirements. Could still include Skills section with items like "Problem solving, collaboration, communication". But we risk duplication/inventing. Better to omit Skills if not distinct content. The instruction: "Prefer a few substantive sections over many thin ones." So we could omit Skills if it would be thin. However we have content for Skills maybe we can extract from the description: "Strong programming skills in Python including FastAPI, async, and production-grade code" etc. But those are already in Requirements. So we can skip Skills.
Benefits: we have content.
Pay: we have salary range.
Schedule: none, omit.
Thus final HTML:
- .
Qualifications: Preferred Qualifications list: Familiarity with LLMs and prompt engineering, Experience building RAG pipelines end-to-end (chunking, embedding, retrieval, reranking), Experience with LLM serving frameworks such as vLLM or Ollama, Knowledge of vector databases such as Qdrant, Some frontend experience with TypeScript and Next.js, Experience with Orchestration tools such as Kubeflow, Kuberay etc.
We'll put as