Software Engineering Manager-Site Reliability
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting and extract relevant info. First, remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove Job ID/requisition numbers as headings. We need to preserve all substantive information. Let's extract sections: - Position Overview: includes description about PNC, role location, weekly time in office needed. That's about the role. Could be "About the role" section. - Needed Skills/experience: bullet list? It's a paragraph: "5 + years of related experience and 3+ years of management experience. Strong experience in Site Reliability Engineering, Production Support, or DevOps. Proven ability to lead teams in high-availability, enterprise environments Deep understanding of incident, problem, and change management frameworks Hands-on knowledge of monitoring tools, cloud/infrastructure platforms, and automation Experience improving system reliability, observability, and operational maturity Strong communication skills with the ability to lead during high-pressure situations. Experience with OCP under infrastructure (Linux/Windows, OCP), MongoDB, Cassandra under databases (Oracle, SQL, MongoDB, Cassandra) and working knowledge of Elasticsearch, Redis, MQ and Kafka is a plus." That's skills/experience. - The Site Reliability Center (SRC) description: maybe part of About the role or Responsibilities. - Key responsibilities include ... list. - Then "As a Software Engineering Manager – Site Reliability Engineering (SRE), you will lead a team..." then bullet list of responsibilities (Manage SRE and related Teams; lead, coach, develop... etc). Many responsibilities repeated. We need to consolidate responsibilities into a list. - Provide after-hours operational leadership and on-call support. - Participate in on-call leadership rotation... - Lead incident management & remediation... - Provide technical leadership in production support... - Drive problem management & root cause resolution... - Oversee change management & release execution... - Advance monitoring, alerting & observability... - Champion resiliency, stability & availability... - Enable scalability & performance optimization... - Lead a Global 24x7 Operation... - Drive Automation & Operational Efficiency... - Ensure Governance, Risk & Compliance... These are responsibilities. - Then later: "PNC is an in-office company..." maybe about culture, but could be part of About the role. - "PNC will not provide sponsorship for employment visas or participate in STEM OPT for this position." That's maybe a note, but could be considered metadata; we might drop as it's not a section heading? It's substantive but maybe we can include in a short p under About the role or a separate note. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." This is not Job ID, but it's a note about visa sponsorship. Could be folded into a short p. - Then "Job Description Manages development projects..." seems like generic job description maybe duplicate; we can ignore as it's boilerplate? It's somewhat generic but still substantive. However it's repeated later? Might be considered boilerplate. The instruction: remove duplicated lines. This seems like a generic job description that may be boilerplate. Might drop. - Then "PNC Employees take pride..." that's about values; could be part of About the role or maybe a separate section like "Company Values" but not requested headings. We could include under About the role. - Then "Qualifications Successful candidates must demonstrate appropriate knowledge, skills, and abilities for a role." Then list Preferred Skills, Competencies, Work Experience, Education, Certifications, Licenses, Language Assessments. We need to map to sections: Qualifications, Skills, Requirements maybe. We have headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have: - About the role: overview, location, weekly time in office, culture, visa note maybe. - Responsibilities: the long list of duties. - Requirements: maybe the needed skills/experience (5+ years, 3+ years management, etc.) Could be considered Requirements. - Qualifications: education, certifications, etc. - Skills: maybe the technical skills list (experience with OCP, MongoDB, Cassandra, etc.) Could be separate Skills section. - Benefits: we have benefits description. - Pay: base salary range. - Schedule: weekly time in the office needed (maybe schedule). Also mention after-hours, on-call, etc. Could be schedule. We need to avoid filler like "commensurate with experience". Not present. We need to ensure we don't create sections with placeholder text. Let's extract content precisely. **About the role**: From start: "R235657 Job Profile Position Overview At PNC, our people are our greatest differentiator and competitive advantage in the markets we serve. We are all united in delivering the best experience for our customers. We work together each day to foster an inclusive workplace culture where all of our employees feel respected, valued and have an opportunity to contribute to the company’s success. As a Software Engineering Manager within PNC's Site Reliability-DnA Data Ops Enterprise Data organization, you will be based in one of these Technology Hub locations: Pittsburgh, PA, Strongsville, OH, Birmingham, AL, Dallas, TX, Phoenix AZ. Weekly time in the office is needed." Later: "PNC is an in-office company that fosters a supportive culture where employees can thrive and achieve balance. We encourage candidates to connect with their recruiter and hiring manager to understand workplace expectations and ensure the role aligns with their goals. PNC will not provide sponsorship for employment visas or participate in STEM OPT for this position." We can combine these into About the role paragraph(s). Might be two paragraphs. **Responsibilities**: List: - driving customer-centric service improvements, implementing proactive and preventative reliability practices, fostering cross-functional collaboration, enhancing monitoring and observability capabilities, promoting a blameless culture of continuous learning, and reducing operational toil through automation. - The ideal candidate will help improve service performance, strengthen operational resiliency, and advance automation and observability initiatives that enhance the overall customer experience. - As a Software Engineering Manager – Site Reliability Engineering (SRE), you will lead a team responsible for ensuring the reliability, scalability, and operational excellence of mission-critical platforms that power PNC’s digital experiences. This role blends technical leadership, hands-on problem solving, and people management, driving both production stability and continuous improvement across complex distributed systems. - Manage SRE and related Teams; lead, coach, and develop a team of SRE engineers; set clear goals, drive accountability, and foster a culture of ownership and excellence; partner with cross-functional stakeholders to align technology and business objectives; support talent development, performance management, and succession planning; encourage innovation, continuous learning, and DevOps/SRE best practices. - Provide after-hours operational leadership and on-call support. Participate in an on-call leadership rotation supporting critical production services, major incidents, and high-severity customer-impacting events. Availability outside standard business hours, including evenings, weekends, and holidays, may be required to support incident response, change events, escalations, and business continuity needs. - Lead incident management & remediation; manage and actively participate in end-to-end incident response for major (P1/P2) incidents; guide real-time triage, diagnostics, and troubleshooting across application, infrastructure, and network layers; ensure rapid execution of remediation actions and service restoration; provide clear, timely communication to stakeholders during incidents; oversee post-incident analysis, reporting, and documentation to drive improvements. - Provide technical leadership in production support; serve as an escalation point for complex production issues; guide troubleshooting across: applications, infrastructure (Linux/Windows), databases (Oracle, SQL), middleware and integrations; ensure efficient log, metric, and system analysis; oversee batch/ETL monitoring and recovery processes; foster strong collaboration across engineering, infrastructure, and vendor teams. - Drive problem management & root cause resolution; lead root cause analysis (RCA) efforts for major and recurring incidents; ensure ownership and resolution of problem records; drive permanent fixes and systemic improvements to eliminate repeat issues, identify trends and patterns to reduce risk and improve stability; partner with engineering teams to resolve code defects and system gaps and promote knowledge sharing via runbooks, knowledge articles, and error catalogs. - Oversee change management & release execution; ensure safe and compliant execution of production changes and releases; validate change readiness, testing, rollback strategies, and risk assessments; represent the team in CAB reviews, providing technical risk evaluation; oversee post-implementation reviews (CPIR) and ensure follow-through and drive improvements in change success rate and reduction in production defects. - Advance monitoring, alerting & observability; lead efforts to build and optimize monitoring, dashboards, and alerting frameworks, champion use of tools such as Dynatrace, BigPanda, Logscale, and enterprise platforms, improve signal-to-noise ratio through alert tuning; enable proactive issue detection before customer impact; strengthen event management and observability practices. - Provide technical leadership in production support; (duplicate) but we can keep once. - Champion resiliency, stability & availability; lead efforts to ensure high availability of critical systems; oversee disaster recovery, failover, and continuity testing; identify and eliminate single points of failure and drive improvements in MTTR, uptime, and service reliability. - Enable scalability & performance optimization; guide capacity planning and performance tuning strategies; ensure systems scale effectively under peak demand; partner with development teams for performance-driven design improvements; optimize system configurations to improve efficiency and throughput. - Lead a Global 24x7 Operation; manage distributed teams supporting critical systems around the clock. Participate in leadership escalation and on-call rotations to support major incidents, critical production events, and operational continuity. - Drive Automation & Operational Efficiency; identify and prioritize opportunities to reduce manual effort through automation; implement automation across: Incident remediation, monitoring and alerting, deployment and validation, promote standardized runbooks and automation frameworks and improve operational metrics and reduce toil. - Ensure Governance, Risk & Compliance; maintain adherence to enterprise policies and regulatory standards; support audits, vulnerability remediation, and risk controls; ensure accurate documentation and operational procedures and champion security, access management, and data governance practices. We need to deduplicate duplicates: "Provide technical leadership in production support" appears twice; we can keep one. **Requirements** (maybe needed skills/experience): - 5 + years of related experience and 3+ years of management experience. - Strong experience in Site Reliability Engineering, Production Support, or DevOps. - Proven ability to lead teams in high-availability, enterprise environments - Deep understanding of incident, problem, and change management frameworks - Hands-on knowledge of monitoring tools, cloud/infrastructure platforms, and automation - Experience improving system reliability, observability, and operational maturity - Strong communication skills with the ability to lead during high-pressure situations. - Experience with OCP under infrastructure (Linux/Windows, OCP), MongoDB, Cassandra under databases (Oracle, SQL, MongoDB, Cassandra) and working knowledge of Elasticsearch, Redis, MQ and Kafka is a plus. We could split into Requirements and Skills. But we have both headings available. **Skills** maybe the technical specific tools: OCP, MongoDB, Cassandra, Elasticsearch, Redis, MQ, Kafka, Dynatrace, BigPanda, Logscale, etc. But the posting also mentions those in responsibilities. However we can create a Skills section listing the technical skills/experience. **Qualifications**: - Education: Bachelors - Work Experience: Roles at this level typically require a university / college degree, with 5+ years of industry-relevant experience. At least 3 years of prior management experience is typically required. In lieu of a degree, a comparable combination of education, job specific certification(s), and experience (including military service) may be considered. - Preferred Skills: AI Platforms, Application Development, Business Management, Customer Solutions, Design, Group Problem Solving, IT Automation, Process Improvements, Release Management