Senior Staff Engineer

We need to output HTML fragment with sections: About the role? The posting includes "Why Join GEICO?" which is like intro. Then "The Role", "Scope & Impact", "What You’ll Do", "Required", "Strongly Preferred", "Annual Salary", "The GEICO Pledge". Also "Why Join GEICO?" could be considered "About the role"? Actually "Why Join GEICO?" is more about company overview. Could map to "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to those headings where appropriate. We should not repeat job title. We need to include sections only when posting has real specific content. We have: - Why Join GEICO? (company overview) could be "About the role"? Actually "About the role" is about the role itself, not company. But we could treat "Why Join GEICO?" as "About the role"? Might be better to treat as "About the role" or maybe we can omit if not matching. However we need to preserve all substantive information. So we need to include that content somewhere. Could put under

About the role

with paragraphs describing GEICO, the pledge, etc. - The Role: description of role responsibilities. Could go under

Responsibilities

or maybe "What You’ll Do". The posting has "What You’ll Do" with bullet points. So we can map that to Responsibilities. - Scope & Impact: maybe also part of Responsibilities or separate? Could be under Responsibilities as well. - Required: qualifications =>

Requirements

- Strongly Preferred: could be

Qualifications

or Skills. Since they are "Strongly Preferred", we could put under

Qualifications

or

Skills

. The instruction list includes Qualifications and Skills. We could put Required under Requirements, Strongly Preferred under Qualifications (or Skills). Let's decide: Requirements = mandatory; Qualifications = preferred; Skills = maybe specific tech skills. But we have both required and preferred. Could combine: Requirements (mandatory) and Qualifications (preferred). Or we could have Requirements and Skills. - Annual Salary: Pay section =>

Pay

- The GEICO Pledge: could be Benefits? Actually it's about company culture and rewards. Could be Benefits or maybe we could create a Benefits section? The pledge includes "Great Company, Great Careers, Great Culture, Great Rewards". That's more about benefits and culture. Could be Benefits. We must not include boilerplate like EEO, etc. Remove that. We must not include duplicated lines. We must not include application instructions. We must not include cookie/navigation/legal. We must not include "At this time, GEICO will not sponsor a new applicant for employment authorization for this position." That's maybe not boilerplate but it's a condition; it's substantive? It's about sponsorship. Might be considered relevant but it's not a heading; we could fold into a short

under Pay or maybe under Requirements? Probably better to include as a short paragraph under Pay or maybe under a generic "Additional Information". But we are limited to headings list; we could add a

after Pay. We must not invent or summarize away detail. Keep all substantive info. Let's extract content: Why Join GEICO? paragraph: "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 The Role paragraph: "The Role We are seeking a Senior Staff Software Engineer to provide technical leadership for critical software development systems while establishing a strong culture of ownership. This role operates at the intersection of architecture, strategic influence, and innovation. You will be responsible for the technical direction of multiple products and systems, and shaping how GEICO Tech develops software and delivers the impact of their work. This Is a Role For Engineers Who Craft thoughtfully designed, scalable systemsDefine culture from team to companyMentor and grow engineers within and across teamsLeverage technology to tackle any challenge" Note there is missing punctuation but we keep as is. Scope & Impact: "Scope & Impact At the Senior Staff level, success is measured by durable impact across and beyond the Developer Engineer org, while leading and developing software. You will build systems while accelerating the growth and transformation of GEICO Tech." What You’ll Do: "Enterprise Technical Leadership Own the long‑term technical direction for our tools as GEICO’s management plane for team structure and roadmap delivery.Define and evolve system orchestration patterns that scale across diverse application architectures and maturity levels.Make architectural tradeoffs balancing reliability, operability, and development speed.Integrate across vendor and bespoke platforms to unify developer experiences. Culture of Ownership – Software Development Develop and mature software development and system ownership across TechCodify team standards and practices into source of truth for team organizationConnect team-based access across agentic development to permissions, to provide seamless, high velocity development experiences Culture of Ownership – Outcomes & Impact Lead how organizations across Tech, from pricing to Platform as a Service, plan and execute on work in an AI-first eraConnect unstructured and unstructured data to quantify impact of technology & AI against business goals and KPIsCultivate engineering culture that recognizes engineers for the success and reliability of their products" Required: "What We’re Looking For 10+ years of experience building and operating large‑scale distributed systems.Deep expertise in fault tolerance, resilience, and recovery design.Proven track record of org‑level technical leadership beyond a single team.Strong ability to reason about and design for partial failure.Experience shaping shared platforms or frameworks used by many teams." Strongly Preferred: "Strongly Preferred Experience with durable execution, or workflow orchestrationExperience with Golang, microservices, Kubernetes; front end experience nice to haveHands‑on experience building and improving developer tooling.Data-driven decision making, from observability to success metrics.Ability to translate low‑level technical risks into clear business and reliability outcomes." Annual Salary: "Annual Salary $130,000.00 - $260,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. At this time, GEICO will not sponsor a new applicant for employment authorization for this position." The GEICO Pledge: "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 need to remove EEO boilerplate after that. Now produce HTML. We'll have sections:

