Project Mgr I (US)
for section headings 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 information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a 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 the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to parse the posting.
Key info:
- Work Location: Wilmington, Delaware, United States of America
- Hours: 40
- Pay Details: $91,000 - $136,240 USD
- There's a paragraph about TD compensation policies, etc.
- Line Of Business: Sales & Customer Distribution Support
- Job Description: The Project Manager provides leadership and guidance to project related staff and business lines. Effectively manages project resources and/or vendors in coordination of competing priorities. Executes project management deliverables within budget working with staff and business partners.
- Depth & Scope: bullet list (actually sentences) describing responsibilities.
- Education & Experience: Bachelor's degree, 3-5 Years of related experience, Excellent communication..., etc.
- Physical Requirements: a list of categories with percentages.
- The above statements... (boilerplate)
- Who We Are: description of TD.
- Our Total Rewards Package: description of benefits.
- Learn more (maybe link)
- Additional Information: about development, training, onboarding, interview process, accommodation.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
We need to keep substantive info: location, hours, pay, line of business, job description (responsibilities), depth & scope (more responsibilities), education & experience (requirements/qualifications), physical requirements (maybe as a section? Could be under Requirements or separate? The instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings.
We have:
- About the role: maybe a brief overview: The Project Manager provides leadership... (job description). Could be under "About the role" or "Responsibilities". The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which sections to include based on content.
We have location, hours, pay details. Pay details: we have a salary range. So we should include a Pay section with that range. Hours: maybe Schedule? Hours 40 could be schedule (full-time). So we could include Schedule section with "40 hours per week". Location maybe could be part of About the role or a separate? Not listed as a heading option but we could include location in About the role paragraph.
Line of Business: maybe part of About the role.
Responsibilities: we have job description and depth & scope bullet points.
Requirements/Qualifications/Skills: Education & Experience includes degree, years experience, skills (communication, problem solving, decision making, etc.). Could split into Requirements (education & experience) and Skills (specific skills). Or combine.
Benefits: Our Total Rewards Package describes benefits: base salary and variable compensation/incentive awards, health and well-being benefits, savings and retirement programs, paid time off, banking benefits and discounts, career development, reward and recognition. So we can include Benefits section with that list.
Schedule: Hours 40 => full-time schedule.
We need to avoid filler like "commensurate with experience", "not specified", etc. We have actual pay range, so Pay section is valid.
We need to remove duplicated lines: there are duplicated sentences in job description: "Provides leadership and guidance to project related staff and/or business lines in support of a project portfolio" appears twice? Actually appears in Depth & Scope list and earlier. We should deduplicate.
We need to preserve all substantive information, not invent or summarize away detail. So we need to include each distinct piece of info.
Let's extract substantive info:
- Work Location: Wilmington, Delaware, United States of America
- Hours: 40 (presumably per week)
- Pay Details: $91,000 - $136,240 USD
- Line Of Business: Sales & Customer Distribution Support
- Job Description (core): The Project Manager provides leadership and guidance to project related staff and business lines. Effectively manages project resources and/or vendors in coordination of competing priorities. Executes project management deliverables within budget working with staff and business partners.
- Depth & Scope (more responsibilities):
- Manages mid-size projects or significant segments of very large projects with limited supervision
- Acts as a consultant to the business lines
- Prepares management reports to summarize the status of projects and work activities
- Initiates project evaluation effectiveness post-implementation; Documents findings and incorporates changes into future project plans
- Coaches employees to ensure activities are undertaken and completed
- Assists employees in compliance with all human resources policies, procedures & guidelines of conduct
- Coordinates the sharing of information, skills, and knowledge among Employees
- Provides leadership and guidance to project related staff and/or business lines in support of a project portfolio
- Ensures compliance to policies and procedures
- Utilizes the Company business project management model as appropriate to manage high visibility, Company Wide projects as appropriate
- Manages all communications to key stakeholders and ensures all are aware of significant changes to project status in a timely manner
- Ensures all employees understand the readiness process and facilitates readiness sessions for implementation
- Education & Experience:
- Bachelor's degree
- 3-5 Years of related experience
- Excellent communication, problem-solving and decision making skills with ability to effectively communicate with all levels of the organization
- Demonstrated ability to build strong collaborative business and technology relationships
- Proven ability to manage multiple competing priorities, making sound business decisions
- Self driven and have excellent problem solving skills
- Detail oriented and have well-developed organizational skills
- Individual must have exceptional interpersonal skills, ability to maintain confidentiality, flexible and possess a high degree of initiative and motivation
- Proven record of providing excellent internal and external Customer service
- Physical Requirements: a table of activities with percentages (Never, Occasional, Frequent, Continuous). This is substantive. Should we include? Possibly under Requirements or a separate section? Not in the list of headings but we could include under Requirements or maybe a separate "Physical Requirements" heading not listed but we are told to prefer sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we can still include other headings if needed? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, not exclusive. But later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text ... and never create Pay/Schedule/Benefits sections unless the posting actually states them." It doesn't forbid other headings, but suggests we should prefer those. However we could include Physical Requirements under Requirements or maybe as a subsection within Requirements. Since we need to preserve all substantive info, we need to include physical requirements somewhere. Could be under Requirements as a list.
- The paragraph about "The above statements are intended to describe the general nature..." is boilerplate; we can remove.
- Who We Are: description of TD; could be considered About the role? Actually it's about the company, not the role. Could be omitted? It's substantive but maybe not required? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it. Where to put? Could be under About the role? But About the role is about the role, not company. However we could have a section "About TD" but not in the list. Might be okay to include as a paragraph under a heading like "About the company". But the instruction didn't forbid other headings; just gave examples. However they said "Prefer a few substantive sections over many thin ones." So we could combine company description into About the role or maybe a brief intro.
- Our Total Rewards Package: benefits description.
- Learn more: maybe a link; we can ignore as it's likely a call to action.
- Additional Information: includes colleague development, training & onboarding, interview process, accommodation. These are substantive. Could be placed under Benefits? Not exactly. Could be under a section like "Development & Training" or "Additional Information". But we need to decide.
We need to avoid application instructions: "Learn more", "Interview Process", "Accommodation" maybe considered application instructions? The instruction says remove application instructions. So we should remove lines about interview process, accommodation, maybe also "Learn more". However "Colleague Development", "Training & Onboarding" are about employee development, not application instructions. Might be okay to keep as part of Benefits or a separate section like "Development". But the instruction says remove application instructions. So we should strip out "Interview Process", "Accommodation", "Learn more". Also maybe "Additional Information" heading itself is just a heading; we can keep the content under appropriate sections.
We need to remove duplicated lines: we saw duplicate "Provides leadership and guidance to project related staff and/or business lines in support of a project portfolio". We'll keep only once.
Now we need to decide on sections.
Potential sections:
- About the role: could include a brief summary: The Project Manager provides leadership and guidance to project related staff and business lines... plus line of business and location/hours? Might be okay.
- Responsibilities: list of duties from Job Description and Depth & Scope.
- Requirements: Education & Experience (degree, years experience) plus maybe physical requirements? Could separate.
- Qualifications: maybe same as Requirements? But we can combine.
- Skills: list of skills from Education & Experience (communication, problem solving, decision making, building relationships, managing priorities, self-driven, detail oriented, interpersonal, confidentiality, flexible, initiative, motivation, customer service).
- Benefits: Total Rewards Package description.
- Pay: salary range.
- Schedule: Hours 40 (full-time).
We need to avoid thin sections. So maybe combine Requirements and Qualifications into one section "Requirements". Or have Requirements (education/experience) and Skills separate.
We need to use - for any list of duties/requirements/benefits. So for responsibilities, requirements, skills, benefits we should use lists.
We need to use
for prose.
We must not repeat job title as heading.
We must not include Job ID/requisition numbers (none present).
We must output only HTML fragment.
Let's craft.
First, maybe a
for location and hours? Could be part of About the role.
Section About the role:
About the role
... includes location, hours, line of business, brief summary.
Then Responsibilities: Responsibilities
- ... each duty.
Then Requirements: Requirements
- Bachelor's degree
- 3-5 years of related experience
Then Skills: Skills
- ... each
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a 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 the posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting. Key info: - Work Location: Wilmington, Delaware, United States of America - Hours: 40 - Pay Details: $91,000 - $136,240 USD - There's a paragraph about TD compensation policies, etc. - Line Of Business: Sales & Customer Distribution Support - Job Description: The Project Manager provides leadership and guidance to project related staff and business lines. Effectively manages project resources and/or vendors in coordination of competing priorities. Executes project management deliverables within budget working with staff and business partners. - Depth & Scope: bullet list (actually sentences) describing responsibilities. - Education & Experience: Bachelor's degree, 3-5 Years of related experience, Excellent communication..., etc. - Physical Requirements: a list of categories with percentages. - The above statements... (boilerplate) - Who We Are: description of TD. - Our Total Rewards Package: description of benefits. - Learn more (maybe link) - Additional Information: about development, training, onboarding, interview process, accommodation. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to keep substantive info: location, hours, pay, line of business, job description (responsibilities), depth & scope (more responsibilities), education & experience (requirements/qualifications), physical requirements (maybe as a section? Could be under Requirements or separate? The instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings. We have: - About the role: maybe a brief overview: The Project Manager provides leadership... (job description). Could be under "About the role" or "Responsibilities". The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which sections to include based on content.
We have location, hours, pay details. Pay details: we have a salary range. So we should include a Pay section with that range. Hours: maybe Schedule? Hours 40 could be schedule (full-time). So we could include Schedule section with "40 hours per week". Location maybe could be part of About the role or a separate? Not listed as a heading option but we could include location in About the role paragraph.
Line of Business: maybe part of About the role.
Responsibilities: we have job description and depth & scope bullet points.
Requirements/Qualifications/Skills: Education & Experience includes degree, years experience, skills (communication, problem solving, decision making, etc.). Could split into Requirements (education & experience) and Skills (specific skills). Or combine.
Benefits: Our Total Rewards Package describes benefits: base salary and variable compensation/incentive awards, health and well-being benefits, savings and retirement programs, paid time off, banking benefits and discounts, career development, reward and recognition. So we can include Benefits section with that list.
Schedule: Hours 40 => full-time schedule.
We need to avoid filler like "commensurate with experience", "not specified", etc. We have actual pay range, so Pay section is valid.
We need to remove duplicated lines: there are duplicated sentences in job description: "Provides leadership and guidance to project related staff and/or business lines in support of a project portfolio" appears twice? Actually appears in Depth & Scope list and earlier. We should deduplicate.
We need to preserve all substantive information, not invent or summarize away detail. So we need to include each distinct piece of info.
Let's extract substantive info:
- Work Location: Wilmington, Delaware, United States of America
- Hours: 40 (presumably per week)
- Pay Details: $91,000 - $136,240 USD
- Line Of Business: Sales & Customer Distribution Support
- Job Description (core): The Project Manager provides leadership and guidance to project related staff and business lines. Effectively manages project resources and/or vendors in coordination of competing priorities. Executes project management deliverables within budget working with staff and business partners.
- Depth & Scope (more responsibilities):
- Manages mid-size projects or significant segments of very large projects with limited supervision
- Acts as a consultant to the business lines
- Prepares management reports to summarize the status of projects and work activities
- Initiates project evaluation effectiveness post-implementation; Documents findings and incorporates changes into future project plans
- Coaches employees to ensure activities are undertaken and completed
- Assists employees in compliance with all human resources policies, procedures & guidelines of conduct
- Coordinates the sharing of information, skills, and knowledge among Employees
- Provides leadership and guidance to project related staff and/or business lines in support of a project portfolio
- Ensures compliance to policies and procedures
- Utilizes the Company business project management model as appropriate to manage high visibility, Company Wide projects as appropriate
- Manages all communications to key stakeholders and ensures all are aware of significant changes to project status in a timely manner
- Ensures all employees understand the readiness process and facilitates readiness sessions for implementation
- Education & Experience:
- Bachelor's degree
- 3-5 Years of related experience
- Excellent communication, problem-solving and decision making skills with ability to effectively communicate with all levels of the organization
- Demonstrated ability to build strong collaborative business and technology relationships
- Proven ability to manage multiple competing priorities, making sound business decisions
- Self driven and have excellent problem solving skills
- Detail oriented and have well-developed organizational skills
- Individual must have exceptional interpersonal skills, ability to maintain confidentiality, flexible and possess a high degree of initiative and motivation
- Proven record of providing excellent internal and external Customer service
- Physical Requirements: a table of activities with percentages (Never, Occasional, Frequent, Continuous). This is substantive. Should we include? Possibly under Requirements or a separate section? Not in the list of headings but we could include under Requirements or maybe a separate "Physical Requirements" heading not listed but we are told to prefer sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we can still include other headings if needed? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, not exclusive. But later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text ... and never create Pay/Schedule/Benefits sections unless the posting actually states them." It doesn't forbid other headings, but suggests we should prefer those. However we could include Physical Requirements under Requirements or maybe as a subsection within Requirements. Since we need to preserve all substantive info, we need to include physical requirements somewhere. Could be under Requirements as a list.
- The paragraph about "The above statements are intended to describe the general nature..." is boilerplate; we can remove.
- Who We Are: description of TD; could be considered About the role? Actually it's about the company, not the role. Could be omitted? It's substantive but maybe not required? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it. Where to put? Could be under About the role? But About the role is about the role, not company. However we could have a section "About TD" but not in the list. Might be okay to include as a paragraph under a heading like "About the company". But the instruction didn't forbid other headings; just gave examples. However they said "Prefer a few substantive sections over many thin ones." So we could combine company description into About the role or maybe a brief intro.
- Our Total Rewards Package: benefits description.
- Learn more: maybe a link; we can ignore as it's likely a call to action.
- Additional Information: includes colleague development, training & onboarding, interview process, accommodation. These are substantive. Could be placed under Benefits? Not exactly. Could be under a section like "Development & Training" or "Additional Information". But we need to decide.
We need to avoid application instructions: "Learn more", "Interview Process", "Accommodation" maybe considered application instructions? The instruction says remove application instructions. So we should remove lines about interview process, accommodation, maybe also "Learn more". However "Colleague Development", "Training & Onboarding" are about employee development, not application instructions. Might be okay to keep as part of Benefits or a separate section like "Development". But the instruction says remove application instructions. So we should strip out "Interview Process", "Accommodation", "Learn more". Also maybe "Additional Information" heading itself is just a heading; we can keep the content under appropriate sections.
We need to remove duplicated lines: we saw duplicate "Provides leadership and guidance to project related staff and/or business lines in support of a project portfolio". We'll keep only once.
Now we need to decide on sections.
Potential sections:
- About the role: could include a brief summary: The Project Manager provides leadership and guidance to project related staff and business lines... plus line of business and location/hours? Might be okay.
- Responsibilities: list of duties from Job Description and Depth & Scope.
- Requirements: Education & Experience (degree, years experience) plus maybe physical requirements? Could separate.
- Qualifications: maybe same as Requirements? But we can combine.
- Skills: list of skills from Education & Experience (communication, problem solving, decision making, building relationships, managing priorities, self-driven, detail oriented, interpersonal, confidentiality, flexible, initiative, motivation, customer service).
- Benefits: Total Rewards Package description.
- Pay: salary range.
- Schedule: Hours 40 (full-time).
We need to avoid thin sections. So maybe combine Requirements and Qualifications into one section "Requirements". Or have Requirements (education/experience) and Skills separate.
We need to use - for any list of duties/requirements/benefits. So for responsibilities, requirements, skills, benefits we should use lists.
We need to use
for prose.
We must not repeat job title as heading.
We must not include Job ID/requisition numbers (none present).
We must output only HTML fragment.
Let's craft.
First, maybe a
for location and hours? Could be part of About the role.
Section About the role:
About the role
... includes location, hours, line of business, brief summary.
Then Responsibilities: Responsibilities
- ... each duty.
Then Requirements: Requirements
- Bachelor's degree
- 3-5 years of related experience
Then Skills: Skills
- ... each
- for any list of duties/requirements/benefits. So for responsibilities, requirements, skills, benefits we should use lists.
We need to use
for prose. We must not repeat job title as heading. We must not include Job ID/requisition numbers (none present). We must output only HTML fragment. Let's craft. First, maybe a
for location and hours? Could be part of About the role. Section About the role:
About the role
... includes location, hours, line of business, brief summary.
Then Responsibilities:Responsibilities
- ... each duty.
Requirements
- Bachelor's degree
- 3-5 years of related experience
Skills
- ... each