Senior Systems Engineer

We need to output HTML fragment with sections: About the role? The posting includes "Why Join GEICO?" which is like intro. Then "Position Description", "Position Responsibilities", "Qualifications", "Experience", "Education", "Annual Salary". Also "The GEICO Pledge". We need to use

for section headings. Do not repeat job title. No Job ID. Remove boilerplate: EEO, equal opportunity, etc. Also remove application instructions (none). Remove duplicated lines. Keep substantive info. We need to decide which sections to include: About the role (maybe combine "Why Join GEICO?" and "Position Description"?). The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use headings like About the role, Responsibilities, Qualifications, Experience, Education, Pay, Benefits? But we should only include sections when posting has real specific content. The posting includes "Annual Salary" => Pay section. It includes benefits mention in GEICO Pledge: "Great Rewards: Competitive pay, benefits, and flexibility". But not detailed benefits. Might be too vague. Probably we should not create Benefits section unless specific benefits listed. The posting does not list specific benefits like health insurance, 401k, etc. So we skip Benefits. Schedule: not mentioned. Skills: could be under Qualifications or Requirements. We can have a Qualifications section that includes experience, skills, etc. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose appropriate headings. We need to preserve all substantive information. So we need to include the intro "Why Join GEICO?" maybe as About the role. Also Position Description. Could combine. We need to output only HTML fragment, no /. Use

headings,

• for lists,

  for prose. We must not include filler like "commensurate with experience". Not present. We need to remove duplicated lines: The Qualifications list repeats similar items as Experience? Actually there is a "Qualifications" bullet list then "Experience" list with similar items. We need to preserve all but avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep both but maybe they are overlapping; we should not remove unless it's duplicate exact same line. Let's see: Qualifications bullet list: - Experience with monitoring, logging, alerting and observability in cloud environments - Experience with tools like Grafana and Promethius - Experience with performance tuning - Familiarity with containerization technologies (e.g., Docker, Kubernetes) - Strong experience with Ansible for automation and configuration management - Hands-on experience with CI/CD tools and workflows (e.g., Jenkins, GitHub Actions, ArgoCD) - Proficiency in Python programming or scripting - Good understanding of networking and security best practices in cloud deployments - Excellent troubleshooting and problem-solving skills - Strong communication and collaboration abilities - Experience with OpenStack administration and operations a plus Experience list: - Experience 4+ years of professional experience in cloud engineering, platform administration, or infrastructure automation - 4+ years of experience with OpenStack or similar cloud platforms - 4+ years of experience with Python and Ansible - 4+ years of experience with monitoring and observability systems - 4+ years of experience with containerization technologies - Experience with hybrid or multi-cloud environments (AWS, GCP, Azure, or on-premises) is a plus - Experience with low level virtualization technologies (QEMU/libvirt) is a plus These are not exact duplicates; they add years and some extra. So keep both. Education: Bachelor’s degree in Computer Science, Information Systems, or equivalent education or work experience. Pay: Annual Salary $100,000.00 - $215,000.00 plus note. We also have GEICO Pledge section with four points. Could be under Benefits? But it's more about culture. Could be a section "About GEICO" or "Company Overview". The instruction says we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The GEICO Pledge is about company values; maybe we can put under About the role or a separate section like "About GEICO". But the instruction only gave examples; we can use other headings if appropriate? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples but not exclusive? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings where applicable. So we should map content to those headings. Thus we need sections: About the role (intro + position description), Responsibilities (list), Qualifications (list), Experience (list), Education (maybe under Qualifications? but we can have a separate Education heading? Not in examples but could be under Qualifications. However we have a separate Education paragraph; we could put it under Qualifications as part of list? But it's not a list item; it's a sentence. Could be a

  under Qualifications. Or we could create a separate heading "Education". The examples didn't list Education but we could still use

  for Education? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use

  for section headings (e.g....)". It might be okay to use other headings, but safer to stick to those. We could incorporate Education into Qualifications as a

  after the list. Pay: we have Pay section. Schedule: none. Benefits: we have GEICO Pledge mentions benefits but not specific; maybe we can skip Benefits. Thus sections: About the role, Responsibilities, Qualifications, Pay. But we also need to include Experience and Education. Could put Experience under Qualifications as a sub-list? But the instruction says preserve all substantive information; we can still have a separate

  for Experience if we want, but not in examples. However we could treat Experience as part of Qualifications (since qualifications often include experience). The posting separates Qualifications and Experience; but we can combine them under Qualifications heading, preserving both lists. That would satisfy preserving all info. Similarly Education can be a

  under Qualifications. Thus final sections: About the role, Responsibilities, Qualifications, Pay. Let's craft. About the role: combine "Why Join GEICO?" and "Position Description". We'll put as

  paragraphs. Responsibilities: list from "Position Responsibilities". Use

  • . Qualifications: include the Qualifications bullet list, Experience list, Education sentence. We'll make a
    for Qualifications bullet list, then another
    for Experience list, then a

    for Education. Pay:

    with salary range and note. We must not include boilerplate like EEO, GEICO Pledge? Actually GEICO Pledge is substantive but maybe we can incorporate into About the role as a paragraph describing culture? The Pledge includes "Great Company, Great Culture, Great Rewards, Great Careers". That's substantive. We should include it. Could be part of About the role. Thus About the role will include the intro paragraph, position description, and the GEICO Pledge paragraph. Let's extract text: "Why Join GEICO? At GEICO, we offer a rewarding career where your ambitions are met with endless possibilities. Every day we honor our iconic brand by offering quality coverage to millions of customers and being there when they need us most. We thrive on relentless innovation to exceed our customers' expectations while making a real impact on local communities nationwide. Founded in 1936, GEICO is a member of the Berkshire Hathaway family of companies and one of the largest auto insurers in the United States. When you join our company, we want you to feel valued, supported, and proud to work here. That's why we offer the GEICO Pledge: Great Company, Great Culture, Great Rewards, and Great Careers." Then "Position Description Our Senior Engineer works with our Distinguished Engineer and Staff Engineers to design, deploy, and maintain OpenStack-based environments. You will help lead improve and expand the observability, performance and operability of our private cloud deployments" Note there is a typo: "help lead improve". We'll keep as is. Then "The GEICO Pledge Great Company: Protecting customers through life’s twists and turns with innovation and integrity. Great Careers: Personalized development programs, mentorship, and certification assistance. Great Culture: Inclusive and collaborative culture rooted in shared success. Great Rewards: Competitive pay, benefits, and flexibility to support your well-being and future." We can include that as a paragraph. Now Responsibilities list: - Improve on monitoring, observability and performance of deployed systems - Design, deploy, and manage OpenStack-based cloud environments - Develop and maintain automation scripts and playbooks using Python, Ansible, and GitHub Workflows - Implement and optimize CI/CD pipelines for infrastructure and application delivery - Support containerization initiatives (e.g., Docker, Kubernetes) - Troubleshoot and resolve issues in cloud and automation workflows - Collaborate with development, operations, and security teams - Share best practices and improve processes within and across teams - Participate in on-call and operational support as needed Qualifications bullet list: - Experience with monitoring, logging, alerting and observability in cloud environments - Experience with tools like Grafana and Promethius - Experience with performance tuning - Familiarity with containerization technologies (e.g., Docker, Kubernetes) - Strong experience with Ansible for automation and configuration management - Hands-on experience with CI/CD tools and workflows (e.g., Jenkins, GitHub Actions, ArgoCD) - Proficiency in Python programming or scripting - Good understanding of networking and security best practices in cloud deployments - Excellent troubleshooting and problem-solving skills - Strong communication and collaboration abilities - Experience with OpenStack administration and operations a plus Experience list: - 4+ years of professional experience in cloud engineering, platform administration, or infrastructure automation - 4+ years of experience with OpenStack or similar cloud platforms - 4+ years of experience with Python and Ansible - 4+ years of experience with monitoring and observability systems - 4+ years of experience with containerization technologies - Experience with hybrid or multi-cloud environments (AWS, GCP, Azure, or on-premises) is a plus - Experience with low level virtualization technologies (QEMU/libvirt) is a plus Education: Bachelor’s degree in Computer Science, Information Systems, or equivalent education or work experience. Pay: Annual Salary $100,000.00 - $215,000.00 The above annual salary range is a general guideline. Multiple factors are taken into consideration to arrive at the final hourly rate/ annual salary to be offered to the selected candidate. Factors include, but are not limited to, the scope and responsibilities of the role, the selected candidate’s work experience, education and training, the work location as well as market and business considerations. GEICO will consider sponsoring a new qualified applicant for employment authorization for this position. We need to output HTML fragment only. Let's construct:

    About the role

    Why Join GEICO? At GEICO, we offer a rewarding career where your ambitions are met with endless possibilities. Every day we honor our iconic brand by offering quality