Systems Engineer II
Shamrock Trading Corporation · Overland Park, KS · 1 mo ago
On-siteInformation 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. We must not repeat job title. No Job ID etc. Remove boilerplate. We need to parse the posting.
Content:
- About Shamrock Trading Corporation (company description) – maybe not needed as a section? The instruction: Use inside
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include sections only if posting has real specific content for them. The posting includes "About The Role" (a paragraph). It includes "What You’ll Do" (responsibilities). It includes "What You’ll Bring" (requirements/qualifications/skills). It includes "What Will Set You Apart" (preferred qualifications). It includes "Benefits" (list). No explicit Pay or Schedule. So we should not include Pay or Schedule sections. We need to map content: - About the role: The paragraph under "About The Role": "Shamrock is looking for a Systems Engineer II with the ability and drive to maintain both on-premises and public cloud systems infrastructure components. The ideal candidate will have an automation-first mindset, strong customer service skills, the capability to learn new skills quickly, and the ability to work across other areas as needed. The ability to handle change and the propensity for knowledge gathering and sharing is necessary." We can put that in
. - Responsibilities: Under "What You’ll Do": list of bullet points. We need to convert each bullet to
- . The bullet points:
Serves as an escalation point for Support Services to resolve Systems tickets in Jira.
Assist the team in deploying and proactively maintaining cloud, on-premises systems and related technologies using Infrastructure-as-Code principles to ensure maximum uptime and security.
Perform troubleshooting to resolve escalated technical issues of affected equipment.
Work effectively with other teams within the Technology department and 3rd party vendors.
Take part in technical project planning and ensure milestones/tasks are completed on time.
Provide peer review for change requests ensuring they meet our technical standards.
Efficiently prioritize triage issues; perform root cause analysis.
Take the initiative to improve our operations and stay educated on the latest relevant technologies.
Implement automations to improve engineer and end-user efficiency.
Consistently follow organizational policies, such as access, change, incident, and problem management.
Take part in the development of technical processes and documentation.
Participate in an on-call rotation and be onsite as needed.
We'll put each as
- .
- Requirements/Qualifications/Skills: The posting has "What You’ll Bring" which includes many items: degree, years experience, etc. Also "What Will Set You Apart" includes preferred qualifications. We need to decide how to split into sections: Requirements, Qualifications, Skills. The instruction says use those headings if there is real specific content. We can distribute.
We could treat "What You’ll Bring" as Requirements (mandatory). "What Will Set You Apart" as Qualifications (preferred) or Skills. But we also have Skills maybe separate.
Better: Use Requirements for the mandatory items (degree, years experience). Use Qualifications for the preferred items (Nutanix, Terraform, Git). Use Skills for technical skills like PowerShell, etc. However the posting lumps many skills in "What You’ll Bring". We could split: Requirements: BA/BS degree, 3+ years Windows Server, 3+ years AD, 3+ years production datacenter, 1+ years AWS, 1+ years Linux, proven production experience with VMWare patching/administration, proven production experience with systems monitoring solutions, ability to automate via PowerShell, ability to communicate clearly, passion for technology, initiative, analytical skills, strong people skills, self-motivated, able to respond quickly on-call, willing to work outside core area.
Qualifications: Production experience with Nutanix, Experience with Infrastructure-as-Code (Terraform), Experience with Git.
Skills: maybe we could list specific technical skills: PowerShell, Windows Server, Active Directory, AWS, Linux, VMWare, monitoring solutions, etc. But that duplicates.
Given instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section? But we have headings list; we can include only those with content. Could do Requirements (mandatory) and Qualifications (preferred) and Skills (maybe not needed). But we need to avoid thin sections.
We could make:
- Requirements (mandatory)
- Qualifications (preferred)
- Skills (maybe we can list specific technical abilities like PowerShell, communication, etc.) but that may be thin.
Alternatively, we could combine Requirements and Qualifications into a single "Requirements" section, and then have a "Skills" section for soft skills like communication, people skills, initiative. But the posting includes those in "What You’ll Bring". Might be okay.
Let's think: The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't require us to use all; we include only those with real specific content.
Thus we can have:
About the role
...
Responsibilities
- ...
Requirements
- ...
Qualifications
- ...
Skills
- ...
for section headings (e.g. About the role, Responsibilities...). It didn't say we cannot have other content outside those headings. But to be safe, we could include a
with the company overview before the sections. It's substantive information; we must preserve all substantive information. So we should include it. But we must not repeat the job title as a heading. The job title is Systems Engineer II. Not included. We must not put Job ID/requisition numbers as headings — none present. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes "Apply Today! We’re so excited to connect with you! If you want to work with forward-thinking people in an award-winning culture, submit your application today. Having trouble submitting your application? Contact us at Recruiting@shamrocktradingcorp.com for support." That's application instructions; we should remove that. Also "Why You’ll Love Working Here" is part of company overview; we can keep as part of description. Now we need to format Benefits: The posting lists: Benefits At Shamrock, we hire bright, ambitious people and give them the tools they need for a successful, long-term career here. Shamrock also offers a premier set of benefits for employees and their families: Training and Development: Ongoing training and professional development opportunities Medical: Fully paid healthcare, dental and vision premiums for employees and eligible dependents, and gym benefits Financial: Generous company 401(k) contributions and employee stock ownership after one year Work-Life Balance: Competitive PTO and fully paid time off opportunities to volunteer within your community We need to turn that into a
- list. Each line after colon is a benefit description. Could treat each bullet as a line.
Thus:
- Training and Development: Ongoing training and professional development opportunities
- Medical: Fully paid healthcare, dental and vision premiums for employees and eligible dependents, and gym benefits
- Financial: Generous company 401(k) contributions and employee stock ownership after one year
- Work-Life Balance: Competitive PTO and fully paid time off opportunities to volunteer within your community
- list. Each line after colon is a benefit description. Could treat each bullet as a line.
Thus: