Alternative Investments Business Transformation Business Analyst, Officer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the job posting. Content: - Who We Are Looking For: description of role: Officer level independent contributor needed for Alternative Investments Transformation team. Work closely with tech, stakeholders, varied role. Candidate must familiarize quickly, design solutions, organized, deliver timely, strong initiative, work under pressure, multiple assignments. - What You Will Be Responsible For: bullet list of responsibilities. - What We Value: list of skills. - Education & Preferred Qualifications: bullet list. - About State Street: description of company, benefits, etc. - Salary Range: $60,000 - $101,250 Annual. - Benefits: description of benefits program. - Also mention flexible work programs, development programs, etc. - There's also "Work, Live and Grow." etc. - There's also "Inclusion, Diversity and Social Responsibility." - There's also "State Street is an equal opportunity..." but we need to remove EEO boilerplate. - Also "Job ID: R-768994" drop. - Also "Salary Range: ..." we need Pay section if actual numbers given. Yes we have salary range. - Benefits: we have description of benefits program. - Schedule: not mentioned explicitly; maybe flexible work programs but not explicit schedule. We should not create Schedule section unless posting actually states them. It mentions flexible Work Programs, but not explicit schedule like full-time, part-time, shift. Probably not enough to create Schedule section. So omit. - Also "About State Street" repeated twice; we can combine into one About the company section? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. There's no "About the company" heading listed, but we could use "About the role" for the initial description? Actually "About the role" is for role description. The "Who We Are Looking For" and "What You Will Be Responsible For" could be under About the role and Responsibilities. Then "What We Value" could be Skills. "Education & Preferred Qualifications" could be Requirements and Qualifications (maybe combine). Benefits and Pay sections. We need to decide mapping. We have: - About the role: could be the "Who We Are Looking For" paragraph. - Responsibilities: the bullet list under "What You Will Be Responsible For". - Requirements: maybe education and experience? Could be "Education & Preferred Qualifications". - Qualifications: maybe also same as Requirements? Could split: Requirements (hard requirements) and Qualifications (preferred). But we have only one section for education & preferred qualifications. Could treat as Qualifications. - Skills: the "What We Value" list. - Benefits: the benefits description. - Pay: salary range. - Schedule: none. We also have "About State Street" description of company; could be omitted? The instruction says we can include sections only when posting has real specific content for it. There's no heading for About the company in the list, but we could include it under maybe "About the role"? Not appropriate. Probably we should not include a separate section for company overview unless we map it to something like "About the role"? But that seems odd. The instruction list includes only those headings; we should not create other headings. So we should omit the company overview unless we can fit it under one of those headings. Perhaps we can put it under "About the role" as part of role description? But that seems misrepresenting. However the instruction says: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It might be okay to use other headings if needed, but they gave examples. Safer to stick to those. Thus we will produce sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We need to ensure we don't repeat job title as heading. Not needed. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them into lists. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to drop Job ID, etc. We need to drop the equal opportunity statements, etc. We need to drop the "Discover more at StateStreet.com/careers" etc. We need to drop the "Read our CEO Statement" etc. We need to drop the "Job Application Disclosure" about lie detector test. We need to drop the "About State Street" duplicated? We'll keep some company description if it's substantive? But maybe it's considered boilerplate? It's about the company, not strictly boilerplate but maybe we can keep under About the role? Hmm. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The company description is not necessarily boilerplate; it's substantive info about the employer. Could be kept. But we lack a heading for it. Perhaps we can include it under "About the role" as a brief intro? But that would mix role and company. Alternatively, we could create a heading "About State Street" even though not in examples; but the instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not an exhaustive list. So we could add other headings like "About State Street". However to be safe, maybe we should include it under "About the role"? But that seems odd. Let's examine the original: "Who We Are Looking For Officer level independent contributor needed for the Alternative Investments Transformation team. This role will work closely ..." That's role description. Then "What You Will Be Responsible For ..." responsibilities. Then "What We Value These skills will help you succeed in this role" list. Then "Education & Preferred Qualifications" list. Then "About State Street What we do. State Street is one of the largest custodian banks..." That's company overview. Then "Work, Live and Grow." benefits description. Then "Inclusion, Diversity and Social Responsibility." (EEO-ish) but we need to remove EEO boilerplate. This section is about inclusion, diversity; might be considered EEO? It's about diversity and inclusion; could be considered EEO-related. The instruction says remove EEO/equal-opportunity boilerplate. So we should remove that section. Then "State Street is an equal opportunity and affirmative action employer." Remove. Then "Discover more at StateStreet.com/careers" remove. Then "About State Street Across the globe, institutional investors rely on us..." another company overview duplicate; remove duplicated lines. Then "Join us in shaping the future." etc. Then "As an Equal Opportunity Employer..." remove. Then "Discover more information on jobs at StateStreet.com/careers" remove. Then "Read our CEO Statement" remove. Then "Job Application Disclosure: It is unlawful..." remove. Then "Job ID: R-768994" remove. Thus we keep: - Who We Are Looking For (role description) - What You Will Be Responsible For (responsibilities) - What We Value (skills) - Education & Preferred Qualifications (requirements/qualifications) - About State Street (first occurrence) maybe keep as company overview. - Work, Live and Grow (benefits description) - includes benefits, flexible work programs, development programs. - Salary Range (pay) - Benefits description (the paragraph after Salary Range about retirement savings plan etc.) Actually there is a benefits paragraph after Salary Range: "Employees are eligible to participate in State Street’s comprehensive benefits program, which includes: our retirement savings plan (401K) with company match; insurance coverage including basic life, medical, dental, vision, long-term disability, and other optional additional coverages; paid-time off including vacation, sick leave, short term disability, and family care responsibilities; access to our Employee Assistance Program; incentive compensation including eligibility for annual performance-based awards (excluding certain sales roles subject to sales incentive plans); and, eligibility for certain tax advantaged savings plans. For a full overview, visit https://hrportal.ehr.com/statestreet/Home." That's also benefits. Thus we have benefits info in two places: Work, Live and Grow (flexible work programs, development programs, volunteer days, etc.) and the benefits paragraph. We should combine them under Benefits section. Now we need to map to headings. Let's define:

