Financial Management Sr Stf - E5

We need to output HTML fragment with sections: About the role? The posting includes description paragraphs. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to parse content. The posting: "Standard Job Description As the GRS F‑35 Labor‑Sustainment Lead/Subject‑Matter Expert supporting Global Readiness Solution (GRS), you will serve as the primary labor sustainment lead. This high-impact role plays a critical part in shaping GRS strategies, guiding financial execution, and driving business performance across LMLS GRS programs. You will provide day‑to‑day leadership to GRS Cost Integrators (CIs) and Control Account Managers (CAMs) across the entire F‑35 sustainment portfolio. Drive the monthly business tempo: coordinate schedule, data collection, and reporting for all sustainment control accounts. Perform comprehensive financial analysis, including managing control accounts budgets, estimates-at-complete (EACs), and forecasting activities. Lead/support CAMs with variance analysis, trend identification, and risk-and-opportunity assessments; recommend corrective actions. Prepare and present concise financial briefings for senior leadership, highlighting key performance indicators and strategic implications. Partners with program managers, engineers, and business management teams to align financial plans with technical and schedule requirements. This role offers direct exposure to senior leadership, making it an excellent opportunity for a finance professional seeking both strategic influence and hands-on ownership." That's the role description. Could be "About the role" or "Responsibilities". We need to separate responsibilities maybe. Then "Basic Qualifications" list. Then "Desired Skills" list. Then "Pay Information" with GeoZones. Then benefits paragraph. We need sections: About the role (maybe summary), Responsibilities (list of duties), Requirements (maybe basic qualifications?), Qualifications (maybe desired skills?), Skills (maybe desired skills?), Benefits, Pay, Schedule. But we must not create sections with filler. We need to decide which sections have real content. We have: - About the role: could be the introductory paragraph summarizing role. - Responsibilities: list of duties (drive monthly business tempo, coordinate schedule, data collection, reporting, perform financial analysis, lead/support CAMs, prepare briefings, partner with program managers, etc.) - Requirements: maybe basic qualifications (Bachelor's degree or higher with 8+ years finance experience, experience with LM Aeronautics business systems, experience with program finance business rhythms, experience in finance and business operations competency, experience creating baselines and managing budget targets, experience working across organizational boundaries). That's a list. - Qualifications: maybe desired skills? But we already have Desired Skills list. Could treat Desired Skills as Skills section. - Skills: maybe the Desired Skills list (demonstrated financial and analytical experience, familiar with cost structure, etc.) - Benefits: paragraph listing benefits. - Pay: GeoZones salary ranges. - Schedule: Not mentioned explicitly; there is mention of flexible work arrangements and schedules (e.g., 4x10) in benefits. But schedule not given as specific. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. Benefits are stated, so include Benefits. Pay is stated (salary ranges). Schedule: there is mention of flexible work arrangements and schedules (e.g., 4x10) under benefits. That's not a specific schedule requirement; but it's still schedule info. However we should only create Schedule section if posting actually states schedule specifics (like typical hours, shift). It mentions flexible work arrangements and schedules (e.g., 4x10) as part of benefits. That could be considered schedule info but it's under benefits. Safer to not create separate Schedule section unless explicit schedule like "Full-time", "Monday-Friday". The posting does not give schedule details beyond flexible work arrangements. I'd omit Schedule section. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from each section. Let's extract. About the role: The first paragraph(s) up to "This role offers direct exposure to senior leadership, making it an excellent opportunity for a finance professional seeking both strategic influence and hands-on ownership." That's prose. Could be one

  . Responsibilities: list of duties: - Drive the monthly business tempo: coordinate schedule, data collection, and reporting for all sustainment control accounts. - Perform comprehensive financial analysis, including managing control accounts budgets, estimates-at-complete (EACs), and forecasting activities. - Lead/support CAMs with variance analysis, trend identification, and risk-and-opportunity assessments; recommend corrective actions. - Prepare and present concise financial briefings for senior leadership, highlighting key performance indicators and strategic implications. - Partners with program managers, engineers, and business management teams to align financial plans with technical and schedule requirements. Also earlier: "You will provide day‑to‑day leadership to GRS Cost Integrators (CIs) and Control Account Managers (CAMs) across the entire F‑35 sustainment portfolio." That's also a responsibility. Also "This high-impact role plays a critical part in shaping GRS strategies, guiding financial execution, and driving business performance across LMLS GRS programs." Might be more about role but could be responsibility. We'll include all. Requirements (Basic Qualifications): list: - Bachelor’s degree or higher with a minimum of 8 or more years of finance professional experience - Experience with LM Aeronautics business systems such as SAP, Deltek Cobra, Aero Editor, Accounting Data Analysis and Reporting (ADAR)/Hyperion or similar systems - Experience with program finance business rhythms (BLCRs/ECRs) - Experience in a Finance and Business Operations competency such as Reporting, Earned Value Management, Contracts Management or Program Finance - Experience in creating, baselining, and managing budget targets - Experience working across organizational boundaries to ensure that program and company goals are achieved. We'll put each as

