External Post

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, etc. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - About the role / Summary: The first paragraph about Menlo Security mission, platform, etc. Also the "Summary Platform Infrastructure Engineering builds and operates Menlo Security's Infrastructure Platform..." That's about the role. - Responsibilities: "What You'll Do" bullet list. - Requirements / Qualifications: "Functional Competencies Required:" list. - Preferred / Nice to Have: "Preferred / Nice to Have:" list. - Skills: maybe combine required and preferred? But we can have separate sections: Requirements (required) and Preferred (nice to have). The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can decide to use Requirements for required competencies, and maybe Skills for preferred? Or we can combine required and preferred under Requirements and Skills. Let's see. We have no explicit Pay or Schedule info. There's mention of "Participate in a 24x7 on-call rotation". That's schedule info? It's about on-call. Could be considered schedule. But we should only include Schedule if posting actually states them. It does mention on-call rotation. That is schedule-related. Could put under Schedule heading. Benefits: Not mentioned explicitly. There's "Why Menlo?" describing culture but not benefits like health, etc. Not specific benefits. So we should not create Benefits section. Pay: Not mentioned. So omit. Thus sections: About the role (maybe using

About the role

), Responsibilities, Requirements, Preferred (maybe Skills), Schedule (on-call). Could also include Qualifications as separate but we have Requirements already covering required competencies. Could also include Qualifications for education etc. The required list includes Bachelor's degree etc. That's qualifications. Could put under Qualifications. But we can combine. We need to avoid filler like "commensurate with experience". Not present. We need to preserve all substantive info. Let's extract details. About the role: Combine the introductory paragraphs: "Menlo Security is the leader in Browser Security for human and agentic workforces. Our mission is to enable humans and agents to connect, communicate, and collaborate securely, without compromise. The Menlo Browser Security Platform protects organizations from cyberattacks by stopping threats across the web, documents, and email before they reach the user. With Menlo Agent Runtime Security (MARS), that protection now extends to the AI agents working alongside every employee. Menlo Security is trusted by major global businesses, including Fortune 500 companies and government agencies, to protect their most valuable asset, their data, and is backed by top-tier investors." Then: "Summary Platform Infrastructure Engineering builds and operates Menlo Security's Infrastructure Platform, enabling our customers to connect to the Internet without compromise. As a Platform Infrastructure Engineer, you'll join a globally distributed team of experienced engineers building and managing the company's core infrastructure services on a cloud-native platform built on Google Kubernetes Engine and VMs spanning multiple regions and environments. The team manages infrastructure as code with Terraform and Spacelift, deploys with Helm, and emphasizes security-first design, comprehensive observability, and multi-region resilience. The team also uses AI-assisted development and code-review tools, including Gemini Code Assist, as part of the standard engineering workflow, and this role is expected to use LLM-based tooling to build and troubleshoot infrastructure code efficiently." We could keep as paragraphs. Outcomes & KPIs: That's also substantive. Could be part of About the role or separate section like "Outcomes & KPIs". But headings limited to given list. Could incorporate into About the role or Responsibilities? It's about outcomes. Might be better to include as part of About the role or maybe a separate section like "Outcomes". But not in allowed headings. We could put under About the role as additional paragraphs. Responsibilities: The "What You'll Do" list: - Design, deploy, and maintain VM and Kubernetes infrastructure on GCP and AWS across dozens of clusters spanning development, staging, and production environments in multiple regions - Build and maintain Infrastructure as Code using Terraform modules and Spacelift (or equivalent TACOS), provisioning networking, compute, storage, and security components, and implementing multi-layer configuration management workflows - Build and maintain observability solutions using Grafana Cloud, Prometheus/Mimir, and OTel collectors, designing dashboards and alerting rules across all platform components - Manage certificate lifecycle, DNS automation, ingress controllers, and service mesh networking with Cilium - Partner with peers and across Engineering, Product, Compliance, and Security teams to align on requirements and consult on capacity planning, disaster recovery, and architectural decisions - Identify and eliminate toil through automation — writing scripts, building CI/CD pipelines, and using AI-assisted coding tools to move faster - Participate in a 24x7 on-call rotation as part of a globally distributed team, responding to incidents and driving post-incident reviews That's responsibilities. Requirements (Functional Competencies Required): - Bachelor's degree in Computer Science, a related technical field, or equivalent practical experience - Proficiency in common programming and scripting languages, particularly Python, Bash, and Go - Understanding of network topologies, communication protocols (e.g., TCP/IP, HTTP/S, UDP, TLS), and enterprise-grade connectivity solutions - Kubernetes expertise, including cluster administration, RBAC, networking, workload management, and troubleshooting in production environments - Proven experience with Terraform for infrastructure provisioning and management - Knowledge of Google Cloud Platform services including GKE, VPC networking, Cloud DNS, Artifact Registry, Secret Manager, IAM, Gemini Code Assist, and Workload Identity - Clear understanding of how to use LLM-based code-assist tools to effectively build and troubleshoot software Preferred / Nice to Have: - Experience with GitOps methodologies and tools Also there is "MSGL-I4" maybe a code? Not needed. Also "Follow us on LinkedIn!" etc - boilerplate to remove. Also "Why Menlo?" culture description: Could be considered as part of About the role or maybe a separate section like "About Menlo". But not in headings list. Could incorporate into About the role as additional paragraph. We must not include EEO etc. So remove the paragraphs about qualified applicants, agencies, etc. Now schedule: The on-call rotation is already in responsibilities. But we could also create a Schedule heading to highlight on-call. However instruction: include a section ONLY when the posting has real, specific content for it. The posting does mention on-call rotation. So we could create Schedule section with that bullet. But then we would duplicate content if also in responsibilities. We need to preserve ALL substantive information; we can either keep it only in responsibilities and not create Schedule section, or we could move it to Schedule and remove from responsibilities. But we must not lose info. Better to keep it in responsibilities and not create Schedule section to avoid duplication. However the instruction says "Prefer a few substantive sections over many thin ones." So we can skip Schedule. Thus sections: About the role, Responsibilities, Requirements, Preferred (maybe Skills). Use headings: About the role, Responsibilities, Requirements, Skills (for preferred). Or we could use Qualifications for required and Skills for preferred. Let's decide: - About the role: includes mission, summary, outcomes. - Responsibilities: What you'll do. - Requirements: Functional Competencies Required. - Skills: Preferred/Nice to Have. We must not repeat job title. Good. Now format: Use