About the role

-> contains the "Who We Are Looking For" paragraph.

Responsibilities

-> list of responsibilities.

Requirements

-> maybe education and experience? Could be "Bachelor’s degree in a relevant field of study. 3+ years of experience working within an investment firm in a technology, front office or software related role". Also PC Skills – Microsoft products, Jira and Confluence. Preferred experience in Alternative Investments. Could be considered requirements.

Qualifications

-> maybe "Preferred experience in Alternative Investments." But we already included that. Could split: Requirements (hard) and Qualifications (preferred). Let's do: Requirements: Bachelor’s degree, 3+ years experience, PC Skills (Microsoft products, Jira, Confluence). Qualifications: Preferred experience in Alternative Investments. Alternatively, we could combine them under Qualifications. But we need to avoid thin sections. Let's make Requirements include degree, experience, PC skills. Qualifications include preferred experience in Alternative Investments.

Skills

-> the "What We Value" list.

Benefits

-> combine Work, Live and Grow and benefits paragraph.

Pay

-> salary range. We must not include Schedule. Now we need to ensure we preserve all substantive information. Let's extract each piece. Who We Are Looking For: "Officer level independent contributor needed for the Alternative Investments Transformation team. This role will work closely with Alternative Investments technology, various internal and external stakeholders in a varied and challenging role. A good candidate is able to familiarize themselves with existing solutions quickly and design meaningful solutions for our internal operations team as well as the client. Additionally, candidates must be well-organized and able to deliver projects in a timely manner. Candidates must demonstrate strong initiative, be able to perform well under pressure and be capable of working on multiple, diverse assignments." We'll keep that as a paragraph (

). Responsibilities: bullet list: - Create, manage and interpret end user requirements and work to meet those needs by working with cross functional teams and follow through to implementation. - Resolve and escalate project and operational issues in a timely fashion. - Provide business requirements and analysis to internal and external clients on current and future state operating models. - Create test and execute documentation to demonstrate newly developed functionality is in line with business use cases. - Understand, follow and demonstrate compliance with all relevant internal policies and procedures, as well as provide input to further development of best practices. We need to preserve exactly; maybe keep as

• each. What We Value (Skills): List: - Excellent communication skills - Creative problem-solving skills and analysis skills to help build solutions - Initiative, self-motivation and the ability to work independently - Strong relationship-building skills - Sense of urgency when performing tasks and projects; ability to respond to shifting priorities - Effectively communicate progress and escalations - Be a team player yet display a culture of individual ownership of tasks. We need to keep each as