Program Manager
Network Connex · Frederick, MD · 3 wk ago
RemoteRemoteInformation Technology$20/hrFull-time
We need to produce HTML fragment with sections: About the role? Actually the posting includes intro paragraph about organization, then "This Opportunity:" with description of role, then "Job Duties and Responsibilities:", then "Skills, Abilities and Competencies:", then "Experience and Education:", then "Supervisory Responsibility:", then "Work Location and Travel:", then maybe "Benefits" earlier in intro (compensation and benefits). Also mention "competitive base pay", "comprehensive benefits package", "Join our Vanguard 401(k) plan...", "10 paid company holidays", "generous PTO accrual schedule", "access to discounts". So we need Benefits section. Pay: they mention competitive base pay but not specific numbers; we should not create Pay section unless posting actually states them. It says "competitive base pay" but no specifics; that is vague. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits specifics (holidays, PTO, discounts, 401k). So we can include Benefits section. Pay: they mention competitive base pay but not a number; that's vague; maybe we should not create Pay section because it's not specific. Schedule: they mention travel 25% but not schedule; maybe not. So we will include Benefits.
We need headings: for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections that have real content. The posting includes: About the role (intro paragraph), Responsibilities (Job Duties and Responsibilities), Skills (Skills, Abilities and Competencies), Qualifications (Experience and Education maybe), Benefits (benefits description). Also Supervisory Responsibility and Work Location and Travel could be part of Responsibilities or Qualifications? Might be separate but we don't have headings for those; we could incorporate into Responsibilities or maybe a separate section like "Additional Information". But only allowed headings are those listed; we cannot create other headings. So we need to map content to those headings.
We have:
- About the role: intro paragraph about organization, team, compensation and benefits, etc. Could include the benefits? But we also have Benefits heading separate. Might split: About the role includes mission, team, etc. Benefits separate.
- Responsibilities: Job Duties and Responsibilities.
- Skills: Skills, Abilities and Competencies.
- Qualifications: Experience and Education (maybe also Supervisory Responsibility? but that's about leading team; could be part of Qualifications). We'll put Supervisory Responsibility under Qualifications or maybe under Responsibilities? It's about leading team; could be under Responsibilities as well. But we have limited headings; we can include Supervisory Responsibility within Responsibilities or Qualifications. I'd put under Qualifications as it's about experience leading.
- Benefits: benefits description.
We should not include Pay or Schedule sections because not specific.
We must preserve all substantive information; not invent or summarize away detail. Must not repeat job title as heading. Must not put Job ID etc.
We must remove boilerplate: EEO, equal opportunity, scam warning, duplicated lines, application instructions, cookie/navigation/legal. The posting includes EEO statements duplicated; we must remove them. Also mention background check, drug screening, AI tools; those are boilerplate? They are part of hiring process but maybe considered boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove EEO statements, background check/drug screening? Those are not exactly EEO but could be considered hiring process details; not sure if they are considered boilerplate. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. Background check and drug screening are not EEO; they are part of hiring process but could be considered standard; but they might be considered boilerplate? Not explicitly listed. Safer to keep them? However they are repetitive? They appear twice? Actually appears once: "Upon acceptance of an offer, all candidates will be required to pass a background check and drug screening." Then later again duplicated: same sentence appears again after EEO duplication. So we should keep one instance? The instruction says remove duplicated lines. So we should keep only one occurrence. Also the AI tools paragraph maybe not boilerplate but could be considered hiring process; we might keep it? It's not EEO. Might keep.
We need to output only HTML fragment.
Let's extract content.
Intro paragraph:
"If being a part of a world-class organization that operates in some of the most advanced technological environments around the world sounds like a dream job, Network Connex might be the right fit for you! You’ll be part of a team working together to solve customer problems every day, with compensation and benefits that are an investment in your career, financial future, and overall well-being. In addition to competitive base pay, Network Connex offers a comprehensive benefits package designed to support your physical, mental, and financial health you can begin participating in our programs on the first of the month following your start date. Join our Vanguard 401(k) plan, with immediate vesting and a generous company match to help you build long-term financial security. Our team also enjoys 10 paid company holidays, a generous PTO accrual schedule, and access to discounts on useful products and services."
That's the benefits description.
Then "This Opportunity: The Program Manager will lead a regional team of Project Managers responsible for delivering a high-volume portfolio of inside plant cabling projects within data center environments. This role is accountable for PM team performance, regional project execution, forecasting accuracy, schedule adherence, cost control, change management, documentation discipline, and client satisfaction. The Program Manager will oversee a regional pipeline of approximately 15-30 active projects, with 4-8 new project starts per month, and will ensure Project Managers have the direction, support, resources, and accountability needed to deliver projects safely, on time, within budget, and in alignment with customer requirements. This role is expected to balance day-to-day project execution with team development, process improvement, and regional program planning."
That's about the role.
Then "Job Duties and Responsibilities:" followed by a list of duties (some are run-on sentences). We need to convert to