Senior Engineering Manager

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: - About Your Role: description of role (lead engineering teams...). That's "About the role" content. - What You'll Do: list of duties (Lead software engineering teams..., Define engineering practices..., Guide modernization programs..., Partner..., Oversee..., Manage..., Coach...). That's responsibilities. - Experience You'll Need To Have: list of required experience (12+ years..., 8+ years..., etc). That's requirements/qualifications. - Experience That Would Be Great To Have: nice-to-have. - How You'll Work: requires use of computer and audio equipment (maybe not needed). Travel: occasional travel up to 10% (schedule? maybe schedule includes travel). Sponsorship: must have US work auth (maybe not needed). Salary Range: $186,000 - $285,600 (Pay). Also mention incentive eligible associates eligible for annual incentive opportunity (bonus/equity). That's pay/benefits. - Benefits: not explicitly listed besides incentive opportunity. Could treat incentive as benefit? But we need to only include sections with real specific content. There's no explicit benefits like health, 401k, etc. So maybe we omit Benefits section. - Schedule: travel up to 10% maybe schedule? Not exactly schedule like hours. Could include Travel as part of Schedule? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include Schedule if there is schedule info. Travel up to 10% could be considered schedule. We'll include Schedule section with that. - Skills: maybe we can extract skills from requirements: Java, Spring Boot, microservices, Kubernetes, cloud technologies, Azure, AWS, GCP, OpenShift, Docker, Terraform, Jenkins, GitHub Enterprise, Azure DevOps, REST APIs, event-driven architecture, Kafka, RabbitMQ, API gateways, service mesh, databases (PostgreSQL, Oracle, SQL Server, MongoDB, Cassandra, Cosmos DB). Also Agile, Scaled Agile Framework, Program Increment planning. Could list as skills. - Qualifications: maybe combine education: Bachelor's degree or higher in CS, Engineering or related field or equivalent. Also Master's degree great to have. We need to avoid repeating job title as heading. Also avoid Job ID etc. We must remove boilerplate: EEO, equal opportunity, scam warning, application instructions, etc. Also remove "Thank You For Considering Employment With Fiserv." etc. Also remove "Please Apply using your legal name..." etc. Also remove "Our Commitment To Equal Opportunity" etc. Also remove "Note To Agencies" etc. Also remove "Warning About Fake Job Posts". Also remove "Individuals with temporary visas..." maybe keep? That's sponsorship requirement; but it's a requirement about work authorization. Could be part of Requirements? Might be considered a requirement but it's about sponsorship. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Sponsorship requirement is maybe minor metadata; we could drop it or include in a short p. Probably drop it as it's not substantive? It's a requirement but maybe we can keep as part of Requirements? However it's about visa sponsorship; it's a condition. Could be included in Requirements as a bullet: "Must possess valid and unrestricted U.S. work authorization". That's substantive. We'll include. Also "How You'll Work This role requires use of a computer and audio equipment." That's minor; could drop. We need to preserve ALL substantive information; do not invent or summarize away detail. So we must keep all details from the posting that are substantive. That includes many bullet points. We must not omit any of the listed experience requirements, etc. So we need to include all those bullet points. Thus we need to create sections:

About the role

with paragraph(s) from "About Your Role" paragraph.

Responsibilities

with

