Senior Systems Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: note about immigration sponsorship, certifications category, legal text, etc. Also remove application instructions (none present). Keep substantive info. We need to parse the job description. Let's extract sections: - About the role: The first paragraph after "Job Description The Role The Workplace Investment (WI) Stability Optimization CoE is looking for a utility player...". This is description of role. Could be "About the role". We'll put that in

. - Responsibilities: The bullet list of duties: "In this role the individual will play a vital role in supporting our testing teams across multiple test environments and will be responsible for leading the environment stability in line with the WI COE group’s roadmap and aligning to WI and needs of other business groups within Fidelity. We do this by coordinating the response to environment issues while also supporting our applications in a customer facing test environment and driving to resolution in a customer technical support model." Also later: "Leading the coordination with stakeholders through resolution of the incident. Closely partnering and collaborating with Infrastructure, Engineering, Operations, Squads and Business Leadership to ensure alignment across the business." Also "Capability to partner with Operations and Stakeholders on stability opportunities based upon reporting/trending findings as well as operational readiness". Also "Bring Stability and Efficiencies to WI Squads and Operations to accelerate development life cycle". Also "Guiding resources assigned to the incident and ensures the incident is receiving the accurate support to drive resolution as quickly as possible". Also "An automation mentality to drive platform stability approaches". Also "Streamlining processes, optimizing workflows, introducing new features with positive business impacts". Also "Bring together technical, procedural, and financial data to reduce toil and increase efficiency". Also "You will execute plans for technical standardization and process refinement within the Stability and Automation engineering organization, especially for Operations and Squads." Also "Must bring flawless execution and results in role of organizational navigator and collaborator." Also "Actively learning, sharing insights, industry practices and developments, within your area of expertise". Also "Impactful, with a passion for contributing to continuing enhancement of our engineering capabilities with a focus on excellence". Many of these are more like value delivered. Might be better to separate Responsibilities and Value You Deliver. - Requirements / Qualifications: The list under "The Expertise And Skills You Bring". That includes education, years experience, mainframe dev, business knowledge SPS preferred, monitoring tools, dashboards, incident triage, ITIL, CI/CD, ETL/Java/Python/cloud, Kubernetes, AKS, EKS, Unix scripting, Python, public cloud, analytical, ensuring policies, etc. Many are skills. We need to decide sections: Could have "About the role", "Responsibilities", "Requirements", "Skills", "Value You Deliver". Benefits, Pay, Schedule not present (no specifics). So omit those. We must not create sections with placeholder text. So only include sections with real content. We need to use

