Program Analyst, F-35- Crystal City, VA
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like location, specific duties bullet points exactly as given (maybe rephrase? Must preserve info, not necessarily exact wording but must not lose detail). We can keep bullet points as given.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we must cut out company overview? The instruction says remove boilerplate, but company overview may be considered boilerplate? It's descriptive of Serco, not directly about the role. Might be considered boilerplate but it's substantive about the employer. However the instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Company overview is not explicitly listed, but could be considered boilerplate? It's not navigation/legal/EEO etc. It's about the company. Might be okay to keep? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Company overview is substantive about Serco. However the sections we are to output are limited to the headings list. There's no heading for Company Overview. So we likely should not include it as a separate section; we could incorporate relevant info into About the role? But About the role is about the role, not company. The instruction says we can only use those headings; we cannot add other headings. So we must either omit company overview or fold it into About the role? The About the role heading is for section headings like About the role, Responsibilities, etc. So we could put a brief description of the role and maybe include company context? But the instruction: "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." So we can include a short
for metadata. Company overview might be considered minor metadata? It's not minor; it's a paragraph about Serco. But we have no heading for it, so we must either drop it or incorporate into About the role? The About the role section could include a sentence about Serco being the employer. That seems acceptable.
Thus we will not include a separate company overview paragraph.
Now we need to extract the exact duty bullets:
From "In This Role You Will":
- Pilot and Maintenance Training Devices – assist Training Systems and Simulation PMO in overseeing the development and delivery of all Pilot Training Devices and Maintenance Training Devices, and in exploring future technology solutions that could potentially resolve existing technology limits within the training systems
- Pilot and Maintenance Training Courseware – assist Training Systems and Simulation PMO in producing the courseware used for classroom training as a supplement to the Pilot and Maintenance Training Devices
- Live, Virtual, and Constructive (LVC) – assist Training Systems and Simulation PMO in managing three subsystems as part of the LVC architecture
- Verification and Validation – assist Training Systems and Simulation PMO in performing verification and validation as part of the development and acceptance of the Training Products (devices, courseware, training aids, etc.) prior to delivery to the customer
- TSS PMO Acquisition Cell and Joint Simulation Environment (JSE) Acquisition Support – Facilitate contract actions from requirements gathering through contract award. Recommend contract strategies. Lead IPT/stakeholders through Request for Proposal (RFP) package development and Proposal Evaluation. Communicate TSS PMO needs with the prime contractor. Review and evaluate both RFP and proposal information and make recommendations to the team. Ensure teams meet deadlines to reduce contract lead times. Organize, record and track contract information changes and communications between contractors and the TSS PMO team. Create products and presentations that present information logically and increase team knowledge. Ensure contract status is updated weekly.
We need to keep each as a list item.
Now Requirements: "To Be Successful In This Role, You Will Have":
- ability to provide onsite support at the F-35 Joint Program Office (JPO) located at Arlington, Crystal City, VA, a minimum of 2 days per week, each week. Onsite days in the JPO office may increase to provide onsite support up to 5 days per week to support the needs of the customer. Exact days in office at the JPO must be coordinated with F-35 customer and approved by your Serco manager.
- An active DoD Secret Security clearance.
- An Associates degree.
- 2 years of experience in program management, technical or business analysis discipline, in weapon systems acquisition and life cycle management.
- Knowledge of the principles, policies, and practices of system acquisition to plan, organize, and coordinate critical aspects of the development, production, deployment, and sustainment of systems, subsystems, and equipment.
- Knowledge of the FAR for the development of contracts and contract modifications required for the acquisition of logistics supportability products.
- Demonstrated experience in the program/project status, schedules, and DoD reporting.
- Demonstrated knowledge of Service and OSD policy and documentation related to PPBE, life- cycle management of military acquisition programs (as specified in the DoD 5000 series), to include DoD Instruction (DoDI) 5000.2, DoD Directive (DODD) 5530.03, and the International Cooperation in Acquisition, Technology and Logistics (IC in AT&L) Handbook.
- The ability to travel up to 10%.
Now Additional Desired Experience And Skills:
- Experience of creating products and working in Microsoft Office Suite- Microsoft Word, Microsoft Excel (data types, formulas and functions in the workbooks), Microsoft Powerpoint, Microsoft Outlook, and Microsoft TEAMS.
We could put that under Skills.
Now Benefits: list:
- Medical, dental, and vision insurance
- Robust vacation and sick leave benefits, and flexible work arrangements where permitted by role or contract
- 401(k) plan that includes employer matching funds
- Tuition reimbursement program
- Life insurance and disability coverage
- Optional coverages that can be purchased, including pet insurance, home and auto insurance, additional life and accident insurance, critical illness insurance, group legal, ID theft protection
- Birth, adoption, parental leave benefits
- Employee Assistance Plan
Now Schedule: we already have onsite days info; we could put that under Schedule section. But we also have it in Requirements. To avoid duplication, we could move schedule info to Schedule section and remove from Requirements. However the instruction says preserve ALL substantive information; we can move it but not duplicate. So we should include schedule info only once. Where does it fit best? The schedule info is about onsite days requirement. Could be under Requirements (as a requirement) or under Schedule. Since we have a Schedule heading possible, we should put it there. Then we can remove it from Requirements to avoid duplication. However the Requirements list includes many other items; we can keep the rest.
Thus Requirements will exclude the onsite days sentence.
Now About the role: we need a prose paragraph summarizing the role: supporting F-35 JPO, Training Systems and Simulation PMO, location Arlington, Crystal City, VA, etc. We'll include location and brief description.
Now we need to ensure we don't include any boilerplate like EEO, legal, etc. We'll omit those.
Now produce HTML:
About the role
Serco is supporting the F-35 Joint Strike Fighter Program Office (
for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like location, specific duties bullet points exactly as given (maybe rephrase? Must preserve info, not necessarily exact wording but must not lose detail). We can keep bullet points as given. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we must cut out company overview? The instruction says remove boilerplate, but company overview may be considered boilerplate? It's descriptive of Serco, not directly about the role. Might be considered boilerplate but it's substantive about the employer. However the instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Company overview is not explicitly listed, but could be considered boilerplate? It's not navigation/legal/EEO etc. It's about the company. Might be okay to keep? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Company overview is substantive about Serco. However the sections we are to output are limited to the headings list. There's no heading for Company Overview. So we likely should not include it as a separate section; we could incorporate relevant info into About the role? But About the role is about the role, not company. The instruction says we can only use those headings; we cannot add other headings. So we must either omit company overview or fold it into About the role? The About the role heading is for section headings like About the role, Responsibilities, etc. So we could put a brief description of the role and maybe include company context? But the instruction: "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." So we can include a short
for metadata. Company overview might be considered minor metadata? It's not minor; it's a paragraph about Serco. But we have no heading for it, so we must either drop it or incorporate into About the role? The About the role section could include a sentence about Serco being the employer. That seems acceptable. Thus we will not include a separate company overview paragraph. Now we need to extract the exact duty bullets: From "In This Role You Will": - Pilot and Maintenance Training Devices – assist Training Systems and Simulation PMO in overseeing the development and delivery of all Pilot Training Devices and Maintenance Training Devices, and in exploring future technology solutions that could potentially resolve existing technology limits within the training systems - Pilot and Maintenance Training Courseware – assist Training Systems and Simulation PMO in producing the courseware used for classroom training as a supplement to the Pilot and Maintenance Training Devices - Live, Virtual, and Constructive (LVC) – assist Training Systems and Simulation PMO in managing three subsystems as part of the LVC architecture - Verification and Validation – assist Training Systems and Simulation PMO in performing verification and validation as part of the development and acceptance of the Training Products (devices, courseware, training aids, etc.) prior to delivery to the customer - TSS PMO Acquisition Cell and Joint Simulation Environment (JSE) Acquisition Support – Facilitate contract actions from requirements gathering through contract award. Recommend contract strategies. Lead IPT/stakeholders through Request for Proposal (RFP) package development and Proposal Evaluation. Communicate TSS PMO needs with the prime contractor. Review and evaluate both RFP and proposal information and make recommendations to the team. Ensure teams meet deadlines to reduce contract lead times. Organize, record and track contract information changes and communications between contractors and the TSS PMO team. Create products and presentations that present information logically and increase team knowledge. Ensure contract status is updated weekly. We need to keep each as a list item. Now Requirements: "To Be Successful In This Role, You Will Have": - ability to provide onsite support at the F-35 Joint Program Office (JPO) located at Arlington, Crystal City, VA, a minimum of 2 days per week, each week. Onsite days in the JPO office may increase to provide onsite support up to 5 days per week to support the needs of the customer. Exact days in office at the JPO must be coordinated with F-35 customer and approved by your Serco manager. - An active DoD Secret Security clearance. - An Associates degree. - 2 years of experience in program management, technical or business analysis discipline, in weapon systems acquisition and life cycle management. - Knowledge of the principles, policies, and practices of system acquisition to plan, organize, and coordinate critical aspects of the development, production, deployment, and sustainment of systems, subsystems, and equipment. - Knowledge of the FAR for the development of contracts and contract modifications required for the acquisition of logistics supportability products. - Demonstrated experience in the program/project status, schedules, and DoD reporting. - Demonstrated knowledge of Service and OSD policy and documentation related to PPBE, life- cycle management of military acquisition programs (as specified in the DoD 5000 series), to include DoD Instruction (DoDI) 5000.2, DoD Directive (DODD) 5530.03, and the International Cooperation in Acquisition, Technology and Logistics (IC in AT&L) Handbook. - The ability to travel up to 10%. Now Additional Desired Experience And Skills: - Experience of creating products and working in Microsoft Office Suite- Microsoft Word, Microsoft Excel (data types, formulas and functions in the workbooks), Microsoft Powerpoint, Microsoft Outlook, and Microsoft TEAMS. We could put that under Skills. Now Benefits: list: - Medical, dental, and vision insurance - Robust vacation and sick leave benefits, and flexible work arrangements where permitted by role or contract - 401(k) plan that includes employer matching funds - Tuition reimbursement program - Life insurance and disability coverage - Optional coverages that can be purchased, including pet insurance, home and auto insurance, additional life and accident insurance, critical illness insurance, group legal, ID theft protection - Birth, adoption, parental leave benefits - Employee Assistance Plan Now Schedule: we already have onsite days info; we could put that under Schedule section. But we also have it in Requirements. To avoid duplication, we could move schedule info to Schedule section and remove from Requirements. However the instruction says preserve ALL substantive information; we can move it but not duplicate. So we should include schedule info only once. Where does it fit best? The schedule info is about onsite days requirement. Could be under Requirements (as a requirement) or under Schedule. Since we have a Schedule heading possible, we should put it there. Then we can remove it from Requirements to avoid duplication. However the Requirements list includes many other items; we can keep the rest. Thus Requirements will exclude the onsite days sentence. Now About the role: we need a prose paragraph summarizing the role: supporting F-35 JPO, Training Systems and Simulation PMO, location Arlington, Crystal City, VA, etc. We'll include location and brief description. Now we need to ensure we don't include any boilerplate like EEO, legal, etc. We'll omit those. Now produce HTML:
About the role
Serco is supporting the F-35 Joint Strike Fighter Program Office (