• . Skills (Desired Skills): list: - Demonstrated Financial and Analytical experience - Familiar with cost structure and flow, Allocations, Rates and Factors - Familiar with Empower and Tableau tools - Experience teaching and mentoring peers - Must possess and execute strong organizational skills, attention to detail, accuracy, and quality of work - Diligent and Proactive approach to problem solving - Excellent verbal and written communication skills and exhibit a proactive, problem solving, cost conscious and company-focused mindset - Experience interacting with Senior LM and Stakeholder Leadership - Employee must be able to effectively handle and execute multiple tasks in addition to working special project assignments simultaneously - High degree of interpersonal skills required in interfacing with Senior Leadership, Control Account Managers, Program Management leads, and other Program Finance personnel across multiple sites. We'll list each. Benefits: paragraph: "At Lockheed Martin, we know mission success starts with taking care of our people. Our Total Rewards program is designed to attract top talent, support your well-being, and help you grow—both professionally and personally. The salary range for this position is as listed on the requisition. Please note that the salary information listed is a general guideline only. Lockheed Martin considers factors such as (but not limited to) scope and responsibilities of the position, candidate's work experience, education/ training, key skills as well as market(work location) and business considerations when extending an offer. Benefits offered: Medical, Dental, Vision, Flexible work arrangements and schedules (e.g., 4x10), 401(k) match, Paid time off, Holidays, Parental Leave, EAP, Flexible Spending Accounts, Education Assistance, Life Insurance, Short-Term Disability, and Long-Term Disability. Annual short-term and/or long-term incentive compensation programs may be offered depending on the position. Payments under these annual programs are not guaranteed and can vary from year to year and are tied to a range of performance metrics.For (Washington state applicants only) Non-represented full-time employees: accrue at least 10 hours per month of Paid Time Off (PTO) to be used for incidental absences and other reasons; receive at least 90 hours for holidays. Represented full time employees accrue 6.67 hours of Vacation per month; accrue up to 52 hours of sick leave annually; receive at least 96 hours for holidays. PTO, Vacation, sick leave, and holiday hours are prorated based on start date during the calendar year." We need to preserve all substantive information. That's a lot. We'll put as

  maybe multiple paragraphs but can be one. Pay: paragraph with GeoZones definitions and salary ranges. We'll keep as

  maybe with

  for each GeoZone? The instruction: Use
  • for any list of duties/requirements/benefits. Pay is not a list but could be presented as list. However we can keep as

    with the details. But we could also use

    for each GeoZone as list items. Since it's a list of salary ranges per GeoZone, using
    would be appropriate. However the instruction says use
    • for any list of duties/requirements/benefits. Pay is not explicitly listed but could be considered a list. Safer to use

      for prose. But we need to preserve all info; we can embed the GeoZone definitions inside

      . Might be long but okay. We must not include boilerplate like cookie/navigation/legal/EEO/equal-opportunity/scam-warning. The posting includes some legal-ish text about salary guideline etc. That's not boilerplate? It's part of the posting. We should keep it as it's substantive? It's about salary guideline. It's not EEO. We'll keep. Now produce HTML fragment:

      About the role

      ...

      Responsibilities

      • ...
      ...

      Requirements

      • ...
      ...

      Skills

      • ...
      ...

      Benefits

      ...

      Pay

      ...

      Make sure no extra whitespace? It's fine. Now craft the content precisely. About the role paragraph: combine the first two sentences? Let's copy: "As the GRS F‑35 Labor‑Sustainment Lead/Subject‑Matter Expert supporting Global Readiness Solution (GRS), you will serve as the primary labor sustainment lead. This high-impact role plays a critical part in shaping GRS strategies, guiding financial execution, and driving business performance across LMLS GRS programs. You will provide day‑to‑day leadership to GRS Cost Integrators (CIs) and Control Account Managers (CAMs) across the entire F‑35 sustainment portfolio. Drive the monthly business tempo: coordinate schedule, data collection, and reporting for all sustainment control accounts. Perform comprehensive financial analysis, including managing control accounts budgets, estimates-at-complete (EACs), and forecasting activities. Lead/support CAMs with variance analysis, trend identification, and risk-and-opportunity assessments; recommend corrective actions. Prepare and present concise financial briefings for senior leadership, highlighting key performance indicators and strategic implications. Partners with program managers, engineers, and business management teams to align financial plans with technical and schedule requirements. This role offers direct exposure to senior leadership, making it an excellent opportunity for a finance professional seeking both strategic influence and hands-on ownership." That's all responsibilities actually. But we split. Maybe About the role: first two sentences? But we need to avoid duplication. Could put About the role as summary: "As the GRS F‑35 Labor