Senior Director, Investment Thought Leadership
BNY · New York, NY · 4 wk ago
OTHRFull-time
We need to output HTML fragment with sections for headings where content exists. Must not repeat job title. Must not include Job ID etc. Must not include boilerplate like EEO, legal, etc. Must not include application instructions. Must preserve substantive info.
We need to parse the job description.
Sections: About the role (intro paragraph). Responsibilities (list). Qualifications (list). Benefits (maybe present). Pay (maybe not explicit). Schedule (none). Skills (maybe part of qualifications). The posting includes "About Us", "About The Team", "Our Benefits And Rewards". We need to include sections only when there is real specific content. "About Us" and "About The Team" maybe not required headings; but we could include "About the company" maybe not required. The instructions: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings if applicable.
We have: About the role: intro paragraph describing role. Responsibilities: bullet list of key responsibilities. Qualifications: list of qualifications. Skills: maybe part of qualifications but we could separate if distinct. Benefits: there is "Our Benefits And Rewards" section with details. Pay: there is mention: "The expected base salary for this position when employment commences can be found in the Job Info section at the bottom of the posting." No actual number given, just says can be found elsewhere. That's not specific content; we should not create Pay section because no actual salary figure. So omit Pay.
Schedule: none.
Requirements: maybe same as Qualifications; but we can use Qualifications heading.
We need to avoid boilerplate like EEO, equal opportunity, scam-warning, etc. Also remove duplicated lines, navigation, cookie, legal. So we must strip the "BNY is an Equal Employment Opportunity..." etc. Also remove "About Us", "About The Team", maybe we could keep as "About the company" but not required headings. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. Probably we should stick to those. So we can include About the role, Responsibilities, Qualifications, Benefits. Possibly Skills if we extract skills from qualifications.
We need to preserve all substantive information. So we need to include the details from About Us and About The Team? Those are substantive but not under prescribed headings. Could we include them under About the role? Probably not; they are about company. But we could omit them if not under allowed headings? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive list. It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive list. It says "Use for section headings (e.g. ...)". So we can use other headings if needed, but better to stick to examples. However, we need to preserve ALL substantive information; if we omit About Us and About The Team, we lose info. So we should include them perhaps under a heading like "About the company" or "About BNY". The instruction didn't forbid other headings; it just gave examples. So we can add an About BNY
containing that info.
Similarly, "About The Team" could be under same heading or separate.
We must not include boilerplate like EEO etc. So we strip that.
We also need to remove duplicated lines, navigation, cookie/legal, etc. So we will produce HTML with sections:
About the role
About BNY
containing that info. Similarly, "About The Team" could be under same heading or separate. We must not include boilerplate like EEO etc. So we strip that. We also need to remove duplicated lines, navigation, cookie/legal, etc. So we will produce HTML with sections:About the role
... intro paragraph ...
Responsibilities
- ... each responsibility ...
Qualifications
- ... each qualification ...
- each. For sub-bullets (like Develop content that conveys: then list), we could either keep as part of the li text or nested list. Simpler: include as part of the li text. Qualifications list: from "Qualifications" paragraph bullet-like sentences: - Significant experience in content marketing, investment communications, editorial strategy, or thought leadership development within wealth management, private banking, asset management, or broader financial services - Strong expertise in investment and market-related content, particularly for wealth management or high-net-worth/client advisory audiences - Deep understanding of financial topics, including: - Asset classes - Federal Reserve and macroeconomic policy - Market dynamics - Investment themes - Portfolio and wealth planning concepts - Demonstrated ability to build content programs strategically, not just execute individual deliverables - Exceptional writing, editing, and storytelling skills, with the ability to translate complex financial subject matter into clear, engaging, and client-friendly content - Proven ability to work effectively with senior stakeholders, advisors, portfolio strategists, and subject matter experts - High degree of independence, judgment, and strategic thinking - Strong understanding of how content supports client engagement, advisor enablement, and thought leadership in a wealth management context - Experience working in or closely with a Chief Investment Office, investment strategy team, wealth platform, or advisory business preferred - People management or team-building experience is a plus We'll format similarly. Benefits: from "Our Benefits And Rewards" paragraph: - BNY offers highly competitive compensation, benefits, and wellbeing programs rooted in a strong culture of excellence and our pay-for-performance philosophy. - We provide access to flexible global resources and tools for your life’s journey. - Focus on your health, foster your personal resilience, and reach your financial goals as a valued member of our team, along with generous paid leaves, including paid volunteer time, that can support you and your family through moments that matter. - BNY is an Equal Employment Opportunity/Affirmative Action Employer ... (we must remove EEO boilerplate). So we need to strip that line. - BNY assesses market data to ensure a competitive compensation package for our employees. - The expected base salary for this position when employment commences can be found in the Job Info section at the bottom of the posting. Base salary offered may vary depending on multiple individualized factors, including market location, job-related knowledge, skills, and experience. Base salary is only part of the total rewards package, which may include eligibility for an annual discretionary incentive award. - Subject to the terms and conditions of the applicable plans then in effect, eligible employees may enroll in a 401(k) plan as well as participate in Company-sponsored medical, dental, vision, and basic life insurance plans for the employee and the employee’s eligible dependents. - Eligible employees also may receive other benefits (including various paid time off benefits, such as vacation and sick time), dependent on the position offered. - Details of participation in these benefit plans will be provided if an employee receives an offer of employment. - If hired, the employee will be in an “at will” position and the Company reserves the right to modify base salary (as well as any other discretionary payments or compensation programs) at any time, including for reasons related to individual performance, Company or individual department/team performance, and market factors. We need to remove EEO line and maybe the "at will" statement? That's still part of benefits? It's more legal. Might be considered boilerplate. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The "at will" statement is legal. So we should remove that as well. Also remove the line about base salary being found elsewhere? That's not a specific salary figure; but it's still about pay. Since we are not including Pay section, we could omit that sentence. However, it's part of Benefits And Rewards paragraph; we could keep it as part of benefits description? It's about compensation. Might be okay to keep but it's not a specific benefit. The instruction: do not create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits section is okay because there are benefits described. Within that section we can include the descriptive sentences about benefits, but we might want to exclude the generic legal statements. We'll keep sentences that describe benefits: competitive compensation, flexible global resources, focus on health, generous paid leaves including volunteer time, 401(k), medical/dental/vision/life insurance, other benefits like paid time off. We'll exclude the base salary variability sentence, the EEO line, the at-will line, the market data line maybe okay as it's about compensation but it's generic.