Systems Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID. Remove boilerplate. We need to parse the job description. Content: - Summary: "GE Vernova is looking for a Systems Platform Engineer to work on exciting projects with high business impact. The role will involve working as part of a global team towards design & development of server platform products for renewable energy domain and contributes to design discussions, immediate team and to other teams across business." That's about the role. - Roles and Responsibilities: list of bullet points. - Basic Qualifications: list. - Desired Characteristics: list. - Business Acumen: list. - Additional Information: includes benefits, pay range, etc. We need to map to sections: About the role (summary), Responsibilities (Roles and Responsibilities), Requirements (maybe Basic Qualifications?), Qualifications (maybe Desired Characteristics?), Skills (maybe technical skills?), Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have pay info: "For candidates applying to a U.S. based position, the pay range for this position is between $80,000.00 and $120,000.00. The Company pays a geographic differential of 110%, 120% or 130% of salary in certain areas. The specific pay offered may be influenced by a variety of factors, including the candidate’s experience, education, and skill set. Bonus eligibility: discretionary annual bonus." Thus Pay section. Schedule: Not mentioned. No schedule info. So we should NOT include Schedule section. Benefits: "Available benefits include medical, dental, vision, and prescription drug coverage; access to Health Coach from GE Vernova, a 24/7 nurse-based resource; and access to the Employee Assistance Program, providing 24/7 confidential assessment, counseling and referral services. Retirement benefits include the GE Vernova Retirement Savings Plan, a tax-advantaged 401(k) savings opportunity with company matching contributions and company retirement contributions, as well as access to Fidelity resources and financial planning consultants. Other benefits include tuition assistance, adoption assistance, paid parental leave, disability benefits, life insurance, 12 paid holidays, and permissive time off." Thus Benefits section. Now we need to decide about sections: About the role (summary). Responsibilities (list). Requirements (maybe Basic Qualifications). Qualifications (maybe Desired Characteristics). Skills (maybe technical skills like PowerShell, Linux bash, etc). But we need to avoid duplication. The instructions: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can choose which to include. We need to preserve all substantive information. So we need to include all info from the posting, but we can group logically. We could have: - About the role (summary paragraph) - Responsibilities (ul list) - Requirements (Basic Qualifications) - Qualifications (Desired Characteristics + Business Acumen maybe) - Skills (maybe technical skills like PowerShell, Linux bash, VMware, Hyper-V, etc) but those are already in qualifications. Might be redundant. Perhaps we can combine Requirements and Qualifications into one? But instructions say prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements (covering Basic Qualifications, Desired Characteristics, Business Acumen), Benefits, Pay. Skills maybe not needed separately if covered in Requirements. But we need to include all substantive info: technical skills like PowerShell, Linux bash, VMware, Hyper-V, Microsoft Windows Server, Linux, relational databases, etc. Those are in Basic Qualifications. So we can include them there. Desired Characteristics and Business Acumen are more about soft skills/architecture. Could be part of Requirements or Qualifications. We could have sections: About the role, Responsibilities, Requirements (including Basic Qualifications, Desired Characteristics, Business Acumen), Benefits, Pay. That seems reasonable. We must not include sections with filler like "commensurate with experience". Not present. Now we need to format lists:

• for any list of duties/requirements/benefits. We need to preserve all substantive info; do not invent or summarize away detail. We need to be careful to not lose any detail. Let's extract details. About the role paragraph: "GE Vernova is looking for a Systems Platform Engineer to work on exciting projects with high business impact. The role will involve working as part of a global team towards design & development of server platform products for renewable energy domain and contributes to design discussions, immediate team and to other teams across business." We'll put that in

  . Responsibilities: list from "Roles and Responsibilities". Let's extract each bullet: - Focus on critical evaluation, selection and validation of the software and hardware components of the server infrastructure. - Influence and create new designs, architectures, standards and methods for server infrastructure. - Apply principles of Lean/Agile and Product Security, Scalability, Documentation Practices and Testing Techniques. - Work with fellow team members to diagnose bugs and formulate solutions. - Provide expertise in the quality engineering, test planning and testing methodology for server platform projects. - Experience in writing PowerShell code that meets standards and delivers desired functionality. - Provide hands-on technical leadership in design and support of VMware, Hyper-V, Microsoft and Linux servers. - Demonstrates the initiative to explore alternate technology and approaches to solving problems. - Promotes transparency by proactively sharing design choices with appropriate audiences, with the appropriate level of detail and timeliness. - Provide hands-on leadership in release of subcomponents of Systems products within product life cycle tool. We need to keep each as

