Finance Analyst (Hybrid)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include metadata like Job ID, etc. Must remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info. We need to parse the posting. Key sections: - About the role: The introductory paragraph about RTX, mission, etc. Could be considered "About the role". The posting includes: "Are you ready to explore the world of aerospace and defense? Do you want to learn from and collaborate with some of the greatest minds in the industry? At RTX, our internships, co-ops and full-time careers provide an exceptional foundation to work on complex problems, advance your skills and create a safer, more connected world. Discover opportunities to make a difference at RTX. At RTX, the world's largest aerospace and defense company, 185,000 great minds are united by purpose and inspired to make a difference solving the world’s most complex problems. With our three market leading businesses, world-class operations and investments in research and development, we offer capabilities and opportunity no one else can. Together, we push the boundaries of known science and find new ways to connect and protect our world. Raytheon brings the strength of more than 100 years of experience and renowned engineering expertise to meet the needs of today’s mission and stay ahead of tomorrow’s threat. We deliver solutions that help our nation and allies defend freedoms and deter aggression, creating a safer, more secure world. Join us and help shape the future of aerospace and defense." That's about the company, could be "About the role". We'll include as

. - Responsibilities: The "What You Will Do" bullet list: Prepare standard financial reports and metrics using provided tools and guidance; Extract data from SAP, Analysis for Office, and related systems; Support reconciliations, variance explanations, and routine finance task; Perform data validation in support of month‑end, quarter‑end, and year‑end cycles; Assist with creation and maintenance of spreadsheets, charts, and presentations. We need to format as

