Financial Analyst Sr
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to not repeat job title as heading.
We need to not put Job ID/requisition numbers as headings.
We need to include a section only when posting has real specific content for it.
We need to avoid filler like "commensurate with experience", etc.
We need to prefer few substantive sections over many thin ones.
Thus we need to decide which sections to include: About the role (maybe a paragraph summarizing role), Responsibilities (list), Requirements (maybe education/experience), Qualifications (maybe preferred?), Skills (maybe list of skills), Benefits, Pay, Schedule (if schedule info present). The posting mentions Full-Time Salary Range, and benefits details. No explicit schedule (like hours) besides Full-Time. Could include Schedule if they mention full-time? Might be considered schedule info. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state Pay (salary range) and Benefits (list). Schedule? It says Full-Time, but not specific schedule like "Monday-Friday 9-5". Might be considered schedule info? The phrase "Full-Time" could be considered schedule. But they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Full-Time, which is a schedule type. So we could include Schedule section with "Full-Time". However we need to avoid filler like "not specified". "Full-Time" is specific enough.
We need to decide sections: About the role (maybe a paragraph describing role), Responsibilities (list), Requirements (education/experience), Qualifications (maybe preferred?), Skills (list of technical skills), Benefits, Pay, Schedule.
But we need to avoid duplication. The posting includes "Required Education, Experience, & Skills" and "Preferred Education, Experience, & Skills". Could combine into Requirements (required) and Qualifications (preferred). Or we could have Requirements (required) and Skills (preferred). But they also have a list of skills within required and preferred.
Better: Use sections: About the role (paragraph summarizing), Responsibilities (list of duties), Requirements (required education/experience), Qualifications (preferred education/experience/skills), Benefits, Pay, Schedule.
But we need to ensure we don't create thin sections. Let's see content.
About the role: The first paragraph: "An experienced Financial Analyst Sr. is sought to join BAE Systems Platforms and Services Program Controls Team to work within its CAS Enterprise Program Controls/ Program Management system supporting on-going Program operations, including but not limited to current and future programs. BAE's current program portfolio includes several multi-year programs to include the U.S. Army’s Acquisition Program of Record. These programs are based in the design and development of the AMPV program with operations in multiple CAS Sites. In addition to managing the on-going requirements of its programs, the Program Controls / Performance Measurement System is integrated with the Financial Systems to provide information required for near-term and long-term planning of the laboratory resource needs. Under limited direction, the selected individual will be responsible for planning and implementing highly complex cost and planning program control functions and systems for various size and types of programs conditioned on requirements as defined by the US Department of Defense (DOD) and the BAE York CAS Program Directorates. Oversee the work, resources, and dollars using program controls tools drawing from advanced understanding of program management methodology, program control principles, and hands-on experience with planning and cost processing software. Junior specialists or analysts, and interface with other Finance Analysts in the development of templates, serving as a planning and cost processing tool expert, and advising division/program managers on the trends and progress of their plans and schedules. Responsible for the preparation and analysis of monthly trend and Earned Value (EV) performance reports (IPMR/CPR’s), processing updates to the Estimate to Complete (EAC) and implementing baseline revisions."
That's a lot of prose; could be split into About the role and Responsibilities. But we need to avoid duplication.
We could treat the first paragraph as About the role (general description). Then responsibilities as bullet list derived from sentences: planning and implementing highly complex cost and planning program control functions; oversee work, resources, dollars; interface with other Finance Analysts; development of templates; serve as planning and cost processing tool expert; advise division/program managers on trends and progress; preparation and analysis of monthly trend and EV performance reports; processing updates to EAC; implementing baseline revisions.
Also maybe "Junior specialists or analysts, and interface with other Finance Analysts..." is part of responsibilities.
We need to preserve all substantive information; we can convert to bullet list.
Requirements: "Bachelor Degree at least 4 years of relevant experience. Work experience considered in lieu of formal education.Earned Value Management tools and concepts of at least 4 years of relevant experience related to baselining, and performance change management.Proficient in Excel understanding Pivot Tables, and V-lookups.Experience in EVMS Site Validations, Joint Surveillance Audits, System Surveillance ReviewsExpertise in understanding and using Earned Value Management concepts and processes."
We can list as bullet points.
Preferred: "Experience in OracleAbility and willingness to work additional hours beyond the normal work day when required to meet deadlines.Subject Matter Expert with Program Controls/ Program Management processes, as applied on developmental engineering and production programs, including but not limited to risk management, financial management, work breakdown structures, change management, cost estimating, configuration management and system surveillance, operations, and procurement. Experience in Implementing EVMS SystemsExperience leading Integrated Baseline ReviewsExperience working in a matrixed environment and experience interfacing with high level internal and external government leadership.Demonstrated ability to support program managers and their control account managers with the use and maintenance of program controls systems and outputs.Demonstrated ability to support the development of resource loaded schedules, including but not limited to schedule statusing, reporting, variance analysis, and change control.Experience leading groups and teams on large programs in a fast paced environment.Experience in directing, training, and mentoring junior staff in program controls systems and tools.Ability to work independently and meet deadlines, including working in a semi-structured environment with the skill to develop and implement new processes and procedures.Ability to effectively communicate and work with both technical and non-technical staff.Experience with Cobra Data Integration Tools, or equivalent (MPM or Cost Manager).Experience with wInsight/APEX Reporting ToolsFamiliarity with Defense Federal Acquisition Regulations, ANSI-748-C, EVMIG, and NDIA Intent Guides.Program Controls/Program Management certification(s) are desirable.Experience in EVMS Site Validations, Joint Surveillance Audits, System Surveillance Reviews"
We can list as bullet points under Qualifications (preferred).
Benefits: paragraph about health, dental, vision, HSA, 401(k), disability, life accident, employee assistance, legal plan, perks, leave programs, recognition program, other incentives.
Pay: "Full-Time Salary Range: $82799 - $140723" plus note about factors.
Schedule: "Full-Time" maybe.
We need to avoid boilerplate like "Please note: This range is based on our market pay structures..." That's still substantive? It's explanatory but maybe we can keep as part of Pay section prose.
We need to remove duplicated lines: there is duplicate "Experience in EVMS Site Validations, Joint Surveillance Audits, System Surveillance Reviews" appears both in required and preferred; we should keep both? It's duplicated content; we should not repeat duplicated lines. So we should include it only once, perhaps under required (since it's required) and not repeat under preferred. But the preferred also repeats it; we can omit duplicate.
Also "Experience in EVMS Site Validations, Joint Surveillance Audits, System Surveillance Reviews" appears twice in required? Actually required includes that phrase once. Preferred includes again at end. We'll keep only once under required.
Now we need to output HTML fragment only.
Let's craft:
About the role
... (paragraph summarizing role)
Responsibilities
- ...
...
Requirements
- Bachelor’s degree or equivalent work experience (minimum 4 years relevant experience)
- At least 4 years of experience with Earned Value Management tools and concepts, including baselining and performance change management
- Proficiency in Excel, including Pivot Tables and V‑lookups
- Experience with EVMS Site Validations, Joint Surveillance Audits, and System Surveillance Reviews
- Expertise in understanding and applying Earned Value Management concepts and processes
Qualifications (Preferred)
- Experience with Oracle
- Willingness to work additional hours beyond the normal workday when required to meet deadlines
- Subject‑matter expertise in Program Controls/Program Management processes applied to developmental engineering and production programs (risk management, financial management, work breakdown structures, change management, cost estimating, configuration management, system surveillance, operations, procurement)
- Experience implementing EVMS systems
- Experience leading Integrated Baseline Reviews
- Experience working in a matrixed environment and interfacing with high‑level internal and external government leadership
- Demonstrated ability to support program managers and control account managers with the use and maintenance of program controls systems and outputs
- Demonstrated ability to support the development of resource‑loaded schedules (schedule statusing, reporting, variance analysis, change control)
- Experience leading groups and teams on large programs in a fast‑paced environment
- Experience directing, training, and mentoring junior staff in program controls systems and tools
- Ability to work independently and meet deadlines in a semi‑structured environment, including developing and implementing new processes and procedures
- Ability to communicate effectively with both technical and non‑technical staff
- Experience with Cobra Data Integration Tools (or equivalent MPM/Cost Manager)
- Experience with wInsight/APEX Reporting Tools
- Familiarity with Defense Federal Acquisition Regulations, ANSI‑748‑C, EVMIG, and NDIA Intent Guides
- Program Controls/Program Management certification(s) desirable
Benefits
Regular employees scheduled to work 20+ hours per week are offered: health, dental, and vision insurance; health savings accounts; a 401(k) savings plan; disability coverage; life and accident insurance; an employee assistance program; a legal plan; and other perks including discounts on home, auto, and pet insurance. Leave programs include paid time off, paid holidays, paid parental, military, bereavement, and applicable federal and state sick leave. Employees may participate in the company recognition program to receive monetary or non‑monetary recognition awards, and other incentives may be available based on position level and/or job specifics.
Pay
Full‑Time Salary Range: $82,799 – $140,723. Individual salaries are determined by factors such as business considerations, local market conditions, internal equity, and candidate qualifications (skills, education, experience).
Schedule
Full‑Time position.
We need to ensure we didn't include any boilerplate like "This position will be posted for at least 5 calendar days..." etc. We removed that
for prose. We need to not repeat job title as heading. We need to not put Job ID/requisition numbers as headings. We need to include a section only when posting has real specific content for it. We need to avoid filler like "commensurate with experience", etc. We need to prefer few substantive sections over many thin ones. Thus we need to decide which sections to include: About the role (maybe a paragraph summarizing role), Responsibilities (list), Requirements (maybe education/experience), Qualifications (maybe preferred?), Skills (maybe list of skills), Benefits, Pay, Schedule (if schedule info present). The posting mentions Full-Time Salary Range, and benefits details. No explicit schedule (like hours) besides Full-Time. Could include Schedule if they mention full-time? Might be considered schedule info. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state Pay (salary range) and Benefits (list). Schedule? It says Full-Time, but not specific schedule like "Monday-Friday 9-5". Might be considered schedule info? The phrase "Full-Time" could be considered schedule. But they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Full-Time, which is a schedule type. So we could include Schedule section with "Full-Time". However we need to avoid filler like "not specified". "Full-Time" is specific enough. We need to decide sections: About the role (maybe a paragraph describing role), Responsibilities (list), Requirements (education/experience), Qualifications (maybe preferred?), Skills (list of technical skills), Benefits, Pay, Schedule. But we need to avoid duplication. The posting includes "Required Education, Experience, & Skills" and "Preferred Education, Experience, & Skills". Could combine into Requirements (required) and Qualifications (preferred). Or we could have Requirements (required) and Skills (preferred). But they also have a list of skills within required and preferred. Better: Use sections: About the role (paragraph summarizing), Responsibilities (list of duties), Requirements (required education/experience), Qualifications (preferred education/experience/skills), Benefits, Pay, Schedule. But we need to ensure we don't create thin sections. Let's see content. About the role: The first paragraph: "An experienced Financial Analyst Sr. is sought to join BAE Systems Platforms and Services Program Controls Team to work within its CAS Enterprise Program Controls/ Program Management system supporting on-going Program operations, including but not limited to current and future programs. BAE's current program portfolio includes several multi-year programs to include the U.S. Army’s Acquisition Program of Record. These programs are based in the design and development of the AMPV program with operations in multiple CAS Sites. In addition to managing the on-going requirements of its programs, the Program Controls / Performance Measurement System is integrated with the Financial Systems to provide information required for near-term and long-term planning of the laboratory resource needs. Under limited direction, the selected individual will be responsible for planning and implementing highly complex cost and planning program control functions and systems for various size and types of programs conditioned on requirements as defined by the US Department of Defense (DOD) and the BAE York CAS Program Directorates. Oversee the work, resources, and dollars using program controls tools drawing from advanced understanding of program management methodology, program control principles, and hands-on experience with planning and cost processing software. Junior specialists or analysts, and interface with other Finance Analysts in the development of templates, serving as a planning and cost processing tool expert, and advising division/program managers on the trends and progress of their plans and schedules. Responsible for the preparation and analysis of monthly trend and Earned Value (EV) performance reports (IPMR/CPR’s), processing updates to the Estimate to Complete (EAC) and implementing baseline revisions." That's a lot of prose; could be split into About the role and Responsibilities. But we need to avoid duplication. We could treat the first paragraph as About the role (general description). Then responsibilities as bullet list derived from sentences: planning and implementing highly complex cost and planning program control functions; oversee work, resources, dollars; interface with other Finance Analysts; development of templates; serve as planning and cost processing tool expert; advise division/program managers on trends and progress; preparation and analysis of monthly trend and EV performance reports; processing updates to EAC; implementing baseline revisions. Also maybe "Junior specialists or analysts, and interface with other Finance Analysts..." is part of responsibilities. We need to preserve all substantive information; we can convert to bullet list. Requirements: "Bachelor Degree at least 4 years of relevant experience. Work experience considered in lieu of formal education.Earned Value Management tools and concepts of at least 4 years of relevant experience related to baselining, and performance change management.Proficient in Excel understanding Pivot Tables, and V-lookups.Experience in EVMS Site Validations, Joint Surveillance Audits, System Surveillance ReviewsExpertise in understanding and using Earned Value Management concepts and processes." We can list as bullet points. Preferred: "Experience in OracleAbility and willingness to work additional hours beyond the normal work day when required to meet deadlines.Subject Matter Expert with Program Controls/ Program Management processes, as applied on developmental engineering and production programs, including but not limited to risk management, financial management, work breakdown structures, change management, cost estimating, configuration management and system surveillance, operations, and procurement. Experience in Implementing EVMS SystemsExperience leading Integrated Baseline ReviewsExperience working in a matrixed environment and experience interfacing with high level internal and external government leadership.Demonstrated ability to support program managers and their control account managers with the use and maintenance of program controls systems and outputs.Demonstrated ability to support the development of resource loaded schedules, including but not limited to schedule statusing, reporting, variance analysis, and change control.Experience leading groups and teams on large programs in a fast paced environment.Experience in directing, training, and mentoring junior staff in program controls systems and tools.Ability to work independently and meet deadlines, including working in a semi-structured environment with the skill to develop and implement new processes and procedures.Ability to effectively communicate and work with both technical and non-technical staff.Experience with Cobra Data Integration Tools, or equivalent (MPM or Cost Manager).Experience with wInsight/APEX Reporting ToolsFamiliarity with Defense Federal Acquisition Regulations, ANSI-748-C, EVMIG, and NDIA Intent Guides.Program Controls/Program Management certification(s) are desirable.Experience in EVMS Site Validations, Joint Surveillance Audits, System Surveillance Reviews" We can list as bullet points under Qualifications (preferred). Benefits: paragraph about health, dental, vision, HSA, 401(k), disability, life accident, employee assistance, legal plan, perks, leave programs, recognition program, other incentives. Pay: "Full-Time Salary Range: $82799 - $140723" plus note about factors. Schedule: "Full-Time" maybe. We need to avoid boilerplate like "Please note: This range is based on our market pay structures..." That's still substantive? It's explanatory but maybe we can keep as part of Pay section prose. We need to remove duplicated lines: there is duplicate "Experience in EVMS Site Validations, Joint Surveillance Audits, System Surveillance Reviews" appears both in required and preferred; we should keep both? It's duplicated content; we should not repeat duplicated lines. So we should include it only once, perhaps under required (since it's required) and not repeat under preferred. But the preferred also repeats it; we can omit duplicate. Also "Experience in EVMS Site Validations, Joint Surveillance Audits, System Surveillance Reviews" appears twice in required? Actually required includes that phrase once. Preferred includes again at end. We'll keep only once under required. Now we need to output HTML fragment only. Let's craft:
About the role
... (paragraph summarizing role)
Responsibilities
- ... ...
Requirements
- Bachelor’s degree or equivalent work experience (minimum 4 years relevant experience)
- At least 4 years of experience with Earned Value Management tools and concepts, including baselining and performance change management
- Proficiency in Excel, including Pivot Tables and V‑lookups
- Experience with EVMS Site Validations, Joint Surveillance Audits, and System Surveillance Reviews
- Expertise in understanding and applying Earned Value Management concepts and processes
Qualifications (Preferred)
- Experience with Oracle
- Willingness to work additional hours beyond the normal workday when required to meet deadlines
- Subject‑matter expertise in Program Controls/Program Management processes applied to developmental engineering and production programs (risk management, financial management, work breakdown structures, change management, cost estimating, configuration management, system surveillance, operations, procurement)
- Experience implementing EVMS systems
- Experience leading Integrated Baseline Reviews
- Experience working in a matrixed environment and interfacing with high‑level internal and external government leadership
- Demonstrated ability to support program managers and control account managers with the use and maintenance of program controls systems and outputs
- Demonstrated ability to support the development of resource‑loaded schedules (schedule statusing, reporting, variance analysis, change control)
- Experience leading groups and teams on large programs in a fast‑paced environment
- Experience directing, training, and mentoring junior staff in program controls systems and tools
- Ability to work independently and meet deadlines in a semi‑structured environment, including developing and implementing new processes and procedures
- Ability to communicate effectively with both technical and non‑technical staff
- Experience with Cobra Data Integration Tools (or equivalent MPM/Cost Manager)
- Experience with wInsight/APEX Reporting Tools
- Familiarity with Defense Federal Acquisition Regulations, ANSI‑748‑C, EVMIG, and NDIA Intent Guides
- Program Controls/Program Management certification(s) desirable
Benefits
Regular employees scheduled to work 20+ hours per week are offered: health, dental, and vision insurance; health savings accounts; a 401(k) savings plan; disability coverage; life and accident insurance; an employee assistance program; a legal plan; and other perks including discounts on home, auto, and pet insurance. Leave programs include paid time off, paid holidays, paid parental, military, bereavement, and applicable federal and state sick leave. Employees may participate in the company recognition program to receive monetary or non‑monetary recognition awards, and other incentives may be available based on position level and/or job specifics.
Pay
Full‑Time Salary Range: $82,799 – $140,723. Individual salaries are determined by factors such as business considerations, local market conditions, internal equity, and candidate qualifications (skills, education, experience).
Schedule
Full‑Time position.
We need to ensure we didn't include any boilerplate like "This position will be posted for at least 5 calendar days..." etc. We removed that