Senior Linux Infrastructure Engineer
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We need to parse the posting.
We need to extract:
- About the role: description of opportunity, what you'll own, what you'll do? Actually "The Opportunity" and "What You'll Own" and "What You'll Do". Could combine into About the role or separate sections? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to these standard headings. Likely:
- About the role: description of the role, opportunity, what you'll own, what you'll do.
- Responsibilities: maybe "What You'll Do" is responsibilities.
- Requirements: "What We Require".
- Qualifications: maybe education etc.
- Skills: maybe specific technical skills.
- Benefits: "Why Join Northern Light" includes competitive salary, benefits, professional growth opportunities, etc. Also maybe "Working at Northern Light" includes benefits.
- Pay: not specified explicitly; no salary figure. So we should NOT include Pay section because no specific content.
- Schedule: maybe mention Eastern Time working hours, remote, occasional after-hours maintenance, on-site days. That could be schedule info. So we can include Schedule section with those details.
We must not include boilerplate like EEO, legal, etc.
We must preserve all substantive information; do not invent or summarize away detail. Must not repeat job title as heading. Must not put Job ID.
We need to output only HTML fragment, no /, no markdown fences.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We need to decide how to structure content.
Let's extract substantive content:
About Northern Light (company description) maybe not needed for role but could be part of About the role? The instruction: "About the role" heading likely includes description of role and maybe company overview. We'll include a paragraph summarizing Northern Light and the opportunity.
But we must preserve all substantive information; we cannot omit details like "Northern Light provides the world's most sophisticated machine learning-powered competitive intelligence platform..." etc. That's company description; maybe it's part of About the role? Could be included.
We need to decide sections:
- About the role: include company description and opportunity overview.
- Responsibilities: list of duties from "What You'll Do" bullet points.
- Requirements: list from "What We Require".
- Qualifications: maybe education (BS/MS) plus experience? But we already have requirements; maybe Qualifications can include education plus certifications? However we must not create thin sections. If we already have Requirements covering experience and skills, we could combine Qualifications into Requirements? But instruction says prefer few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements, Benefits, Schedule. Possibly Skills could be part of Requirements.
But we need to follow the given headings list as examples, not mandatory. We can choose which to include.
We need to include Benefits section if posting states them: "Why Join Northern Light" includes competitive salary, benefits, professional growth opportunities, own a real production environment, regular team offsites, cross-functional collaboration. Also maybe "Working at Northern Light" includes location info. So we can include Benefits.
Schedule: Eastern Time working hours, remote within 2-3 hour drive, occasional on-site days, after-hours maintenance 3-5 times per year. So we can include Schedule.
Pay: not specified, so omit.
Now we need to ensure we don't repeat content.
Let's extract details:
Company description (About Northern Light):
- Northern Light provides the world's most sophisticated machine learning-powered competitive intelligence platform for market research.
- For over 25 years, helping Fortune 1000 enterprises make smarter, faster, more informed decisions through award-winning SinglePoint knowledge management platform.
- Clients include global leaders across technology, pharmaceuticals, telecommunications, life sciences.
- They transform fragmented data into strategic clarity.
- Pride in compulsive drive to provide exceptional client support.
- Recent innovations: generative AI capabilities, machine learning insights, advanced competitive intelligence automation.
Opportunity:
- Senior Linux Infrastructure Engineer to take hands-on ownership of Linux infrastructure behind platform's compute-heavy backend, runs on own hardware in private colocation cage in Somerville, MA.
- Primary owner of datacenter environment: keep reliable and secure, lead next phase including hardware refresh across fleet and deeper automation.
- On Platform team, own Linux infrastructure, work closely with engineering, security, operations teams, including team that runs customer-facing frontend in AWS.
- Philosophy: buy platforms rather than build them; where supported vendor-backed product exists, run it and follow vendor best practices; automation on top of those platforms is work.
What You'll Own (list):
- Fleet of ~60 HPE ProLiant DL360 Gen9/Gen10 bare-metal servers and ~100 VMs running RHEL-family Linux (currently Oracle Linux 9).
- Virtualization: ~50 VMs on VMware, moving to new platform this year, and a KVM/libvirt environment running remaining ~50 VMs, which serve as Kubernetes nodes managed by DevOps.
- Core infrastructure services: BIND, LDAP, mail relay, SFTP, Foreman.
- Self-hosted applications and database servers product teams depend on: GitLab Self-Managed Premium, MariaDB, PostgreSQL, MongoDB. These are yours at system level; application and DBA-level tuning stay with teams.
- Operational tooling: inventory (NetBox), monitoring (LogicMonitor / Site24x7 / Grafana), vulnerability management (Tenable One), automation hub (Ansible Automation Platform), backups (Veeam).
- Physical environment: six-rack private colo cage in Somerville, MA, including spare-parts inventory and hardware lifecycle tracking.
- Routine network operations: wiring and top-of-rack switch port configuration. Major network reconfiguration and network device patching sit with network engineering partner.
What You'll Do (list):
- Keep fleet current and consistent: patch, harden, upgrade Linux servers on controlled cadence through managed repositories and staged rollouts; install, upgrade, maintain applications and database servers to vendor guidance — largely through Ansible roles and playbooks you write and the Ansible Automation Platform you operate.
- Run vulnerability management cycle: scheduled Tenable scans, triage of findings, remediation prioritization, patching or documented mitigation, compliance reporting that stands up to customer security reviews and audits.
- Own infrastructure backups (policy, platform administration, restore testing) and partner with application team on disaster recovery planning and exercises.
- Keep monitoring and logging reliable and free of noise: complete coverage of fleet, alerts that fire on real problems and not on everything else, log collection you can trust when investigating incident.
- Lead incident response for infrastructure issues, run post-incident reviews, drive corrective actions to closure, keep resulting SOPs, runbooks, and infrastructure diagrams current and clear to technical and non-technical readers.
- Run datacenter as remotely operated facility: accurate NetBox records, labeled cabling, iLO/out-of-band access to everything, spare parts on shelf, clear work orders for remote hands.
- Work with vendors and colo provider on hardware lifecycle and capacity, coordinate scheduled maintenance windows and network changes with network partner.
- Participate in occasional scheduled after-hours maintenance (historically 3–5 times per year).
What We Require (list):
- Substantial production Linux systems engineering experience, typically 7+ years, including several years where you were accountable for reliability and security of environment, whether alone or as senior member of small team.
- BS or MS in Computer Science, Computer Engineering, or Information Technology is a plus, but practical experience matters more.
- Deep RHEL-family Linux skills (RHEL, Oracle Linux, Rocky, Alma, CentOS): systemd, kernel and performance tuning, storage (LVM, RAID, NFS), networking (bonding, VLANs, firewalld/iptables).
- Production experience administering a virtualization platform (VMware vSphere, KVM/libvirt, OpenShift Virtualization, Proxmox, Hyper-V, or similar).
- Hands-on Ansible authoring: written and maintained roles and playbooks, not only run them.
- Experience running a patch and vulnerability management program in production: scheduled scanning with Tenable/Nessus, Qualys, Rapid7, or similar, interpreting results, driving remediation across fleet.
- Experience installing and operating server applications and database servers at system level (packaging, storage, TLS, access control, backups) from vendor documentation, including judgment to plan a database upgrade that can be rolled back and to treat a backup as unproven until restored.
- Experience with enterprise server hardware (HPE ProLiant or equivalent): out-of-band management (iLO/IPMI), firmware, diagnostics, component replacement, comfort doing occasional physical work in datacenter.
- Experience designing or materially improving highly available, redundant infrastructure, and track record of leading incident response and writing useful root-cause analyses.
- Solid networking fundamentals: enough to make routine switch changes yourself, and to diagnose and scope switch, firewall, load-balancer issues well enough to hand them to network engineers.
- Strong documentation habits and clear written and spoken communication.
- Prior experience with specific products named above is a plus but not required; we expect a strong engineer to pick them up here.
Job Details (maybe not needed as heading):
- Job Type: Full-Time
- Location: Remote, within a two- to three-hour drive of Somerville, MA; local candidates especially welcome. Role is home-based, you will come to Somerville office and datacenter for hands-on datacenter projects and for planning and brainstorming sessions with team, typically a couple of consecutive days at a time, every few weeks. Travel for on-site days reimbursed with pre-approval.
- Eastern Time working hours.
- Datacenter work: You decide how much of it you do yourself. Colo offers remote-hands service that can handle routine tasks such as drive and component swaps, cabling, receiving shipments, provided planning, documentation, work orders are in good order. When you do work in cage yourself, expect elevated noise levels and variable temperatures.
- Work authorization requirements: Must be authorized to work in the United States (cannot sponsor visas).
Why Join Northern Light (Benefits):
- Join a company shaping the future of competitive and market intelligence.
- Work with a collaborative, high-performing team that values creativity, experimentation, and measurable results.
- Competitive salary, benefits, and professional growth opportunities.
- Own a real production environment end to end, on supported enterprise platforms with vendor backing.
- Regular team offsites and opportunities for cross-functional collaboration.
Working at Northern Light (maybe location):
- Northern Light is based in the Boston, MA area.
- Northern Light is proud to provide equal employment opportunities... (EEO boilerplate) - we must remove.
- Northern Light SinglePoint, LLC participates in E-Verify... (legal) - remove.
- It is unlawful in Massachusetts to require or administer a lie detector test... (legal) - remove.
We must remove all boilerplate EEO/legal etc.
Now we need to produce HTML with sections.
We'll decide sections:
About the role
- include company description and opportunity overview (maybe combine). Could be a few paragraphs.
Responsibilities
- list of duties from What You'll Do.
Requirements
- list from What We Require.
Benefits
- list from Why Join Northern Light (excluding boilerplate).
Schedule
- details about location, remote, on-site, after-hours, Eastern Time.
We might also include Qualifications? But we have Requirements covering experience and education; could add Qualifications for education plus maybe certifications? But we already have BS/MS as plus in Requirements. Could keep Requirements only.
We must not create thin sections; we have 4 sections with substantive content.
Now
- for any list of duties/requirements/benefits, and
for prose. We need to decide how to structure content. Let's extract substantive content: About Northern Light (company description) maybe not needed for role but could be part of About the role? The instruction: "About the role" heading likely includes description of role and maybe company overview. We'll include a paragraph summarizing Northern Light and the opportunity. But we must preserve all substantive information; we cannot omit details like "Northern Light provides the world's most sophisticated machine learning-powered competitive intelligence platform..." etc. That's company description; maybe it's part of About the role? Could be included. We need to decide sections: - About the role: include company description and opportunity overview. - Responsibilities: list of duties from "What You'll Do" bullet points. - Requirements: list from "What We Require". - Qualifications: maybe education (BS/MS) plus experience? But we already have requirements; maybe Qualifications can include education plus certifications? However we must not create thin sections. If we already have Requirements covering experience and skills, we could combine Qualifications into Requirements? But instruction says prefer few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements, Benefits, Schedule. Possibly Skills could be part of Requirements. But we need to follow the given headings list as examples, not mandatory. We can choose which to include. We need to include Benefits section if posting states them: "Why Join Northern Light" includes competitive salary, benefits, professional growth opportunities, own a real production environment, regular team offsites, cross-functional collaboration. Also maybe "Working at Northern Light" includes location info. So we can include Benefits. Schedule: Eastern Time working hours, remote within 2-3 hour drive, occasional on-site days, after-hours maintenance 3-5 times per year. So we can include Schedule. Pay: not specified, so omit. Now we need to ensure we don't repeat content. Let's extract details: Company description (About Northern Light): - Northern Light provides the world's most sophisticated machine learning-powered competitive intelligence platform for market research. - For over 25 years, helping Fortune 1000 enterprises make smarter, faster, more informed decisions through award-winning SinglePoint knowledge management platform. - Clients include global leaders across technology, pharmaceuticals, telecommunications, life sciences. - They transform fragmented data into strategic clarity. - Pride in compulsive drive to provide exceptional client support. - Recent innovations: generative AI capabilities, machine learning insights, advanced competitive intelligence automation. Opportunity: - Senior Linux Infrastructure Engineer to take hands-on ownership of Linux infrastructure behind platform's compute-heavy backend, runs on own hardware in private colocation cage in Somerville, MA. - Primary owner of datacenter environment: keep reliable and secure, lead next phase including hardware refresh across fleet and deeper automation. - On Platform team, own Linux infrastructure, work closely with engineering, security, operations teams, including team that runs customer-facing frontend in AWS. - Philosophy: buy platforms rather than build them; where supported vendor-backed product exists, run it and follow vendor best practices; automation on top of those platforms is work. What You'll Own (list): - Fleet of ~60 HPE ProLiant DL360 Gen9/Gen10 bare-metal servers and ~100 VMs running RHEL-family Linux (currently Oracle Linux 9). - Virtualization: ~50 VMs on VMware, moving to new platform this year, and a KVM/libvirt environment running remaining ~50 VMs, which serve as Kubernetes nodes managed by DevOps. - Core infrastructure services: BIND, LDAP, mail relay, SFTP, Foreman. - Self-hosted applications and database servers product teams depend on: GitLab Self-Managed Premium, MariaDB, PostgreSQL, MongoDB. These are yours at system level; application and DBA-level tuning stay with teams. - Operational tooling: inventory (NetBox), monitoring (LogicMonitor / Site24x7 / Grafana), vulnerability management (Tenable One), automation hub (Ansible Automation Platform), backups (Veeam). - Physical environment: six-rack private colo cage in Somerville, MA, including spare-parts inventory and hardware lifecycle tracking. - Routine network operations: wiring and top-of-rack switch port configuration. Major network reconfiguration and network device patching sit with network engineering partner. What You'll Do (list): - Keep fleet current and consistent: patch, harden, upgrade Linux servers on controlled cadence through managed repositories and staged rollouts; install, upgrade, maintain applications and database servers to vendor guidance — largely through Ansible roles and playbooks you write and the Ansible Automation Platform you operate. - Run vulnerability management cycle: scheduled Tenable scans, triage of findings, remediation prioritization, patching or documented mitigation, compliance reporting that stands up to customer security reviews and audits. - Own infrastructure backups (policy, platform administration, restore testing) and partner with application team on disaster recovery planning and exercises. - Keep monitoring and logging reliable and free of noise: complete coverage of fleet, alerts that fire on real problems and not on everything else, log collection you can trust when investigating incident. - Lead incident response for infrastructure issues, run post-incident reviews, drive corrective actions to closure, keep resulting SOPs, runbooks, and infrastructure diagrams current and clear to technical and non-technical readers. - Run datacenter as remotely operated facility: accurate NetBox records, labeled cabling, iLO/out-of-band access to everything, spare parts on shelf, clear work orders for remote hands. - Work with vendors and colo provider on hardware lifecycle and capacity, coordinate scheduled maintenance windows and network changes with network partner. - Participate in occasional scheduled after-hours maintenance (historically 3–5 times per year). What We Require (list): - Substantial production Linux systems engineering experience, typically 7+ years, including several years where you were accountable for reliability and security of environment, whether alone or as senior member of small team. - BS or MS in Computer Science, Computer Engineering, or Information Technology is a plus, but practical experience matters more. - Deep RHEL-family Linux skills (RHEL, Oracle Linux, Rocky, Alma, CentOS): systemd, kernel and performance tuning, storage (LVM, RAID, NFS), networking (bonding, VLANs, firewalld/iptables). - Production experience administering a virtualization platform (VMware vSphere, KVM/libvirt, OpenShift Virtualization, Proxmox, Hyper-V, or similar). - Hands-on Ansible authoring: written and maintained roles and playbooks, not only run them. - Experience running a patch and vulnerability management program in production: scheduled scanning with Tenable/Nessus, Qualys, Rapid7, or similar, interpreting results, driving remediation across fleet. - Experience installing and operating server applications and database servers at system level (packaging, storage, TLS, access control, backups) from vendor documentation, including judgment to plan a database upgrade that can be rolled back and to treat a backup as unproven until restored. - Experience with enterprise server hardware (HPE ProLiant or equivalent): out-of-band management (iLO/IPMI), firmware, diagnostics, component replacement, comfort doing occasional physical work in datacenter. - Experience designing or materially improving highly available, redundant infrastructure, and track record of leading incident response and writing useful root-cause analyses. - Solid networking fundamentals: enough to make routine switch changes yourself, and to diagnose and scope switch, firewall, load-balancer issues well enough to hand them to network engineers. - Strong documentation habits and clear written and spoken communication. - Prior experience with specific products named above is a plus but not required; we expect a strong engineer to pick them up here. Job Details (maybe not needed as heading): - Job Type: Full-Time - Location: Remote, within a two- to three-hour drive of Somerville, MA; local candidates especially welcome. Role is home-based, you will come to Somerville office and datacenter for hands-on datacenter projects and for planning and brainstorming sessions with team, typically a couple of consecutive days at a time, every few weeks. Travel for on-site days reimbursed with pre-approval. - Eastern Time working hours. - Datacenter work: You decide how much of it you do yourself. Colo offers remote-hands service that can handle routine tasks such as drive and component swaps, cabling, receiving shipments, provided planning, documentation, work orders are in good order. When you do work in cage yourself, expect elevated noise levels and variable temperatures. - Work authorization requirements: Must be authorized to work in the United States (cannot sponsor visas). Why Join Northern Light (Benefits): - Join a company shaping the future of competitive and market intelligence. - Work with a collaborative, high-performing team that values creativity, experimentation, and measurable results. - Competitive salary, benefits, and professional growth opportunities. - Own a real production environment end to end, on supported enterprise platforms with vendor backing. - Regular team offsites and opportunities for cross-functional collaboration. Working at Northern Light (maybe location): - Northern Light is based in the Boston, MA area. - Northern Light is proud to provide equal employment opportunities... (EEO boilerplate) - we must remove. - Northern Light SinglePoint, LLC participates in E-Verify... (legal) - remove. - It is unlawful in Massachusetts to require or administer a lie detector test... (legal) - remove. We must remove all boilerplate EEO/legal etc. Now we need to produce HTML with sections. We'll decide sections:
About the role
- include company description and opportunity overview (maybe combine). Could be a few paragraphs.Responsibilities
- list of duties from What You'll Do.Requirements
- list from What We Require.Benefits
- list from Why Join Northern Light (excluding boilerplate).Schedule
- details about location, remote, on-site, after-hours, Eastern Time. We might also include Qualifications? But we have Requirements covering experience and education; could add Qualifications for education plus maybe certifications? But we already have BS/MS as plus in Requirements. Could keep Requirements only. We must not create thin sections; we have 4 sections with substantive content. Now