Product Support Engineer II
SEI · Oaks, PA · 2 wk ago
Information TechnologyFull-time
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. The posting includes description of role (What You Will Do) -> Responsibilities. Also "What We Need From You" -> Requirements/Qualifications. "What We Would Like From You" -> maybe Skills or Preferred Qualifications. Benefits described. No explicit Pay or Schedule. So we should not include Pay or Schedule sections. Also maybe include "About the role" as a heading summarizing the first paragraph? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role (intro paragraph), Responsibilities (list of duties), Requirements (maybe mandatory), Qualifications (maybe education?), Skills (preferred), Benefits. But we must not create sections with filler. We need to decide mapping.
We have content:
Intro paragraph: "As an Automation Engineer II, you will be a member of the Site Reliability Engineering (SRE) team and play a key role in designing, developing, and maintaining automation solutions that support enterprise infrastructure and operational capabilities. Working closely with infrastructure, application, security, and operations teams, you will help streamline processes, improve system reliability, and reduce manual effort across Linux and Windows environments. This role requires strong technical troubleshooting skills, hands-on systems administration experience, and a passion for identifying opportunities to automate and optimize technology operations."
That could be About the role.
Responsibilities: bullet list from "What You Will Do". Each line starts with a verb. We'll make
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role (intro paragraph), Responsibilities (list of duties), Requirements (maybe mandatory), Qualifications (maybe education?), Skills (preferred), Benefits. But we must not create sections with filler. We need to decide mapping.
We have content:
Intro paragraph: "As an Automation Engineer II, you will be a member of the Site Reliability Engineering (SRE) team and play a key role in designing, developing, and maintaining automation solutions that support enterprise infrastructure and operational capabilities. Working closely with infrastructure, application, security, and operations teams, you will help streamline processes, improve system reliability, and reduce manual effort across Linux and Windows environments. This role requires strong technical troubleshooting skills, hands-on systems administration experience, and a passion for identifying opportunities to automate and optimize technology operations."
That could be About the role.
Responsibilities: bullet list from "What You Will Do". Each line starts with a verb. We'll make - .
Requirements: "What We Need From You" includes BA/BS degree, 3 years experience, strong experience supporting/admin Linux and Windows, experience developing automation solutions using listed tools, strong understanding of middleware, web and container technology, troubleshooting, infrastructure concepts, experience automating infrastructure provisioning, system power user tasks, deployments, monitoring, operational workflows, familiarity with configuration management, IaC, modern automation practices, demonstrated ability to analyze processes and identify automation opportunities, strong troubleshooting, analytical, documentation, problem-solving skills, ability to work independently while collaborating across cross-functional teams.
We could split Requirements (mandatory) and Qualifications (preferred). But the instruction says we can have both Requirements and Qualifications sections. We need to decide what goes where. Usually Requirements = mandatory, Qualifications = preferred. However "What We Would Like From You" is clearly preferred qualifications. So we can map:
- Requirements: BA/BS degree, 3 years experience, strong experience supporting/admin Linux and Windows, experience developing automation solutions using Python, PowerShell, Bash, Ansible, Terraform, Jenkins, or similar, strong understanding of middleware, web and container technology, troubleshooting, infrastructure concepts, experience automating infrastructure provisioning, system power user tasks, deployments, monitoring, operational workflows, familiarity with configuration management, IaC, modern automation practices, demonstrated ability to analyze existing processes and identify opportunities for automation and optimization, strong troubleshooting, analytical, documentation, and problem-solving skills, ability to work independently while collaborating effectively across cross-functional technical teams.
- Qualifications (maybe "Preferred Qualifications"): Experience supporting large-scale enterprise infrastructure environments, exposure to cloud platforms, container technologies, modern DevOps practices, experience with monitoring, observability, operational tooling, familiarity with CI/CD pipelines and automated deployment frameworks, strong project coordination and organizational skills, excellent verbal and written communication skills, team player and self-starter with continuous improvement mindset, demonstrated ability to prioritize and manage multiple initiatives in fast-paced environment, strong interpersonal skills with ability to collaborate and influence stakeholders across various levels, ability to maintain confidentiality and follow established security and operational standards, someone who will embody SEI Values.
But we also have Skills section maybe for technical skills? However we already covered skills in Requirements. Could create Skills section for specific tools: Python, PowerShell, Bash, Ansible, Terraform, Jenkins, Linux, Windows, etc. But we already have them in Requirements. To avoid duplication, maybe we combine.
The instruction: "Prefer a few substantive sections over many thin ones." So we could have About the role, Responsibilities, Requirements, Benefits. Possibly Skills as part of Requirements. But we have a distinct "What We Would Like From You" which is preferred qualifications; we could treat as Qualifications section.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits.
We must not include Pay or Schedule.
Now we need to format:
About the role
then ...
. Then Responsibilities
then - ... each duty.
. Then Requirements
then - ... each requirement.
. Then Qualifications
then - ... each preferred.
. Then Benefits
then - ... each benefit.
.
We must preserve all substantive information, not invent or summarize away detail. Must not omit any detail. So we need to include each bullet point exactly as in posting, but we can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the substance, but we can format as list items; we can keep the same wording. Should we keep the exact sentences? Probably yes.
We need to ensure we don't lose any detail. Let's extract each piece.
First, About the role paragraph: exactly as given.
Responsibilities: list from "What You Will Do". Let's copy each line:
- Design, develop, implement, and maintain automation solutions supporting enterprise Linux and Windows environments.
- Develop and maintain automation scripts, workflows, and orchestration processes using tools such as Python, PowerShell, Bash, Ansible, Terraform, Jenkins, and related technologies.
- Perform hands-on administration, configuration, monitoring, troubleshooting, and maintenance of Linux and Windows operating systems.
- Support infrastructure, application, and operational teams by automating deployment, provisioning, configuration management, and operational processes.
- Collaborate with engineering, security, and support teams to ensure automation solutions align with enterprise standards and best practices.
- Develop implementation plans, test plans, operational procedures, and technical documentation to support automation initiatives.
- Participate in testing, deployment, troubleshooting, and continuous improvement activities for automation solutions and supporting infrastructure.
- Support change management, release management, and operational readiness activities for automation solutions.
- Promote automation best practices, operational excellence, and continuous improvement across the technology organization.
- Work collaboratively and effectively with internal subject matter experts (SMEs), stakeholders, and technology teams to deliver scalable and reliable automation capabilities.
That's 10 bullets.
Now Requirements: from "What We Need From You". Let's list each sentence as bullet.
- BA/BS degree in Computer Science, Information Technology, Engineering, or equivalent work experience.
- A minimum of 3 years of hands-on experience in Linux, automation engineering, scripting, web technology solutions and support, or a related technical field.
- Strong experience supporting and administering Linux and Windows operating systems in enterprise environments.
- Experience developing automation solutions using Python, PowerShell, Bash, Ansible, Terraform, Jenkins, or similar automation technologies.
- Strong understanding of middleware, web and container technology, troubleshooting, and infrastructure concepts.
- Experience automating infrastructure provisioning, system power user tasks, deployments, monitoring, and operational workflows.
- Familiarity with configuration management, infrastructure-as-code, and modern automation practices.
- Demonstrated ability to analyze existing processes and identify opportunities for automation and optimization.
- Strong troubleshooting, analytical, documentation, and problem-solving skills.
- Ability to work independently while collaborating effectively across cross-functional technical teams.
That's 10 bullets.
Now Qualifications (preferred): from "What We Would Like From You". Let's list each bullet.
- Experience supporting large-scale enterprise infrastructure environments.
- Exposure to cloud platforms, container technologies, and modern DevOps practices.
- Experience with monitoring, observability, and operational tooling.
- Familiarity with CI/CD pipelines and automated deployment frameworks.
- Strong project coordination and organizational skills.
- Excellent verbal and written communication skills.
- A team player and self-starter with a continuous improvement mindset.
- Demonstrated ability to prioritize and manage multiple initiatives in a fast-paced environment.
- Strong interpersonal skills with the ability to collaborate and influence stakeholders across various levels of the organization.
- Ability to maintain confidentiality and follow established security and operational standards.
- Someone who will embody our SEI Values of courage, integrity, collaboration, inclusion, connection, and fun.
That's 11 bullets.
Now Benefits: from paragraph after "Please see our website for more information." Actually after that there is "SEI’s Competitive Advantage To help you stay energized, engaged and inspired, we offer a wide range of benefits including comprehensive care for your physical and mental well-being, a strong retirement plan, tuition reimbursement, support for working parents and flexible Paid Time Off (PTO) so you can relax, recharge and be there for the people you care about. Benefits include healthcare (medical, dental, vision, prescription, wellness, EAP, FSA), life and disability insurance (premiums paid for base coverage), 401(k) match, education assistance, commuter benefits, up to 11 paid holidays/year, 21 days PTO/year pro-rated for new hires which increases over time, paid parental leave, back-up childcare arrangements, paid volunteer days, a discounted stock purchase plan, investment options, access to thriving employee networks and more."
We need to capture all benefits as list items. Let's break down:
- comprehensive care for your physical and mental well-being
- a strong retirement plan
- tuition reimbursement
- support for working parents
- flexible Paid Time Off (PTO) so you can relax, recharge and be there for the people you care about
- healthcare (medical, dental, vision, prescription, wellness, EAP, FSA)
- life and disability insurance (premiums paid for base coverage)
- 401(k) match
- education assistance
- commuter benefits
- up to 11 paid holidays/year
- 21 days PTO/year pro-rated for new hires which increases over time
- paid parental leave
- back-up childcare arrangements
- paid volunteer days
- a discounted stock purchase plan
- investment options
- access to thriving employee networks and more
Also later: "We offer our employees paid parental leave, back-up childcare arrangements, paid volunteer days, education assistance and access to thriving employee networks." That's duplicate but we should not duplicate? The instruction: "Remove duplicated lines". So we should avoid repeating same benefit. We'll keep unique.
Thus benefits list includes those unique items.
Now we need to output HTML fragment only, no extra text.
Let's craft.
Be careful to escape any HTML special characters? The text includes parentheses, ampersand? Not many. We have "&" in "EAP"? Actually "EAP" is fine. No &.
We'll output:
About the role
As an Automation Engineer II, you will be a member of the Site Reliability Engineering (SRE) team and play a key role in designing, developing, and maintaining automation solutions that support enterprise infrastructure and operational capabilities. Working closely with infrastructure, application, security, and operations teams, you will help streamline processes, improve system reliability, and reduce manual effort across Linux and Windows environments. This role requires strong technical troubleshooting skills, hands-on systems administration experience, and a passion for identifying opportunities to automate and optimize technology operations.
Responsibilities
- Design, develop, implement, and maintain automation solutions supporting enterprise Linux and Windows environments.
- Develop and maintain automation scripts, workflows, and orchestration processes using tools such as Python, PowerShell, Bash, Ansible, Terraform, Jenkins, and related technologies.
- Perform hands-on administration, configuration, monitoring, troubleshooting, and maintenance of Linux and Windows operating systems.
About the role
then...
. ThenResponsibilities
then- ... each duty.
Requirements
then- ... each requirement.
Qualifications
then- ... each preferred.
Benefits
then- ... each benefit.
About the role
As an Automation Engineer II, you will be a member of the Site Reliability Engineering (SRE) team and play a key role in designing, developing, and maintaining automation solutions that support enterprise infrastructure and operational capabilities. Working closely with infrastructure, application, security, and operations teams, you will help streamline processes, improve system reliability, and reduce manual effort across Linux and Windows environments. This role requires strong technical troubleshooting skills, hands-on systems administration experience, and a passion for identifying opportunities to automate and optimize technology operations.
Responsibilities
- Design, develop, implement, and maintain automation solutions supporting enterprise Linux and Windows environments.
- Develop and maintain automation scripts, workflows, and orchestration processes using tools such as Python, PowerShell, Bash, Ansible, Terraform, Jenkins, and related technologies.
- Perform hands-on administration, configuration, monitoring, troubleshooting, and maintenance of Linux and Windows operating systems.