Senior Software Engineer - Tooling & Automation
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. The posting includes: Who We Are (company description) maybe not needed as heading? The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to include sections: About the role (maybe from "Who We Are"? Actually "Who We Are" is company description; but they said use About the role heading for section headings. Could treat "Who We Are" as About the role? The posting includes "Who We Are" describing Vultr. That's substantive. So we can have
About the role
with that description. Responsibilities: there is a list under "Key Responsibilities". Use- .
Qualifications: there is a "Qualifications" section with bullet points. Use
- .
Skills: maybe not separate; but we could combine qualifications and skills? The instruction says we can have Skills section if there is real specific content. The posting includes qualifications that list skills; we could put them under Qualifications. But we could also create Skills section for things like scripting ability, dashboard building, etc. However we should avoid thin sections. Probably better to have Qualifications section covering the bullet list. Skills maybe not needed.
Benefits: The posting includes a list of benefits under "Vultr Cares" etc. So we should have Benefits section with those details.
Pay: The posting includes "Compensation $125,000 - $135,000". So we need Pay section.
Schedule: Not mentioned. No schedule info. So we should NOT create Schedule section.
We must not include boilerplate like Inclusion & Privacy etc. Remove that.
We also need to preserve all substantive information: company description, responsibilities, qualifications, benefits, pay.
We need to format as HTML fragment: use
headings,
for prose,
- for lists.
We need to ensure we don't repeat job title. Not needed.
We need to drop minor metadata like Job ID etc. Not present.
We need to ensure we don't include placeholder text like "commensurate with experience". Not present.
We need to include the compensation range exactly as given.
Let's extract content:
Who We Are: "Vultr is on a mission to make high-performance cloud infrastructure easy to use, affordable, and locally accessible for enterprises and AI innovators around the world. With 33 global cloud data center locations, Vultr is trusted by hundreds of thousands of active customers across 185 countries for its flexible, scalable, global Cloud Compute, Cloud GPU, Bare Metal, and Cloud Storage solutions. In December 2024 Vultr announced an equity financing at a $3.5 billion valuation. Founded by David Aninowsky and self-funded for over a decade, Vultr has grown to become the world’s largest privately-held cloud infrastructure company."
Then after that: "Vultr Cares 100% company-paid insurance premiums for employee medical, dental and vision plans. 401(k) plan that matches 100% up to 4%, with immediate vesting Professional Development Reimbursement of $2,500 each year 11 Holidays + Paid Time Off Accrual + Rollover Plan Commitment matters to Vultr! Increased PTO at 3 year and 10 year anniversary + 1 month paid sabbatical every 5 years + Anniversary Bonus each year $500 stipend for remote office setup in first year + $400 each following year Internet reimbursement up to $75 per month Gym membership reimbursement up to $50 per month Company paid Wellable subscription"
We need to format benefits as list.
Responsibilities: list of bullet points under "Key Responsibilities". Let's capture each sentence as a bullet.
- Map every alert source owned by Systems, Network, and Security engineering (Icinga, Grafana, SIEM/Splunk/QRadar/Sentinel, BMC/IPMI, provider-native consoles) and identify the cleanest integration point for each — webhook, syslog forward, API poll, or native connector
- Build and maintain the routing/forwarding layer that pushes agreed top-priority alerts from each pillar into GIOC's ticketing and paging tools, with priority/severity preserved and enough context for L1 triage without direct console access
- Work with each pillar's engineering SMEs to validate that routing logic matches each pillar's defined resolve-vs-escalate boundary
- Own the on-call/notification wiring so critical alerts reach GIOC within agreed acknowledgment SLAs, with no manual relay step
- Design and build a unified operational dashboard spanning all five datacenter/provider platforms (Airtel, Nextra, Equinix, QTS, CoreSite), replacing today's tool-hopping model
- Define dashboard v1 scope jointly with GIOC and pillar leads and ship it on a committed milestone
- Run legacy tools and the new dashboard in parallel during transition so GIOC never loses visibility mid-cutover
- Build in SLA/health visualizations (ack time, escalation accuracy, open-alert aging) that GIOC leadership can use directly in status reporting
- Build correlation engines and integrate all sources of telemetry from various product teams
- Document the routing architecture and dashboard so both can be maintained by GIOC or the Tools team after this assignment ends
Qualifications: bullet list:
- 5–8 years in Tools/Platform Engineering or a similar infrastructure role, including 3–5 years hands-on with monitoring/alerting tooling (Icinga or equivalent NMS, Grafana, and at least one SIEM platform — Splunk, QRadar, or Sentinel)
- Experience rapidly mapping an unfamiliar, multi-team monitoring and alerting estate and consolidating it — ideally at a cloud, hosting, or multi-datacenter operator. Equivalent hands-on Vultr experience is a strong plus.
- 3+ years building integrations against APIs/webhooks, with scripting ability (Python or similar)
- 2–3 years building or substantially modifying operational dashboards (Grafana, Kibana, Power BI, or similar)
- Understanding of ticketing/ITSM workflow tools (Jira, Confluence, Mattermost) and how alert priority/severity maps into ticket fields
- Preferred: prior exposure to multi-provider/datacenter operational environments, and experience supporting or building for a NOC/SOC or similar 24x7 operations function
Pay: "$125,000 - $135,000 Final compensation will vary depending on years of experience, background/skill set, location, and applicable laws."
We need to keep that as prose maybe.
Now produce HTML:
About the role
Vultr is on a mission to make high-performance cloud infrastructure easy to use, affordable, and locally accessible for enterprises and AI innovators around the world. With 33 global cloud data center locations, Vultr is trusted by hundreds of thousands of active customers across 185 countries for its flexible, scalable, global Cloud Compute, Cloud GPU, Bare Metal, and Cloud Storage solutions. In December 2024 Vultr announced an equity financing at a $3.5 billion valuation. Founded by David Aninowsky and self-funded for over a decade, Vultr has grown to become the world’s largest privately-held cloud infrastructure company.
Responsibilities
- Map every alert source owned by Systems, Network, and Security engineering (Icinga, Grafana, SIEM/Splunk/QRadar/Sentinel, BMC/IPMI, provider-native consoles) and identify the cleanest integration point for each — webhook, syslog forward, API poll, or native connector
- Build and maintain the routing/forwarding layer that pushes agreed top-priority alerts from each pillar into GIOC's ticketing and paging tools, with priority/severity preserved and enough context for L1 triage without direct console access
- Work with each pillar's engineering SMEs to validate that routing logic matches each pillar's defined resolve-vs-escalate boundary
- Own the on-call/notification wiring so critical alerts reach GIOC within agreed acknowledgment SLAs, with no manual relay step
- Design and build a unified operational dashboard spanning all five datacenter/provider platforms (Airtel, Nextra, Equinix, QTS, CoreSite), replacing today's tool-hopping model
- Define dashboard v1 scope jointly with GIOC and pillar leads and ship it on a committed milestone
- Run legacy tools and the new dashboard in parallel during transition so GIOC never loses visibility mid-cutover
- Build in SLA/health visualizations (ack time, escalation accuracy, open-alert aging) that GIOC leadership can use directly in status reporting
- Build correlation engines and integrate all sources of telemetry from various product teams
- Document the routing architecture and dashboard so both can be maintained by GIOC or the Tools team after this assignment ends
Qualifications
- 5–8 years in Tools/Platform Engineering or a similar infrastructure role, including 3–5 years hands-on with monitoring/alerting tooling (Icinga or equivalent NMS, Grafana, and at least one SIEM platform — Splunk, QRadar, or Sentinel)
- Experience rapidly mapping an unfamiliar, multi-team monitoring and alerting estate and consolidating it — ideally at a cloud, hosting, or multi-datacenter operator. Equivalent hands-on Vultr experience is a strong plus.
- 3+ years building integrations against APIs/webhooks, with scripting ability (Python or similar)
- 2–3 years building or substantially modifying operational dashboards (Grafana, Kibana, Power BI, or similar)
- Understanding of ticketing/ITSM workflow tools (Jira, Confluence, Mattermost) and how alert priority/severity maps into ticket fields
- Preferred: prior exposure to multi-provider/datacenter operational environments, and experience supporting or building for a NOC/SOC or similar 24x7 operations function
Benefits
- 100% company-paid insurance premiums for employee medical, dental and vision plans
- 401(k) plan that matches 100% up to 4%, with immediate vesting
- Professional Development Reimbursement of $2,500 each year
- 11 Holidays + Paid Time Off Accrual + Rollover Plan
- Increased PTO at 3 year and 10 year anniversary
- 1 month paid sabbatical every 5 years
- Anniversary Bonus each year
- $500 stipend for remote office setup in first year + $400 each following year
- Internet reimbursement up to $75 per month
- Gym membership reimbursement up to $50 per month
- Company paid Wellable subscription
Pay
$1
- for lists.
We need to ensure we don't repeat job title. Not needed.
We need to drop minor metadata like Job ID etc. Not present.
We need to ensure we don't include placeholder text like "commensurate with experience". Not present.
We need to include the compensation range exactly as given.
Let's extract content:
Who We Are: "Vultr is on a mission to make high-performance cloud infrastructure easy to use, affordable, and locally accessible for enterprises and AI innovators around the world. With 33 global cloud data center locations, Vultr is trusted by hundreds of thousands of active customers across 185 countries for its flexible, scalable, global Cloud Compute, Cloud GPU, Bare Metal, and Cloud Storage solutions. In December 2024 Vultr announced an equity financing at a $3.5 billion valuation. Founded by David Aninowsky and self-funded for over a decade, Vultr has grown to become the world’s largest privately-held cloud infrastructure company."
Then after that: "Vultr Cares 100% company-paid insurance premiums for employee medical, dental and vision plans. 401(k) plan that matches 100% up to 4%, with immediate vesting Professional Development Reimbursement of $2,500 each year 11 Holidays + Paid Time Off Accrual + Rollover Plan Commitment matters to Vultr! Increased PTO at 3 year and 10 year anniversary + 1 month paid sabbatical every 5 years + Anniversary Bonus each year $500 stipend for remote office setup in first year + $400 each following year Internet reimbursement up to $75 per month Gym membership reimbursement up to $50 per month Company paid Wellable subscription"
We need to format benefits as list.
Responsibilities: list of bullet points under "Key Responsibilities". Let's capture each sentence as a bullet.
- Map every alert source owned by Systems, Network, and Security engineering (Icinga, Grafana, SIEM/Splunk/QRadar/Sentinel, BMC/IPMI, provider-native consoles) and identify the cleanest integration point for each — webhook, syslog forward, API poll, or native connector
- Build and maintain the routing/forwarding layer that pushes agreed top-priority alerts from each pillar into GIOC's ticketing and paging tools, with priority/severity preserved and enough context for L1 triage without direct console access
- Work with each pillar's engineering SMEs to validate that routing logic matches each pillar's defined resolve-vs-escalate boundary
- Own the on-call/notification wiring so critical alerts reach GIOC within agreed acknowledgment SLAs, with no manual relay step
- Design and build a unified operational dashboard spanning all five datacenter/provider platforms (Airtel, Nextra, Equinix, QTS, CoreSite), replacing today's tool-hopping model
- Define dashboard v1 scope jointly with GIOC and pillar leads and ship it on a committed milestone
- Run legacy tools and the new dashboard in parallel during transition so GIOC never loses visibility mid-cutover
- Build in SLA/health visualizations (ack time, escalation accuracy, open-alert aging) that GIOC leadership can use directly in status reporting
- Build correlation engines and integrate all sources of telemetry from various product teams
- Document the routing architecture and dashboard so both can be maintained by GIOC or the Tools team after this assignment ends
Qualifications: bullet list:
- 5–8 years in Tools/Platform Engineering or a similar infrastructure role, including 3–5 years hands-on with monitoring/alerting tooling (Icinga or equivalent NMS, Grafana, and at least one SIEM platform — Splunk, QRadar, or Sentinel)
- Experience rapidly mapping an unfamiliar, multi-team monitoring and alerting estate and consolidating it — ideally at a cloud, hosting, or multi-datacenter operator. Equivalent hands-on Vultr experience is a strong plus.
- 3+ years building integrations against APIs/webhooks, with scripting ability (Python or similar)
- 2–3 years building or substantially modifying operational dashboards (Grafana, Kibana, Power BI, or similar)
- Understanding of ticketing/ITSM workflow tools (Jira, Confluence, Mattermost) and how alert priority/severity maps into ticket fields
- Preferred: prior exposure to multi-provider/datacenter operational environments, and experience supporting or building for a NOC/SOC or similar 24x7 operations function
Pay: "$125,000 - $135,000 Final compensation will vary depending on years of experience, background/skill set, location, and applicable laws."
We need to keep that as prose maybe.
Now produce HTML:
- .
Skills: maybe not separate; but we could combine qualifications and skills? The instruction says we can have Skills section if there is real specific content. The posting includes qualifications that list skills; we could put them under Qualifications. But we could also create Skills section for things like scripting ability, dashboard building, etc. However we should avoid thin sections. Probably better to have Qualifications section covering the bullet list. Skills maybe not needed.
Benefits: The posting includes a list of benefits under "Vultr Cares" etc. So we should have Benefits section with those details.
Pay: The posting includes "Compensation $125,000 - $135,000". So we need Pay section.
Schedule: Not mentioned. No schedule info. So we should NOT create Schedule section.
We must not include boilerplate like Inclusion & Privacy etc. Remove that.
We also need to preserve all substantive information: company description, responsibilities, qualifications, benefits, pay.
We need to format as HTML fragment: use