Staff Software Engineer
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We need to preserve all substantive info, remove boilerplate like EEO, legal, etc. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
We need to decide sections: Possibly "About the role" (position summary), "Responsibilities", "Qualifications" (maybe includes experience, education), "Skills" (maybe technical skills), "Pay" (salary range), "Benefits" (GEICO Pledge mentions benefits?), "Schedule"? Not present. So we should not include Schedule if not present.
We need to avoid placeholder like "commensurate with experience". Not present.
We need to include Pay section because salary range is given.
Benefits: The posting mentions GEICO Pledge with Great Company, Great Culture, Great Rewards, Great Careers. Also "Great Rewards: Competitive pay, benefits, and flexibility". So we can include Benefits section summarizing that.
We must not repeat job title as heading. The page already shows it, so we don't add heading for title.
We need to use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information. So we need to include the "Why Join GEICO?" paragraph as maybe About the role? Or we could have an "About the role" section containing that summary plus position summary.
Let's parse content:
- Why Join GEICO? paragraph: description of company, mission, GEICO Pledge.
- Position Summary: description of role.
- Position Description: description of Staff Engineers work.
- Position Responsibilities: bullet list (starting with "As a Staff Engineer on the System Catalog & CMDB team, you will:" then list items).
- Qualifications: list of qualifications (technical skills, experience, leadership, etc.)
- Education: Bachelor's degree...
- Annual Salary: $110,000 - $230,000 plus note.
- The GEICO Pledge: bullet points (Great Company, Great Careers, Great Culture, Great Rewards) each with description.
- EEO etc: remove.
We need to avoid duplication: The "Why Join GEICO?" and "The GEICO Pledge" may overlap; but we should keep both as they are substantive.
We need to decide sections:
- About the role: could combine "Why Join GEICO?" and "Position Summary" and "Position Description". But we need to avoid too thin sections. Maybe we make one About the role section containing the narrative about company and role summary.
- Responsibilities: the bullet list under Position Responsibilities.
- Qualifications: the bullet list under Qualifications (including experience, education maybe separate? Education could be part of Qualifications or separate section Education. But we have no explicit Education heading in allowed list; we could put Education under Qualifications or as its own section if we want but allowed headings list includes Qualifications, Skills, Benefits, Pay, Schedule. Education not listed, but we can still include as part of Qualifications or maybe as a separate section but not in allowed list? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying 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 only. So we should map content to those headings. Education could go under Qualifications. Skills could be separate if we want to list technical skills. But Qualifications already includes skills. Might be okay to have Qualifications and Skills separate but we need to avoid thin sections. Perhaps we combine technical skills under Skills section, and experience/leadership under Qualifications. However the Qualifications section already includes both technical and experience. Could split: Qualifications (experience, education) and Skills (technical). But we need to avoid filler. Let's see content: Qualifications list includes many technical skills: Fluency in Go, Python, Typescript, React; SQL/NoSQL; graph databases; data modeling; automated discovery; API design; networking; hybrid cloud; infrastructure automation; leadership; problem-solving; visionary thinker; experience years; etc. That's a mix. Could treat all as Qualifications. Skills section maybe not needed.
We have Benefits: GEICO Pledge details.
Pay: salary range.
Schedule: not present, so omit.
We also need to include maybe "About the role" heading with company description and position summary.
Let's craft HTML:
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 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.
Position Summary: GEICO is seeking an experienced Staff Software Engineer with a passion for building high-performance, low-maintenance, and authoritative platforms that give the entire organization a single source of truth for its technology landscape. In this role you will own the strategy, architecture, and engineering of our System Catalog and Configuration Management Database (CMDB) — the connective tissue that maps every service, application, infrastructure component, and the relationships between them. You will help drive our insurance business transformation as we transition from a traditional IT model to a modern tech organization with engineering excellence as its mission, while co-creating a culture of psychological safety and continuous improvement.
Position Description: Our Staff Engineers work with other engineers at all levels to innovate and build new systems, improve and enhance existing ones, and identify new opportunities to apply their knowledge to solve critical problems. As the technical leader for the System Catalog and CMDB, you will define and execute a roadmap that turns configuration data from a static inventory into a living, accurate, API-driven product that powers incident response, change management, dependency analysis, security, and cost visibility. The ideal candidate combines deep software engineering expertise with a strong understanding of data modeling, service mapping, automated discovery, and architecture principles to design resilient systems that keep configuration data trustworthy at enterprise scale.
Then Responsibilities:
Responsibilities
- Develop and drive the overall strategy for the System Catalog and CMDB, aligning it with the organization’s business goals, operating model, and technology processes.
- Provide thought leadership in configuration management, service cataloging, and data governance, staying ahead of industry trends and emerging technologies.
- Define and own the configuration data model — classes, attributes, relationships, and dependency mappings — ensuring it is extensible, consistent, and aligned to a common taxonomy.
- Establish and enforce CMDB data governance, including CI lifecycle management, ownership, reconciliation rules, and measurable data-quality and completeness standards.
- Lead the design and architecture of resilient, scalable catalog and CMDB systems, considering both on-premises and cloud-based solutions.
- Design and implement automated discovery and service mapping so the CMDB stays accurate with minimal manual intervention across hybrid and multi-cloud environments.
- Evaluate, select, and implement cutting-edge technologies and tools to enhance catalog and CMDB capabilities, including processes, compliance, and visibility.
- Work closely with executive leadership, IT teams, and other stakeholders to communicate the value of accurate configuration data and foster a culture of ownership.
- Be a role model and mentor, coaching and strengthening the technical expertise of our engineering and product community, and influencing and educating executives.
- Analyze cost and forecast, incorporating them into business plans, and support resource requirements while measuring outcomes to ensure desired results.
Qualifications:
Qualifications
- Fluency and specialization in software development and best practices using modern programming languages such as Go, Python, Typescript and React.
- Strong understanding of SQL and NoSQL databases, and experience with graph databases for modeling configuration items, relationships, and dependencies.
- Experience with data modeling, taxonomy/ontology design, and master-data or reference-data management for large, heterogeneous environments.
- Experience building data-quality, reconciliation, and drift-detection processes that keep configuration data accurate over time.
- Experience designing automated discovery and service-mapping pipelines across on-prem, hybrid, and multi-cloud estates.
- Strong API design experience (REST and/or GraphQL), including versioning, schema governance, and building catalog data as a consumable platform service.
- Experience working with networking, caches, key/value stores, load balancing, queues, DNS, and CDN as configuration items to be modeled and tracked.
- In-depth knowledge of hybrid cloud architecture, IaaS and PaaS technologies, container orchestration platforms (e.g., Kubernetes), and observability.
- Experience with infrastructure automation, tooling, and configuration management frameworks (e.g., Ansible, Terraform).
- Excellent leadership and communication skills, with a passion for mentoring and fostering professional growth.
- Strong problem-solving and analytical abilities, with a keen eye for detail and a drive for operational excellence.
- Visionary thinker able to anticipate future challenges and opportunities, with a proven record of leading and building software in large, complex organizations.
- Experience: 10+ years of professional experience in software engineering; 8+ years of experience with architecture and design; 6+ years of experience with open-source frameworks; 4+ years of experience with AWS, GCP, Azure, or another cloud service; Demonstrated experience building or owning a system catalog, service catalog, or configuration management at enterprise scale.
- Education: Bachelor's degree in computer science, Information Systems, or equivalent education or work experience.
Benefits:
Benefits
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.
Pay:
Pay
Annual Salary: $110,000.00 - $230,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.
We should remove EEO etc. Already omitted.
Check for any duplicated lines: we have not duplicated.
Check for any placeholder like
- for any list of duties/requirements/benefits. Use
for prose. We need to preserve all substantive information. So we need to include the "Why Join GEICO?" paragraph as maybe About the role? Or we could have an "About the role" section containing that summary plus position summary. Let's parse content: - Why Join GEICO? paragraph: description of company, mission, GEICO Pledge. - Position Summary: description of role. - Position Description: description of Staff Engineers work. - Position Responsibilities: bullet list (starting with "As a Staff Engineer on the System Catalog & CMDB team, you will:" then list items). - Qualifications: list of qualifications (technical skills, experience, leadership, etc.) - Education: Bachelor's degree... - Annual Salary: $110,000 - $230,000 plus note. - The GEICO Pledge: bullet points (Great Company, Great Careers, Great Culture, Great Rewards) each with description. - EEO etc: remove. We need to avoid duplication: The "Why Join GEICO?" and "The GEICO Pledge" may overlap; but we should keep both as they are substantive. We need to decide sections: - About the role: could combine "Why Join GEICO?" and "Position Summary" and "Position Description". But we need to avoid too thin sections. Maybe we make one About the role section containing the narrative about company and role summary. - Responsibilities: the bullet list under Position Responsibilities. - Qualifications: the bullet list under Qualifications (including experience, education maybe separate? Education could be part of Qualifications or separate section Education. But we have no explicit Education heading in allowed list; we could put Education under Qualifications or as its own section if we want but allowed headings list includes Qualifications, Skills, Benefits, Pay, Schedule. Education not listed, but we can still include as part of Qualifications or maybe as a separate section but not in allowed list? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying 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 only. So we should map content to those headings. Education could go under Qualifications. Skills could be separate if we want to list technical skills. But Qualifications already includes skills. Might be okay to have Qualifications and Skills separate but we need to avoid thin sections. Perhaps we combine technical skills under Skills section, and experience/leadership under Qualifications. However the Qualifications section already includes both technical and experience. Could split: Qualifications (experience, education) and Skills (technical). But we need to avoid filler. Let's see content: Qualifications list includes many technical skills: Fluency in Go, Python, Typescript, React; SQL/NoSQL; graph databases; data modeling; automated discovery; API design; networking; hybrid cloud; infrastructure automation; leadership; problem-solving; visionary thinker; experience years; etc. That's a mix. Could treat all as Qualifications. Skills section maybe not needed. We have Benefits: GEICO Pledge details. Pay: salary range. Schedule: not present, so omit. We also need to include maybe "About the role" heading with company description and position summary. Let's craft HTML:
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 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.
Position Summary: GEICO is seeking an experienced Staff Software Engineer with a passion for building high-performance, low-maintenance, and authoritative platforms that give the entire organization a single source of truth for its technology landscape. In this role you will own the strategy, architecture, and engineering of our System Catalog and Configuration Management Database (CMDB) — the connective tissue that maps every service, application, infrastructure component, and the relationships between them. You will help drive our insurance business transformation as we transition from a traditional IT model to a modern tech organization with engineering excellence as its mission, while co-creating a culture of psychological safety and continuous improvement.
Position Description: Our Staff Engineers work with other engineers at all levels to innovate and build new systems, improve and enhance existing ones, and identify new opportunities to apply their knowledge to solve critical problems. As the technical leader for the System Catalog and CMDB, you will define and execute a roadmap that turns configuration data from a static inventory into a living, accurate, API-driven product that powers incident response, change management, dependency analysis, security, and cost visibility. The ideal candidate combines deep software engineering expertise with a strong understanding of data modeling, service mapping, automated discovery, and architecture principles to design resilient systems that keep configuration data trustworthy at enterprise scale.
Then Responsibilities:Responsibilities
- Develop and drive the overall strategy for the System Catalog and CMDB, aligning it with the organization’s business goals, operating model, and technology processes.
- Provide thought leadership in configuration management, service cataloging, and data governance, staying ahead of industry trends and emerging technologies.
- Define and own the configuration data model — classes, attributes, relationships, and dependency mappings — ensuring it is extensible, consistent, and aligned to a common taxonomy.
- Establish and enforce CMDB data governance, including CI lifecycle management, ownership, reconciliation rules, and measurable data-quality and completeness standards.
- Lead the design and architecture of resilient, scalable catalog and CMDB systems, considering both on-premises and cloud-based solutions.
- Design and implement automated discovery and service mapping so the CMDB stays accurate with minimal manual intervention across hybrid and multi-cloud environments.
- Evaluate, select, and implement cutting-edge technologies and tools to enhance catalog and CMDB capabilities, including processes, compliance, and visibility.
- Work closely with executive leadership, IT teams, and other stakeholders to communicate the value of accurate configuration data and foster a culture of ownership.
- Be a role model and mentor, coaching and strengthening the technical expertise of our engineering and product community, and influencing and educating executives.
- Analyze cost and forecast, incorporating them into business plans, and support resource requirements while measuring outcomes to ensure desired results.
Qualifications
- Fluency and specialization in software development and best practices using modern programming languages such as Go, Python, Typescript and React.
- Strong understanding of SQL and NoSQL databases, and experience with graph databases for modeling configuration items, relationships, and dependencies.
- Experience with data modeling, taxonomy/ontology design, and master-data or reference-data management for large, heterogeneous environments.
- Experience building data-quality, reconciliation, and drift-detection processes that keep configuration data accurate over time.
- Experience designing automated discovery and service-mapping pipelines across on-prem, hybrid, and multi-cloud estates.
- Strong API design experience (REST and/or GraphQL), including versioning, schema governance, and building catalog data as a consumable platform service.
- Experience working with networking, caches, key/value stores, load balancing, queues, DNS, and CDN as configuration items to be modeled and tracked.
- In-depth knowledge of hybrid cloud architecture, IaaS and PaaS technologies, container orchestration platforms (e.g., Kubernetes), and observability.
- Experience with infrastructure automation, tooling, and configuration management frameworks (e.g., Ansible, Terraform).
- Excellent leadership and communication skills, with a passion for mentoring and fostering professional growth.
- Strong problem-solving and analytical abilities, with a keen eye for detail and a drive for operational excellence.
- Visionary thinker able to anticipate future challenges and opportunities, with a proven record of leading and building software in large, complex organizations.
- Experience: 10+ years of professional experience in software engineering; 8+ years of experience with architecture and design; 6+ years of experience with open-source frameworks; 4+ years of experience with AWS, GCP, Azure, or another cloud service; Demonstrated experience building or owning a system catalog, service catalog, or configuration management at enterprise scale.
- Education: Bachelor's degree in computer science, Information Systems, or equivalent education or work experience.
Benefits
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.
Pay
Annual Salary: $110,000.00 - $230,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.
We should remove EEO etc. Already omitted. Check for any duplicated lines: we have not duplicated. Check for any placeholder like