Deputy Program Manager, Technical TS/SCI with Poly REQUIRED
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We must include a section only when posting has real specific content. We have:
- About the role: The description includes position description, mission, etc. So we can have About the role section with prose.
- Responsibilities: The "Your Future Duties And Responsibilities" list includes bullet points. So we can have Responsibilities section with - .
- Requirements: There's "Required Qualifications To Be Successful In This Role" includes education/experience, security clearance, project management tools, deep technical experience, functional and technical requirements, governance, system security accreditation experience, analytical & problem solving skills, leadership & communication. This is a mix of qualifications and requirements. We can treat as Requirements section (maybe combine with Qualifications). But we need separate sections for Requirements and Qualifications if content exists. The posting lumps them; we could split: Requirements (education/experience, security clearance, tools) and Qualifications (deep technical experience, functional/technical requirements, governance, system security accreditation, analytical skills, leadership). However the instruction: "Prefer a few substantive sections over many thin ones." So maybe combine into one Requirements section. But we have both Requirements and Qualifications headings allowed; we can choose to include only one if content is sufficient. However we need to preserve all substantive info; we can put all under Requirements (or Qualifications). Let's decide to have a single "Requirements" section covering all.
- Skills: There's a line "#CGIFederalJob LB1 #ClearanceJobs Skills CollaborationGraphQLPythonRequirements AnalysisRESTful (Rest-APIs)". That seems like a list of skills: Collaboration, GraphQL, Python, Requirements Analysis, RESTful (Rest-APIs). We'll extract those as skills.
- Benefits: The posting lists benefits: Competitive compensation, Comprehensive insurance options, Matching contributions through the 401(k) plan and the share purchase plan, Paid time off for vacation, holidays, and sick time, Paid parental leave, Learning opportunities and tuition assistance, Wellness and Well being programs.
- Pay: The posting includes compensation range: $127,500 - $127,500 USD yearly? Actually earlier line: "$127,500 - $127,500 USD yearly Position Description". Then later: "A reasonable estimate of the current range for this role in the U.S. is $127,500.00 $245,500.00." There's contradictory. The first says $127,500 - $127,500 (maybe a typo). The later says $127,500.00 $245,500.00 (missing hyphen). We need to preserve ALL substantive information; we should include both? The instruction: "Do NOT invent or summarize away detail." So we need to include the compensation info as stated. There's a line: "CGI is required by law in some jurisdictions to include a reasonable estimate of the compensation range for this role. ... A reasonable estimate of the current range for this role in the U.S. is $127,500.00 $245,500.00." So we should include that as Pay section. Also there is earlier "$127,500 - $127,500 USD yearly". That seems like a placeholder maybe from the scraper. We could include both but that would be repetitive. Better to include the range as described in the later paragraph: $127,500.00 - $245,500.00 (we need to infer hyphen). But we must not invent. The text says "$127,500.00 $245,500.00" missing hyphen; we could keep exactly as written: "$127,500.00 $245,500.00". That is weird but we must preserve. We'll include that as Pay.
- Schedule: The posting mentions hybrid working model acceptable. So we have schedule info: hybrid working model acceptable. Also location: Arlington, VA office; hybrid working model acceptable. So we can have Schedule section with that.
Now we need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes a lot of EEO statement at the end, accommodation info, veteran link, background investigation, etc. We must remove those.
We must output only HTML fragment, no /, no markdown fences.
We'll structure:
About the role
... prose ...
Responsibilities
- ...
...
Requirements
... maybe combine education/experience, security clearance, etc as prose? Or we could use
for list items. The instruction: Use - for any list of duties/requirements/benefits, and
for prose. So for requirements we should use list if it's a list. The requirements are enumerated items; we can make a list.
Similarly Skills: list.
Benefits: list.
Pay: maybe
with the range.
Schedule:
with hybrid model.
We need to ensure we don't repeat job title as heading.
Let's extract About the role prose: The first paragraph after Position Description: "CGI Federal has an exciting opportunity for a Deputy Project Manager (Technical) within our Intel sector advancing the national security mission through cutting edge technology. You must be a visionary with a passion for effectively keeping pace with rapidly evolving technology advancements and leveraging your knowledge on a highly collaborative team to deliver state of the art capabilities. On this program we are focused on delivering quality innovation to accelerate successful mission outcomes. The Deputy Project Manager (Technical) assists a Project Manager by coordinating technical projects, managing project plans, budgets, and schedules, and supervising project teams to ensure successful delivery and client satisfaction."
We can combine that into About the role.
Now Responsibilities list: from "Your Future Duties And Responsibilities" bullet points:
- Project Planning & Execution: Develop, implement, and update technical project plans, scope, and schedules.
- Technical Oversight: Coordinating complex technical tasks across teams, evaluating work products, and ensuring project deliverables meet technical and quality standards.
- Team & Resource Management: Lead and coordinate technical and administrative project teams, allocate resources effectively, and oversee staffing to ensure optimal utilization.
- Client & Stakeholder Liaison: Serve as a client liaison, ensuring the project meets client expectations and satisfaction.
- Risk & Issue Management: Identify and resolve technical project challenges, assess risks, and implement change control processes.
- Reporting: Prepare and present project status reports, performance metrics, and updates to the Project Manager and stakeholders.
We'll make each as
- .
Now Requirements: Let's list items:
- Education and/or Experience: Bachelor's degree and/or 5 to 8 years of experience
- Security Clearance: TS/SCI with CI Poly
- Project Management Tools: Proficiency in using project management software and methodologies. Experience in the art of developing and managing intuitive project schedules.
- Deep technical experience in two or more of the following: application development (preferably using Java or Python), writing SQL and/or Graph query language (e.g., GQL, Cipher, Gremlin, etc.), data modeling, data integration using JSON( LD), development of REST services and/or clients, developing automated test scripts, developing solution architectures to include hardware, software, and integration layers, and/or deep experience developing artificial intelligence solutions.
- Functional and Technical Requirements: Experience eliciting, decomposing, and developing high quality functional and technical requirements. Understanding of Requirements Traceability Matrices (RTM) or equivalents.
- Governance: Demonstrated experience in governance processes (change control boards, requirements prioritization, release management, etc.).
- System Security Accreditation Experience: Experience with frameworks such as RMF or continuous ATO. Demonstrated high level understanding of policies and security requirements for systems accreditation.
- Analytical & Problem Solving Skills: The ability to analyze complex problems, develop action plans, and find effective solutions.
- Leadership & Communication: Excellent communication and interpersonal skills to coordinate teams, manage client relationships, and facilitate meetings.
We'll make each as
- .
Now Skills: list: Collaboration, GraphQL, Python, Requirements Analysis, RESTful (Rest-APIs). We'll make
- each.
Now Benefits: list:
- Competitive compensation
- Comprehensive insurance options
- Matching contributions through the 401(k) plan and the share purchase plan
- Paid time off for vacation, holidays, and sick time
- Paid parental leave
- Learning opportunities and tuition assistance
- Wellness and Well being programs
Now Pay: The compensation range: "A reasonable estimate of the current range for this role in the U.S. is $127,500.00 $245,500.00." We'll output as
$127,500.00 $245,500.00
. Could also include the earlier "$127,500 - $127,500 USD yearly" but that seems redundant and maybe erroneous. We'll include only the range from the later statement to avoid duplication. However we must preserve ALL substantive information; the earlier line is also substantive (though maybe duplicate). But it's basically same info but with a typo. To be safe, we could include both but note they are separate statements. However that would be repetitive and maybe considered duplication. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines". The duplicated lines refers to duplicated lines in the posting; the two compensation statements are not exactly same but similar. Might be considered duplicated? Not sure. Safer to include both? But we risk violating "Prefer a few substantive sections over many thin ones." Including both as separate might be thin. I'd choose to include the later range as it's more detailed. The earlier line "$127,500 - $127,500 USD yearly" is likely a mistake; but it's still substantive. However we could incorporate it into the Pay section as note: "The posting also lists a yearly salary of $127,500 - $127,500 USD." That would be summarizing. Better to include both as separate sentences within same
. Eg: "
The posting indicates a yearly salary of $127,500 - $127,500 USD, and a reasonable estimate of the current range for this role in the U.S. is $127,500.00 $245,500.00.
" That preserves both without creating separate thin sections.
Now Schedule: hybrid working model acceptable; location Arlington, VA office. We'll put in The position is located in the Arlington, VA office; a hybrid working model is acceptable.
Now ensure we don't include any boilerplate like EEO statement, accommodation, veteran link, background investigation, etc.
Now produce HTML fragment.
Let's craft.
Check for any stray content: The posting also includes "#CGIFederalJob LB1 #ClearanceJobs Skills CollaborationGraphQLPythonRequirements AnalysisRESTful (Rest-APIs)". We extracted skills.
Now final HTML:
About the role
CGI Federal has an exciting opportunity for a Deputy Project Manager (Technical) within our Intel sector advancing the national security mission through cutting edge technology. You must be a visionary with a passion for effectively keeping pace with rapidly evolving technology advancements and leveraging your knowledge on a highly collaborative team to deliver state of the art
About the role
... prose ...
Responsibilities
- ... ...
Requirements
... maybe combine education/experience, security clearance, etc as prose? Or we could use
- for list items. The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So for requirements we should use list if it's a list. The requirements are enumerated items; we can make a list. Similarly Skills: list. Benefits: list. Pay: maybe
with the range. Schedule:
with hybrid model. We need to ensure we don't repeat job title as heading. Let's extract About the role prose: The first paragraph after Position Description: "CGI Federal has an exciting opportunity for a Deputy Project Manager (Technical) within our Intel sector advancing the national security mission through cutting edge technology. You must be a visionary with a passion for effectively keeping pace with rapidly evolving technology advancements and leveraging your knowledge on a highly collaborative team to deliver state of the art capabilities. On this program we are focused on delivering quality innovation to accelerate successful mission outcomes. The Deputy Project Manager (Technical) assists a Project Manager by coordinating technical projects, managing project plans, budgets, and schedules, and supervising project teams to ensure successful delivery and client satisfaction." We can combine that into About the role. Now Responsibilities list: from "Your Future Duties And Responsibilities" bullet points: - Project Planning & Execution: Develop, implement, and update technical project plans, scope, and schedules. - Technical Oversight: Coordinating complex technical tasks across teams, evaluating work products, and ensuring project deliverables meet technical and quality standards. - Team & Resource Management: Lead and coordinate technical and administrative project teams, allocate resources effectively, and oversee staffing to ensure optimal utilization. - Client & Stakeholder Liaison: Serve as a client liaison, ensuring the project meets client expectations and satisfaction. - Risk & Issue Management: Identify and resolve technical project challenges, assess risks, and implement change control processes. - Reporting: Prepare and present project status reports, performance metrics, and updates to the Project Manager and stakeholders. We'll make each as
- . Now Requirements: Let's list items: - Education and/or Experience: Bachelor's degree and/or 5 to 8 years of experience - Security Clearance: TS/SCI with CI Poly - Project Management Tools: Proficiency in using project management software and methodologies. Experience in the art of developing and managing intuitive project schedules. - Deep technical experience in two or more of the following: application development (preferably using Java or Python), writing SQL and/or Graph query language (e.g., GQL, Cipher, Gremlin, etc.), data modeling, data integration using JSON( LD), development of REST services and/or clients, developing automated test scripts, developing solution architectures to include hardware, software, and integration layers, and/or deep experience developing artificial intelligence solutions. - Functional and Technical Requirements: Experience eliciting, decomposing, and developing high quality functional and technical requirements. Understanding of Requirements Traceability Matrices (RTM) or equivalents. - Governance: Demonstrated experience in governance processes (change control boards, requirements prioritization, release management, etc.). - System Security Accreditation Experience: Experience with frameworks such as RMF or continuous ATO. Demonstrated high level understanding of policies and security requirements for systems accreditation. - Analytical & Problem Solving Skills: The ability to analyze complex problems, develop action plans, and find effective solutions. - Leadership & Communication: Excellent communication and interpersonal skills to coordinate teams, manage client relationships, and facilitate meetings. We'll make each as
- . Now Skills: list: Collaboration, GraphQL, Python, Requirements Analysis, RESTful (Rest-APIs). We'll make
- each.
Now Benefits: list:
- Competitive compensation
- Comprehensive insurance options
- Matching contributions through the 401(k) plan and the share purchase plan
- Paid time off for vacation, holidays, and sick time
- Paid parental leave
- Learning opportunities and tuition assistance
- Wellness and Well being programs
Now Pay: The compensation range: "A reasonable estimate of the current range for this role in the U.S. is $127,500.00 $245,500.00." We'll output as
$127,500.00 $245,500.00
. Could also include the earlier "$127,500 - $127,500 USD yearly" but that seems redundant and maybe erroneous. We'll include only the range from the later statement to avoid duplication. However we must preserve ALL substantive information; the earlier line is also substantive (though maybe duplicate). But it's basically same info but with a typo. To be safe, we could include both but note they are separate statements. However that would be repetitive and maybe considered duplication. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines". The duplicated lines refers to duplicated lines in the posting; the two compensation statements are not exactly same but similar. Might be considered duplicated? Not sure. Safer to include both? But we risk violating "Prefer a few substantive sections over many thin ones." Including both as separatemight be thin. I'd choose to include the later range as it's more detailed. The earlier line "$127,500 - $127,500 USD yearly" is likely a mistake; but it's still substantive. However we could incorporate it into the Pay section as note: "The posting also lists a yearly salary of $127,500 - $127,500 USD." That would be summarizing. Better to include both as separate sentences within same
. Eg: "
The posting indicates a yearly salary of $127,500 - $127,500 USD, and a reasonable estimate of the current range for this role in the U.S. is $127,500.00 $245,500.00.
" That preserves both without creating separate thin sections. Now Schedule: hybrid working model acceptable; location Arlington, VA office. We'll put inThe position is located in the Arlington, VA office; a hybrid working model is acceptable.
Now ensure we don't include any boilerplate like EEO statement, accommodation, veteran link, background investigation, etc. Now produce HTML fragment. Let's craft. Check for any stray content: The posting also includes "#CGIFederalJob LB1 #ClearanceJobs Skills CollaborationGraphQLPythonRequirements AnalysisRESTful (Rest-APIs)". We extracted skills. Now final HTML:About the role
CGI Federal has an exciting opportunity for a Deputy Project Manager (Technical) within our Intel sector advancing the national security mission through cutting edge technology. You must be a visionary with a passion for effectively keeping pace with rapidly evolving technology advancements and leveraging your knowledge on a highly collaborative team to deliver state of the art