Reporting Analyst Co-op - Spring 2027
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We must not repeat job title as heading. No Job ID etc.
We must preserve all substantive information; do not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the EEO statements, accommodation request, California privacy policy, lie detector, fair chance, etc. Also remove "We are committed to fostering an inclusive environment..." etc. Those are EEO boilerplate. Also remove "Please email thebrightside@sunlife.com to request an accommodation." etc. Also remove "For applicants residing in California..." etc. Also remove "We do not require or administer lie detector tests..." etc. Also remove "Sun Life will consider for employment all qualified applicants..." etc. Also remove "All qualified applicants will receive consideration..." etc. Also remove "Job Category Temporary Employee Posting End Date 15/10/2026" maybe considered metadata; we can fold minor metadata into a short
or drop it. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we could include a short
with posting end date maybe. But it's minor metadata; we could drop it. Safer to drop it.
We need to preserve substantive info: purpose, values, student programs, description of role, responsibilities list, core skill sets, eligibility requirements, compensation.
We need to format sections: maybe "About the role" (includes purpose, values, student programs, description). Could also have "About Sun Life" but instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings.
We have content about role: "As a member of the Health and Risk Solutions Finance Reporting Center of Excellence Team, you will drive the successful development and delivery of accurate and timely data and reporting supporting management decision making. You will prepare presentation quality reports, dashboards and analytic tools using Tableau as well as various SQL based reporting applications. You will also learn about SunLife’s various products and operations while building relationships across various levels of management. We are looking for an individual with a proven track record of delivering professional work products with a strong attention to detail, a self-starter who is inquisitive and has a strong sense of ownership and continuous-improvement mind-set". That could go under "About the role" or maybe "Qualifications"? But we have separate "Core Skill Sets Needed For This Role". So "About the role" could be the description of role and what you'll do.
Responsibilities list: bullet points.
Core Skill Sets Needed: list.
Requirements: eligibility (currently enrolled, major, work eligibility, full-time). Could be under "Requirements". Also maybe "Qualifications" could be same as requirements? But we have both headings; we need to decide which to use. The instruction: Prefer a few substantive sections over many thin ones. So we could combine eligibility and skill sets into one "Requirements" section? But we have separate headings for Skills and Qualifications. Might be better to have "Requirements" for eligibility, and "Skills" for core skill sets. Or "Qualifications" for eligibility and "Skills" for skill sets. Let's see typical usage: Requirements often include eligibility, qualifications include education/experience, skills include technical. We'll follow:
Requirements
for eligibility (enrollment, major, work auth, full-time). Skills
for core skill sets needed. Could also have Qualifications
maybe not needed if we already have Requirements and Skills. But we could put "Qualifications" for education/major? However we already have major in Requirements. Might be redundant. Better to have Requirements (eligibility) and Skills (skill sets). Omit Qualifications.
Pay: we have compensation $22.00/hr. So Pay
with $22.00 per hour
.
Schedule: they mention Ability to work full-time (40 hours/week) during co-op session. That's schedule info. So Schedule
with Full-time, 40 hours per week during the co-op session (January – June 2027)
.
We also have posting end date maybe minor; we can drop.
We need to remove duplicated lines: there is duplicate "Ability to work full-time (40 hours/week) during co-op session" appears in requirements and also schedule; we can keep it in schedule section only, but we need to preserve all substantive info; we can mention it in schedule and not repeat in requirements. However requirements also need to mention eligibility to work full-time; we could keep it there as part of eligibility but then schedule repeats. To avoid duplication, we could mention full-time in requirements and schedule just says "Full-time, 40 hours/week". But that's still duplication. The instruction: remove duplicated lines. So we should not repeat the same sentence. We can keep full-time mention in requirements (eligibility) and schedule could be omitted? But schedule is a section; we need to include schedule only if posting has real specific content. It does: full-time 40 hours/week. We could keep schedule section with that info, and not repeat in requirements. But then requirements would lack mention of full-time eligibility. However the eligibility includes "Ability to work full-time (40 hours/week) during co-op session". That's a requirement. So we need to keep it somewhere. We could keep it in requirements and schedule could be something like "Co-op session: January – June 2027" (the duration). But schedule section expects schedule info; we could put the duration there. However the posting says "Currently enrolled in an accredited college or university during the time of co-op (January – June 2027)". That's about timing. So schedule could be the co-op period. The full-time requirement is separate. So we can put schedule: "Co-op session runs January – June 2027". And full-time requirement in requirements. That avoids duplication.
Thus:
Requirements: Currently enrolled in an accredited college or university during the time of co-op (January – June 2027); Must be an undergraduate or graduate student in Data Science, Management Information Systems, Business Analytics, Business Administration, or related field of study; Eligible to legally work in the United States; Ability to work full-time (40 hours/week) during co-op session.
Skills: list bullet points.
Pay: $22.00/hr.
Schedule: Co-op session: January – June 2027 (maybe also mention full-time? but we already have full-time in requirements). We'll just state the period.
About the role: combine the introductory paragraphs about Sun Life purpose, values, student programs, and the role description. We'll need to keep all substantive info. Let's extract:
- At Sun Life, we’re driven by our Purpose: helping our Clients achieve lifetime financial security and live healthier lives. Our values shape how we work: caring, authentic, bold, inspiring, and impactful. Our student and new graduate programs offer a chance to explore Sun Life from the inside. You’ll make a difference in the lives of our customers and communities, while building the skills and experience that allow you to grow in a meaningful and rewarding way.
- Job Description You are as unique as your background, experience, and point of view. Here, you’ll be encouraged, empowered, and challenged to be your best self. You'll work with dynamic colleagues - experts in their fields - who are eager to share their knowledge with you. Your leaders will inspire and help you reach your potential and soar to new heights. Every day, you'll have new and exciting opportunities to make life brighter for our Clients - who are at the heart of everything we do. Discover how you can make a difference in the lives of individuals, families, and communities around the world. What’s it like to work at Sun Life? You’ll find it dynamic and highly professional; collaborative and supportive. We encourage career mobility. Sun Life is also a socially responsible employer, supporting the communities in which we live and work, with a globally recognized commitment to the environment and sustainability.
- The Role As a member of the Health and Risk Solutions Finance Reporting Center of Excellence Team, you will drive the successful development and delivery of accurate and timely data and reporting supporting management decision making. You will prepare presentation quality reports, dashboards and analytic tools using Tableau as well as various SQL based reporting applications. You will also learn about SunLife’s various products and operations while building relationships across various levels of management. We are looking for an individual with a proven track record of delivering professional work products with a strong attention to detail, a self-starter who is inquisitive and has a strong sense of ownership and continuous-improvement mind-set
We need to preserve all that. We'll put in paragraphs.
We must not include boilerplate like EEO etc. We'll strip those.
Now produce HTML fragment.
Structure:
About the role
...
...
...
Responsibilities
- Develop and deliver daily and monthly reporting, along with ad hoc analysis to support our business partners.
- Develop end user tools/reporting that can be leveraged for analysis.
- Work within the team, partnering with IT to expand our reporting/data environment.
- Identify opportunities for process improvement, articulating the rational for the change and impact.
- Identify and escalate issues while proposing options towards resolution.
- Participate in ad-hoc projects, as requested.
Skills
- Comfort in assembling/manipulating large amounts of data for use in analysis/reporting
- Experience developing interactive reporting that supports management decision making
- Experience utilizing SSRS or similar SQL based applications a must
- Experience with Tableau or similar visualization tools a plus
- Excellent communication skills
- Proactive, able to manage multiple projects with demanding deadlines
- Highly motivated, self-driven, focused, strong attention to detail
Requirements
- Currently enrolled in an accredited college or university during the time of co-op (January – June 2027)
- Must be an undergraduate or graduate student in Data Science, Management Information Systems, Business Analytics, Business Administration, or related field of study
- Eligible to legally work in the United States
- Ability to work full-time (40 hours/week) during co-op session
Pay
$22.00 per hour
Schedule
Co-op session: January – June 2027
Check for any leftover boilerplate: we removed EEO lines. Also removed "Job Category Temporary Employee Posting End Date 15/10
for prose. We must not repeat job title as heading. No Job ID etc. We must preserve all substantive information; do not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the EEO statements, accommodation request, California privacy policy, lie detector, fair chance, etc. Also remove "We are committed to fostering an inclusive environment..." etc. Those are EEO boilerplate. Also remove "Please email thebrightside@sunlife.com to request an accommodation." etc. Also remove "For applicants residing in California..." etc. Also remove "We do not require or administer lie detector tests..." etc. Also remove "Sun Life will consider for employment all qualified applicants..." etc. Also remove "All qualified applicants will receive consideration..." etc. Also remove "Job Category Temporary Employee Posting End Date 15/10/2026" maybe considered metadata; we can fold minor metadata into a short
or drop it. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we could include a short
with posting end date maybe. But it's minor metadata; we could drop it. Safer to drop it. We need to preserve substantive info: purpose, values, student programs, description of role, responsibilities list, core skill sets, eligibility requirements, compensation. We need to format sections: maybe "About the role" (includes purpose, values, student programs, description). Could also have "About Sun Life" but instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings. We have content about role: "As a member of the Health and Risk Solutions Finance Reporting Center of Excellence Team, you will drive the successful development and delivery of accurate and timely data and reporting supporting management decision making. You will prepare presentation quality reports, dashboards and analytic tools using Tableau as well as various SQL based reporting applications. You will also learn about SunLife’s various products and operations while building relationships across various levels of management. We are looking for an individual with a proven track record of delivering professional work products with a strong attention to detail, a self-starter who is inquisitive and has a strong sense of ownership and continuous-improvement mind-set". That could go under "About the role" or maybe "Qualifications"? But we have separate "Core Skill Sets Needed For This Role". So "About the role" could be the description of role and what you'll do. Responsibilities list: bullet points. Core Skill Sets Needed: list. Requirements: eligibility (currently enrolled, major, work eligibility, full-time). Could be under "Requirements". Also maybe "Qualifications" could be same as requirements? But we have both headings; we need to decide which to use. The instruction: Prefer a few substantive sections over many thin ones. So we could combine eligibility and skill sets into one "Requirements" section? But we have separate headings for Skills and Qualifications. Might be better to have "Requirements" for eligibility, and "Skills" for core skill sets. Or "Qualifications" for eligibility and "Skills" for skill sets. Let's see typical usage: Requirements often include eligibility, qualifications include education/experience, skills include technical. We'll follow:
Requirements
for eligibility (enrollment, major, work auth, full-time).Skills
for core skill sets needed. Could also haveQualifications
maybe not needed if we already have Requirements and Skills. But we could put "Qualifications" for education/major? However we already have major in Requirements. Might be redundant. Better to have Requirements (eligibility) and Skills (skill sets). Omit Qualifications. Pay: we have compensation $22.00/hr. SoPay
with$22.00 per hour
. Schedule: they mention Ability to work full-time (40 hours/week) during co-op session. That's schedule info. SoSchedule
withFull-time, 40 hours per week during the co-op session (January – June 2027)
. We also have posting end date maybe minor; we can drop. We need to remove duplicated lines: there is duplicate "Ability to work full-time (40 hours/week) during co-op session" appears in requirements and also schedule; we can keep it in schedule section only, but we need to preserve all substantive info; we can mention it in schedule and not repeat in requirements. However requirements also need to mention eligibility to work full-time; we could keep it there as part of eligibility but then schedule repeats. To avoid duplication, we could mention full-time in requirements and schedule just says "Full-time, 40 hours/week". But that's still duplication. The instruction: remove duplicated lines. So we should not repeat the same sentence. We can keep full-time mention in requirements (eligibility) and schedule could be omitted? But schedule is a section; we need to include schedule only if posting has real specific content. It does: full-time 40 hours/week. We could keep schedule section with that info, and not repeat in requirements. But then requirements would lack mention of full-time eligibility. However the eligibility includes "Ability to work full-time (40 hours/week) during co-op session". That's a requirement. So we need to keep it somewhere. We could keep it in requirements and schedule could be something like "Co-op session: January – June 2027" (the duration). But schedule section expects schedule info; we could put the duration there. However the posting says "Currently enrolled in an accredited college or university during the time of co-op (January – June 2027)". That's about timing. So schedule could be the co-op period. The full-time requirement is separate. So we can put schedule: "Co-op session runs January – June 2027". And full-time requirement in requirements. That avoids duplication. Thus: Requirements: Currently enrolled in an accredited college or university during the time of co-op (January – June 2027); Must be an undergraduate or graduate student in Data Science, Management Information Systems, Business Analytics, Business Administration, or related field of study; Eligible to legally work in the United States; Ability to work full-time (40 hours/week) during co-op session. Skills: list bullet points. Pay: $22.00/hr. Schedule: Co-op session: January – June 2027 (maybe also mention full-time? but we already have full-time in requirements). We'll just state the period. About the role: combine the introductory paragraphs about Sun Life purpose, values, student programs, and the role description. We'll need to keep all substantive info. Let's extract: - At Sun Life, we’re driven by our Purpose: helping our Clients achieve lifetime financial security and live healthier lives. Our values shape how we work: caring, authentic, bold, inspiring, and impactful. Our student and new graduate programs offer a chance to explore Sun Life from the inside. You’ll make a difference in the lives of our customers and communities, while building the skills and experience that allow you to grow in a meaningful and rewarding way. - Job Description You are as unique as your background, experience, and point of view. Here, you’ll be encouraged, empowered, and challenged to be your best self. You'll work with dynamic colleagues - experts in their fields - who are eager to share their knowledge with you. Your leaders will inspire and help you reach your potential and soar to new heights. Every day, you'll have new and exciting opportunities to make life brighter for our Clients - who are at the heart of everything we do. Discover how you can make a difference in the lives of individuals, families, and communities around the world. What’s it like to work at Sun Life? You’ll find it dynamic and highly professional; collaborative and supportive. We encourage career mobility. Sun Life is also a socially responsible employer, supporting the communities in which we live and work, with a globally recognized commitment to the environment and sustainability. - The Role As a member of the Health and Risk Solutions Finance Reporting Center of Excellence Team, you will drive the successful development and delivery of accurate and timely data and reporting supporting management decision making. You will prepare presentation quality reports, dashboards and analytic tools using Tableau as well as various SQL based reporting applications. You will also learn about SunLife’s various products and operations while building relationships across various levels of management. We are looking for an individual with a proven track record of delivering professional work products with a strong attention to detail, a self-starter who is inquisitive and has a strong sense of ownership and continuous-improvement mind-set We need to preserve all that. We'll put inparagraphs. We must not include boilerplate like EEO etc. We'll strip those. Now produce HTML fragment. Structure:
About the role
...
...
...
Responsibilities
- Develop and deliver daily and monthly reporting, along with ad hoc analysis to support our business partners.
- Develop end user tools/reporting that can be leveraged for analysis.
- Work within the team, partnering with IT to expand our reporting/data environment.
- Identify opportunities for process improvement, articulating the rational for the change and impact.
- Identify and escalate issues while proposing options towards resolution.
- Participate in ad-hoc projects, as requested.
Skills
- Comfort in assembling/manipulating large amounts of data for use in analysis/reporting
- Experience developing interactive reporting that supports management decision making
- Experience utilizing SSRS or similar SQL based applications a must
- Experience with Tableau or similar visualization tools a plus
- Excellent communication skills
- Proactive, able to manage multiple projects with demanding deadlines
- Highly motivated, self-driven, focused, strong attention to detail
Requirements
- Currently enrolled in an accredited college or university during the time of co-op (January – June 2027)
- Must be an undergraduate or graduate student in Data Science, Management Information Systems, Business Analytics, Business Administration, or related field of study
- Eligible to legally work in the United States
- Ability to work full-time (40 hours/week) during co-op session
Pay
$22.00 per hour
Schedule
Co-op session: January – June 2027
Check for any leftover boilerplate: we removed EEO lines. Also removed "Job Category Temporary Employee Posting End Date 15/10