• . Now Requirements: Basic Qualifications list: - Bachelors Degree in Computer Science or in Electronics/ Instrumentation/ Electrical/ Power Systems. - IT Infrastructure knowledge, e.g. Microsoft Technology Associate (MTA) certification. - Clear understanding of Microsoft Windows Server, e.g. Microsoft Certified Solutions Associate (MCSA) certification (recommend). - Clear understanding of IP networks and OSI network model. - Clear understanding of Microsoft Hyper-V and VMware ESXi. - Clear understanding of relational databases like Microsoft SQL Server or PostgreSQL. - Sound knowledge in Microsoft PowerShell and Linux bash. - Good written and verbal communication skills and working in global team environment. Now Desired Characteristics list: - Understands technical and business discussions relative to future architecture direction aligning with business goals - Understands concepts of setting and driving architecture direction - Familiar with elements of gathering architecture requirements - Understands architecture standards concepts to apply to project work - Expertise in designing, analyzing and troubleshooting edge and/or large-scale distributed systems - Experience in working on Linux/Unix, Microsoft Windows and VMware environments. - Experience of working with virtual machines (VMs) as part of a test/validation infrastructure - Knowledge of Microsoft SQL Server/ PostgreSQL and or other SQL/non-SQL databases would be a plus - Minimum of 2 years experience in an enterprise support role ideally with exposure to datacenter or off prem/cloud environments. Business Acumen list: - Demonstrates the initiative to explore alternate technology and approaches to solving problems - Skilled in breaking down problems, documenting problem statements and estimating efforts - Demonstrates awareness about competitors and industry trends - Understand key cross-functional concepts that impact the organization - Is aware of business priorities and organizational dynamics Note some duplicates: "Demonstrates the initiative to explore alternate technology and approaches to solving problems" appears also in Responsibilities. But we keep as is. Now Benefits list: we need to break into items. Benefits paragraph: "Available benefits include medical, dental, vision, and prescription drug coverage; access to Health Coach from GE Vernova, a 24/7 nurse-based resource; and access to the Employee Assistance Program, providing 24/7 confidential assessment, counseling and referral services. Retirement benefits include the GE Vernova Retirement Savings Plan, a tax-advantaged 401(k) savings opportunity with company matching contributions and company retirement contributions, as well as access to Fidelity resources and financial planning consultants. Other benefits include tuition assistance, adoption assistance, paid parental leave, disability benefits, life insurance, 12 paid holidays, and permissive time off." We can split into list items: maybe each benefit category as separate
• . But we need to preserve all detail; we can list each benefit as separate items. Let's enumerate: - Medical coverage - Dental coverage - Vision coverage - Prescription drug coverage - Access to Health Coach from GE Vernova, a 24/7 nurse-based resource - Access to the Employee Assistance Program, providing 24/7 confidential assessment, counseling and referral services - GE Vernova Retirement Savings Plan, a tax-advantaged 401(k) savings opportunity with company matching contributions and company retirement contributions - Access to Fidelity resources and financial planning consultants - Tuition assistance - Adoption assistance - Paid parental leave - Disability benefits - Life insurance - 12 paid holidays - Permissive time off Now Pay section: we need to include pay range and bonus eligibility. Pay info: "For candidates applying to a U.S. based position, the pay range for this position is between $80,000.00 and $120,000.00. The Company pays a geographic differential of 110%, 120% or 130% of salary in certain areas. The specific pay offered may be influenced by a variety of factors, including the candidate’s experience, education, and skill set. Bonus eligibility: discretionary annual bonus." We'll put that in

  maybe with

  for bullet points? It's prose; we can keep as

  . Now we need to ensure we don't include Schedule section. Now we need to output only HTML fragment, no /, no markdown. We'll structure:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Benefits

  • ...
  ...

  Pay

  ...

  We might also include a

  Qualifications

  but we combined into Requirements. The instructions allow us to choose sections; we can omit Qualifications if we covered its content in Requirements. That's okay as long as we preserve all substantive info. We have included Desired Characteristics and Business Acumen in Requirements? We haven't yet added them. We need to add them somewhere. If we only have Requirements for Basic Qualifications, we miss Desired Characteristics and Business Acumen. So we need to include them either in Requirements or a separate Qualifications section. We could have Requirements (Basic Qualifications) and Qualifications (Desired Characteristics + Business Acumen). That would be two sections. That's okay; we prefer few sections but we need to include all info. Having About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay is six sections. That's fine. Let's do that. Thus: - About the role - Responsibilities - Requirements (Basic Qualifications) - Qualifications (Desired Characteristics + Business Acumen) - Benefits - Pay Now we need to ensure we don't repeat content. Let's extract Requirements list (Basic Qualifications) as above. Qualifications list: combine Desired Characteristics and Business Acumen. We need to list each as
  • . Ensure no duplication: "Demonstrates the initiative to explore alternate technology and approaches to solving problems" appears both in Responsibilities and Business Acumen. It's okay to duplicate? The instruction says preserve ALL substantive information; do not invent or summarize away detail. Duplication is present in source; we should preserve it. So we can keep duplicate. Now Benefits list as above. Pay section: we can put as

    with