Coordinator Assc- Coordinator Sr
American Electric Power · New Albany, OH · 1 mo ago
On-siteInformation Technology$63k–$78k/yrFull-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 remove boilerplate like EEO, navigation, etc. Must include sections only if real specific content.
We need to parse the posting.
Key sections:
- Job Summary (maybe heading "About the role"? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to those headings.
We have:
Job Summary: description of role.
Job Description: includes "What you'll do:" list of duties.
Required Skills And Qualifications: list.
Preferred Experience: list.
What we're looking for: includes grade details (education, experience). This could be under Qualifications or Requirements.
OTHER REQUIREMENTS: list.
What you'll get: includes salary ranges per grade.
Where You'll work: location.
Additional paragraphs about benefits, mission statement.
We need to decide which sections to output.
We must include sections only when posting has real specific content.
We have:
- About the role: could be Job Summary.
- Responsibilities: the "What you'll do:" list.
- Requirements / Qualifications: could combine Required Skills And Qualifications, Preferred Experience, What we're looking for (education/experience), OTHER REQUIREMENTS.
- Skills: maybe separate but we can combine.
- Benefits: "What you'll get:" includes salary ranges and mention of benefits package.
- Pay: could be separate but we have salary ranges; maybe we put under Benefits or Pay. The instruction says include Pay section only if posting actually states them. It does state salary ranges for each grade. So we can have a Pay section.
- Schedule: not mentioned; no schedule info. So omit.
- Benefits: mention of comprehensive benefits package; we can include Benefits section.
We must not include filler like "commensurate with experience". Not present.
We need to preserve all substantive info; not invent or summarize away detail.
We need to use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to those headings.
We have:
Job Summary: description of role.
Job Description: includes "What you'll do:" list of duties.
Required Skills And Qualifications: list.
Preferred Experience: list.
What we're looking for: includes grade details (education, experience). This could be under Qualifications or Requirements.
OTHER REQUIREMENTS: list.
What you'll get: includes salary ranges per grade.
Where You'll work: location.
Additional paragraphs about benefits, mission statement.
We need to decide which sections to output.
We must include sections only when posting has real specific content.
We have:
- About the role: could be Job Summary.
- Responsibilities: the "What you'll do:" list.
- Requirements / Qualifications: could combine Required Skills And Qualifications, Preferred Experience, What we're looking for (education/experience), OTHER REQUIREMENTS.
- Skills: maybe separate but we can combine.
- Benefits: "What you'll get:" includes salary ranges and mention of benefits package.
- Pay: could be separate but we have salary ranges; maybe we put under Benefits or Pay. The instruction says include Pay section only if posting actually states them. It does state salary ranges for each grade. So we can have a Pay section.
- Schedule: not mentioned; no schedule info. So omit.
- Benefits: mention of comprehensive benefits package; we can include Benefits section.
We must not include filler like "commensurate with experience". Not present.
We need to preserve all substantive info; not invent or summarize away detail.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We must not repeat job title as heading.
We must not put Job ID etc.
We need to output only HTML fragment.
Let's structure:
About the role
Job Summary ...
Responsibilities
- Track and maintain schedules, milestones, deadlines, and deliverable dates for multiple concurrent projects.
...
Requirements
Maybe we split into Required Skills and Qualifications, Preferred Experience, Education/Experience combos, OTHER REQUIREMENTS. Could combine into one Requirements section with multiple lists? But instruction: use - for any list of duties/requirements/benefits. So we can have multiple lists under same heading.
We need to preserve all details: Required Skills And Qualifications (list), Preferred Experience (list), What we're looking for (education/experience combos for grades 5,6,7), OTHER REQUIREMENTS (list). Also maybe note "Work Experience: No additional work experience required beyond the education and experience combinations listed above." etc.
We need to include those details exactly.
We'll create subheadings? Not allowed; only h3 for section headings. Could we have multiple h3 sections like Required Skills, Preferred Experience, Qualifications, Other Requirements? That would be okay as they are headings. But instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. We can use those headings; we could also add other headings if needed but better to stick to those categories. However we have a lot of detail; we could split into Requirements, Qualifications, Skills. But we need to preserve all details; we can put them under appropriate headings.
Let's map:
- Required Skills And Qualifications -> could go under Skills or Requirements.
- Preferred Experience -> maybe under Qualifications.
- What we're looking for (education/experience combos) -> Qualifications.
- OTHER REQUIREMENTS -> Requirements.
We could have:
Requirements
OTHER REQUIREMENTS: ...
...
Qualifications
What we're looking for: ...
...
Skills
Required Skills And Qualifications: ...
...
But we might duplicate.
Better to have one Requirements section that includes all lists: Required Skills And Qualifications, Preferred Experience, Education/Experience combos, OTHER REQUIREMENTS. But we need to keep them distinct? Not required; just preserve all info. We can combine into one but that would lose grouping. However we can still preserve all items by listing them all; grouping not required.
But we need to avoid losing nuance like "Preferred Experience" vs "Required Skills". But we can still list all items; it's okay.
Let's extract each bullet.
From Required Skills And Qualifications:
- Strong organizational skills with the ability to manage multiple priorities, deadlines, and project details simultaneously.
- Ability to track complex project information across multiple disciplines while maintaining accuracy and consistency.
- Effective written and verbal communication skills, including the ability to follow up clearly and professionally with internal and external stakeholders.
- Proficiency with project tracking tools, spreadsheets, calendars, shared workspaces, and document management systems.
- Ability to understand project schedules, deliverable requirements, dependencies, and basic workflow relationships between disciplines.
- High attention to detail and the ability to identify missing information, conflicting dates, or incomplete requirements.
- Ability to work independently, prioritize tasks, and escalate issues when project timelines or requirements are at risk.
- Experience supporting project teams, technical teams, design teams, construction teams, or cross-functional business groups is preferred.
Preferred Experience:
- Previous experience in project coordination, project administration, scheduling, document control, or technical support.
- Familiarity with engineering, design, construction, utility, infrastructure, or multidisciplinary project environments.
- Experience maintaining project dashboards, milestone trackers, requirement matrices, or action item logs.
- Working knowledge of Microsoft Excel, Microsoft Lists, Microsoft Planner, Microsoft Project, SharePoint, Teams, or similar project coordination tools.
What we're looking for: includes grade details.
We need to preserve the exact text for each grade.
Let's copy:
Coordinator Assc( Grade 5) Education: Bachelor's degree in a related field from an accredited university or college; ORAssociate's degree and 2 years of experience in the design, operations, planning, construction, or maintenance of systems and/or equipment; ORHigh school diploma or GED and 4 years of experience in the design, operations, planning, construction, or maintenance of systems and/or equipment. Work Experience: No additional work experience required beyond the education and experience combinations listed above.
Coordinator(Grade 6) Education: Bachelor's degree in a related field from an accredited university or college; OR an Associate's technical degree and 3 years of experience in the design, operations, planning, construction, or maintenance of systems and/or equipment; ORA high school diploma or GED and 5 years of experience in the design, operations, planning, construction, or maintenance of systems and/or equipment. Work Experience: Typically requires a minimum of 3 years of experience in work activities and projects requiring technical knowledge.
Coordinator Sr(Grade 7) Education: Bachelor's degree in a related field from an accredited university or college; ORAssociate's technical degree and 6 years of experience in the design, operations, planning, construction, or maintenance of systems and/or equipment; ORA high school diploma or GED and 8 years of experience in the design, operations, planning, construction, or maintenance of systems and/or equipment. Work Experience: Typically requires a minimum of 6 years of experience in work activities and projects requiring technical knowledge.
We need to preserve exactly; note there are some typos like missing spaces. We'll copy as is.
OTHER REQUIREMENTS list:
- Demonstrate the highest standards of ethical behavior and support the Company's Corporate Compliance Policy.
- Demonstrates strong interpersonal skills backed by an enthusiastic approach and a diligent client focus.
- Ability to interface and work well with different levels of individual contributors and management is required.
- Experience in business unit operations and business acumen strongly preferred.
- Understanding of business unit financial and operations systems and databases preferred.
- Is proactive in responsibilities and does not wait for direction from management to conduct work.
What you'll get: salary ranges:
Grade 5: $63,496- $78,000
Grade 6: $72,380 - $90,475
Grade 7: $85,081 - $106,35
Note missing last digit? It says $106,35 (should be $106,350?). We'll keep as given.
Also mention: In addition to competitive compensation, AEP offers a unique comprehensive benefits package that aims to support and enhance the overall well-being of our employees.
Where You'll work: New Albany, OH
Additional paragraphs about mission etc. Those are boilerplate? Might be considered company description; we could include under About the role or maybe a separate section? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The mission statement might be considered boilerplate but it's specific to AEP; not sure. It's not EEO or legal; it's a company description. Might be okay to keep as part of About the role? But we already have Job Summary. Could add another under About the role containing that mission paragraph.
But we must not include duplicated lines. The mission paragraph appears after "Where Putting the Customer First Powers Everything We Do". That's not duplicated elsewhere. We'll keep it.
Also there is "American Electric Power (On-Site) #AEPCareers" etc. That's maybe metadata; we can drop.
Compensation Data etc. Might be duplicate of salary ranges; we can ignore.
Physical Demand Level etc. That's extra info; we could include under a section? Not listed as heading; maybe we could include under Benefits? Not exactly. It's not Pay/Benefits/Schedule. Could be omitted as not required? It's substantive but not fitting headings. The instruction says we should include sections only when posting has real specific content for it; we can create a custom heading? The examples given are not exclusive; we could add a heading like "Physical Demands". But better to stick to given headings; if not fitting, we could drop? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep that info somewhere. We could put it under a
within an appropriate section like "About the role" or maybe a new heading "Other Details". Since not prohibited to add other headings, but examples are just examples. Safer to add a heading like "Other Details" using
. However the instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use for section headings (e.g. ...). So we can use for any section heading; the examples are just examples. So we can add a heading like "Physical Demands". That seems okay.
Similarly, "Where You'll work: New Albany, OH" could be under a heading "Location". Could add.
But we already have "Where You'll work" in the text; we could incorporate into a Location section.
We need to decide how many sections to output. Prefer a few substantive sections over many thin ones. So we should combine where possible.
We could have:
- About the role (Job Summary + mission paragraph)
- Responsibilities
- Requirements (combining Required Skills, Preferred Experience, Education/Experience combos
for prose. We must not repeat job title as heading. We must not put Job ID etc. We need to output only HTML fragment. Let's structure:
About the role
Job Summary ...
Responsibilities
- Track and maintain schedules, milestones, deadlines, and deliverable dates for multiple concurrent projects. ...
Requirements
Maybe we split into Required Skills and Qualifications, Preferred Experience, Education/Experience combos, OTHER REQUIREMENTS. Could combine into one Requirements section with multiple- lists? But instruction: use
- for any list of duties/requirements/benefits. So we can have multiple lists under same heading.
We need to preserve all details: Required Skills And Qualifications (list), Preferred Experience (list), What we're looking for (education/experience combos for grades 5,6,7), OTHER REQUIREMENTS (list). Also maybe note "Work Experience: No additional work experience required beyond the education and experience combinations listed above." etc.
We need to include those details exactly.
We'll create subheadings? Not allowed; only h3 for section headings. Could we have multiple h3 sections like Required Skills, Preferred Experience, Qualifications, Other Requirements? That would be okay as they are headings. But instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. We can use those headings; we could also add other headings if needed but better to stick to those categories. However we have a lot of detail; we could split into Requirements, Qualifications, Skills. But we need to preserve all details; we can put them under appropriate headings.
Let's map:
- Required Skills And Qualifications -> could go under Skills or Requirements.
- Preferred Experience -> maybe under Qualifications.
- What we're looking for (education/experience combos) -> Qualifications.
- OTHER REQUIREMENTS -> Requirements.
We could have:
Requirements
OTHER REQUIREMENTS: ...
- ...
Qualifications
What we're looking for: ...
- ...
Skills
Required Skills And Qualifications: ...
- ...
- but that would lose grouping. However we can still preserve all items by listing them all; grouping not required.
But we need to avoid losing nuance like "Preferred Experience" vs "Required Skills". But we can still list all items; it's okay.
Let's extract each bullet.
From Required Skills And Qualifications:
- Strong organizational skills with the ability to manage multiple priorities, deadlines, and project details simultaneously.
- Ability to track complex project information across multiple disciplines while maintaining accuracy and consistency.
- Effective written and verbal communication skills, including the ability to follow up clearly and professionally with internal and external stakeholders.
- Proficiency with project tracking tools, spreadsheets, calendars, shared workspaces, and document management systems.
- Ability to understand project schedules, deliverable requirements, dependencies, and basic workflow relationships between disciplines.
- High attention to detail and the ability to identify missing information, conflicting dates, or incomplete requirements.
- Ability to work independently, prioritize tasks, and escalate issues when project timelines or requirements are at risk.
- Experience supporting project teams, technical teams, design teams, construction teams, or cross-functional business groups is preferred.
Preferred Experience:
- Previous experience in project coordination, project administration, scheduling, document control, or technical support.
- Familiarity with engineering, design, construction, utility, infrastructure, or multidisciplinary project environments.
- Experience maintaining project dashboards, milestone trackers, requirement matrices, or action item logs.
- Working knowledge of Microsoft Excel, Microsoft Lists, Microsoft Planner, Microsoft Project, SharePoint, Teams, or similar project coordination tools.
What we're looking for: includes grade details.
We need to preserve the exact text for each grade.
Let's copy:
Coordinator Assc( Grade 5) Education: Bachelor's degree in a related field from an accredited university or college; ORAssociate's degree and 2 years of experience in the design, operations, planning, construction, or maintenance of systems and/or equipment; ORHigh school diploma or GED and 4 years of experience in the design, operations, planning, construction, or maintenance of systems and/or equipment. Work Experience: No additional work experience required beyond the education and experience combinations listed above.
Coordinator(Grade 6) Education: Bachelor's degree in a related field from an accredited university or college; OR an Associate's technical degree and 3 years of experience in the design, operations, planning, construction, or maintenance of systems and/or equipment; ORA high school diploma or GED and 5 years of experience in the design, operations, planning, construction, or maintenance of systems and/or equipment. Work Experience: Typically requires a minimum of 3 years of experience in work activities and projects requiring technical knowledge.
Coordinator Sr(Grade 7) Education: Bachelor's degree in a related field from an accredited university or college; ORAssociate's technical degree and 6 years of experience in the design, operations, planning, construction, or maintenance of systems and/or equipment; ORA high school diploma or GED and 8 years of experience in the design, operations, planning, construction, or maintenance of systems and/or equipment. Work Experience: Typically requires a minimum of 6 years of experience in work activities and projects requiring technical knowledge.
We need to preserve exactly; note there are some typos like missing spaces. We'll copy as is.
OTHER REQUIREMENTS list:
- Demonstrate the highest standards of ethical behavior and support the Company's Corporate Compliance Policy.
- Demonstrates strong interpersonal skills backed by an enthusiastic approach and a diligent client focus.
- Ability to interface and work well with different levels of individual contributors and management is required.
- Experience in business unit operations and business acumen strongly preferred.
- Understanding of business unit financial and operations systems and databases preferred.
- Is proactive in responsibilities and does not wait for direction from management to conduct work.
What you'll get: salary ranges:
Grade 5: $63,496- $78,000
Grade 6: $72,380 - $90,475
Grade 7: $85,081 - $106,35
Note missing last digit? It says $106,35 (should be $106,350?). We'll keep as given.
Also mention: In addition to competitive compensation, AEP offers a unique comprehensive benefits package that aims to support and enhance the overall well-being of our employees.
Where You'll work: New Albany, OH
Additional paragraphs about mission etc. Those are boilerplate? Might be considered company description; we could include under About the role or maybe a separate section? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The mission statement might be considered boilerplate but it's specific to AEP; not sure. It's not EEO or legal; it's a company description. Might be okay to keep as part of About the role? But we already have Job Summary. Could add another
under About the role containing that mission paragraph. But we must not include duplicated lines. The mission paragraph appears after "Where Putting the Customer First Powers Everything We Do". That's not duplicated elsewhere. We'll keep it. Also there is "American Electric Power (On-Site) #AEPCareers" etc. That's maybe metadata; we can drop. Compensation Data etc. Might be duplicate of salary ranges; we can ignore. Physical Demand Level etc. That's extra info; we could include under a section? Not listed as heading; maybe we could include under Benefits? Not exactly. It's not Pay/Benefits/Schedule. Could be omitted as not required? It's substantive but not fitting headings. The instruction says we should include sections only when posting has real specific content for it; we can create a custom heading? The examples given are not exclusive; we could add a heading like "Physical Demands". But better to stick to given headings; if not fitting, we could drop? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep that info somewhere. We could put it under a
within an appropriate section like "About the role" or maybe a new heading "Other Details". Since not prohibited to add other headings, but examples are just examples. Safer to add a heading like "Other Details" using
. However the instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use
for section headings (e.g. ...). So we can use
for any section heading; the examples are just examples. So we can add a heading like "Physical Demands". That seems okay. Similarly, "Where You'll work: New Albany, OH" could be under a heading "Location". Could add. But we already have "Where You'll work" in the text; we could incorporate into a Location section. We need to decide how many sections to output. Prefer a few substantive sections over many thin ones. So we should combine where possible. We could have: - About the role (Job Summary + mission paragraph) - Responsibilities - Requirements (combining Required Skills, Preferred Experience, Education/Experience combos