• list of duties from "What You'll Do".

  Requirements

  maybe combine required experience and education? Could split into Requirements and Qualifications. The instruction says prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section? But they listed both as possible headings. We could have Requirements (includes experience) and Qualifications (includes education). But that's two sections; maybe okay if both have substantive content. However we could also have Requirements covering experience and Qualifications covering education and nice-to-have? But we also have Skills section. We need to decide. Let's think: The posting has: - Experience You'll Need To Have (list of 8+ years etc). That's definitely requirements. - Experience That Would Be Great To Have (nice-to-have). Could be Skills or Qualifications. - Bachelor’s degree or higher ... (education requirement). That's qualification. - Master’s degree ... great to have (nice-to-have qualification). - Certifications etc great to have. Thus we could have:

  Requirements

  for mandatory experience and education.

  Preferred Qualifications

  for nice-to-have (but heading not in list; we could use Qualifications). The list includes Qualifications as a possible heading. So we can use

  Qualifications

  for preferred qualifications (nice-to-have). But we also have mandatory education; maybe we put that in Requirements. Alternatively, we could have Requirements (experience), Qualifications (education + certifications), Skills (technical skills). But that may be many sections. Given instruction: Prefer a few substantive sections over many thin ones. So maybe combine Requirements and Qualifications into one section called Requirements (or Qualifications). But we need to follow the headings list: they gave examples but not mandatory to use all. We can choose which headings to use based on content. So we could have: - About the role - Responsibilities - Requirements (covers mandatory experience, education, work auth) - Skills (covers technical skills, tools, methodologies) - Pay (salary range + incentive) - Schedule (travel up to 10%) We could omit Benefits as none. We need to ensure we don't miss any substantive info: Let's extract all substantive content: From About Your Role: "As a Senior Engineering Manager, you will lead engineering teams that design, develop, modernize and operate cloud-native enterprise applications. You will work with Product Management, Architecture, Security, Infrastructure and Operations teams to deliver scalable platforms using Java, Spring Boot, microservices, Kubernetes and cloud technologies. Your work will support secure, resilient software delivery for financial services and other mission-critical environments." From What You'll Do (list): - Lead software engineering teams that build and operate cloud-native applications using Java, Spring Boot and microservices architecture. - Define engineering practices, coding standards and architecture principles that support scalable, secure and maintainable platforms. - Guide modernization programs that move enterprise applications toward containerized, cloud-native and automated delivery models. - Partner with product, architecture, security, infrastructure and operations teams to align platform delivery with business and compliance requirements. - Oversee Kubernetes, OpenShift and cloud platform deployment strategies across Azure, Amazon Web Services or Google Cloud Platform environments. - Manage Agile, Scaled Agile Framework and Program Increment planning activities across concurrent development initiatives and releases. - Coach engineers, technical leads and managers through performance planning, career development and succession planning. - Responsibilities listed are not intended to be all-inclusive and may be modified as necessary. (This is a note; maybe we can include as part of responsibilities? It's a disclaimer; could be omitted? It's substantive? It's a note about responsibilities not being all-inclusive. Might be considered boilerplate? It's part of the job description; but it's a generic statement. Might be okay to keep as a paragraph after list.) From Experience You'll Need To Have (list): - 12+ years of experience in software engineering delivering enterprise applications using Java, Spring Boot, microservices and cloud-native technologies. - 8+ years of experience managing and developing engineering teams that deliver enterprise platforms or mission-critical applications. - 8+ years of experience leading architecture, modernization or platform engineering initiatives in distributed systems environments. - 8+ years of experience with cloud platforms, containerized deployments and DevOps automation using technologies such as Azure, Amazon Web Services, Google Cloud Platform, Kubernetes, OpenShift, Docker, Terraform, Jenkins, GitHub Enterprise or Azure DevOps. - 8+ years of experience delivering secure application integrations using Representational State Transfer Application Programming Interfaces, event-driven architecture, Kafka, RabbitMQ, API gateways or service mesh technologies. - 8+ years of experience with relational or nonrelational databases such as PostgreSQL, Oracle, SQL Server, MongoDB, Cassandra or Cosmos DB. - Bachelor’s degree or higher in Computer Science, Engineering or related field or equivalent combination of education, related experience and/or military experience. From Experience That Would Be Great To Have (list): - Experience in banking, payments, financial technology or other regulated industries. - Experience modernizing monolithic applications into microservices architecture. - Experience with observability tools such as Dynatrace, Splunk, Prometheus or Grafana. - Master’s degree in Computer Science, Engineering, Business Administration or related field, Scaled Agile Framework certification or equivalent Agile credential, or cloud architecture certification or equivalent cloud credential. From How You'll Work: "This role requires use of a computer and audio equipment." (maybe minor, could drop) Travel: "This role requires occasional travel (up to 10%)." Sponsorship: "You must currently possess valid and unrestricted U.S. work authorization to be considered for this role. Individuals with temporary visas including, but not limited to, F-1 (OPT, CPT, STEM), H-1B, H-2, or TN, or any candidate requiring sponsorship, now or in the future, will not be considered for this role." Salary Range: "$186,000.00 - $285,600.00 These pay ranges apply to employees in New Jersey and New York. Pay ranges for employees in other states may differ. It is unlawful to discriminate against a prospective employee due to the individual's status as a veteran. For incentive eligible associates, the successful candidate is eligible for an annual incentive opportunity which may be delivered as a mix of cash bonus and equity awards in the Company’s sole discretion." Also there is a line: "Thank You For Considering Employment With Fiserv. Please Apply using your legal nameComplete the step-by-step profile and attach your resume (either is acceptable, both are preferable)." That's application instruction; we must remove. Also EEO etc remove. Thus we need to include all substantive info: About role, responsibilities, requirements (experience + education), preferred qualifications (nice-to-have), skills (maybe we can incorporate technical skills into requirements or qualifications). But we already have a lot of technical skills listed in experience requirements; we could keep them there. However we might want a Skills section to list specific technologies: Java, Spring Boot, microservices, Kubernetes, cloud platforms, Azure, AWS, GCP, OpenShift, Docker, Terraform, Jenkins, GitHub Enterprise, Azure DevOps, REST APIs, event-driven architecture, Kafka, RabbitMQ, API gateways, service mesh, databases (PostgreSQL, Oracle, SQL Server, MongoDB, Cassandra, Cosmos DB), Agile, Scaled Agile Framework, Program Increment planning, observability tools (Dynatrace, Splunk, Prometheus, Grafana), banking/payments experience, modernizing monoliths, etc. But we risk duplication. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we put skills in a separate section, we must ensure we don't lose any detail from the experience lists. We could keep the experience lists as is in Requirements section, and also have a Skills section that