Sr Project Manager
Scientific Research Corporation · North Charleston, SC · 3 wk ago
Project ManagementFull-time
We need to produce HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "About Us" maybe? Actually "About Us" is not a required heading; we can include if content is substantive. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should stick to those. However we have content like "Providing structured program oversight..." which is responsibilities. Then bullet list of responsibilities? The posting includes paragraphs describing responsibilities. We'll need to extract responsibilities, requirements, qualifications, skills, benefits, etc.
Let's parse the posting:
First sentence: "Providing structured program oversight, weekly reporting, and stakeholder coordination from award through service acceptance" - that's a responsibility.
Second: "Supporting navy shore installation programs, well-versed in the associated documentation requirements, including Facilities Requirements Control Boards (FRCBs) and related support documents" - also responsibility.
Third: "Serving as the primary point of contact for task order execution, ensuring all contract performance, deliverable submission, and stakeholder communication requirements are met" - responsibility.
Then "Requirements" heading appears in text: "Requirements Bachelor’s degree in information technology, engineering, construction management, or a related technical field Minimum eight years of progressive project management experience, including direct support of navy shore installation programs or similar DoD shore-based facility and infrastructure projects Demonstrated experience conducting status reviews and preparing written reports for Navy or DoD government clients Thorough knowledge of navy shore installation processes, including planning, execution, and closeout phases Proficiency preparing and processing Facilities Requirements Control Board (FRCB) packages and all associated support documentation (DD Form 1391s, project justifications, cost estimates, environmental reviews, and coordination packages) Experience navigating NAVFAC (Naval Facilities Engineering Systems Command) project delivery processes, including coordination with Installation Commanding Officers, Public Works Officers (PWOs), and regional stakeholders Hands-on or oversight experience with IT network design, infrastructure deployment, or systems integration Familiarity with network protocols, enterprise infrastructure components (routers, switches, firewalls, servers), and IT service delivery models Proficiency in schedule management tools (e.g., Microsoft Project, Smartsheet) Strong written and verbal communication skills Ability to obtain and maintain required security clearance Project Management Professional (PMP) certification or equivalent"
That's a block of requirements/qualifications.
Then "Desired Skills" heading: "Prior experience working directly with NAVFAC commands, installation public works departments, or navy regional offices Familiarity with Performance Work Statements (PWS), Acceptable Quality Levels (AQLs), and DoD acquisition frameworks Knowledge of MILCON (Military Construction) and O&M (Operations and Maintenance) funding processes as they apply to shore installation projects Experience with additional Navy/DoD shore installation documents such as ISPs (Installation Support Plans), MOAs, and environmental compliance documentation Prior experience managing IT network upgrades, infrastructure refresh cycles, or data center operations Experience with IT risk management and mitigation in network-dependent environments Relevant IT certifications such as CompTIA Network+, CCNA, or ITIL Foundation"
Then "Clearance Information SRC IS A CONTRACTOR FOR THE U.S. GOVERNMENT, THIS POSITION WILL REQUIRE U.S. CITIZENSHIP AS WELL AS, A U.S. GOVERNMENT SECURITY CLEARANCE AT THE SECRET LEVEL WITH TOP SECRET ELIGIBILITY Travel Requirements 10-15%"
Then "About Us Scientific Research Corporation is an advanced information technology and engineering company that provides innovative products and services to government and private industry, as well as independent institutions. At the core of our capabilities is a seasoned team of highly skilled engineers and scientists with multidisciplinary backgrounds. This team is challenged daily to provide cutting edge technology solutions to our clients. SRC offers a generous benefit package, including medical, dental, and vision plans, 401(k) with a company match, life insurance, vacation and sick paid time off accruals with amounts increasing based on role and years of service, 11 paid holidays, tuition reimbursement, and a work environment that encourages excellence and more. For positions requiring a security clearance, selected applicants will be subject to a government security investigation and must meet eligibility requirements for access to classified information."
Then EEO boilerplate etc.
We need to remove boilerplate: EEO, accessibility contact, etc. Also remove "About Us"? The instruction says we can include sections only when posting has real specific content. "About Us" is not one of the prescribed headings but we could treat it as "About the role"? Actually "About Us" is company description; could be placed under a heading like "About the role"? But the instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the expected headings. Safer to map content to those.
Thus we need sections:
- Responsibilities: bullet list of duties.
- Requirements: bullet list of mandatory requirements.
- Qualifications: maybe same as Requirements? Could combine? But we have both Requirements and Desired Skills. Could treat Requirements as mandatory, Qualifications as desired? Actually the posting has "Requirements" then later "Desired Skills". So we can have Requirements (mandatory) and Skills (desired). Also we have "Qualifications" maybe not separate; we could treat Requirements as Qualifications. But we need to follow instruction: include a section ONLY when posting has real, specific content for it. So we can have sections: Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Also maybe "Qualifications" if we want to separate education/experience vs skills? But we can combine.
We have Pay: not mentioned explicitly. No salary. So we should NOT include Pay section.
Schedule: not mentioned besides travel 10-15% maybe schedule? Not exactly. No schedule info. So omit Schedule.
Benefits: we have benefits described in About Us: "SRC offers a generous benefit package, including medical, dental, and vision plans, 401(k) with a company match, life insurance, vacation and sick paid time off accruals with amounts increasing based on role and years of service, 11 paid holidays, tuition reimbursement, and a work environment that encourages excellence and more." That's benefits. So we can include Benefits section.
Also we have Clearance Information and Travel Requirements: that could be placed under Requirements? Or maybe under a separate section like "Clearance" but not in list. Could fold into Requirements as a bullet: "U.S. citizenship and ability to obtain/maintain Secret clearance with Top Secret eligibility; travel 10-15%". That seems appropriate.
Thus sections:
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "About Us" maybe? Actually "About Us" is not a required heading; we can include if content is substantive. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should stick to those. However we have content like "Providing structured program oversight..." which is responsibilities. Then bullet list of responsibilities? The posting includes paragraphs describing responsibilities. We'll need to extract responsibilities, requirements, qualifications, skills, benefits, etc.
Let's parse the posting:
First sentence: "Providing structured program oversight, weekly reporting, and stakeholder coordination from award through service acceptance" - that's a responsibility.
Second: "Supporting navy shore installation programs, well-versed in the associated documentation requirements, including Facilities Requirements Control Boards (FRCBs) and related support documents" - also responsibility.
Third: "Serving as the primary point of contact for task order execution, ensuring all contract performance, deliverable submission, and stakeholder communication requirements are met" - responsibility.
Then "Requirements" heading appears in text: "Requirements Bachelor’s degree in information technology, engineering, construction management, or a related technical field Minimum eight years of progressive project management experience, including direct support of navy shore installation programs or similar DoD shore-based facility and infrastructure projects Demonstrated experience conducting status reviews and preparing written reports for Navy or DoD government clients Thorough knowledge of navy shore installation processes, including planning, execution, and closeout phases Proficiency preparing and processing Facilities Requirements Control Board (FRCB) packages and all associated support documentation (DD Form 1391s, project justifications, cost estimates, environmental reviews, and coordination packages) Experience navigating NAVFAC (Naval Facilities Engineering Systems Command) project delivery processes, including coordination with Installation Commanding Officers, Public Works Officers (PWOs), and regional stakeholders Hands-on or oversight experience with IT network design, infrastructure deployment, or systems integration Familiarity with network protocols, enterprise infrastructure components (routers, switches, firewalls, servers), and IT service delivery models Proficiency in schedule management tools (e.g., Microsoft Project, Smartsheet) Strong written and verbal communication skills Ability to obtain and maintain required security clearance Project Management Professional (PMP) certification or equivalent"
That's a block of requirements/qualifications.
Then "Desired Skills" heading: "Prior experience working directly with NAVFAC commands, installation public works departments, or navy regional offices Familiarity with Performance Work Statements (PWS), Acceptable Quality Levels (AQLs), and DoD acquisition frameworks Knowledge of MILCON (Military Construction) and O&M (Operations and Maintenance) funding processes as they apply to shore installation projects Experience with additional Navy/DoD shore installation documents such as ISPs (Installation Support Plans), MOAs, and environmental compliance documentation Prior experience managing IT network upgrades, infrastructure refresh cycles, or data center operations Experience with IT risk management and mitigation in network-dependent environments Relevant IT certifications such as CompTIA Network+, CCNA, or ITIL Foundation"
Then "Clearance Information SRC IS A CONTRACTOR FOR THE U.S. GOVERNMENT, THIS POSITION WILL REQUIRE U.S. CITIZENSHIP AS WELL AS, A U.S. GOVERNMENT SECURITY CLEARANCE AT THE SECRET LEVEL WITH TOP SECRET ELIGIBILITY Travel Requirements 10-15%"
Then "About Us Scientific Research Corporation is an advanced information technology and engineering company that provides innovative products and services to government and private industry, as well as independent institutions. At the core of our capabilities is a seasoned team of highly skilled engineers and scientists with multidisciplinary backgrounds. This team is challenged daily to provide cutting edge technology solutions to our clients. SRC offers a generous benefit package, including medical, dental, and vision plans, 401(k) with a company match, life insurance, vacation and sick paid time off accruals with amounts increasing based on role and years of service, 11 paid holidays, tuition reimbursement, and a work environment that encourages excellence and more. For positions requiring a security clearance, selected applicants will be subject to a government security investigation and must meet eligibility requirements for access to classified information."
Then EEO boilerplate etc.
We need to remove boilerplate: EEO, accessibility contact, etc. Also remove "About Us"? The instruction says we can include sections only when posting has real specific content. "About Us" is not one of the prescribed headings but we could treat it as "About the role"? Actually "About Us" is company description; could be placed under a heading like "About the role"? But the instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. "About Us" could be considered "About the role"? Not exactly. Maybe we can include a section "About the role" with the introductory responsibilities? But we already have responsibilities. The "About Us" is company overview; could be placed under a heading like "About the role"? Might be okay but not sure. 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 we should stick to those. The company description could be placed under a heading like "About the role"? Might be odd. Better to omit "About Us" as it's not required; but we must preserve ALL substantive information. The company description is substantive? It describes the employer; maybe we can include it under a heading like "About the role"? However the instruction says "do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but we should stick to those. The company description could be placed under a heading like "About the role"? Might be odd. Better to omit "About Us" as it's not required; but we must preserve ALL substantive information. The company description is substantive? It describes the employer; maybe we can include it under a heading like "About the role"? However the instruction says "do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." It doesn't forbid other headings like "About Us". But the list of headings is just examples; we could include "About Us" as a heading if we want. However the instruction says "Use