• . - Requirements: The posting includes "U.S. Citizen, U.S. Person, or Immigration Status Requirements: U.S. citizenship is required, as only U.S. citizens are authorized to access information under this program/contract." Also "Security Clearance Type: None/Not Required" and "Security Clearance Status: Not Required". Also "Position Role Type: Hybrid". Also location info maybe not needed. Also "Date Posted" etc. We need to include substantive requirements: U.S. citizenship required. Hybrid role (maybe schedule). But schedule section separate. We'll include citizenship requirement under Requirements. Also maybe "Hybrid" is schedule? Actually schedule is about work arrangement; but we have a Schedule section for schedule details. The posting says "Hybrid: Employees who are working in Hybrid roles will work regularly both onsite and offsite. Ratio of time working onsite will be determined in partnership with your leader." That's schedule info. So we can put that under Schedule. - Qualifications: "Qualifications You Must Have Bachelor’s degree in Finance, Accounting, Economics, Math, Business, or relevant field and obtained by start date. Knowledge of Microsoft Office (Excel, PowerPoint, Word) Experience may be obtained through on-the-job experience, research, coursework, or projects." Also "Qualifications We Prefer Project exposure to finance or analytics Experience creating basic presentations or financial visuals Strong math and spreadsheet skills". So we can combine into Qualifications section with required and preferred. - Skills: Could be extracted from qualifications: Microsoft Office, Excel, PowerPoint, Word; strong math and spreadsheet skills; project exposure to finance or analytics; creating basic presentations or financial visuals. Might be separate Skills section. But we could also incorporate into Qualifications. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Qualifications and Skills into one Qualifications section. But we have separate headings allowed. We need to decide. We have to include sections only when posting has real specific content. We have content for About the role, Responsibilities, Requirements (citizenship), Qualifications (degree, MS Office, etc), Benefits (they list benefits), Pay (salary range), Schedule (Hybrid description). So we can include all those sections. We must not include placeholder like "commensurate with experience". Not present. We must not include duplicated lines. Ensure we capture all substantive info. Let's extract details: About the role: The paragraph(s) about RTX mission etc. We'll combine into one

  maybe multiple sentences. Responsibilities: list as above. Requirements: U.S. citizenship required. Also maybe "U.S. Citizen, U.S. Person, or Immigration Status Requirements". We'll phrase: "U.S. citizenship is required (only U.S. citizens authorized to access information under this program/contract)." Also maybe mention that security clearance not required? That's not a requirement but could be included. However it's not a requirement; it's a statement that none required. Could be included but it's not a requirement. Might be okay to include under Requirements as "No security clearance required." But it's not a requirement; it's a condition. I'd include it as part of Requirements: "No security clearance required." But the instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should include that detail. So Requirements: U.S. citizenship required; No security clearance required. Qualifications: Required: Bachelor’s degree in Finance, Accounting, Economics, Math, Business, or relevant field obtained by start date. Knowledge of Microsoft Office (Excel, PowerPoint, Word). Experience may be obtained through on-the-job experience, research, coursework, or projects. Preferred: Project exposure to finance or analytics; Experience creating basic presentations or financial visuals; Strong math and spreadsheet skills. We could list required and preferred as separate

  maybe with headings? But we only allowed
  • for any list of duties/requirements/benefits. Could embed headings inside

    ? Probably better to just list all qualifications as

    • items, maybe marking preferred. But we must not invent headings inside list. Could just list them as items. Benefits: List: medical, dental, vision, life insurance, short-term disability, long-term disability, 401(k) match, flexible spending accounts, flexible work schedules, employee assistance program, Employee Scholar Program, parental leave, paid time off, holidays. Also mention that specific benefits depend on business unit and collective bargaining. Also mention eligibility for annual short-term and/or long-term incentive compensation programs depending on level and collective bargaining; payments not guaranteed. We'll include those as list items. Pay: Salary range: 57,200 USD - 108,800 USD. Also note that it's a good faith estimate representative of all experience levels; factors considered. We'll include that as

      . Schedule: Hybrid description: Employees work regularly both onsite and offsite; ratio of time onsite determined in partnership with leader. Also mention that as part of commitment to maintaining a secure hiring process, candidates may be asked to attend select steps of interview process in-person at office locations regardless of role designation. That's more about interview process, not schedule. Might be considered schedule? It's about interview. Could be omitted as not schedule. But it's substantive. However we have no section for interview process. Could we include under Schedule? Might be stretching. Better to maybe include under Requirements? Not really. Could we create a separate section? Not allowed headings beyond the list. The instruction: Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings. So we cannot add a custom heading for interview process. We could incorporate that info into Schedule as part of hybrid description? It's not exactly schedule but maybe we can add as a note. However we must not invent or summarize away detail. If we put it under Schedule, we are not inventing, we are placing it under a heading that may not be perfectly accurate but it's allowed headings. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can put interview process under Schedule if we consider it schedule-related? Might be questionable but it's still specific content. However the schedule section is meant for work schedule details. Adding interview process might be misleading but not invented. The instruction does not forbid placing unrelated content under a heading as long as the heading exists and we have real content for that heading. The heading Schedule expects schedule content; we have schedule content (Hybrid). Adding extra content about interview process may be considered filler? Not exactly filler but not schedule. Safer to omit interview process details, as they are not strictly schedule. The instruction says preserve ALL substantive information; we cannot omit substantive info. So we need to include it somewhere. If we cannot create a new heading, we must place it under an existing heading where it fits logically. Perhaps under Requirements? Not really. Could be under About the role? Not really. Could be under Qualifications? No. Could be under Benefits? No. Could be under Pay? No. Could be under Responsibilities? No. Maybe we can treat it as part of Schedule because it's about work arrangement (onsite/offsite) and interview process also about onsite attendance. It's a stretch but maybe acceptable. Alternatively, we could create a section "Schedule" and include both hybrid work description and interview process note. That would be specific content for Schedule (the hybrid work) plus extra note. It's not filler; it's real info. So we can include. Thus Schedule section will contain: Hybrid work description; plus note about interview process possibly requiring in-person attendance. Now we need to output HTML fragment only, no /, no markdown fences. We'll produce:

      About the role

      ...

      Responsibilities

      • ...
      ...

      Requirements

      • U.S. citizenship is required (only U.S. citizens authorized to access information under this program/contract).
      • No security clearance required.

      Qualifications

      • Bachelor’s degree in Finance, Accounting, Economics, Math, Business, or relevant field obtained by start date.
      • Knowledge of Microsoft Office (Excel, PowerPoint, Word).
      • Experience may be obtained through on-the-job experience, research, coursework, or projects.
      • Preferred: Project exposure to finance or analytics.
      • Preferred: Experience creating basic presentations or financial visuals.
      • Preferred: Strong math and spreadsheet skills.
      But we used "Preferred:" inside li; that's okay. Alternatively we could separate required and preferred with headings but not allowed. We could also add a

      for qualifications prose but we have list. Now Benefits:

      Benefits

      • Medical insurance
      • Dental insurance
      • Vision insurance
      • Life insurance
      • Short-term disability
      • Long-term disability
      • 401(k) match
      • Flexible spending accounts
      • Flexible work schedules
      • Employee assistance program
      • Employee Scholar Program
      • Parental leave
      • Paid time off
      • Holidays
      • Eligibility for annual short-term and/or long-term incentive compensation programs (dependent on position level and collective‑bargaining coverage; payments not guaranteed)
      Pay:

      Pay

      The salary range for this role is 57,200 USD – 108,800 USD. This