GIS Business Information Specialist
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for lists of duties/requirements/benefits, and
for prose
3. Do NOT repeat the job title as a heading
4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it
5. Preserve ALL substantive information; do NOT invent or summarize away detail
6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text
8. Never create Pay/Schedule/Benefits sections unless the posting actually states them
9. Prefer a few substantive sections over many thin ones
10. Output ONLY the HTML fragment — no /, no markdown code fences
Let me analyze the job posting content:
The posting appears to be for a "GIS Business Information Specialist" role at Nationwide, but there's also a "Specialist, Business Information" role described. It seems like there might be two roles mixed together or a combined posting. Let me parse carefully.
First part: "If you're passionate about helping people protect what matters most..." - this is an intro about Nationwide's Property and Casualty team.
Then: "The GIS Business Information Specialist supports Nationwide's geographical management..." - this describes the GIS Business Information Specialist role with specific responsibilities.
Then there's a "Skills" section with bullet points.
Then: "This role does not qualify for employer-sponsored work authorization..." - metadata.
Then: "Job Description Summary" - describes "Specialist, Business Information" role.
Then: "Job Description Key Responsibilities:" - list of responsibilities.
Then: "Reporting Relationships:" - reports to Manager/Director.
Then: "Typical Skills And Experiences" - Education, Experience, Knowledge, Abilities and Skills.
Then: "Staffing Exceptions..." - HR info.
Then: "Values:" - Nationwide values.
Then: "Job Conditions" - Overtime Eligibility, Working Conditions, ADA.
Then: "We currently anticipate accepting applications until 10/30/2026..." - application deadline.
Then: "Benefits" - list of benefits.
Then: EEO statement, location info, Iowa smoking statement, NY law info, note to employment agencies, compensation info.
I need to structure this into semantic HTML with appropriate sections. The posting seems to have two roles: GIS Business Information Specialist and Specialist, Business Information. But they might be the same role with different descriptions? The title at the top isn't explicitly stated but the first role is "GIS Business Information Specialist". The second is "Specialist, Business Information". The compensation section says "The national salary range for Specialist, Business Information". So likely the job title is "Specialist, Business Information" with a GIS focus.
I should create sections based on the content:
- About the role (intro)
- Responsibilities (for GIS Business Information Specialist)
- Skills (for GIS role)
- Responsibilities (for Specialist, Business Information) - but maybe combine? The posting has two sets of responsibilities. I'll need to include both but perhaps under separate subsections or combine if they're for the same role. The first set is under "Mapping and Territory Definition Delivery" and "Process Improvement and Automation". The second set is under "Job Description Key Responsibilities:". They seem distinct but for the same position? The first is more GIS-specific, the second is general Business Information Specialist. Since the posting includes both, I should include both.
- Qualifications (Education, Experience, Knowledge, Abilities and Skills)
- Benefits (listed)
- Pay (salary ranges given)
- Schedule (Working Conditions mentions "Occasional extended and non-standard hours", Overtime Eligibility: Not Eligible (Exempt))
Also metadata: "This role does not qualify for employer-sponsored work authorization..." and application deadline.
I'll fold minor metadata into a short
at the end or in an appropriate section.
Now, I must not include EEO, equal opportunity, scam warnings, note to employment agencies, Iowa smoking statement, NY law info, etc. Those are boilerplate.
I'll create sections only where there is real content.
Let me outline:
1. About the role (intro paragraph)
2. Responsibilities (GIS-specific) - with two subsections: Mapping and Territory Definition Delivery, Process Improvement and Automation
3. Skills (GIS-specific)
4. Responsibilities (General Business Information Specialist) - from Key Responsibilities
5. Qualifications (Education, Experience, Knowledge, Abilities and Skills)
6. Job Conditions (Overtime, Working Conditions, ADA)
7. Benefits
8. Pay (salary ranges)
9. Schedule (maybe combine with Job Conditions? But Schedule is a separate heading type. The rules mention Schedule as a possible heading. Working Conditions includes schedule info. I'll create a Schedule section if there's specific schedule info. The posting says "Occasional extended and non-standard hours based on business information needs." That's schedule-related. Also "Overtime Eligibility: Not Eligible (Exempt)". I'll include in Job Conditions or separate Schedule. I'll put in Job Conditions as it's part of conditions.
But the rules say use
for section headings including Schedule. I'll create a Schedule section if there's specific schedule info. There is: "Working Conditions: Normal office environment. Extended periods of personal computer usage and report/information verification. Occasional extended and non-standard hours based on business information needs." That's schedule and conditions. I'll create a "Job Conditions" section (not a standard heading but I can use for "Job Conditions") and include overtime, working conditions, ADA. The rules list "Schedule" as a possible heading. I'll use "Job Conditions" as heading.
The rules say: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I should use those standard headings where appropriate. I can use "Job Conditions" but maybe "Schedule" and "Requirements" etc. I'll map:
- About the role
- Responsibilities (maybe two sections: GIS Responsibilities and General Responsibilities? But better to combine under one Responsibilities heading with sub-lists? The rules don't forbid subheadings but they said use for section headings. I could use for subsections but not required. I'll keep it simple: one Responsibilities section with two subsections using or just separate lists with descriptive text. However, the rules say use for section headings. I'll use for main sections only. For subsections, I can use or just bold text. But the output should be semantic HTML. I'll use for subsections within Responsibilities.
But the instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other headings. I'll use for main sections, and for sub-sections if needed.
Let's structure:
About the role
...intro paragraph...
Responsibilities
Mapping and Territory Definition Delivery
- ...
Process Improvement and Automation
- ...
General Business Information Specialist Duties
- ...
Skills
- ...
Qualifications
Education
...
Experience
...
Knowledge, Abilities and Skills
- ...
Job Conditions
Overtime Eligibility: Not Eligible (Exempt)
Working Conditions: Normal office environment. Extended periods of personal computer usage and report/information verification. Occasional extended and non-standard hours based on business information needs.
ADA: The above statements cover what are generally believed to the principal and essential function of this job. Specific circumstances may allow or require some associated assigned to the job to perform a somewhat different combination of duties.
Benefits
- ...
Pay
National salary range: $79,500.00-$148,500.00
Expected starting salary range: $79,500.00 - $119,500.00
Note: Nationwide pays on a geographic-specific salary structure and placement within the actual starting salary range for this position will be determined by a number of factors including the skills, education, training, credentials and experience of the candidate; the scope, complexity and location of the role as well as the cost of labor in the market; and other conditions of employment. If a Sales job, Sales Incentives, based on performance goals are possible in addition to this range. Note on Compensation for Part-Time Roles: Please be aware that the salary ranges listed below reflect full-time compensation. Actual compensation may be prorated based on the number of hours worked relative to a full-time schedule.
Additional Information
This role does not qualify for employer-sponsored work authorization. Nationwide does not participate in the STEM OPT Extension program.
Applications accepted until 10/30/2026, though the posting may close sooner if a strong candidate slate is identified.
This position could be filled within any of the lower 48 U.S. states.
I should not include the reporting relationships, staffing exceptions, values, EEO, note to agencies, Iowa smoking, NY law, etc.
Now, ensure I preserve all substantive information. The responsibilities lists are long; I need to include each bullet point.
Let me extract the GIS responsibilities:
Mapping and Territory Definition Delivery:
- Lead the intake, interpretation, preparation, validation, and handoff of GIS maps and territory-related deliverables
- Translate business, pricing, underwriting, and product needs into clear GIS maps and related requirements
- Define expected results and test or validate map outputs and underlying data for completeness, accuracy, consistency, and alignment with approved territory definitions
- Coordinate dependencies with GIS IT and other technology partners for data loads, production updates, releases, and issue resolution
- Maintain visibility to work in progress, upcoming deadlines, risks, and required stakeholder decisions
Process Improvement and Automation:
- Develop understanding of end-to-end GIS processes, from source geography and vendor data, through map and territory production, GIS IT handoffs, testing and release, to downstream use in Personal Lines rating and underwriting systems
- Create and maintain documentation for critical GIS data flows, mapping processes, and handoffs
- Identify opportunities to streamline or automate steps in the process, to reduce manual work and speed delivery
- Own data-quality checks and identify recurring sources of defects, rework, or ambiguity
- Identify opportunities to automate manual quarterly data processing, validation, and other repeatable activities
Skills (GIS):
- An understanding of Geographic Information System (GIS) processes and capabilities
- Experience with ESRI's ArcGIS suite of software, including, but not limited to: ArcGIS Pro and ArcGIS Enterprise
- Ability to analyze data, identify anomalies and potential resolution
- Strong attention to detail and ability
for prose 3. Do NOT repeat the job title as a heading 4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless the posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting content: The posting appears to be for a "GIS Business Information Specialist" role at Nationwide, but there's also a "Specialist, Business Information" role described. It seems like there might be two roles mixed together or a combined posting. Let me parse carefully. First part: "If you're passionate about helping people protect what matters most..." - this is an intro about Nationwide's Property and Casualty team. Then: "The GIS Business Information Specialist supports Nationwide's geographical management..." - this describes the GIS Business Information Specialist role with specific responsibilities. Then there's a "Skills" section with bullet points. Then: "This role does not qualify for employer-sponsored work authorization..." - metadata. Then: "Job Description Summary" - describes "Specialist, Business Information" role. Then: "Job Description Key Responsibilities:" - list of responsibilities. Then: "Reporting Relationships:" - reports to Manager/Director. Then: "Typical Skills And Experiences" - Education, Experience, Knowledge, Abilities and Skills. Then: "Staffing Exceptions..." - HR info. Then: "Values:" - Nationwide values. Then: "Job Conditions" - Overtime Eligibility, Working Conditions, ADA. Then: "We currently anticipate accepting applications until 10/30/2026..." - application deadline. Then: "Benefits" - list of benefits. Then: EEO statement, location info, Iowa smoking statement, NY law info, note to employment agencies, compensation info. I need to structure this into semantic HTML with appropriate sections. The posting seems to have two roles: GIS Business Information Specialist and Specialist, Business Information. But they might be the same role with different descriptions? The title at the top isn't explicitly stated but the first role is "GIS Business Information Specialist". The second is "Specialist, Business Information". The compensation section says "The national salary range for Specialist, Business Information". So likely the job title is "Specialist, Business Information" with a GIS focus. I should create sections based on the content: - About the role (intro) - Responsibilities (for GIS Business Information Specialist) - Skills (for GIS role) - Responsibilities (for Specialist, Business Information) - but maybe combine? The posting has two sets of responsibilities. I'll need to include both but perhaps under separate subsections or combine if they're for the same role. The first set is under "Mapping and Territory Definition Delivery" and "Process Improvement and Automation". The second set is under "Job Description Key Responsibilities:". They seem distinct but for the same position? The first is more GIS-specific, the second is general Business Information Specialist. Since the posting includes both, I should include both. - Qualifications (Education, Experience, Knowledge, Abilities and Skills) - Benefits (listed) - Pay (salary ranges given) - Schedule (Working Conditions mentions "Occasional extended and non-standard hours", Overtime Eligibility: Not Eligible (Exempt)) Also metadata: "This role does not qualify for employer-sponsored work authorization..." and application deadline. I'll fold minor metadata into a short
at the end or in an appropriate section. Now, I must not include EEO, equal opportunity, scam warnings, note to employment agencies, Iowa smoking statement, NY law info, etc. Those are boilerplate. I'll create sections only where there is real content. Let me outline: 1. About the role (intro paragraph) 2. Responsibilities (GIS-specific) - with two subsections: Mapping and Territory Definition Delivery, Process Improvement and Automation 3. Skills (GIS-specific) 4. Responsibilities (General Business Information Specialist) - from Key Responsibilities 5. Qualifications (Education, Experience, Knowledge, Abilities and Skills) 6. Job Conditions (Overtime, Working Conditions, ADA) 7. Benefits 8. Pay (salary ranges) 9. Schedule (maybe combine with Job Conditions? But Schedule is a separate heading type. The rules mention Schedule as a possible heading. Working Conditions includes schedule info. I'll create a Schedule section if there's specific schedule info. The posting says "Occasional extended and non-standard hours based on business information needs." That's schedule-related. Also "Overtime Eligibility: Not Eligible (Exempt)". I'll include in Job Conditions or separate Schedule. I'll put in Job Conditions as it's part of conditions. But the rules say use
for section headings including Schedule. I'll create a Schedule section if there's specific schedule info. There is: "Working Conditions: Normal office environment. Extended periods of personal computer usage and report/information verification. Occasional extended and non-standard hours based on business information needs." That's schedule and conditions. I'll create a "Job Conditions" section (not a standard heading but I can use for "Job Conditions") and include overtime, working conditions, ADA. The rules list "Schedule" as a possible heading. I'll use "Job Conditions" as heading.
The rules say: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I should use those standard headings where appropriate. I can use "Job Conditions" but maybe "Schedule" and "Requirements" etc. I'll map:
- About the role
- Responsibilities (maybe two sections: GIS Responsibilities and General Responsibilities? But better to combine under one Responsibilities heading with sub-lists? The rules don't forbid subheadings but they said use for section headings. I could use for subsections but not required. I'll keep it simple: one Responsibilities section with two subsections using or just separate lists with descriptive text. However, the rules say use for section headings. I'll use for main sections only. For subsections, I can use or just bold text. But the output should be semantic HTML. I'll use for subsections within Responsibilities.
But the instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other headings. I'll use for main sections, and for sub-sections if needed.
Let's structure:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I should use those standard headings where appropriate. I can use "Job Conditions" but maybe "Schedule" and "Requirements" etc. I'll map:
- About the role
- Responsibilities (maybe two sections: GIS Responsibilities and General Responsibilities? But better to combine under one Responsibilities heading with sub-lists? The rules don't forbid subheadings but they said use for section headings. I could use for subsections but not required. I'll keep it simple: one Responsibilities section with two subsections using or just separate lists with descriptive text. However, the rules say use for section headings. I'll use for main sections only. For subsections, I can use or just bold text. But the output should be semantic HTML. I'll use for subsections within Responsibilities.
But the instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other headings. I'll use for main sections, and for sub-sections if needed.
Let's structure:
About the role
for subsections but not required. I'll keep it simple: one Responsibilities section with two subsections using or just separate lists with descriptive text. However, the rules say use for section headings. I'll use for main sections only. For subsections, I can use or just bold text. But the output should be semantic HTML. I'll use for subsections within Responsibilities.
But the instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other headings. I'll use for main sections, and for sub-sections if needed.
Let's structure:
About the role
for section headings. I'll use for main sections only. For subsections, I can use or just bold text. But the output should be semantic HTML. I'll use for subsections within Responsibilities.
But the instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other headings. I'll use for main sections, and for sub-sections if needed.
Let's structure:
About the role
or just bold text. But the output should be semantic HTML. I'll use for subsections within Responsibilities.
But the instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other headings. I'll use for main sections, and for sub-sections if needed.
Let's structure:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other headings. I'll use for main sections, and for sub-sections if needed.
Let's structure:
About the role
for sub-sections if needed.
Let's structure:
About the role
...intro paragraph...
Responsibilities
Mapping and Territory Definition Delivery
- ...
Process Improvement and Automation
- ...
General Business Information Specialist Duties
- ...
Skills
- ...
Qualifications
Education
...
Experience
...
Knowledge, Abilities and Skills
- ...
Job Conditions
Overtime Eligibility: Not Eligible (Exempt)
Working Conditions: Normal office environment. Extended periods of personal computer usage and report/information verification. Occasional extended and non-standard hours based on business information needs.
ADA: The above statements cover what are generally believed to the principal and essential function of this job. Specific circumstances may allow or require some associated assigned to the job to perform a somewhat different combination of duties.
Benefits
- ...
Pay
National salary range: $79,500.00-$148,500.00
Expected starting salary range: $79,500.00 - $119,500.00
Note: Nationwide pays on a geographic-specific salary structure and placement within the actual starting salary range for this position will be determined by a number of factors including the skills, education, training, credentials and experience of the candidate; the scope, complexity and location of the role as well as the cost of labor in the market; and other conditions of employment. If a Sales job, Sales Incentives, based on performance goals are possible in addition to this range. Note on Compensation for Part-Time Roles: Please be aware that the salary ranges listed below reflect full-time compensation. Actual compensation may be prorated based on the number of hours worked relative to a full-time schedule.
Additional Information
This role does not qualify for employer-sponsored work authorization. Nationwide does not participate in the STEM OPT Extension program.
Applications accepted until 10/30/2026, though the posting may close sooner if a strong candidate slate is identified.
This position could be filled within any of the lower 48 U.S. states.
I should not include the reporting relationships, staffing exceptions, values, EEO, note to agencies, Iowa smoking, NY law, etc. Now, ensure I preserve all substantive information. The responsibilities lists are long; I need to include each bullet point. Let me extract the GIS responsibilities: Mapping and Territory Definition Delivery: - Lead the intake, interpretation, preparation, validation, and handoff of GIS maps and territory-related deliverables - Translate business, pricing, underwriting, and product needs into clear GIS maps and related requirements - Define expected results and test or validate map outputs and underlying data for completeness, accuracy, consistency, and alignment with approved territory definitions - Coordinate dependencies with GIS IT and other technology partners for data loads, production updates, releases, and issue resolution - Maintain visibility to work in progress, upcoming deadlines, risks, and required stakeholder decisions Process Improvement and Automation: - Develop understanding of end-to-end GIS processes, from source geography and vendor data, through map and territory production, GIS IT handoffs, testing and release, to downstream use in Personal Lines rating and underwriting systems - Create and maintain documentation for critical GIS data flows, mapping processes, and handoffs - Identify opportunities to streamline or automate steps in the process, to reduce manual work and speed delivery - Own data-quality checks and identify recurring sources of defects, rework, or ambiguity - Identify opportunities to automate manual quarterly data processing, validation, and other repeatable activities Skills (GIS): - An understanding of Geographic Information System (GIS) processes and capabilities - Experience with ESRI's ArcGIS suite of software, including, but not limited to: ArcGIS Pro and ArcGIS Enterprise - Ability to analyze data, identify anomalies and potential resolution - Strong attention to detail and ability