Senior Manager - Site Reliability Engineering (SRE)
Ferguson · United States · 1 mo ago
RemoteRemoteQuality Assurance$9k–$17k/moFull-time
We need to output HTML fragment with sections: About the role? Actually we need to use for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. Must include sections only when posting has real specific content. We have content: description (intro) maybe "About the role". Duties and Responsibilities: we have list. Qualifications and Requirements: list. Benefits: we have description of benefits. Pay: we have pay range. Schedule: not mentioned. Skills: maybe we can combine with qualifications? But we could have a Skills section if there is specific skill list. The posting includes many technical skills; we could put them under Skills. However we already have Qualifications and Requirements which includes experience and skills. The instruction: prefer a few substantive sections over many thin ones. So we could have sections: About the role (intro paragraph), Responsibilities (list), Qualifications (list), Benefits (list), Pay (maybe paragraph). Avoid Schedule as not present. Skills maybe not needed if covered in Qualifications. We'll include About the role, Responsibilities, Qualifications, Benefits, Pay.
We must not include boilerplate like EEO etc. Remove that.
We need to preserve all substantive information. So we need to include the intro paragraph about Ferguson and the role description. Also location info. Also mention remote/hybrid location requirement. Also mention that applicants must be based within Eastern or Central time zones. Also mention that it's Bonus or Incentive Plan eligible. Also mention pay range.
We need to format using
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. Must include sections only when posting has real specific content. We have content: description (intro) maybe "About the role". Duties and Responsibilities: we have list. Qualifications and Requirements: list. Benefits: we have description of benefits. Pay: we have pay range. Schedule: not mentioned. Skills: maybe we can combine with qualifications? But we could have a Skills section if there is specific skill list. The posting includes many technical skills; we could put them under Skills. However we already have Qualifications and Requirements which includes experience and skills. The instruction: prefer a few substantive sections over many thin ones. So we could have sections: About the role (intro paragraph), Responsibilities (list), Qualifications (list), Benefits (list), Pay (maybe paragraph). Avoid Schedule as not present. Skills maybe not needed if covered in Qualifications. We'll include About the role, Responsibilities, Qualifications, Benefits, Pay.
We must not include boilerplate like EEO etc. Remove that.
We need to preserve all substantive information. So we need to include the intro paragraph about Ferguson and the role description. Also location info. Also mention remote/hybrid location requirement. Also mention that applicants must be based within Eastern or Central time zones. Also mention that it's Bonus or Incentive Plan eligible. Also mention pay range.
We need to format using for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. So no
Senior Manager - Site Reliability Engineering
. Good.
We need to output only HTML fragment, no /, no markdown fences.
Let's craft.
First, maybe an About the role
with containing the introductory paragraphs: Since 1953... up to "You will build a career that you are proud of, at a company you can believe in." plus the role summary: "Join Ferguson as a Senior Manager, Site Reliability Engineering and help shape the reliability, performance, and availability of our digital commerce platform." plus location info.
We need to include location: "Location: Remote (Eastern or Central Time Zone) or Hybrid (Newport News, VA), in accordance with company policy. Applicants must be based within the Eastern or Central time zones."
Also mention Bonus or Incentive Plan eligible maybe under Pay or separate? Could be under Pay.
Now Responsibilities: list items from Duties and Responsibilities.
We need to convert each bullet into
- . The duties list is long; we need to preserve all. We'll copy each sentence as separate
- . Ensure we don't lose any.
Let's extract duties:
- Lead and develop a high-performing group of Site Reliability Engineers who coordinate the reliability, availability, and performance of Linux-based systems and infrastructure supporting digital commerce applications.
- Set technical and strategic vision for the SRE domain, driving adoption of Kubernetes-based container platforms, Docker workloads, and modern SRE/DevOps practices across teams.
- Establish and continuously improve CI/CD standards, driving improvements to pipelines built with GitHub Action Workflows and other modern tooling, including infrastructure-as-code practices using Terraform.
- Define configuration management and automation standards using Puppet and Python to reduce toil and eliminate repetitive manual work at scale.
- Guide strategy for load balancing, application delivery, and virtualized infrastructure using F5 and VMware, and for tuning web and application servers such as Nginx and Apache Tomcat.
- Champion observability using Datadog (logging, metrics, distributed traces, alerting) and sound artifact management practices using JFrog Artifactory so the team can detect and resolve issues early.
- Own incident management for the domain, defining incident response and on-call practices, leading root cause analysis for significant incidents, and converting findings into durable engineering improvements.
- Drive adoption of SRE/DevOps principles such as SLIs/SLOs and error budgets, balancing reliability, velocity, and technical debt across the platform.
- Champion a culture of accountability, collaboration, innovation, and continuous learning, and act as a technical escalation and decision point for sophisticated reliability and infrastructure challenges.
- Recruit, mentor, and retain top SRE talent while supporting career development, performance management, and succession planning, and coach lead and senior engineers to strengthen technical capability and leadership.
- Partner with Product Management, Architecture, Infrastructure, Security, and Networking team members to align reliability strategy with platform and business priorities.
Now Qualifications and Requirements: list items.
Extract:
- 8+ years of professional experience administering Linux systems in a production environment, including 3+ years leading or managing engineering or SRE teams.
- Proven success setting technical direction for reliability, automation, or infrastructure initiatives at a scope comparable to or greater than a Lead Site Reliability Engineer.
- Strong hands-on experience with Kubernetes and Docker or similar container orchestration/containerization platforms.
- Good experience building, maintaining, and defining standards for CI/CD pipelines using GitHub Actions or similar tooling, and solid experience with Terraform or other infrastructure-as-code tools.
- Extensive experience with configuration management tools such as Puppet, along with extensive experience standardizing automation using Python or a similar language.
- Proven expertise in load balancing/application delivery and virtualization technologies, coupled with tuning web and application servers such as Nginx and Apache Tomcat.
- Good experience with observability tooling such as Datadog, including the ability to define observability standards, and with artifact repository tools such as JFrog Artifactory.
- Good understanding of networking, storage, and IT infrastructure fundamentals, including security concepts relevant to enterprise infrastructure.
- Experience defining incident response processes and on-call rotation structures, and championing SRE/DevOps principles such as SLIs/SLOs and error budgets across a team.
- Strong troubleshooting and systems-thinking skills with the ability to convert incident findings into durable engineering improvements.
- Experience working within Agile product delivery organizations and collaborating with Product Management, Architecture, Infrastructure, Security, and Networking team members.
- Good communication, leadership, and team development skills, with a passion for mentoring engineers and building high-performing teams.
Then there is a "Leadership Skills:" subsection with bullet points. Those could be part of Qualifications or separate Skills section. Since we want few sections, we could incorporate them into Qualifications as well, but they are more about leadership. Could create a Skills section for leadership skills. However instruction: prefer a few substantive sections over many thin ones. So maybe we keep Qualifications (including experience and technical skills) and then a Skills section for leadership skills. But we could also merge leadership skills into Qualifications as they are also qualifications. Let's see: The posting has "Leadership Skills:" with bullet points. Those are substantive. We could include them under Qualifications as additional items. That would keep sections: About the role, Responsibilities, Qualifications, Benefits, Pay.
Thus Qualifications list will include both the earlier items and the leadership skills items.
Now Benefits: we have paragraph describing benefits. We need to turn into
- for any list of benefits. The paragraph lists many benefits: health, dental, vision, paid time off, life insurance, 401(k) with company match, mental health coverage, gender affirming and family building benefits, paid parental leave, associate discounts, community involvement opportunities and more! Also mention holistic approach, competitive offering. We'll create list items for each benefit.
Pay: we have pay range paragraph. We'll put in
.
Now ensure we don't include boilerplate like EEO etc. Remove all that.
Now construct HTML.
We'll start with
About the role
...
Then Responsibilities
...
Then Qualifications
...
Then Benefits
...
Then Pay
...
Make sure no extra whitespace issues.
Now craft the About the role paragraph.
Combine:
"Since 1953, Ferguson has been a source of quality supplies for a variety of industries. Together We Build Better infrastructure, better homes and better businesses. We exist to make our customers’ complex projects simple, successful, and sustainable. We proactively solve problems, adapt and grow to continuously serve our customers, communities and each other. Ferguson, a Fortune 500 company, is proud to provide best-in-class products, service and capabilities across the following industries: Commercial/Mechanical, Facilities Supply, Fire and Fabrication, HVAC, Industrial, Residential Trade, Residential Building and Remodel, Waterworks and Residential Digital Commerce. Ferguson has approximately 36,000 associates across 1,700 locations. Ferguson is a community of proud associates who operate with the shared purpose of building something meaningful. You will build a career that you are proud of, at a company you can believe in. Join Ferguson as a Senior Manager, Site Reliability Engineering and help shape the reliability, performance, and availability of our digital commerce platform. In this leadership role, you'll guide a team of Site Reliability Engineers responsible for the stability, automation, and observability of the Linux-based systems and infrastructure that power Ferguson's digital commerce, while driving the modernization of our SRE and DevOps practices. You'll partner closely with Backend Engineers, Frontend Engineers, Principal Solution Architects, Infrastructure Engineers, and Networking teams to deliver resilient platform capabilities, improve engineering standards, and pull digital commerce forward into more modern standard processes. This is an opportunity for a proven, systems-thinking SRE leader who is passionate about developing high-performing teams, driving engineering excellence, and delivering meaningful business outcomes through reliability engineering and automation. The ideal candidate is technically strong enough to set strategic direction for the SRE domain — at least at the level of a Lead Site Reliability Engineer — while coaching senior and lead engineers to raise the reliability bar across the platform. Location: Remote (Eastern or Central Time Zone) or Hybrid (Newport News, VA), in accordance with company policy. Applicants must be based within the Eastern or Central time zones."
That is a long paragraph but okay.
Now Responsibilities list as above.
Now Qualifications list: combine the earlier items and leadership skills.
Leadership skills bullets:
- Strong leader who builds trust, accountability, and ownership across an SRE team.
- Demonstrable ability to lead engineering teams through modernization of SRE/DevOps practices and organizational change.
- Good communication skills coupled with the capacity to convey reliability and infrastructure concepts in terms of business value.
- Passion for mentoring engineers and developing future technical and reliability leaders.
- Ability to establish a culture focused on engineering excellence, operational reliability, continuous improvement, and customer outcomes.
- Demonstrated ability to influence without authority and collaborate across engineering, infrastructure, and networking organizations.
- Strong execution mentality with a focus on delivering measurable reliability and business results while continuously improving engineering quality.
Add these to Qualifications list.
Now Benefits list: items:
- Health insurance
- Dental insurance
- Vision insurance
- Paid time off
- Life insurance
- 401(k) with company match
- Mental health coverage
- Gender affirming and family building benefits
- Paid parental leave
- Associate discounts
- Community involvement opportunities
We could also include "holistic approach towards benefits plans and programs that support the mental, physical and financial well-being of our associates" but that's descriptive; we could keep as a paragraph before list? But instruction: use - for any list of duties/requirements/benefits. So we should put benefits as list. The introductory sentence could be a
before list? But we can incorporate as part of list? Might be okay to have a
preceding list describing the approach, then
for benefits. However instruction says use - for any list of benefits. It doesn't forbid a preceding paragraph. We'll add a
- for any list of duties/requirements/benefits. Use
for prose. We must not repeat job title as heading. So no
Senior Manager - Site Reliability Engineering
. Good. We need to output only HTML fragment, no /, no markdown fences. Let's craft. First, maybe anAbout the role
withcontaining the introductory paragraphs: Since 1953... up to "You will build a career that you are proud of, at a company you can believe in." plus the role summary: "Join Ferguson as a Senior Manager, Site Reliability Engineering and help shape the reliability, performance, and availability of our digital commerce platform." plus location info. We need to include location: "Location: Remote (Eastern or Central Time Zone) or Hybrid (Newport News, VA), in accordance with company policy. Applicants must be based within the Eastern or Central time zones." Also mention Bonus or Incentive Plan eligible maybe under Pay or separate? Could be under Pay. Now Responsibilities: list items from Duties and Responsibilities. We need to convert each bullet into
- . The duties list is long; we need to preserve all. We'll copy each sentence as separate
- . Ensure we don't lose any.
Let's extract duties:
- Lead and develop a high-performing group of Site Reliability Engineers who coordinate the reliability, availability, and performance of Linux-based systems and infrastructure supporting digital commerce applications.
- Set technical and strategic vision for the SRE domain, driving adoption of Kubernetes-based container platforms, Docker workloads, and modern SRE/DevOps practices across teams.
- Establish and continuously improve CI/CD standards, driving improvements to pipelines built with GitHub Action Workflows and other modern tooling, including infrastructure-as-code practices using Terraform.
- Define configuration management and automation standards using Puppet and Python to reduce toil and eliminate repetitive manual work at scale.
- Guide strategy for load balancing, application delivery, and virtualized infrastructure using F5 and VMware, and for tuning web and application servers such as Nginx and Apache Tomcat.
- Champion observability using Datadog (logging, metrics, distributed traces, alerting) and sound artifact management practices using JFrog Artifactory so the team can detect and resolve issues early.
- Own incident management for the domain, defining incident response and on-call practices, leading root cause analysis for significant incidents, and converting findings into durable engineering improvements.
- Drive adoption of SRE/DevOps principles such as SLIs/SLOs and error budgets, balancing reliability, velocity, and technical debt across the platform.
- Champion a culture of accountability, collaboration, innovation, and continuous learning, and act as a technical escalation and decision point for sophisticated reliability and infrastructure challenges.
- Recruit, mentor, and retain top SRE talent while supporting career development, performance management, and succession planning, and coach lead and senior engineers to strengthen technical capability and leadership.
- Partner with Product Management, Architecture, Infrastructure, Security, and Networking team members to align reliability strategy with platform and business priorities.
Now Qualifications and Requirements: list items.
Extract:
- 8+ years of professional experience administering Linux systems in a production environment, including 3+ years leading or managing engineering or SRE teams.
- Proven success setting technical direction for reliability, automation, or infrastructure initiatives at a scope comparable to or greater than a Lead Site Reliability Engineer.
- Strong hands-on experience with Kubernetes and Docker or similar container orchestration/containerization platforms.
- Good experience building, maintaining, and defining standards for CI/CD pipelines using GitHub Actions or similar tooling, and solid experience with Terraform or other infrastructure-as-code tools.
- Extensive experience with configuration management tools such as Puppet, along with extensive experience standardizing automation using Python or a similar language.
- Proven expertise in load balancing/application delivery and virtualization technologies, coupled with tuning web and application servers such as Nginx and Apache Tomcat.
- Good experience with observability tooling such as Datadog, including the ability to define observability standards, and with artifact repository tools such as JFrog Artifactory.
- Good understanding of networking, storage, and IT infrastructure fundamentals, including security concepts relevant to enterprise infrastructure.
- Experience defining incident response processes and on-call rotation structures, and championing SRE/DevOps principles such as SLIs/SLOs and error budgets across a team.
- Strong troubleshooting and systems-thinking skills with the ability to convert incident findings into durable engineering improvements.
- Experience working within Agile product delivery organizations and collaborating with Product Management, Architecture, Infrastructure, Security, and Networking team members.
- Good communication, leadership, and team development skills, with a passion for mentoring engineers and building high-performing teams.
Then there is a "Leadership Skills:" subsection with bullet points. Those could be part of Qualifications or separate Skills section. Since we want few sections, we could incorporate them into Qualifications as well, but they are more about leadership. Could create a Skills section for leadership skills. However instruction: prefer a few substantive sections over many thin ones. So maybe we keep Qualifications (including experience and technical skills) and then a Skills section for leadership skills. But we could also merge leadership skills into Qualifications as they are also qualifications. Let's see: The posting has "Leadership Skills:" with bullet points. Those are substantive. We could include them under Qualifications as additional items. That would keep sections: About the role, Responsibilities, Qualifications, Benefits, Pay.
Thus Qualifications list will include both the earlier items and the leadership skills items.
Now Benefits: we have paragraph describing benefits. We need to turn into
- for any list of benefits. The paragraph lists many benefits: health, dental, vision, paid time off, life insurance, 401(k) with company match, mental health coverage, gender affirming and family building benefits, paid parental leave, associate discounts, community involvement opportunities and more! Also mention holistic approach, competitive offering. We'll create list items for each benefit.
Pay: we have pay range paragraph. We'll put in
. Now ensure we don't include boilerplate like EEO etc. Remove all that. Now construct HTML. We'll start with
About the role
...
ThenResponsibilities
- ...
Qualifications
- ...
Benefits
- ...
Pay
...
Make sure no extra whitespace issues. Now craft the About the role paragraph. Combine: "Since 1953, Ferguson has been a source of quality supplies for a variety of industries. Together We Build Better infrastructure, better homes and better businesses. We exist to make our customers’ complex projects simple, successful, and sustainable. We proactively solve problems, adapt and grow to continuously serve our customers, communities and each other. Ferguson, a Fortune 500 company, is proud to provide best-in-class products, service and capabilities across the following industries: Commercial/Mechanical, Facilities Supply, Fire and Fabrication, HVAC, Industrial, Residential Trade, Residential Building and Remodel, Waterworks and Residential Digital Commerce. Ferguson has approximately 36,000 associates across 1,700 locations. Ferguson is a community of proud associates who operate with the shared purpose of building something meaningful. You will build a career that you are proud of, at a company you can believe in. Join Ferguson as a Senior Manager, Site Reliability Engineering and help shape the reliability, performance, and availability of our digital commerce platform. In this leadership role, you'll guide a team of Site Reliability Engineers responsible for the stability, automation, and observability of the Linux-based systems and infrastructure that power Ferguson's digital commerce, while driving the modernization of our SRE and DevOps practices. You'll partner closely with Backend Engineers, Frontend Engineers, Principal Solution Architects, Infrastructure Engineers, and Networking teams to deliver resilient platform capabilities, improve engineering standards, and pull digital commerce forward into more modern standard processes. This is an opportunity for a proven, systems-thinking SRE leader who is passionate about developing high-performing teams, driving engineering excellence, and delivering meaningful business outcomes through reliability engineering and automation. The ideal candidate is technically strong enough to set strategic direction for the SRE domain — at least at the level of a Lead Site Reliability Engineer — while coaching senior and lead engineers to raise the reliability bar across the platform. Location: Remote (Eastern or Central Time Zone) or Hybrid (Newport News, VA), in accordance with company policy. Applicants must be based within the Eastern or Central time zones." That is a long paragraph but okay. Now Responsibilities list as above. Now Qualifications list: combine the earlier items and leadership skills. Leadership skills bullets: - Strong leader who builds trust, accountability, and ownership across an SRE team. - Demonstrable ability to lead engineering teams through modernization of SRE/DevOps practices and organizational change. - Good communication skills coupled with the capacity to convey reliability and infrastructure concepts in terms of business value. - Passion for mentoring engineers and developing future technical and reliability leaders. - Ability to establish a culture focused on engineering excellence, operational reliability, continuous improvement, and customer outcomes. - Demonstrated ability to influence without authority and collaborate across engineering, infrastructure, and networking organizations. - Strong execution mentality with a focus on delivering measurable reliability and business results while continuously improving engineering quality. Add these to Qualifications list. Now Benefits list: items: - Health insurance - Dental insurance - Vision insurance - Paid time off - Life insurance - 401(k) with company match - Mental health coverage - Gender affirming and family building benefits - Paid parental leave - Associate discounts - Community involvement opportunities We could also include "holistic approach towards benefits plans and programs that support the mental, physical and financial well-being of our associates" but that's descriptive; we could keep as a paragraph before list? But instruction: use- for any list of duties/requirements/benefits. So we should put benefits as list. The introductory sentence could be a
before list? But we can incorporate as part of list? Might be okay to have a
preceding list describing the approach, then
- for benefits. However instruction says use
- for any list of benefits. It doesn't forbid a preceding paragraph. We'll add a
- for any list of duties/requirements/benefits. So we should put benefits as list. The introductory sentence could be a
- for any list of benefits. The paragraph lists many benefits: health, dental, vision, paid time off, life insurance, 401(k) with company match, mental health coverage, gender affirming and family building benefits, paid parental leave, associate discounts, community involvement opportunities and more! Also mention holistic approach, competitive offering. We'll create list items for each benefit.
Pay: we have pay range paragraph. We'll put in