Senior Software Engineer I

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the job description. Content: Job Description Infrastructure as Code Engineer – Multi-Cloud We are seeking an experienced Infrastructure as Code (IaC) Engineer to design, automate, and secure scalable infrastructure across GCP, AWS, and Azure. The role requires strong expertise in Terraform, cloud networking, network security, IAM, Kubernetes networking, and API gateways. The engineer will build reusable IaC modules and secure multi-cloud patterns, implement network and security controls, automate infrastructure through CI/CD and policy-as-code, and establish standardized self-service capabilities for engineering teams. The role will also support AI and agentic enablement, orchestrating secure connectivity, identity, API/tool access, and infrastructure patterns for deploying agentic workloads across multi-cloud environments. Responsibilities (list of bullet points but they are actually requirements? The text after "Responsibilities" includes many bullet-like sentences starting with numbers? Actually they are listed as bullet points but not with bullet characters. They start with "7+ years of infrastructure engineering experience..." etc. Those seem like qualifications/requirements. Then later there is a "Qualifications" heading with more bullet-like sentences. Then "About Us", "About The Team", benefits list. We need to map to sections: About the role (intro paragraph), Responsibilities (list of duties), Requirements (maybe experience?), Qualifications (certifications etc), Skills (maybe technical skills), Benefits (list from About The Team), Pay (salary range mentioned at end), Schedule (maybe flexible working model? There's mention of flexible working model with hybrid, onsite or virtual arrangements). So we can include Schedule section if there is specific content. We must not include filler like "commensurate with experience". The posting includes salary range? It says "The below represents the expected salary range for this job requisition. Ultimately, in determining your pay, we’ll consider your location, experience, and other job-related factors." No actual numbers given. So we cannot create Pay section because no specific numbers. The instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Since salary range not given, we should not include Pay section. However there is mention of flexible working model; that could be Schedule. It states: "Depending on role and business needs, colleagues will either work onsite, in a hybrid model (combination of in-office and virtual days) or fully virtually." That's specific enough for Schedule. So include Schedule section. Benefits: The About The Team section lists many benefits: Competitive base salaries, Bonus incentives, 6% Company Match on retirement savings plan, Free financial coaching..., Comprehensive medical..., Flexible working model..., 20+ weeks paid parental leave..., Free access to global on-site wellness centers..., Free and confidential counseling..., Career development and training opportunities. Also mention of Amex Flex etc. So we can include Benefits section with those items as list. Now we need to decide sections: About the role (intro paragraph), Responsibilities (maybe the bullet list after "Responsibilities"? Actually the bullet list after "Responsibilities" seems to be qualifications/experience. But we can treat that as Responsibilities? The heading "Responsibilities" appears in the text, then after that there is a list of bullet points that are actually experience requirements. However the instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should follow the headings present in the posting: there is "Responsibilities", "Qualifications", "About Us", "About The Team". We need to map to our allowed headings. We can create sections: About the role (intro), Responsibilities (the bullet list after Responsibilities heading), Requirements (maybe we can combine some?), Qualifications (the bullet list after Qualifications heading), Skills (maybe we can extract technical skills from responsibilities/qualifications?), Benefits (from About The Team), Schedule (flexible working model). We must not invent sections without content. Let's extract content: Intro paragraph: "We are seeking an experienced Infrastructure as Code (IaC) Engineer to design, automate, and secure scalable infrastructure across GCP, AWS, and Azure. The role requires strong expertise in Terraform, cloud networking, network security, IAM, Kubernetes networking, and API gateways. The engineer will build reusable IaC modules and secure multi-cloud patterns, implement network and security controls, automate infrastructure through CI/CD and policy-as-code, and establish standardized self-service capabilities for engineering teams. The role will also support AI and agentic enablement, orchestrating secure connectivity, identity, API/tool access, and infrastructure patterns for deploying agentic workloads across multi-cloud environments." That's About the role. Responsibilities: The text after "Responsibilities" heading includes a series of bullet-like sentences (starting with "7+ years of infrastructure engineering experience..." etc). Actually those are more like requirements/experience. But we will treat them as Responsibilities as per heading. Let's list them: - 7+ years of infrastructure engineering experience with strong expertise in Infrastructure as Code (IaC) using Terraform, OpenTofu, or similar frameworks. - 7+ years of hands-on experience designing and automating infrastructure across Google Cloud Platform (GCP), AWS, and/or Azure, with an emphasis on reusable, standardized multi-cloud patterns. - Strong knowledge of cloud networking, including VPC/VNet architecture, subnets, routing, DNS, NAT, load balancing, private connectivity, peering, transit architectures, VPN, and dedicated interconnects. - Deep understanding of network security, including security groups, firewall policies/rules, network ACLs, micro-segmentation, ingress/egress controls, private endpoints, and Zero Trust principles. - Proven experience implementing network segmentation and isolation patterns across applications, environments, business units, and cloud platforms. - Strong experience with API gateways and API infrastructure, including secure ingress/egress, authentication and authorization, rate limiting, routing, policy enforcement, private APIs, and service-to-service connectivity. - Experience designing secure connectivity for Kubernetes and containerized workloads, including GKE/EKS/AKS networking, network policies, service ingress/egress, and workload isolation. - Strong understanding of IAM, secrets management, encryption, certificates/PKI, and cloud security architecture, with the ability to integrate these controls into IaC modules and deployment pipelines. - Proven experience building enterprise-grade reusable Terraform modules, policy-driven infrastructure patterns, CI/CD integrations, automated testing, and infrastructure governance. - Experience designing and operating large-scale, highly available, resilient multi-cloud infrastructure using standardized automation and security controls. - Strong understanding of distributed systems, microservices, service-to-service communication, and modern application connectivity patterns. - Experience enabling AI/agentic workloads in multi-cloud environments, including secure agent-to-API/tool connectivity, identity and authorization, controlled network access, API gateway integration, secrets handling, and infrastructure automation for agentic platforms. That's a lot; we can keep as list. Requirements: The posting also has a "Qualifications" heading with bullet list. But we need a Requirements section maybe separate from Qualifications. The instruction list includes Requirements as a possible heading. We could put the "Qualifications" bullet list under Requirements? But there is also a separate "Qualifications" heading later. Actually after Responsibilities, there is a "Qualifications" heading then bullet list. Then after that there is "About Us", "About The Team". So we have two sections: Qualifications (the bullet list after that heading) and maybe we can treat the earlier bullet list as Responsibilities (though they look like requirements). We'll follow the headings as they appear: Responsibilities (the bullet list after that heading) and Qualifications (the bullet list after Qualifications heading). Then we can also have Skills maybe extracted from both? But we might not need Skills if we already have Responsibilities and Qualifications covering skills. However we could create Skills section summarizing technical skills like Terraform, cloud networking, etc. But we must not invent content; we can list skills explicitly mentioned. The posting mentions many skills: Terraform, OpenTofu, GCP, AWS, Azure, cloud networking, VPC/VNet, subnets, routing, DNS, NAT, load balancing, private connectivity, peering, transit architectures, VPN, dedicated interconnects, security groups, firewall policies/rules, network ACLs, micro-segmentation, ingress/egress controls, private endpoints, Zero Trust, API gateways, authentication, authorization, rate limiting, routing, policy enforcement, private APIs, service-to-service connectivity, Kubernetes networking (GKE/EKS/AKS), network policies, service ingress/egress, workload isolation, IAM, secrets management, encryption, certificates/PKI, cloud security architecture, reusable Terraform modules, policy-driven infrastructure patterns, CI/CD, automated testing, infrastructure governance, distributed systems, microservices, service-to-service communication, modern application connectivity patterns, AI/agentic workloads, secure agent-to-API/tool connectivity, identity and authorization, controlled network access, API gateway integration, secrets handling, infrastructure automation for agentic platforms, multi-cloud network and security architectures, IaC platform capabilities, reusable modules, golden patterns, self-service infrastructure, policy-as-code, automated compliance, developer enablement, network security platforms (Cloud NGFW/firewalls, AWS Network Firewall, Azure Firewall, WAF, IDS/IPS, secure web gateways, service mesh), API management platforms (Apigee, AWS API Gateway, Azure API Management, Kong), Zero Trust, least privilege, defense-in-depth, micro-segmentation, secure-by-default, policy-as-code (OPA, Sentinel, organization policies, IAM policies, automated IaC security scanning), FinOps and cloud cost optimization (network, data-transfer, NAT, load-balancing, API, multi-cloud connectivity costs), enabling agentic AI platforms, secure access to enterprise APIs, MCP/tool integrations, agent identity, guardrails, observability, controlled cross-cloud connectivity, establishing IaC standards and governance for AI/agentic infrastructure, relevant certifications (HashiCorp Terraform Associate, GCP Professional Cloud Network Engineer/Cloud Architect/Cloud Security Engineer, AWS Advanced Networking or Security Specialty, Azure Network/Security certifications). That's a lot; we could put them in Skills section as list. But we already have Responsibilities and Qualifications sections with detailed bullet points; adding Skills might be redundant but allowed if we have specific content. However we must not create thin sections; we should prefer few substantive sections over many thin ones. So maybe we combine Responsibilities and Qualifications into one section? But the instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid having both Responsibilities and Qualifications. We'll include both as they have substantive content. We also need Requirements section: maybe we can treat the bullet list after Responsibilities as Requirements? But the heading is Responsibilities. However we could rename to Requirements? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not strict requirement to use exactly those headings; we should use those headings for sections. So we should use the heading "Responsibilities" for the bullet list after that heading. For the bullet list after Qualifications heading, we should use heading "Qualifications". For Requirements, we might not have explicit content; but we could derive from the bullet list after Responsibilities? But that's already used as Responsibilities. Maybe we can treat the bullet list after Responsibilities as Requirements and rename heading to Requirements? But then we would deviate from the actual heading in the posting. The instruction: "use

for section headings (e.g. About the role