• for any list of duties/requirements/benefits. So for responsibilities list, we should make
  • . For requirements list, also
    • . For skills maybe also list. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include each bullet point as a list item, preserving the exact phrasing? We can keep the sentences as they appear, but we need to break them into list items. The original text is paragraph style with many statements separated by periods. We need to convert to list items. Must not lose any detail. We need to be careful not to duplicate content. Also we need to remove boilerplate like "Note: Fidelity will not provide immigration sponsorship for this position." That's a note but maybe considered minor metadata; we can drop it. Also "Certifications Category: Information Technology" and legal paragraphs about SEC etc. Remove. Also "Fidelity’s Onsite Working Model" paragraph: that's substantive? It describes onsite expectations. Could be considered relevant but maybe not a section heading; we could include as a paragraph under About the role or separate? It's about work model. The instructions: we can include a short

      for minor metadata. This is not a heading like Benefits etc. So we could include it as a paragraph under About the role or separate

      without heading. But we must not create a heading unless there is real specific content for a section heading like About the role, Responsibilities, etc. The onsite model could be part of About the role or maybe a separate section like "Work Model". But the allowed headings list does not include Work Model; only those specified. So we should not create a heading for it. Instead we can incorporate that info into a paragraph under About the role or maybe as a

      after the role description. Similarly "The Team" paragraph about WI QE Center of Excellence: that's substantive. Could be included under About the role or as a separate section? Not in allowed headings. So we can incorporate as paragraph. We need to output only HTML fragment, no /, no markdown. Let's structure:

      About the role

      ... (combining initial role description, the team description, onsite working model maybe)

      Responsibilities

      • ... each responsibility sentence

      Requirements

      • ... each requirement bullet
      Maybe also

      Skills

      but many requirements overlap with skills. Could combine Requirements and Skills into one section? The instruction: Prefer a few substantive sections over many thin ones. So we could have just Requirements covering education, experience, technical skills, etc. That's fine. We also have "The Value You Deliver" section which is like impact/outcomes. Could be a separate section but maybe we can incorporate into Responsibilities? However it's distinct: "Bring Stability and Efficiencies..." etc. Could be a section "Value You Deliver". Allowed heading includes "Skills" but not "Value". However we could treat it as part of Responsibilities or maybe as a separate section using

      but not in allowed list? The instruction says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list? It says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should not create a heading like "Value You Deliver". Instead we could incorporate those points into Responsibilities or maybe as a

      under About the role. But they are substantive; we need to preserve them. Could add them as list items under Responsibilities (makes sense as they are outcomes/deliverables). So we can include them in Responsibilities list. Thus Responsibilities will include both duties and value delivered. Now we need to extract each distinct statement. Let's copy the text and break. Original paragraphs: "The Role The Workplace Investment (WI) Stability Optimization CoE is looking for a utility player with strong communication, highly customer obsessed, proven engineering and multiple years production support experience. In this role the individual will play a vital role in supporting our testing teams across multiple test environments and will be responsible for leading the environment stability in line with the WI COE group’s roadmap and aligning to WI and needs of other business groups within Fidelity. We do this by coordinating the response to environment issues while also supporting our applications in a customer facing test environment and driving to resolution in a customer technical support model. Note: Fidelity will not provide immigration sponsorship for this position." "The Expertise And Skills You Bring A Bachelor’s or master’s degree in Computer Science, Software engineering or related fieldAt least 6 years of experience working in sophisticated production environment, on-Prem and CloudConfirmed experience of mainframe development/tools including COBOL, CICS, db2, JCL, VSAM, MQ, etc. and writing COBOL/Native stored procedures.Having business knowledge of Stock Plan Services(SPS) is preferredExperience with monitoring/observability tools such as CloudWatch, Datadog/Splunk, ELK stack.Strong experience of creating dashboards in Datadog and SplunkShould have experience in coordinating and triaging incidents within the managed environments, with ITIL practice knowledge to support the day-to-day operationsKnowledge of CI/CD pipelines stacks like Github, Jenkins, Maven, Docker, Artifactory, Kubernetes, uDeployKnowledge of ETL, Java, Python, or other Distributed Technologies, including experience in Cloud platform such as AWS and/or AzureStrong Experience with Kubernetes, AKS and, EKSHands-on Experience in Unix scripting, Python, or related programming languagesHands-on Experience with Public Cloud environments, preferably AWS and Azure.Analytical and detail orientated thought process with the ability to take methodical approach to activities such as data analysis and stability trending.Ensuring all agreed to operational policies and procedures are adhered to.Leading the coordination with stakeholders through resolution of the incident. Closely partnering and collaborating with Infrastructure, Engineering, Operations, Squads and Business Leadership to ensure alignment across the business.Capability to partner with Operations and Stakeholders on stability opportunities based upon reporting/trending findings as well as operational readinessAbility to quickly learn new concepts and technologies to support day to day operationsCustomer orientated personality exhibiting professionalism and enthusiasmDemonstrate ability to form trusted working relationships with business unit stakeholders through collaboration and enhanced effective communicationsDeeply self-motivated with the ability to work independently, coordinating activities within cross-regional and multi-functional teamsAble to mentor team members in areas where you have domain expertise and able to coordinate with partners onStrong self-starting, analytical, communication, and critical thinking skills" "The Value You Deliver Bring Stability and Efficiencies to WI Squads and Operations to accelerate development life cycleGuiding resources assigned to the incident and ensures the incident is receiving the accurate support to drive resolution as quickly as possibleAn automation mentality to drive platform stability approachesStreamlining processes, optimizing workflows, introducing new features with positive business impactsBring together technical, procedural, and financial data to reduce toil and increase efficiencyYou will execute plans for technical standardization and process refinement within the Stability and Automation engineering organization, especially for Operations and Squads.Must bring flawless execution and results in role of organizational navigator and collaborator.Actively learning, sharing insights, industry practices and developments, within your area of expertiseImpactful, with a passion for contributing to continuing enhancement of our engineering capabilities with a focus on excellence" "The Team The WI QE Center of Excellence (COE) is passionate about driving WI organizational’ s technological innovation initiatives and improvements which accelerates the squad, operational efficiencies and improve the customer experience. The mission of the COE is engineering excellence across the WI business with focus areas on engineering effectiveness, engineering measurement and maturity, engineering innovation and engineering culture and craft. Stability is our top priority!" "Fidelity’s Onsite Working Model Fidelity is transitioning to a full-time onsite working model through a phased rollout across regions and roles. Currently, some roles and locations require 100% onsite presence, while others require less. Onsite expectations are likely to evolve as the rollout continues. This transition does not apply to fully remote roles." "Certifications Category: Information Technology Please be advised that Fidelity’s business is governed by the provisions of the Securities Exchange Act of 1934, the Investment Advisers Act of 1940, the Investment Company Act of 1940, ERISA, numerous state laws governing securities, investment and retirement-related financial activities and the rules and regulations of numerous self-regulatory organizations, including FINRA, among others. Those laws and regulations may restrict Fidelity from hiring and/or associating with individuals with certain Criminal Histories." We need to drop the note about immigration sponsorship, certifications category, legal paragraphs. Now we need to construct About the role paragraph: combine the initial role