Planning Engineer III

We need to output only HTML fragment, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Must preserve all substantive info. We need to parse the job description. Job Description: Planning Engineer III (Sr. Transport Planning Engineer) Position Summary: The Planning Engineer III is responsible for developing network growth, capacity, and evolution plans for the National Core Transport Network and supporting metropolitan transport networks. This role creates implementation-ready planning packages for design and field engineering teams, manages project funding, and budgets, and supports network modernization initiatives. The position provides technical leadership, mentoring, and collaboration across engineering and operations teams while ensuring compliance with telecommunications standards and regulations. Key Responsibilities: list items: SONET network planning and capacity management; Core backbone and metro network growth planning; Development of implementation-ready engineering packages; Capital and expense budget management; Network data analysis and forecasting; Stakeholder coordination and engagement; Mentoring and training of junior engineers; Compliance with telecommunications regulations and standards Technical Skills: list: Optical Transport Networks; SONET; Ethernet; DWDM; Capacity Planning & Forecasting; Central Office Infrastructure (Power, Alarms, Common Systems); Outside Plant (OSP) Engineering; Telecommunications Network Design; Transport Engineering Principles Systems & Tools: list: TIRKS; NDC; ASPEN Portal; LCAM; MetaSolv; Fireworks; CORE; Microsoft Excel, PowerPoint, Word, Outlook, and Teams Preferred Qualifications: list: Lumen experience; 5+ years of transport planning or network engineering experience; Strong analytical and problem-solving skills; Excellent written and verbal communication skills; Budget and project management experience; Ability to lead cross-functional initiatives and mentor others Then there's a paragraph about Everforth Apex (company description) and benefits overview. We need sections: About the role (position summary), Responsibilities (key responsibilities), Requirements (maybe technical skills?), Qualifications (preferred qualifications?), Skills (maybe technical skills and systems & tools?), Benefits (benefits overview), Pay (none given), Schedule (none given). We should only include sections with real specific content. Pay and Schedule not given, so omit. We need to decide mapping: The instructions say use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only those with real content. We have: - About the role: Position Summary (good) - Responsibilities: Key Responsibilities (list) - Requirements: maybe Technical Skills? Or maybe "Requirements" could be the required qualifications? The posting includes "Preferred Qualifications". There's no explicit "Requirements" separate. Could treat "Preferred Qualifications" as Qualifications. "Requirements" maybe could be "Technical Skills" or "Systems & Tools"? But we have separate Skills heading. The instructions allow us to use Skills heading for any list of skills. So we could put Technical Skills and Systems & Tools under Skills. Or we could split: Skills heading for technical skills, and maybe Requirements heading for preferred qualifications? But the instructions say we should prefer a few substantive sections over many thin ones. So we could combine. We need to preserve all substantive information. So we need to include all details: Position Summary, Responsibilities list, Technical Skills list, Systems & Tools list, Preferred Qualifications list, Benefits overview. We can structure:

About the role

Position summary paragraph.

Responsibilities

• ...

Skills

Maybe combine Technical Skills and Systems & Tools into one list? Could separate with subheadings? But we cannot add extra headings beyond allowed ones? The instruction only 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 (list). It might be okay to use other headings but better to stick to allowed. We could put both under Skills heading with sub-lists maybe using

with items that include both categories? Could separate with

headings? Might be okay to have

Technical Skills

then list, then

Systems & Tools

then list. That's not a heading, just a paragraph. That should be fine.

Qualifications

Preferred Qualifications list

Benefits

Benefits overview paragraph(s).

