Project Management Operations: Financial Analysis Co-op Spring 2027 (January - June)

We need to output HTML fragment with sections: About the role? Actually the posting includes a culture description at top; we can treat that as "About the role" or maybe "About MFS". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real, specific content. We have: - About the role: The initial paragraph about culture and mission could be considered "About the role" or "About MFS". We'll put as About the role. - Responsibilities: There's a "Responsibilities" heading in the posting, with bullet list: "Joining our team provides opportunities..." then bullet list of structured activities, then later "Key Responsibilities" list, then "What You Will Do" list. We need to combine all responsibilities into a

• . Should we separate? Probably combine all bullet points into one list under Responsibilities. - Requirements: There's "What We Are Looking For" bullet list: interpersonal skills, analytical skills, detail-oriented, ability to handle multiple tasks, experience with Excel required, PowerPoint/Visio plus, Tableau/Power BI plus. That's requirements. - Qualifications: Could be education: "Our program is designed for undergraduate students who are currently enrolled in a co-op program through their college or university and can meet our requirements." Also maybe "MFS Co-op positions are a 6-month commitment, working Monday – Friday (beginning on Wednesday, January 13th through Friday June 25th, 2027), and work between 35-40 hours." That's schedule info. Also "Job Summary" maybe part of About the role. But we need to decide sections. We have Pay: "Hourly Pay Rate: $21.00-$25.00". So we need a Pay section. Schedule: The posting includes schedule: "MFS Co-op positions are a 6-month commitment, working Monday – Friday (beginning on Wednesday, January 13th through Friday June 25th, 2027), and work between 35-40 hours." That's schedule info. So we can create Schedule section. Benefits: Not mentioned besides maybe structured activities (Co-Op New Hire Orientation etc.) but those are more responsibilities/learning. No explicit benefits like health, etc. So we should not create Benefits section unless there is real content. There's mention of "participate in a series of structured activities designed to enhance their learning experience including: Co-Op New Hire Orientation Senior Leadership Speaker Series Social & Networking Events Presentation Challenges". That could be considered benefits or learning opportunities. But the instruction: only create Benefits section if posting actually states them. It does mention structured activities; could be considered benefits. However they said "Prefer a few substantive sections over many thin ones." Might combine those into Responsibilities or maybe a separate "Benefits" if we think it's substantive. But it's more about learning activities; could be considered part of the role. I'd treat them as part of Responsibilities (or maybe as a separate "Learning Opportunities" but not in allowed headings). Since allowed headings list includes Benefits, we could put those under Benefits. However the instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". The structured activities are specific. So we could create Benefits section with those items. But we also have "What You Will Do" which is more responsibilities. Might be redundant. We need to avoid duplication. Let's extract distinct content: Culture/intro: first paragraph(s) about MFS culture, mission, history. That's About the role. Responsibilities: combine: - Joining our team provides opportunities to share your voice and talents, tackle challenging problems, create solutions and collaborate with dedicated co-workers. - This Co-op experience provides participants with meaningful, relevant work experience as part of their academic studies. - In addition to daily responsibilities, participants will have the opportunity to participate in a series of structured activities designed to enhance their learning experience including: * Co-Op New Hire Orientation * Senior Leadership Speaker Series * Social & Networking Events * Presentation Challenges - At the conclusion of this position, Co-ops will have gained practical exposure to how technology supports an asset manager, including project operations, financial analysis, budgeting and reporting, process documentation, data analysis, and cross-functional collaboration with Global Information Technology (GIT) and Corporate Finance teams. - Key Responsibilities: * Collaborate with Corporate Finance to support budgeting and reporting for Business Technology initiatives. * Track and analyze project costs, identifying opportunities for financial and operational optimization. * Assist Project Managers, Product Owners, and GIT team members with staffing, financials, and metrics reporting. * Work on Ad-Hoc projects that support Financial and Process optimization as it relates to Monthly reporting and / or Budget Reporting and associated analysis * Deliver high-impact outputs that support strategic decision-making across GIT projects. - What You Will Do (working with PM Ops team and GIT): * Help with analysis and documentation of current state and future state workflows for key processes such as General Maintenance * Create graphs, charts and materials to support improvement efforts * Help to coordinate data gathering and data updates (if necessary) across teams * Analyze year over year data trends and help consolidate data for recommendations * Based on analysis, identify problem areas and recommend solutions for consideration * Define and coordinate creation of new reports (if necessary) or enhancements to existing reports (with help from the GIT team) * Assist with furthering MFS' best practices, including help with the management of project artifacts, metrics, status reports across MFS' initiatives * Provide administrative support for data updates, presentations, and other ad-hoc activities * Maintain process documentation and write new procedures when needed. * Work on various ad-hoc projects and look to continually improve and / or simplify monthly reporting and analysis We could combine all these bullet points into one list under Responsibilities. Might be long but okay. Requirements/Qualifications: "What We Are Looking For" list: - Excellent interpersonal and communication skills to work effectively in a team environment. - Strong analytical skills and interest with working with large volumes of data and to help with interpretation/reporting - Detail-oriented with good organizational and problem solving skills, and self-motivated. - Ability and willingness to handle multiple tasks within a fast-paced casual yet professional environment. - Experience with Excel required - Experience using Microsoft Power Point and Visio are a plus - Experience with Tableau, Power BI or other data and visualization tools is a plus Also maybe "Our program is designed for undergraduate students who are currently enrolled in a co-op program through their college or university and can meet our requirements." That's a qualification (education). Could be under Requirements or Qualifications. Since we have both Requirements and Qualifications allowed headings, we could put education under Qualifications. But we need to avoid thin sections. Could combine education into Requirements as well. However we have separate headings: Requirements, Qualifications, Skills. The instruction says use those headings as examples; we can decide which to use. Probably we need Requirements for mandatory items, Qualifications for preferred/education, Skills for specific tools. But we can also just have Requirements and Skills. Let's think. We have: - Requirements: Excel required (mandatory), interpersonal skills, analytical skills, detail-oriented, ability to handle multiple tasks, etc. Those are requirements. - Qualifications: currently enrolled undergraduate in co-op program. - Skills: Experience with PowerPoint/Visio plus, Tableau/Power BI plus. But the instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Qualifications and Skills into Requirements? But they'd be thin if separated. However we have enough content for each. Let's decide: Section: About the role (intro) Section: Responsibilities (combined list) Section: Requirements (mandatory: Excel required, interpersonal/communication, analytical, detail-oriented, ability to handle multiple tasks, self-motivated, etc.) Section: Qualifications (currently enrolled undergraduate in co-op program) Section: Skills (PowerPoint/Visio, Tableau/Power BI, etc.) Section: Pay (Hourly Pay Rate: $21.00-$25.00) Section: Schedule (6-month commitment, Mon-Fri, Jan 13 2027 - Jun 25 2027, 35-40 hours) We should not include Benefits unless we have specific content; we have structured activities but we could put them under Responsibilities as learning opportunities. That would avoid a thin Benefits section. Let's incorporate those structured activities into Responsibilities list. Thus we will not create Benefits. Now we need to output HTML fragment only, with

  headings and

  • for lists,

    for prose. We must not repeat job title as heading. Not include Job ID etc. We must preserve all substantive information; not invent or summarize away detail. We need to ensure we don't lose any detail: The structured activities list items, the conclusion exposure list, the key responsibilities list, the what you will do list, the culture paragraph, the program description, the job summary maybe. We need to include the job summary: "Join the GIT team as part of the Project Operations and Analytics (PM Ops) group, where you'll play a key role in shaping and executing operational and financial processes of the Technology organization. This position supports GIT project management through project onboarding, resource planning, performance metrics, and financial monitoring." That's substantive; could be part of About the role or Responsibilities. Probably put under About the role as a paragraph. We also have "MFS Co-op positions are a 6-month commitment, working Monday – Friday (beginning on Wednesday, January 13th through Friday June 25th, 2027), and work between 35-40 hours." That's schedule. We have "Our program is designed for undergraduate students who are currently enrolled in a co-op program through their college or university and can meet our requirements." That's qualification. We have "At the conclusion of this position, Co-ops will have gained practical exposure to how technology supports an asset manager, including project operations, financial analysis, budgeting and reporting, process documentation, data analysis, and cross-functional collaboration with Global Information Technology (GIT) and Corporate Finance teams." That's responsibilities/outcome. We have "Key Responsibilities" list. We have "What You Will Do" list. We have "Joining our team provides opportunities to share your voice and talents, tackle challenging problems, create solutions and collaborate with dedicated co-workers." That's responsibilities. We have "This Co-op experience provides participants with meaningful, relevant work experience as part of their academic studies." That's responsibilities. We have "In addition to daily responsibilities, participants will have the opportunity to participate in a series of structured activities designed to enhance their learning experience including: Co-Op New Hire Orientation Senior Leadership Speaker Series Social & Networking Events Presentation Challenges" That's responsibilities/benefits. We need to ensure we don't duplicate same content across sections. Let's craft sections:

    About the role

    At MFS, you will find a culture that supports you in doing what you do best. Our employees work together to reach better outcomes, favoring the strongest idea over the strongest individual. We put people first and demonstrate care and compassion for our community and each other. Because what we do matters – to us as valued professionals and to the millions of people and institutions who rely on us to help them build more secure and prosperous futures. MFS is a global investment management firm focused on creating long-term value responsibly by doing what’s right for our clients every day. Our rich history dates to 1924, when our founders invented the mutual fund. Since then, collaboration and innovation have fueled our success. Our unwavering commitment to finding the best, most durable investment opportunities is what sets us apart – and our success is grounded in our unique approach, disciplined philosophy and collaborative