Senior Linux Platform Engineer
TEKsystems · Burlington, NJ · 1 mo ago
Hybrid$115k–$150k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We have description with many details. We need to parse.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove sections like "About TEKsystems", "San Francisco Fair Chance Ordinance", etc. Those are boilerplate.
We need to preserve all substantive information. So we need to extract:
- Description: The Senior Linux Platform Engineer is responsible for ... (the first paragraph). That's about the role.
- Then "A Day in the Life" with subsections: Linux Platform Engineering, Automation, and Lifecycle Management; Production Reliability, Observability, and Operations Engineering; Security, Compliance, and Governance; Virtualization, Cloud, Storage, Backup, and Modernization; Technical Leadership, Managed Services Coordination, Standards, and Documentation.
These are responsibilities.
- Then "You'll Come With": qualifications (education, experience). That's requirements/qualifications.
- Then "Skills": deep Linux expertise etc. That's skills.
- Then "Additional Skills & Qualifications Using Terraform today Experience Level Expert Level Job Type & Location This is a Permanent position based out of Burlington, NJ." That's location and job type.
- Then "Pay And Benefits": pay range and list of benefits.
- Then "Workplace Type": hybrid position in Burlington,NJ.
- Then "Application Deadline": anticipated to close on Sep 18, 2026. That's schedule? Actually schedule maybe not; but we have schedule section only if posting actually states schedule (like shift, hours). Not present. So we should not include Schedule section.
- Also we have "About TEKsystems" etc which is boilerplate; remove.
- Also "San Francisco Fair Chance Ordinance", etc remove.
- Also "Use of Artificial Intelligence (AI)" remove.
Thus sections we will include:
- About the role (maybe combine first paragraph and maybe "A Day in the Life" intro? Actually "A Day in the Life" is responsibilities. So About the role could be the first paragraph describing role.
- Responsibilities: combine the bullet-like paragraphs under each subheading. We'll need to produce
- for each duty. We'll need to extract each duty as list items.
- Requirements: maybe combine education and experience from "You'll Come With". Could be Requirements.
- Qualifications: maybe separate? The instruction says use headings for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need both Requirements and Qualifications sections. We have "You'll Come With" includes education, experience, etc. Could split: Requirements = mandatory experience/education; Qualifications = maybe additional? But we have only one block. Could treat Requirements as the list of mandatory qualifications (education, years experience, etc.) and Qualifications as maybe the skills? But we already have Skills section. Hmm.
We could assign:
- Requirements: education and years experience, core experience (RHEL/SUSE, troubleshooting, automation tools, virtualization, observability, storage, security compliance, project leadership, communication, offshore coordination, mentoring). That's a lot.
- Qualifications: maybe "Deep Linux expertise, Automation, server deployments, patching, fleet management, ansible playbooks, terraform, Troubleshooting, suse, rhel, azure, devops, cloud" plus "Additional Skills & Qualifications Using Terraform today Experience Level Expert Level". Actually that seems like skills.
Better: Use Requirements for the mandatory qualifications (education, experience). Use Qualifications for the "Skills" list? But we already have Skills heading. The instruction says we can have Skills section. So we need both Requirements and Qualifications distinct.
We could treat:
- Requirements: education (Bachelor’s degree ... or equivalent experience), 10+ years hands-on Linux engineering, strong experience with RHEL/SUSE, strong Linux troubleshooting skills, experience with automation tools, understanding of vSphere, experience with observability tools, working knowledge of networking, experience with storage/backup, experience supporting security hardening, ability to lead technical projects, strong communication skills, experience with managed services/offshore, experience mentoring junior engineers, experience holding resources accountable.
- Qualifications: maybe "Deep Linux expertise, Automation, server deployments, patching, fleet management, ansible playbooks, terraform, Troubleshooting, suse, rhel, azure, devops, cloud" plus "Using Terraform today Experience Level Expert Level". But that seems overlapping with Skills.
Alternatively, we could treat Qualifications as the "Skills" list and Skills as maybe the "Additional Skills & Qualifications". But that seems redundant.
Given the instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So they expect those headings. We need to decide content for each. We have substantive content for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. No Schedule. We need to split the "You'll Come With" into Requirements and Qualifications. Perhaps Requirements = the bullet list of mandatory qualifications (education, years experience, etc.) and Qualifications = the "Skills" list (deep Linux expertise, automation, etc.) and Skills = maybe the "Additional Skills & Qualifications" (Using Terraform today Experience Level Expert Level). But that seems weird. Better: Let's treat: - Requirements: education and years experience, core experience (RHEL/SUSE, troubleshooting, automation, virtualization, observability, storage, security, project leadership, communication, offshore, mentoring). That's a long list. - Qualifications: maybe "Deep Linux expertise, Automation, server deployments, patching, fleet management, ansible playbooks, terraform, Troubleshooting, suse, rhel, azure, devops, cloud". That's a skill set. - Skills: maybe "Additional Skills & Qualifications Using Terraform today Experience Level Expert Level". But that's not really skills; it's more about expertise level. Alternatively, we could combine Qualifications and Skills into one, but we need both headings. Could make Qualifications empty? Not allowed: must not emit heading followed by filler/placeholder text. So we need real content for each. Thus we need to derive distinct content for Qualifications and Skills from the text. Look at the text: After "You'll Come With" we have: "Bachelor’s degree in Computer Science, Information Technology, Engineering, or equivalent experience. 10+ years of hands-on Linux engineering, systems engineering, DevOps, or platform engineering experience in enterprise production environments. Strong experience with RHEL and/or SUSE Linux in mission-critical environments. Strong Linux troubleshooting skills across OS, kernel, storage, networking, authentication, services, performance, and application dependencies. Experience with automation and configuration management tools such as Ansible, Terraform, Puppet, Bash, Python, Git, and CI/CD tooling. Strong understanding of vSphere or similar virtualization platforms, compute, server hardware, firmware, and lifecycle management. Experience with observability, monitoring, logging, alerting, and operational health tools such as Datadog, Dynatrace, Nagios, SolarWinds, New Relic, or similar. Working knowledge of TCP/IP, DNS, DHCP, NTP, LDAP/Active Directory integration, VPN, routing, firewall dependencies, and load-balancing concepts. Experience with enterprise storage and backup technologies, including SAN, NAS, RAID, NFS, CIFS, Veeam, NetBackup, Rubrik, or similar. Experience supporting security hardening, vulnerability remediation, access controls, auditing, and compliance requirements such as SOX and PCI-DSS. Ability to lead technical projects independently, develop implementation plans, communicate risks, execute changes, and drive issues to closure. Strong communication skills with technical and non-technical stakeholders. Demonstrated experience working with managed services providers, including offshore technical delivery teams. Experience directing, coordinating, and overseeing offshore or external engineering resources to ensure alignment with service levels, operational standards, quality expectations, business priorities and cross-time-zone collaboration. Hands-on experience leading and mentoring junior engineers or administrators, including providing technical guidance, work prioritization, and day-to-day direction. Experience holding internal and external technical resources accountable through clear expectations, performance feedback, defined processes, and governance." Then after that: "Skills Deep Linux expertise, Automation, server deployments, patching, fleet management, ansible playbooks, terraform, Troubleshooting, suse, rhel, azure, devops, cloud Top Skills Details Deep Linux expertise, Automation,server deployments, patching, fleet management, ansible playbooks, terraform, Troubleshooting Additional Skills & Qualifications Using Terraform today Experience Level Expert Level Job Type & Location This is a Permanent position based out of Burlington, NJ." So the "Skills" section appears to list: Deep Linux expertise, Automation, server deployments, patching, fleet management, ansible playbooks, terraform, Troubleshooting, suse, rhel, azure, devops, cloud. Then "Additional Skills & Qualifications Using Terraform today Experience Level Expert Level". That seems like additional qualification: expertise level expert, using Terraform today. Thus we can map: - Requirements: the long list of mandatory qualifications (education, experience, etc.) - Qualifications: the "Skills" list (Deep Linux expertise, Automation, server deployments, patching, fleet management, ansible playbooks, terraform, Troubleshooting, suse, rhel, azure, devops, cloud) - Skills: the "Additional Skills & Qualifications" (Using Terraform today, Experience Level Expert Level). But that seems thin. However we could also include "Expert Level" as skill level. But maybe better: Qualifications = the "Skills" list, Skills = the "Additional Skills & Qualifications". That gives us content for both. Check if "Additional Skills & Qualifications Using Terraform today Experience Level Expert Level" is substantive: It says "Using Terraform today Experience Level Expert Level". That's not much but still specific: they want Terraform experience and expert level. Could be considered substantive. Thus we will output:
About the role
...first paragraph...
Responsibilities
- ...each duty from A Day in the Life...
Requirements
- ...each item from You'll Come With list...
Qualifications
- Deep Linux expertise
- Automation
- Server deployments
- Patching
- Fleet management
- Ansible playbooks
- Terraform
- Troubleshooting
- SUSE
- RHEL
- Azure
- DevOps
- Cloud
Skills
- Using Terraform today
- Experience Level: Expert
Benefits
- 401K
- Medical Insurance
- Dental Insurance
- Vision Insurance
- Life Insurance
- Disability Insurance
- Pet Insurance
- Associate Assistance Programs
- Tuition Reimbursement
- Parental Leave
Pay
The pay range for this position is $115000.00 - $150000.00/yr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors.
We should not include Schedule. We also need to include Workplace Type