Senior Business Analyst
Gallagher Bassett · Rolling Meadows, IL · 1 mo ago
On-siteInformation TechnologyFull-time
We need to output HTML fragment with sections: About the role? The posting includes Introduction, How You'll Make An Impact (with subsections: Solution Design & Delivery, Data Quality, Testing & Governance, Stakeholder Leadership & Communication), About You (Required, Preferred Experience & Qualifications), Compensation And Benefits.
We must use for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections that have real content. The posting does not have explicit "Responsibilities" heading but the "How You'll Make An Impact" includes responsibilities. We could map that to a Responsibilities section. Also "About You" includes Requirements and Preferred Experience & Qualifications (Qualifications). "Compensation And Benefits" includes Benefits (but no explicit Pay or Schedule). There's no Pay or Schedule specifics, so we should not create those sections. Benefits: they mention "Competitive compensation", "Comprehensive benefits programs", "Career development opportunities", "collaborative, people-first culture", "opportunity to do meaningful work". That's benefits content. So we can have a Benefits section.
We should not repeat job title. No Job ID.
We need to preserve all substantive information, not invent or summarize away detail. Use
for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections that have real content. The posting does not have explicit "Responsibilities" heading but the "How You'll Make An Impact" includes responsibilities. We could map that to a Responsibilities section. Also "About You" includes Requirements and Preferred Experience & Qualifications (Qualifications). "Compensation And Benefits" includes Benefits (but no explicit Pay or Schedule). There's no Pay or Schedule specifics, so we should not create those sections. Benefits: they mention "Competitive compensation", "Comprehensive benefits programs", "Career development opportunities", "collaborative, people-first culture", "opportunity to do meaningful work". That's benefits content. So we can have a Benefits section.
We should not repeat job title. No Job ID.
We need to preserve all substantive information, not invent or summarize away detail. Use - for any list of duties/requirements/benefits, and
for prose.
We need to decide how to structure: maybe sections: About the role (intro paragraph), Responsibilities (list of duties), Requirements (required qualifications), Qualifications (preferred), Benefits.
But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include only those with content. Skills maybe not present explicitly; we could omit Skills if no specific skills list. However there are skills mentioned: interpersonal, communication, organization, time management, SQL, Salesforce, etc. Those could go under Skills. But we need to decide: The posting includes "Excellent interpersonal skills...", "Strong verbal and written communication...", "Ability to work independently...", "Proven ability to meet tight deadlines...", "Self-motivated, creative, and efficient...", "Ability to work successfully in cross-functional teams...", "Strong work ethic...", plus preferred: Hands-on experience with Salesforce, finance teams, basic SQL, leading junior team members. Those could be considered Skills. However we already have Requirements and Qualifications sections; we could put required skills under Requirements, preferred under Qualifications. The instruction says we can use Skills heading if we have skill-specific content. But we can also incorporate skills into Requirements/Qualifications. To follow instruction, we might create a Skills section for the skill-based items (like communication, organization, SQL, Salesforce). But we risk duplication. Better to follow the instruction: Use headings only when posting has real, specific content for it. The posting does have explicit skill statements; we could put them under Skills. However the posting also has "Required: Typically requires a University Degree..." which is more about qualifications. So we could have Requirements (education/experience) and Skills (soft/technical skills). Qualifications could be preferred experience.
Let's parse:
Introduction paragraph: about company purpose, culture.
How You'll Make An Impact: includes responsibilities broken into subsections: Solution Design & Delivery, Data Quality, Testing & Governance, Stakeholder Leadership & Communication. Those are duties.
About You: Required (education/experience, interpersonal skills, etc.) and Preferred Experience & Qualifications (Salesforce, finance, SQL, leading junior).
Compensation And Benefits: benefits description.
Thus we can map:
- About the role: introduction paragraph (maybe combine with responsibilities? but we can have About the role as intro).
- Responsibilities: list of duties from How You'll Make An Impact (including sub-bullets). We'll need to create
- for each duty. Could break into subpoints.
- Requirements: required education/experience and core competencies (interpersonal skills, communication, organization, time management, ability to work independently, meet deadlines, self-motivated, creative, efficient, cross-functional teamwork, work ethic). Those are required.
- Qualifications: preferred experience & qualifications (Salesforce, finance teams, basic SQL, leading junior team members). Could also include "Experience working with finance teams and finance applications", "Ability to perform basic SQL queries", "Experience leading junior team members". Also maybe "Hands-on experience working with Salesforce". That's it.
- Benefits: list of benefits from Compensation And Benefits.
We should not include Skills heading unless we have skill-specific content not covered elsewhere. But we already have required skills under Requirements and preferred under Qualifications. So we can omit Skills.
We must not include Pay or Schedule as no specifics.
We must not include boilerplate like EEO etc. Remove that.
We must preserve all substantive information: need to keep all details from the posting.
Let's extract text.
Introduction:
"At Gallagher Bassett, we're there when it matters most because helping people through challenging moments is more than just our job, it’s our purpose. Every day, we help clients navigate complexity, support recovery, and deliver outcomes that make a real difference in people’s lives. It takes empathy, precision, and a strong sense of partnership—and that’s exactly what you’ll find here. We’re a team of fast-paced fixers, empathetic experts, and outcomes drivers — people who care deeply about doing the right thing and doing it well. Whether you're managing claims, supporting clients, or improving processes, you’ll play a vital role in helping businesses and individuals move forward with confidence. Here, you’ll be supported by a culture that values teamwork, encourages curiosity, and celebrates the impact of your work. Because when you’re here, you’re part of something bigger. You’re part of a team that shows up, stands together, and leads with purpose."
That's the intro.
How You'll Make An Impact: heading then paragraph: "Gallagher Bassett is seeking a seasoned Senior Business Analyst to serve as the liaison between our business partners and the technical development team. This role is responsible for eliciting, analyzing, validating, specifying, verifying, prioritizing and managing stakeholder business needs from initial discovery through successful implementation. Partner closely with business units, subject matter experts, customers, end users, technical resources, and vendor partners to identify business needs and define effective solutions. Translate business objectives into clear, actionable requirements and designs, and support the development effort through completion. Balance usability, performance, data integrity, delivery risk, and technical feasibility while helping stakeholders make informed decisions. Elicit requirements through interviews, document analysis, workshops, surveys, site visits, process descriptions, use cases, scenarios, business analysis, and task and workflow analysis. Critically evaluate information from multiple sources, reconcile conflicts, and decompose high-level needs into detailed functional and non-functional requirements. Define and document internal and external user interfaces, and clarify system and data requirements. Drive and challenge business units on assumptions about how they will successfully execute their plans."
Then subheading "Solution Design & Delivery": bullet points? Actually it's a paragraph: "Work with functional leads to transform new business requirements into designs and implementation plans. Interface with vendor partners to design optimal solutions and integrations. Create and maintain workflows, approval processes, and validation rules based on internal stakeholder requirements. Collaborate with developers and subject matter experts to establish the technical vision and assess tradeoffs between usability and performance. Partner with internal and external peer groups to design and implement solutions."
Then "Data Quality, Testing & Governance": "Develop, maintain, and execute processes that continuously monitor data quality and integrity across platform applications. Assist with quality assurance, including defining the testing strategy, identifying risks, and supporting validation of delivered solutions. Manage requirements throughout the project lifecycle to maintain traceability, alignment, and delivery quality. Assist with troubleshooting reports of production environment defects from intake to resolution."
Then "Stakeholder Leadership & Communication": "Maintain courteous and professional working relationships with employees at all levels of the organization. Communicate effectively with technical and non-technical stakeholders through excellent active listening, verbal communication, and business writing. Adapt to shifting priorities and demands while maintaining focus on business outcomes. Mentor and influence others through example."
About You: Required: "Typically requires a University Degree and minimum 5 years of prior relevant experience, or equivalent experience. Bachelor's degree or an equivalent combination of relevant education and experience Minimum of 5 years of experience in a Business Systems Analyst or comparable business analysis role. Excellent interpersonal skills and demonstrated ability to work effectively with diverse personality types. Proven ability to work independently with limited supervision and collaborate effectively with personnel across departments. Strong verbal and written communication, organization, and time management skills. Ability to communicate clearly and effectively with both technical and non-technical stakeholders. Proven ability to meet tight deadlines, manage multiple priorities, and prioritize workload effectively. Self-motivated, creative, and efficient in proposing solutions to complex, time-critical problems. Ability to work successfully in cross-functional teams and communicate with colleagues in both business and technical roles. Strong work ethic and a demonstrated desire to exceed expectations."
Preferred Experience & Qualifications: "Hands-on experience working with Salesforce Experience working with finance teams and finance applications Ability to perform basic SQL queries Experience leading junior team members"
Compensation And Benefits: paragraph: "At Gallagher, we believe supporting our colleagues goes far beyond the role itself. For more information, visit our Benefits page. Competitive compensation Comprehensive benefits programs designed to support your well-being Career development opportunities and ongoing learning A collaborative, people-first culture with accessible leadership The opportunity to do meaningful work with global reach and local impact At Gallagher, we are dedicated to building an inclusive and authentic workplace. If your past experience doesn’t align perfectly, we encourage you to join our Talent Community to stay connected to additional career opportunities. At times, we will consider transferable skills from previous roles. Gallagher is an affirmative action/equal opportunity employer (Minorities/Females/Veterans/Disabled)"
We need to remove EEO boilerplate etc. So we should cut out the last sentences about Talent Community, transferable skills, affirmative action. Also remove "For more information, visit our Benefits page." That's a navigation/instruction; we should remove application instructions and boilerplate. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So "For more information, visit our Benefits page." is like a navigation instruction; we should remove it. Also the Talent Community and transferable skills lines are also maybe considered boilerplate? They are not EEO but could be considered generic; but they are part of the posting; however they are not substantive about the role? They are about applying. The instruction says remove application instructions. Those lines about Talent Community and transferable skills are like encouraging to join talent community; that's application-related. So we should remove them. Also the EEO line definitely remove.
Thus benefits content we keep: "Competitive compensation Comprehensive benefits programs designed to support your well-being Career development opportunities and ongoing learning A collaborative, people-first culture with accessible leadership The opportunity to do meaningful work with global reach and local impact"
We need to format as list items.
Now construct HTML.
We'll have:
About the role
Intro paragraph...
Responsibilities
- Elicit, analyze, validate, specify, verify, prioritize and manage stakeholder business needs from initial discovery through successful implementation.
- Partner closely with business units, subject matter experts, customers, end users, technical resources, and vendor partners to identify business needs and define effective solutions.
- Translate business objectives into clear, actionable requirements and designs, and support the development effort through completion.
- Balance usability, performance, data integrity, delivery risk, and technical feasibility while helping stakeholders make informed decisions.
- Elicit requirements through interviews, document analysis, workshops, surveys, site visits, process descriptions, use cases, scenarios, business analysis, and task and workflow analysis.
- Critically evaluate information from multiple sources, reconcile conflicts, and decompose high-level needs into detailed functional and non-functional requirements.
- Define and document internal and external user interfaces, and
for prose. We need to decide how to structure: maybe sections: About the role (intro paragraph), Responsibilities (list of duties), Requirements (required qualifications), Qualifications (preferred), Benefits. But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include only those with content. Skills maybe not present explicitly; we could omit Skills if no specific skills list. However there are skills mentioned: interpersonal, communication, organization, time management, SQL, Salesforce, etc. Those could go under Skills. But we need to decide: The posting includes "Excellent interpersonal skills...", "Strong verbal and written communication...", "Ability to work independently...", "Proven ability to meet tight deadlines...", "Self-motivated, creative, and efficient...", "Ability to work successfully in cross-functional teams...", "Strong work ethic...", plus preferred: Hands-on experience with Salesforce, finance teams, basic SQL, leading junior team members. Those could be considered Skills. However we already have Requirements and Qualifications sections; we could put required skills under Requirements, preferred under Qualifications. The instruction says we can use Skills heading if we have skill-specific content. But we can also incorporate skills into Requirements/Qualifications. To follow instruction, we might create a Skills section for the skill-based items (like communication, organization, SQL, Salesforce). But we risk duplication. Better to follow the instruction: Use headings only when posting has real, specific content for it. The posting does have explicit skill statements; we could put them under Skills. However the posting also has "Required: Typically requires a University Degree..." which is more about qualifications. So we could have Requirements (education/experience) and Skills (soft/technical skills). Qualifications could be preferred experience. Let's parse: Introduction paragraph: about company purpose, culture. How You'll Make An Impact: includes responsibilities broken into subsections: Solution Design & Delivery, Data Quality, Testing & Governance, Stakeholder Leadership & Communication. Those are duties. About You: Required (education/experience, interpersonal skills, etc.) and Preferred Experience & Qualifications (Salesforce, finance, SQL, leading junior). Compensation And Benefits: benefits description. Thus we can map: - About the role: introduction paragraph (maybe combine with responsibilities? but we can have About the role as intro). - Responsibilities: list of duties from How You'll Make An Impact (including sub-bullets). We'll need to create
- for each duty. Could break into subpoints.
- Requirements: required education/experience and core competencies (interpersonal skills, communication, organization, time management, ability to work independently, meet deadlines, self-motivated, creative, efficient, cross-functional teamwork, work ethic). Those are required.
- Qualifications: preferred experience & qualifications (Salesforce, finance teams, basic SQL, leading junior team members). Could also include "Experience working with finance teams and finance applications", "Ability to perform basic SQL queries", "Experience leading junior team members". Also maybe "Hands-on experience working with Salesforce". That's it.
- Benefits: list of benefits from Compensation And Benefits.
We should not include Skills heading unless we have skill-specific content not covered elsewhere. But we already have required skills under Requirements and preferred under Qualifications. So we can omit Skills.
We must not include Pay or Schedule as no specifics.
We must not include boilerplate like EEO etc. Remove that.
We must preserve all substantive information: need to keep all details from the posting.
Let's extract text.
Introduction:
"At Gallagher Bassett, we're there when it matters most because helping people through challenging moments is more than just our job, it’s our purpose. Every day, we help clients navigate complexity, support recovery, and deliver outcomes that make a real difference in people’s lives. It takes empathy, precision, and a strong sense of partnership—and that’s exactly what you’ll find here. We’re a team of fast-paced fixers, empathetic experts, and outcomes drivers — people who care deeply about doing the right thing and doing it well. Whether you're managing claims, supporting clients, or improving processes, you’ll play a vital role in helping businesses and individuals move forward with confidence. Here, you’ll be supported by a culture that values teamwork, encourages curiosity, and celebrates the impact of your work. Because when you’re here, you’re part of something bigger. You’re part of a team that shows up, stands together, and leads with purpose."
That's the intro.
How You'll Make An Impact: heading then paragraph: "Gallagher Bassett is seeking a seasoned Senior Business Analyst to serve as the liaison between our business partners and the technical development team. This role is responsible for eliciting, analyzing, validating, specifying, verifying, prioritizing and managing stakeholder business needs from initial discovery through successful implementation. Partner closely with business units, subject matter experts, customers, end users, technical resources, and vendor partners to identify business needs and define effective solutions. Translate business objectives into clear, actionable requirements and designs, and support the development effort through completion. Balance usability, performance, data integrity, delivery risk, and technical feasibility while helping stakeholders make informed decisions. Elicit requirements through interviews, document analysis, workshops, surveys, site visits, process descriptions, use cases, scenarios, business analysis, and task and workflow analysis. Critically evaluate information from multiple sources, reconcile conflicts, and decompose high-level needs into detailed functional and non-functional requirements. Define and document internal and external user interfaces, and clarify system and data requirements. Drive and challenge business units on assumptions about how they will successfully execute their plans."
Then subheading "Solution Design & Delivery": bullet points? Actually it's a paragraph: "Work with functional leads to transform new business requirements into designs and implementation plans. Interface with vendor partners to design optimal solutions and integrations. Create and maintain workflows, approval processes, and validation rules based on internal stakeholder requirements. Collaborate with developers and subject matter experts to establish the technical vision and assess tradeoffs between usability and performance. Partner with internal and external peer groups to design and implement solutions."
Then "Data Quality, Testing & Governance": "Develop, maintain, and execute processes that continuously monitor data quality and integrity across platform applications. Assist with quality assurance, including defining the testing strategy, identifying risks, and supporting validation of delivered solutions. Manage requirements throughout the project lifecycle to maintain traceability, alignment, and delivery quality. Assist with troubleshooting reports of production environment defects from intake to resolution."
Then "Stakeholder Leadership & Communication": "Maintain courteous and professional working relationships with employees at all levels of the organization. Communicate effectively with technical and non-technical stakeholders through excellent active listening, verbal communication, and business writing. Adapt to shifting priorities and demands while maintaining focus on business outcomes. Mentor and influence others through example."
About You: Required: "Typically requires a University Degree and minimum 5 years of prior relevant experience, or equivalent experience. Bachelor's degree or an equivalent combination of relevant education and experience Minimum of 5 years of experience in a Business Systems Analyst or comparable business analysis role. Excellent interpersonal skills and demonstrated ability to work effectively with diverse personality types. Proven ability to work independently with limited supervision and collaborate effectively with personnel across departments. Strong verbal and written communication, organization, and time management skills. Ability to communicate clearly and effectively with both technical and non-technical stakeholders. Proven ability to meet tight deadlines, manage multiple priorities, and prioritize workload effectively. Self-motivated, creative, and efficient in proposing solutions to complex, time-critical problems. Ability to work successfully in cross-functional teams and communicate with colleagues in both business and technical roles. Strong work ethic and a demonstrated desire to exceed expectations."
Preferred Experience & Qualifications: "Hands-on experience working with Salesforce Experience working with finance teams and finance applications Ability to perform basic SQL queries Experience leading junior team members"
Compensation And Benefits: paragraph: "At Gallagher, we believe supporting our colleagues goes far beyond the role itself. For more information, visit our Benefits page. Competitive compensation Comprehensive benefits programs designed to support your well-being Career development opportunities and ongoing learning A collaborative, people-first culture with accessible leadership The opportunity to do meaningful work with global reach and local impact At Gallagher, we are dedicated to building an inclusive and authentic workplace. If your past experience doesn’t align perfectly, we encourage you to join our Talent Community to stay connected to additional career opportunities. At times, we will consider transferable skills from previous roles. Gallagher is an affirmative action/equal opportunity employer (Minorities/Females/Veterans/Disabled)"
We need to remove EEO boilerplate etc. So we should cut out the last sentences about Talent Community, transferable skills, affirmative action. Also remove "For more information, visit our Benefits page." That's a navigation/instruction; we should remove application instructions and boilerplate. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So "For more information, visit our Benefits page." is like a navigation instruction; we should remove it. Also the Talent Community and transferable skills lines are also maybe considered boilerplate? They are not EEO but could be considered generic; but they are part of the posting; however they are not substantive about the role? They are about applying. The instruction says remove application instructions. Those lines about Talent Community and transferable skills are like encouraging to join talent community; that's application-related. So we should remove them. Also the EEO line definitely remove.
Thus benefits content we keep: "Competitive compensation Comprehensive benefits programs designed to support your well-being Career development opportunities and ongoing learning A collaborative, people-first culture with accessible leadership The opportunity to do meaningful work with global reach and local impact"
We need to format as list items.
Now construct HTML.
We'll have:
About the role
Intro paragraph...
Responsibilities
- Elicit, analyze, validate, specify, verify, prioritize and manage stakeholder business needs from initial discovery through successful implementation.
- Partner closely with business units, subject matter experts, customers, end users, technical resources, and vendor partners to identify business needs and define effective solutions.
- Translate business objectives into clear, actionable requirements and designs, and support the development effort through completion.
- Balance usability, performance, data integrity, delivery risk, and technical feasibility while helping stakeholders make informed decisions.
- Elicit requirements through interviews, document analysis, workshops, surveys, site visits, process descriptions, use cases, scenarios, business analysis, and task and workflow analysis.
- Critically evaluate information from multiple sources, reconcile conflicts, and decompose high-level needs into detailed functional and non-functional requirements.
- Define and document internal and external user interfaces, and