Construction Project Manager
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info; do not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them.
We need to parse the job description.
Content:
- Job Description: "We’re seeking a future team member for the role of Construction Project Manager to join our CPM team .This role is in New York City, NY."
- Then: "In this role you’ll make an impact in the following ways:" followed by bullet-like sentences separated by periods? Actually they are sentences separated by periods but not bullet list. They are:
1. Lead, manage and collaborate with construction and design staff, internal partners (i.e., Technology, Security, Corporate Services) and outsource providers for building sites in multiple regions.
2. Provide leadership to outsourced partners, professional staff, and contractors to implement and monitor processes and procedures.
3. Oversee initiatives to execute business plans and develop functional strategies to achieve key objectives.
4. Set specialty priorities, allocate resources, and manage the performance of senior construction managers.
5. Have an expert understanding of all building sites and construction-related matters in the portfolio.
These are responsibilities/duties.
Then: "To be successful in this role, we’re seeking the following:" then list:
- 10+ years of relevant experience in a corporate environment with ≥ 7 years in a leadership role emphasizing international work and significant US HQ Renovation projects (preferably NYC).
- Bachelor's degree or the equivalent combination of education and experience
- Knowledge of construction and project management software
- Strong written and oral communication skills
- Proficiency in Microsoft Excel, Word, and PowerPoint
- Interest in financial services and a corporate workplace.
These are requirements/qualifications/skills.
Then "About Us" paragraph: description of BNY.
Then "About The Team" paragraph: mentions BNY newsroom, LinkedIn, recent awards.
Then "Our Benefits And Rewards": description of benefits.
Then EEO statement etc.
We need to extract sections: About the role (maybe summary), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide which sections have content.
- About the role: Could be the introductory paragraph: "We’re seeking a future team member for the role of Construction Project Manager to join our CPM team. This role is in New York City, NY." That's about the role. We can put that as
About the role
with .
- Responsibilities: The list of impact ways. That's responsibilities.
- Requirements: The list of experience, degree, etc. Could be Requirements.
- Qualifications: Might overlap with requirements; but we can separate: maybe Qualifications includes Bachelor's degree etc. However we need to avoid thin sections. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Requirements and Qualifications into one section? But they ask to use headings for those specific names if content exists. We need to decide if we have enough content for each.
We have:
- Requirements: 10+ years experience, leadership, etc. That's substantive.
- Qualifications: Bachelor's degree or equivalent combination, knowledge of software, communication skills, proficiency in MS Office, interest in financial services. Those are also qualifications/skills.
- Skills: Could be the same as qualifications; maybe we can treat "Skills" as the list of software, communication, MS Office, interest in financial services.
But we need to avoid duplication. Perhaps we can have:
- Responsibilities (list)
- Requirements (list of experience and education)
- Skills (list of technical and soft skills)
- Benefits (list from Benefits And Rewards)
- About the role (intro)
- About the team / About Us maybe combine? But we have About Us and About The Team separate. Could combine into About the company/team.
But we need to follow instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings if we have content.
We have content for About the role, Responsibilities, Requirements, Qualifications (maybe), Skills, Benefits. Pay and Schedule: not explicitly stated. The posting mentions base salary can be found in Job Info section at bottom, but not given. It says "Base salary offered may vary depending on multiple individualized factors..." but no actual number. So we should NOT create Pay or Schedule sections because they are not stated specifically (no numbers). So we omit Pay and Schedule.
We need to ensure we don't create sections with filler like "commensurate with experience". We have actual content.
Now we need to strip boilerplate: EEO statement, legal, etc. Also remove duplicated lines, navigation, cookie, application instructions. The posting includes "BNY is an Equal Employment Opportunity/Affirmative Action Employer..." etc. That's boilerplate; remove.
Also remove "If hired, the employee will be in an “at will” position..." etc. That's legal; remove.
Also remove "BNY assesses market data..." etc. That's part of benefits? Actually it's about compensation; but it's generic. Might be considered boilerplate. However the Benefits And Rewards section includes some substantive info: "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." That's substantive.
Then later: "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." That's also substantive benefits.
We should keep that.
We need to format Benefits as a list using
- . The benefits description includes multiple items: competitive compensation, benefits, wellbeing programs, flexible global resources/tools, focus on health, personal resilience, financial goals, generous paid leaves (including paid volunteer time), 401(k) plan, medical/dental/vision/basic life insurance, other benefits (paid time off vacation/sick time). We can turn each into list items.
Now we need to ensure we don't repeat content.
Let's extract sections:
About the role: "We’re seeking a future team member for the role of Construction Project Manager to join our CPM team. This role is in New York City, NY."
Responsibilities: list of 5 items.
Requirements: maybe combine experience and education? Actually the list after "To be successful in this role, we’re seeking the following:" includes both experience/education and skills. Could split: Requirements: 10+ years experience..., Bachelor's degree or equivalent. Qualifications: Knowledge of construction and project management software, Strong written and oral communication skills, Proficiency in Microsoft Excel, Word, and PowerPoint, Interest in financial services and a corporate workplace.
But we could also treat Requirements as the experience/education, Qualifications as the knowledge/skills, Skills as maybe the software proficiency etc. However to avoid thin sections, we could combine Requirements and Qualifications into one section called Requirements (or Qualifications). But the instruction says to use those headings if content exists. It doesn't forbid combining similar content under one heading; but we should not create empty headings.
We could have:
- About the role
- Responsibilities
- Requirements (includes experience, education, knowledge, skills, etc.)
- Benefits
But then we would miss Qualifications and Skills headings. However the instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we must use all of them; just that if we use a heading, it should be one of those. So we can choose which to include.
Thus we can include About the role, Responsibilities, Requirements, Benefits. That seems sufficient.
But we might also include Qualifications if we want to separate experience/education from skills. However that would create two sections; each would be substantive. Let's see if we can split meaningfully:
Requirements: "10+ years of relevant experience in a corporate environment with ≥ 7 years in a leadership role emphasizing international work and significant US HQ Renovation projects (preferably NYC). Bachelor's degree or the equivalent combination of education and experience"
Qualifications: "Knowledge of construction and project management software, Strong written and oral communication skills, Proficiency in Microsoft Excel, Word, and PowerPoint, Interest in financial services and a corporate workplace."
That seems reasonable.
Skills: Could be the same as Qualifications? Actually Qualifications already includes skills. But we could treat Skills as maybe the software proficiency etc. However that would be thin.
Better to have Requirements and Qualifications as above, and maybe not separate Skills.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits.
Now we need to format lists.
Responsibilities: each sentence as
- .
Requirements: two items? Actually we have two bullet points: experience and education. Could be two
- .
Qualifications: four items: knowledge of software, communication skills, proficiency in MS Office, interest in financial services.
Benefits: we need to extract list items from the benefits paragraph.
Benefits 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."
Then later: "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."
We can turn each distinct benefit into list items:
- Highly competitive compensation, benefits, and wellbeing programs (pay-for-performance philosophy)
- Access to flexible global resources and tools for your life’s journey
- Focus on health, foster personal resilience, reach financial goals
- Generous paid leaves, including paid volunteer time
- 401(k) plan eligibility
- Company-sponsored medical, dental, vision, and basic life insurance plans (employee and dependents)
- Other benefits including various paid time off (vacation, sick time)
We could combine some.
Now we need to output HTML fragment only, no /, no markdown.
We'll produce something like:
About the role
We’re seeking a future team member for the role of Construction Project Manager to join our CPM team. This role is in
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info; do not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. We need to parse the job description. Content: - Job Description: "We’re seeking a future team member for the role of Construction Project Manager to join our CPM team .This role is in New York City, NY." - Then: "In this role you’ll make an impact in the following ways:" followed by bullet-like sentences separated by periods? Actually they are sentences separated by periods but not bullet list. They are: 1. Lead, manage and collaborate with construction and design staff, internal partners (i.e., Technology, Security, Corporate Services) and outsource providers for building sites in multiple regions. 2. Provide leadership to outsourced partners, professional staff, and contractors to implement and monitor processes and procedures. 3. Oversee initiatives to execute business plans and develop functional strategies to achieve key objectives. 4. Set specialty priorities, allocate resources, and manage the performance of senior construction managers. 5. Have an expert understanding of all building sites and construction-related matters in the portfolio. These are responsibilities/duties. Then: "To be successful in this role, we’re seeking the following:" then list: - 10+ years of relevant experience in a corporate environment with ≥ 7 years in a leadership role emphasizing international work and significant US HQ Renovation projects (preferably NYC). - Bachelor's degree or the equivalent combination of education and experience - Knowledge of construction and project management software - Strong written and oral communication skills - Proficiency in Microsoft Excel, Word, and PowerPoint - Interest in financial services and a corporate workplace. These are requirements/qualifications/skills. Then "About Us" paragraph: description of BNY. Then "About The Team" paragraph: mentions BNY newsroom, LinkedIn, recent awards. Then "Our Benefits And Rewards": description of benefits. Then EEO statement etc. We need to extract sections: About the role (maybe summary), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. - About the role: Could be the introductory paragraph: "We’re seeking a future team member for the role of Construction Project Manager to join our CPM team. This role is in New York City, NY." That's about the role. We can put that as
About the role
with. - Responsibilities: The list of impact ways. That's responsibilities. - Requirements: The list of experience, degree, etc. Could be Requirements. - Qualifications: Might overlap with requirements; but we can separate: maybe Qualifications includes Bachelor's degree etc. However we need to avoid thin sections. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Requirements and Qualifications into one section? But they ask to use headings for those specific names if content exists. We need to decide if we have enough content for each. We have: - Requirements: 10+ years experience, leadership, etc. That's substantive. - Qualifications: Bachelor's degree or equivalent combination, knowledge of software, communication skills, proficiency in MS Office, interest in financial services. Those are also qualifications/skills. - Skills: Could be the same as qualifications; maybe we can treat "Skills" as the list of software, communication, MS Office, interest in financial services. But we need to avoid duplication. Perhaps we can have: - Responsibilities (list) - Requirements (list of experience and education) - Skills (list of technical and soft skills) - Benefits (list from Benefits And Rewards) - About the role (intro) - About the team / About Us maybe combine? But we have About Us and About The Team separate. Could combine into About the company/team. But we need to follow instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings if we have content. We have content for About the role, Responsibilities, Requirements, Qualifications (maybe), Skills, Benefits. Pay and Schedule: not explicitly stated. The posting mentions base salary can be found in Job Info section at bottom, but not given. It says "Base salary offered may vary depending on multiple individualized factors..." but no actual number. So we should NOT create Pay or Schedule sections because they are not stated specifically (no numbers). So we omit Pay and Schedule. We need to ensure we don't create sections with filler like "commensurate with experience". We have actual content. Now we need to strip boilerplate: EEO statement, legal, etc. Also remove duplicated lines, navigation, cookie, application instructions. The posting includes "BNY is an Equal Employment Opportunity/Affirmative Action Employer..." etc. That's boilerplate; remove. Also remove "If hired, the employee will be in an “at will” position..." etc. That's legal; remove. Also remove "BNY assesses market data..." etc. That's part of benefits? Actually it's about compensation; but it's generic. Might be considered boilerplate. However the Benefits And Rewards section includes some substantive info: "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." That's substantive. Then later: "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." That's also substantive benefits. We should keep that. We need to format Benefits as a list using
- . The benefits description includes multiple items: competitive compensation, benefits, wellbeing programs, flexible global resources/tools, focus on health, personal resilience, financial goals, generous paid leaves (including paid volunteer time), 401(k) plan, medical/dental/vision/basic life insurance, other benefits (paid time off vacation/sick time). We can turn each into list items.
Now we need to ensure we don't repeat content.
Let's extract sections:
About the role: "We’re seeking a future team member for the role of Construction Project Manager to join our CPM team. This role is in New York City, NY."
Responsibilities: list of 5 items.
Requirements: maybe combine experience and education? Actually the list after "To be successful in this role, we’re seeking the following:" includes both experience/education and skills. Could split: Requirements: 10+ years experience..., Bachelor's degree or equivalent. Qualifications: Knowledge of construction and project management software, Strong written and oral communication skills, Proficiency in Microsoft Excel, Word, and PowerPoint, Interest in financial services and a corporate workplace.
But we could also treat Requirements as the experience/education, Qualifications as the knowledge/skills, Skills as maybe the software proficiency etc. However to avoid thin sections, we could combine Requirements and Qualifications into one section called Requirements (or Qualifications). But the instruction says to use those headings if content exists. It doesn't forbid combining similar content under one heading; but we should not create empty headings.
We could have:
- About the role
- Responsibilities
- Requirements (includes experience, education, knowledge, skills, etc.)
- Benefits
But then we would miss Qualifications and Skills headings. However the instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we must use all of them; just that if we use a heading, it should be one of those. So we can choose which to include. Thus we can include About the role, Responsibilities, Requirements, Benefits. That seems sufficient. But we might also include Qualifications if we want to separate experience/education from skills. However that would create two sections; each would be substantive. Let's see if we can split meaningfully: Requirements: "10+ years of relevant experience in a corporate environment with ≥ 7 years in a leadership role emphasizing international work and significant US HQ Renovation projects (preferably NYC). Bachelor's degree or the equivalent combination of education and experience" Qualifications: "Knowledge of construction and project management software, Strong written and oral communication skills, Proficiency in Microsoft Excel, Word, and PowerPoint, Interest in financial services and a corporate workplace." That seems reasonable. Skills: Could be the same as Qualifications? Actually Qualifications already includes skills. But we could treat Skills as maybe the software proficiency etc. However that would be thin. Better to have Requirements and Qualifications as above, and maybe not separate Skills. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. Now we need to format lists. Responsibilities: each sentence as
- . Requirements: two items? Actually we have two bullet points: experience and education. Could be two
- .
Qualifications: four items: knowledge of software, communication skills, proficiency in MS Office, interest in financial services.
Benefits: we need to extract list items from the benefits paragraph.
Benefits 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."
Then later: "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."
We can turn each distinct benefit into list items:
- Highly competitive compensation, benefits, and wellbeing programs (pay-for-performance philosophy)
- Access to flexible global resources and tools for your life’s journey
- Focus on health, foster personal resilience, reach financial goals
- Generous paid leaves, including paid volunteer time
- 401(k) plan eligibility
- Company-sponsored medical, dental, vision, and basic life insurance plans (employee and dependents)
- Other benefits including various paid time off (vacation, sick time)
We could combine some.
Now we need to output HTML fragment only, no /, no markdown.
We'll produce something like:
About the role
We’re seeking a future team member for the role of Construction Project Manager to join our CPM team. This role is in