About the role

with paragraphs: the Why Join GEICO? text plus maybe the GEICO Pledge? Actually the pledge could be Benefits. But we could put the pledge under Benefits. Better: About the role: include company overview and why join. Responsibilities: include The Role, Scope & Impact, What You’ll Do (maybe combine). Could be multiple paragraphs. Requirements: Required. Qualifications: Strongly Preferred. Pay: Annual Salary. Benefits: The GEICO Pledge. We must not include empty sections. Let's craft. We need to preserve all substantive info, not lose any. We'll need to ensure we don't duplicate lines. We'll need to format paragraphs with

. Lists: we have bullet-like content but not explicit bullet list; they are sentences concatenated. Could we convert to

• ? The instruction: Use
  • for any list of duties/requirements/benefits. The posting does not have explicit bullet list markers but contains lists of items separated by periods. We could treat each sentence as a list item? Might be overkill. Safer to keep as paragraphs (

    ) because they are not explicitly list. However the instruction says use

    • for any list of duties/requirements/benefits. The content includes lists like "10+ years of experience building and operating large‑scale distributed systems.Deep expertise in fault tolerance, resilience, and recovery design.Proven track record of org‑level technical leadership beyond a single team.Strong ability to reason about and design for partial failure.Experience shaping shared platforms or frameworks used by many teams." That's a list of requirements. Could be formatted as
      • . Similarly for duties. We need to decide: Should we convert to list? The instruction says use
        • for any list of duties/requirements/benefits. So we should parse those into list items. Thus we need to split each requirement into separate
        • . Similarly for duties. Let's extract requirements list: - 10+ years of experience building and operating large‑scale distributed systems. - Deep expertise in fault tolerance, resilience, and recovery design. - Proven track record of org‑level technical leadership beyond a single team. - Strong ability to reason about and design for partial failure. - Experience shaping shared platforms or frameworks used by many teams. Strongly Preferred list: - Experience with durable execution, or workflow orchestration - Experience with Golang, microservices, Kubernetes; front end experience nice to have - Hands‑on experience building and improving developer tooling - Data-driven decision making, from observability to success metrics - Ability to translate low‑level technical risks into clear business and reliability outcomes Duties list from What You’ll Do and Scope & Impact and The Role. We have many statements; we could combine into a list. Let's extract duties: From The Role: "provide technical leadership for critical software development systems while establishing a strong culture of ownership." "operates at the intersection of architecture, strategic influence, and innovation." "responsible for the technical direction of multiple products and systems, and shaping how GEICO Tech develops software and delivers the impact of their work." "Craft thoughtfully designed, scalable systems" "Define culture from team to company" "Mentor and grow engineers within and across teams" "Leverage technology to tackle any challenge" From Scope & Impact: "success is measured by durable impact across and beyond the Developer Engineer org, while leading and developing software." "You will build systems while accelerating the growth and transformation of GEICO Tech." From What You’ll Do: many bullet-like statements: - Own the long‑term technical direction for our tools as GEICO’s management plane for team structure and roadmap delivery. - Define and evolve system orchestration patterns that scale across diverse application architectures and maturity levels. - Make architectural tradeoffs balancing reliability, operability, and development speed. - Integrate across vendor and bespoke platforms to unify developer experiences. - Develop and mature software development and system ownership across Tech - Codify team standards and practices into source of truth for team organization - Connect team-based access across agentic development to permissions, to provide seamless, high velocity development experiences - Lead how organizations across Tech, from pricing to Platform as a Service, plan and execute on work in an AI-first era - Connect unstructured and un