for each heading. Then content: use

for prose,

• for lists. We need to ensure we don't include any extra markup like or . Just fragment. Let's craft. About the role: combine paragraphs into maybe two

  elements. First paragraph: Menlo Security leader... etc. Second paragraph: Summary Platform Infrastructure Engineering... etc. Third paragraph: Outcomes & KPIs? Could be separate

  . We'll include outcomes as a paragraph. Responsibilities:

  • each bullet. Requirements:
    • each bullet. Skills:
      • each bullet (only one bullet for GitOps). Make sure to preserve all details exactly as in posting, but we can slightly rephrase? Must preserve all substantive information; do not invent or summarize away detail. We can keep the exact wording. Let's copy bullets exactly. Responsibilities bullets: - Design, deploy, and maintain VM and Kubernetes infrastructure on GCP and AWS across dozens of clusters spanning development, staging, and production environments in multiple regions - Build and maintain Infrastructure as Code using Terraform modules and Spacelift (or equivalent TACOS), provisioning networking, compute, storage, and security components, and implementing multi-layer configuration management workflows - Build and maintain observability solutions using Grafana Cloud, Prometheus/Mimir, and OTel collectors, designing dashboards and alerting rules across all platform components - Manage certificate lifecycle, DNS automation, ingress controllers, and service mesh networking with Cilium - Partner with peers and across Engineering, Product, Compliance, and Security teams to align on requirements and consult on capacity planning, disaster recovery, and architectural decisions - Identify and eliminate toil through automation — writing scripts, building CI/CD pipelines, and using AI-assisted coding tools to move faster - Participate in a 24x7 on-call rotation as part of a globally distributed team, responding to incidents and driving post-incident reviews Requirements bullets: - Bachelor's degree in Computer Science, a related technical field, or equivalent practical experience - Proficiency in common programming and scripting languages, particularly Python, Bash, and Go - Understanding of network topologies, communication protocols (e.g., TCP/IP, HTTP/S, UDP, TLS), and enterprise-grade connectivity solutions - Kubernetes expertise, including cluster administration, RBAC, networking, workload management, and troubleshooting in production environments - Proven experience with Terraform for infrastructure provisioning and management - Knowledge of Google Cloud Platform services including GKE, VPC networking, Cloud DNS, Artifact Registry, Secret Manager, IAM, Gemini Code Assist, and Workload Identity - Clear understanding of how to use LLM-based code-assist tools to effectively build and troubleshoot software Preferred bullet: - Experience with GitOps methodologies and tools Now About the role paragraphs: Paragraph1: "Menlo Security is the leader in Browser Security for human and agentic workforces. Our mission is to enable humans and agents to connect, communicate, and collaborate securely, without compromise. The Menlo Browser Security Platform protects organizations from cyberattacks by stopping threats across the web, documents, and email before they reach the user. With Menlo Agent Runtime Security (MARS), that protection now extends to the AI agents working alongside every employee. Menlo Security is trusted by major global businesses, including Fortune 500 companies and government agencies, to protect their most valuable asset, their data, and is backed by top-tier investors." Paragraph2: "Summary Platform Infrastructure Engineering builds and operates Menlo Security's Infrastructure Platform, enabling our customers to connect to the Internet without compromise. As a Platform Infrastructure Engineer, you'll join a globally distributed team of experienced engineers building and managing the company's core infrastructure services on a cloud-native platform built on Google Kubernetes Engine and VMs spanning multiple regions and environments. The team manages infrastructure as code with Terraform and Spacelift, deploys with Helm, and emphasizes security-first design, comprehensive observability, and multi-region resilience. The team also uses AI-assisted development and code-review tools, including Gemini Code Assist, as part of the standard engineering workflow, and this role is expected to use LLM-based tooling to build and troubleshoot infrastructure code efficiently." Paragraph3 (Outcomes & KPIs): "Outcomes & KPIs Key Outcome(s) Owned: Reliable, secure, and scalable infrastructure across GCP and AWS supporting Menlo's platform globally. Reduced operational toil and incident recurrence through automation and