We must not include Pay or Schedule. We need to remove boilerplate: company description about Everforth Apex (the paragraph about being world-class IT services, awards, virtual recruiter, etc.) That's considered boilerplate? It's not directly about the job; it's generic company description. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description might be considered boilerplate? It's not legal/EEO, but it's generic marketing. Might be considered not substantive to the job? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The company description is not about the job specifics; it's about the company. Could be considered boilerplate but not explicitly listed. However, it's not about the job duties/requirements/benefits. The benefits section is separate and we need to keep that. The company description paragraph about Everforth Apex being world-class etc. could be considered boilerplate; but it's not explicitly listed to remove. Safer to keep? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not say to remove generic company overview. So we might keep it? However, the instruction also says "Prefer a few substantive sections over many thin ones." Including a company overview might be a thin section. But we don't have a heading for company overview; we could incorporate it into About the role? But About the role is position summary; we could add a sentence about company after summary? That would be adding info not originally in position summary. Might be okay but could be considered adding detail not originally there? It's already in the posting; we could include it as part of About the role? The position summary is separate; the company description is after that. Could we treat it as part of About the role? The About the role heading could contain both position summary and company overview. That would preserve the info. But the instruction says "About the role" heading for section headings (e.g. About the role, Responsibilities...). It didn't forbid adding extra paragraphs under that heading. So we could put the company description under About the role as a paragraph after the position summary. That would keep all info. Similarly, the benefits overview we already have. We need to remove duplicated lines: there are duplicated EEO statements at the end. Remove those. Also remove application instructions: "Click here for more details." and the virtual recruiter stuff, and the consent to receive calls etc. Also remove the privacy policy link and the opt-out text. Also remove the EEO statements. Also remove the address and NYSE ticker? That's maybe not boilerplate but could be considered contact info; but not explicitly required to remove. Might be considered metadata like Job ID; we should drop minor metadata into a short

or drop it. The address and NYSE ticker could be considered minor metadata; we could drop it or put in a short p. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can drop the address and ticker. Thus final HTML:

About the role

The Planning Engineer III is responsible for developing network growth, capacity, and evolution plans for the National Core Transport Network and supporting metropolitan transport networks. This role creates implementation-ready planning packages for design and field engineering teams, manages project funding, and budgets, and supports network modernization initiatives. The position provides technical leadership, mentoring, and collaboration across engineering and operations teams while ensuring compliance with telecommunications standards and regulations.

Everforth Apex is a world-class IT services company that serves thousands of clients across the globe. When you join Everforth Apex, you become part of a team that values innovation, collaboration, and continuous learning. We offer quality career resources, training, certifications, development opportunities, and a comprehensive benefits package. Our commitment to excellence is reflected in many awards, including ClearlyRateds Best of Staffing® in Talent Satisfaction in the United States and Great Place to Work® in the United Kingdom and Mexico.

Responsibilities

• SONET network planning and capacity management
• Core backbone and metro network growth planning
• Development of implementation-ready engineering packages
• Capital and expense budget management
• Network data analysis and forecasting
• Stakeholder coordination and engagement
• Mentoring and training of junior engineers
• Compliance with telecommunications regulations and standards

Skills

Technical Skills

• Optical Transport Networks
• SONET
• Ethernet
• DWDM
• Capacity Planning & Forecasting
• Central Office Infrastructure (Power, Alarms, Common Systems)
• Outside Plant (OSP) Engineering
• Telecommunications Network Design
• Transport Engineering Principles

Systems & Tools

• TIRKS
• NDC
• ASPEN Portal
• LCAM
• MetaSolv
• Fireworks
• CORE
• Microsoft Excel, PowerPoint, Word, Outlook, and Teams

Qualifications

• Lumen experience
• 5+ years of transport planning or network engineering experience
• Strong analytical and problem-solving skills
• Excellent written and verbal communication skills
• Budget and project management experience
• Ability to lead cross-functional initiatives and mentor others

Benefits

Everforth Apex offers a range of supplemental benefits, including medical, dental, vision, life, disability, and other insurance plans that offer an optional layer of financial protection. We offer an ESPP (employee stock purchase program) and a 401K program which allows you to contribute typically within 30 days of starting, with a company match after 12 months of tenure. Everforth Apex also offers a HSA (Health Savings Account on the HDHP plan), a SupportLinc Employee Assistance Program (EAP) with up to 8 free counseling sessions, a corporate discount savings program and other discounts. In terms of professional development, Everforth Apex hosts an on-demand training program, provides access to certification prep and a library of technical and leadership courses/books/seminars once you have 6+ months of tenure, and certification discounts and other perks to associations that include CompTIA and IIBA. Everforth Apex has a dedicated customer service team for our Consultants that can address questions around benefits and other resources, as well as a certified Career Coach. You can access a full list of our benefits, programs, support teams and resources within our ‘Welcome Packet’ as well, which an Everforth Apex team member can provide.

We must ensure no extra whitespace? It's fine. Check that we didn't include Pay or Schedule sections. Good. Check that we didn't repeat job