Specialist, IT Solutions 1

We need to output only HTML fragment, no html/body tags. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content. Let's parse the posting. We have: - Summary: "The Specialist, IT Solutions will engage with site business functions to identify and advocate business process improvement opportunities through the use of IT solutions. Collect, analyze, develop, document and communicate business requirements, and work with various IT teams to develop and deliver solutions. Provide support and user training on selected systems (for example SFC, ERP and local applications). Participate in IT projects in various capacities, including project coordination and management." That's about the role. Could be "About the role" or "Responsibilities". The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings. We have a "Detailed Description" with bullet-like list: "Performs tasks such as, but not limited to, the following: Engage with community to explore opportunities for the use of IT solutions Gather and document business requirements Work with various IT teams to develop and deliver IT solutions Respond to system problems by analyzing the issue and determining the next course of action Provide system training to end users Participate in and lead various IT projects as required" That's responsibilities/duties. Then "Knowledge/Skills/Competencies" list: many items. Then "Physical Demands": description. Then "Typical Experience": 4 to 6 years; Experience in similar roles "Typical Education": Bachelor Degree or consideration of an equivalent combination of education and experience. Educational Requirements may vary by Geography Then "Notes": generic. Then "Company Overview": description of Celestica. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove the EEO statement, notes about equal opportunity, company overview? The company overview might be considered not boilerplate but maybe we keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Company overview is not necessarily boilerplate but could be considered generic marketing. However, it's substantive info about the company. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep company overview unless it's considered boilerplate. It's not EEO or legal; it's a description of the company. Likely we keep it. We also need to not repeat the job title as a heading (the page already shows it). So we don't put a heading for "Specialist, IT Solutions". Also do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a short paragraph with Req ID, Region, Country, State/Province, City maybe. We need to decide sections. Potential sections: - About the role (maybe from Summary) - Responsibilities (from Detailed Description) - Knowledge/Skills/Competencies (maybe split into Skills and Qualifications) - Experience and Education (maybe Qualifications) - Physical Demands (maybe not a standard heading; but we could include as a section? Not in list of allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Physical Demands is not listed; we could either omit or incorporate into something else? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, not exclusive? But later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't restrict to only those headings, but suggests those as typical. However, to be safe, we could map Physical Demands under "Requirements" or "Qualifications". But it's not exactly a requirement; it's about physical demands. Could be part of "Requirements". We'll include a

under Requirements. Similarly, Typical Experience and Education could go under "Qualifications". Or we could have separate "Experience" and "Education" headings but not in list; better to put under Qualifications. We have no explicit Benefits, Pay, Schedule info. So we should NOT create those sections. Thus sections: About the role, Responsibilities, Skills, Qualifications (maybe combine Knowledge/Skills/Competencies and Experience/Education). Could also split Skills and Qualifications. Let's decide: - About the role: summary paragraph. - Responsibilities: detailed description list. - Skills: Knowledge/Skills/Competencies list (maybe split into technical skills and soft skills). We'll just list as

. - Qualifications: Typical Experience, Typical Education, Physical Demands (maybe as a note). Also maybe include "Knowledge of programming languages" etc but that's skill. We need to avoid duplication. Ensure we preserve all substantive information. Let's extract details. Summary paragraph: "The Specialist, IT Solutions will engage with site business functions to identify and advocate business process improvement opportunities through the use of IT solutions. Collect, analyze, develop, document and communicate business requirements, and work with various IT teams to develop and deliver solutions. Provide support and user training on selected systems (for example SFC, ERP and local applications). Participate in IT projects in various capacities, including project coordination and management." We'll put that as

under About the role. Detailed Description list: - Engage with community to explore opportunities for the use of IT solutions - Gather and document business requirements - Work with various IT teams to develop and deliver IT solutions - Respond to system problems by analyzing the issue and determining the next course of action - Provide system training to end users - Participate in and lead various IT projects as required We'll output as

• ...
under Responsibilities. Knowledge/Skills/Competencies list (the bullet list after that heading). Let's extract each item: - Knowledge of programming languages (C++, Java, etc.). - Strong customer service orientation - Leadership and teamwork skills. - Good ability to plan projects and tasks. - Project management skills. - Good analytical, technical, troubleshooting and problem solving skills. - Good communication, documentation (including flow charting) and presentation skills. - Understanding of an electronic manufacturing environment, materials and processes. - Understanding of SCM, shop floor control and ERP applications. - Solid knowledge of the business area to be supported and a solid understanding of its associated business processes. - Strong understanding of software development life cycle concepts and practices. - Knowledge/experience with application-to-application and business-to-business integration. - Basic to good coding skills in specified programming languages. - Understanding of interrelations between IT components (software, OS, databases, network, servers, etc.) We'll put these as
under Skills. Physical Demands: "Duties of this position are performed in a normal office environment.Duties may require extended periods of sitting and sustained visual concentration on a computer monitor or on numbers and other detailed data. Repetitive manual movements (e.g., data entry, using a computer mouse, using a calculator, etc.) are frequently required." We'll put as

under Qualifications (or maybe a separate section but we can incorporate). Typical Experience: "4 to 6 years; Experience in similar roles" Typical Education: "Bachelor Degree or consideration of an equivalent combination of education and experience. Educational Requirements may vary by Geography" We'll combine these as

under Qualifications. We also have metadata: Req ID: 141148 Region: Americas Country: USA State/Province: Texas City: Richardson We can put a short

at top: "Req ID: 141148 | Region: Americas | Country: USA | State/Province: Texas | City: Richardson" We must not put Job ID as heading. We must remove boilerplate: EEO statements, Notes, Company Overview? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company Overview is not explicitly listed as boilerplate, but it's a generic marketing paragraph. However, it's substantive info about the company. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it unless it's considered boilerplate. I'd keep it. But we need to check if any duplicated lines: The summary and detailed description have overlapping content; we should not duplicate. We'll keep summary as About the role, and detailed description as Responsibilities (which includes some similar points but more detailed). That's fine. Now, we need to output only HTML fragment, no /, no markdown fences. Thus output something like:

Req ID: 141148 | Region: Americas | Country: USA | State/Province: Texas | City: Richardson

About the role

The Specialist, IT Solutions will engage with site business functions to identify and advocate business process improvement opportunities through the use of IT solutions. Collect, analyze, develop, document and communicate business requirements, and work with various IT teams to develop and deliver solutions. Provide support and user training on selected systems (for example SFC, ERP and local applications). Participate in IT projects in various capacities, including project coordination and management.

Responsibilities

• Engage with community to explore opportunities for the use of IT solutions
• Gather and document business requirements
• Work with various IT teams to develop and deliver IT solutions
• Respond to system problems by analyzing the issue and determining the next course of action
• Provide system training to end users
• Participate in and lead various IT projects as required

Skills

• Knowledge of programming languages (C++, Java, etc.)
• Strong customer service orientation
• Leadership and teamwork skills
• Good ability to plan projects and tasks
• Project management skills
• Good analytical, technical, troubleshooting and problem solving skills
• Good communication, documentation (including flow charting) and presentation skills
• Understanding of an electronic manufacturing environment, materials and processes
• Understanding of SCM, shop floor control and ERP applications
• Solid knowledge of the business area to be supported and a solid understanding of its associated business processes
• Strong understanding of software development life cycle concepts and practices
• Knowledge/experience with application-to-application and business-to-business integration
• Basic to good coding skills in specified programming languages
• Understanding of interrelations between IT components (software, OS, databases, network, servers, etc.)

Qualifications

Typical Experience: 4 to 6 years; Experience in similar roles

Typical Education: Bachelor Degree or consideration of an equivalent combination of education and experience. Educational Requirements may vary by Geography

Physical Demands: Duties of this position are performed in a normal office environment. Duties may require extended periods of sitting and sustained visual concentration on a computer monitor or on numbers and other detailed data. Repetitive manual movements (e.g., data entry, using a computer mouse, using a calculator, etc.) are frequently required.

Company Overview

Celestica (NYSE, TSX: CLS) enables the world's best brands. Through our recognized customer-centric approach, we partner with leading companies in Aerospace