Senior Program Control Analyst
AV · Germantown, MD · 1 mo ago
On-siteFinance$145k–$221k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually we need to use for section headings like 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. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Also remove cookie/navigation/legal/EEO etc. Also remove "Principals only need apply. NO agencies please." That's application instruction? Probably remove. Also remove "About AV" maybe not needed? The instruction says use headings for sections like About the role, Responsibilities, etc. The "About AV" could be considered "About the role"? Actually "About AV" is company description, not role. Might be considered "About the role"? Not sure. The instruction: "use
for section headings like 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. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Also remove cookie/navigation/legal/EEO etc. Also remove "Principals only need apply. NO agencies please." That's application instruction? Probably remove. Also remove "About AV" maybe not needed? The instruction says use headings for sections like About the role, Responsibilities, etc. The "About AV" could be considered "About the role"? Actually "About AV" is company description, not role. Might be considered "About the role"? Not sure. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include About the role heading and put the summary description there. The initial part: "Worker Type Regular Summary Job Description Being on the AV team means..." That's basically about the role/company. We'll put that under About the role.
Responsibilities: list of duties. We'll extract bullet points from "Position Responsibilities" paragraph. It's a long sentence with many responsibilities separated by periods. We'll split into list items.
Requirements: maybe Education Qualifications? The posting has "Education Qualifications (Preferred Skills & Experience): Bachelor’s degree and minimum of twelve (12) years of related project control experience; or Master’s degree and minimum of eight (8) years of project control experience." That's qualifications. Also maybe "Clearance Level No Clearance" but that's not a requirement? It says "Clearance Level No Clearance". Might be a requirement? It's a statement that no clearance needed. Could be included under Requirements? But it's not a requirement; it's a condition. Might be omitted as boilerplate? It's substantive but maybe not needed. We'll include under Requirements? The instruction: include sections only when posting has real specific content. We have Education Qualifications. Also Skills: list of skills. Also Benefits: they list benefits. Also Pay: Salary range. Also Schedule: they mention "9/80 work schedule". That's schedule info. So we include Schedule.
We must not include sections with placeholder like "commensurate with experience". Not present.
We must not include duplicated lines. Also remove ITAR requirement? That's substantive but maybe not a standard heading. Could be included under Requirements? But it's a legal requirement. Might be considered part of Requirements. However instruction says remove EEO/equal-opportunity/scam-warning boilerplate. ITAR is not EEO but is a legal requirement. Might be kept. But we have no specific heading for ITAR; we could include under Requirements as a note. But maybe better to omit as it's not a standard heading and could be considered boilerplate? It's substantive though. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". ITAR is legal. So we should remove it. Also "ITAR U.S. Citizenship required" at end is legal; remove.
Also remove "Principals only need apply. NO agencies please." That's application instruction; remove.
Also remove links to benefits website? Might keep benefits description but not the URL? The instruction: preserve ALL substantive information; do not invent or summarize away detail. The URL is substantive? It's a reference for more info. Might be considered navigation? It's a link. Might be considered boilerplate? Not sure. Safer to keep the benefits description but maybe drop the URL as it's a navigation link. However it's part of benefits info. Could keep as plain text without link. We'll keep the benefits description sentence without the URL.
Also remove "For more information about our company benefit offerings please visit: http://www.avinc.com/myavbenefits." That's navigation; remove.
Also remove "We also encourage you to review our company website at http://www.avinc.com to learn more about us." Remove.
Also remove "About AV" paragraph? That's company description, not role. Might be considered About the role? But it's about company. Could be omitted as not directly about role. However the initial summary already describes role. We'll keep About the role as the initial summary paragraph (Worker Type Regular Summary Job Description Being on the AV team means...). We'll strip "Worker Type Regular Summary Job Description" maybe? That's metadata. We'll keep the substantive sentences.
Let's extract About the role text: Starting after "Worker Type Regular Summary Job Description". The text: "Being on the AV team means working alongside the brightest minds in technology on the toughest challenges facing our nation – not just every once in a while, but every single day. Together, we are leading the transformation of modern warfare and each AV employee plays a key role. That’s why our investment in you goes beyond a rewarding salary and benefits package. We’re committed to providing our people with the best opportunities to develop their skills, share their knowledge, and push their innovative ideas to the cutting-edge. Having fun doing it with a team that feels like family all across AV Nation is the ultimate perk. From Space and Directed Energy to Cyber and Intelligence to C4ISR and Air & Missile Defense, there is no limit to where you can take your career with us. Are you ready to launch a career at AV? As the Senior Program Control Analyst, you will play a highly visible role as part of the finance team in supporting multiple programs. If you are a driven, career-focused and customer-oriented program control/financial analyst with strong working knowledge of federal contracting concepts, practices, and procedures, join our team leading the transformation of modern warfare."
We'll keep that as About the role.
Responsibilities: list items from the paragraph after "Position Responsibilities". Let's split by periods (but careful with abbreviations). We'll produce list items:
- Review and understand contract terms and conditions (multiple contract types to include T&M, FFP, FFP LOE, CPFF, & CPIF) & ensure compliance to financial clauses and contractual requirements throughout project implementation.
- Ultimately responsible for quality of product and services, cost control, timeliness and business relations across awarded TO(s)
- Establish and maintain time-phased cost/schedule baseline, enforce strict change control, monitor status/availability, and ensure proper work authorization.
- Prepare manpower and non-labor forecasts and assist in resource planning.
- Responsible for forecasting, monitoring, and updating program revenue.
- Identify potential resource gaps and works with business leadership to address.
- Demonstrate strong analytical / data-driven problem-solving skills
- Provide continuous assessment and evaluation of contract performance and initiate appropriate corrective action as needed to ensure compliance.
- Ensure responsive customer-focused services through communication and coordination with the Government Contracting Officer (KO), Contracting Officer Representative (COR), Contracting Officer Technical Representative (COTR), AV PM, and Subcontractor PM team.
- Monitor performance of functional managers/supervisors and submissions of required reports and Contract Data Requirements List (CDRL).
- Prompt resolution of issues associated with performance
- Work with and advise Project Managers, Control Account Management team (CAMs) and senior technical personnel to ensure uniform application of Earned Value Management procedures.
- Assist and advise management in program setup, planning, and control (including tailored EVMS).
- Monitor performance, provide variance analysis & visibility on projects of varying contract type, size, complexity, and level of risk.
- Monitor contract value and CLINs to ensure proper cost collection, reporting and related funding status.
- Develop standard and ad hoc reports to effectively communicate status and provide management with clear, timely and accurate information; make recommendations to assist in decision-making.
- Produce and validate Integrated Program Management Reports (IPMRs) and similar status reports for customers and program management.
- Track subcontract cost & schedule status, material receipts, open commitments, and termination liability.
- Utilize MS Office Suite and other applications including Cobra, Unanet and SharePoint.
- Track and report on material purchases, cost of goods sold and revenue for commercial products/product lines.
- Mentor and coach Program Control Analysts.
- Performs other duties as assigned or required.
We'll keep as - .
Education Qualifications: we have "Education Qualifications (Preferred Skills & Experience): Bachelor’s degree and minimum of twelve (12) years of related project control experience; or Master’s degree and minimum of eight (8) years of project control experience." We'll put under Requirements or Qualifications? The headings list includes Requirements, Qualifications, Skills. We could put education under Qualifications. But we also have Skills separate. Let's put Education under Qualifications. Or we could have Requirements for experience and Qualifications for education. But we have only one education statement. We'll put under Qualifications.
Skills: list: "Strong working knowledge of MS Office Suite, Cobra, and Unanet", "Must be able to work well as a team member in a fast-paced environment with limited direction", "Excellent oral and written communication skills", "Ability to effectively interface with all levels of internal and external customers", "Excellent problem-solving skills", "Customer-centric mindset, ability to translate customer issues/needs into profitable business solutions", "Candidate must be able to obtain and maintain a security clearance." Also maybe "Physical Demands" but that's not skill. We'll include skills list.
Benefits: "AV offers an excellent benefits package including medical, dental vision, 401K with company matching, a 9/80 work schedule and a paid holiday shutdown." We'll keep that.
Pay: "The Salary Range For This Role Is $145,000 - $221,250". We'll put under Pay.
Schedule: The benefits already mention 9/80 work schedule; but schedule section could be separate. However we already have schedule info in benefits. The instruction: prefer a few substantive sections over many thin ones. Could combine schedule into Benefits? But we have a separate Schedule heading possible. Since schedule is mentioned, we could create Schedule section with "9/80 work schedule". However benefits also mention it. To avoid duplication, we could keep only Benefits and not Schedule. But the instruction says include Schedule only if posting actually states them. It does state 9/80 work schedule. So we could include Schedule section with that detail. However we would be duplicating the same info in Benefits. Might be considered duplication. Better to keep Benefits and not Schedule to avoid thin sections. But we need to decide. The instruction: "Prefer a few substantive sections over many thin ones." So if we can incorporate schedule into Benefits, we avoid extra heading. Benefits already includes schedule. So we can omit Schedule section.
Thus sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay.
Check for any other sections: maybe "Clearance Level No Clearance" could be under Requirements? But it's not a requirement; it's a statement that no clearance needed. Could be omitted as not needed. We'll drop.
Now produce HTML fragment: use
for each heading, then content:
for prose,
- for lists.
We must not include or . Just fragment.
Let's craft.
About the role: put the paragraph(s) as
. Might be two paragraphs? We'll combine into one
with the text.
Responsibilities:
Responsibilities
- ... etc.
Qualifications:
Qualifications
Bachelor’s degree and minimum of twelve (12) years of related project control experience; or Master’s degree and minimum of eight (8) years of project control experience.
Skills: Skills
- ... etc.
Benefits:
Benefits
AV offers an excellent benefits package including medical, dental vision, 401
- .
Education Qualifications: we have "Education Qualifications (Preferred Skills & Experience): Bachelor’s degree and minimum of twelve (12) years of related project control experience; or Master’s degree and minimum of eight (8) years of project control experience." We'll put under Requirements or Qualifications? The headings list includes Requirements, Qualifications, Skills. We could put education under Qualifications. But we also have Skills separate. Let's put Education under Qualifications. Or we could have Requirements for experience and Qualifications for education. But we have only one education statement. We'll put under Qualifications.
Skills: list: "Strong working knowledge of MS Office Suite, Cobra, and Unanet", "Must be able to work well as a team member in a fast-paced environment with limited direction", "Excellent oral and written communication skills", "Ability to effectively interface with all levels of internal and external customers", "Excellent problem-solving skills", "Customer-centric mindset, ability to translate customer issues/needs into profitable business solutions", "Candidate must be able to obtain and maintain a security clearance." Also maybe "Physical Demands" but that's not skill. We'll include skills list.
Benefits: "AV offers an excellent benefits package including medical, dental vision, 401K with company matching, a 9/80 work schedule and a paid holiday shutdown." We'll keep that.
Pay: "The Salary Range For This Role Is $145,000 - $221,250". We'll put under Pay.
Schedule: The benefits already mention 9/80 work schedule; but schedule section could be separate. However we already have schedule info in benefits. The instruction: prefer a few substantive sections over many thin ones. Could combine schedule into Benefits? But we have a separate Schedule heading possible. Since schedule is mentioned, we could create Schedule section with "9/80 work schedule". However benefits also mention it. To avoid duplication, we could keep only Benefits and not Schedule. But the instruction says include Schedule only if posting actually states them. It does state 9/80 work schedule. So we could include Schedule section with that detail. However we would be duplicating the same info in Benefits. Might be considered duplication. Better to keep Benefits and not Schedule to avoid thin sections. But we need to decide. The instruction: "Prefer a few substantive sections over many thin ones." So if we can incorporate schedule into Benefits, we avoid extra heading. Benefits already includes schedule. So we can omit Schedule section.
Thus sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay.
Check for any other sections: maybe "Clearance Level No Clearance" could be under Requirements? But it's not a requirement; it's a statement that no clearance needed. Could be omitted as not needed. We'll drop.
Now produce HTML fragment: use
for each heading, then content:
for prose,
- for lists.
We must not include or . Just fragment.
Let's craft.
About the role: put the paragraph(s) as
. Might be two paragraphs? We'll combine into one
with the text. Responsibilities:
Responsibilities
- ... etc.
Qualifications:
Qualifications
Bachelor’s degree and minimum of twelve (12) years of related project control experience; or Master’s degree and minimum of eight (8) years of project control experience.
Skills:Skills
- ... etc.
Benefits:
Benefits
AV offers an excellent benefits package including medical, dental vision, 401
- ... etc.
Benefits:
- ... etc.
Qualifications:
- for lists.
We must not include or . Just fragment.
Let's craft.
About the role: put the paragraph(s) as