Corporate FP&A Analyst

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (or Basic Qualifications), maybe Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. The posting includes "About The Role" paragraph, then "Key Responsibilities" list, then "Basic Qualifications" with subparts: Education & Experience, Technical & Functional Skills & Expertise. Also location info, Additional Compensation, Benefits, etc. We need to decide which sections to include. We must not repeat job title as heading. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to preserve all substantive info, not invent or summarize away detail. Remove boilerplate like EEO, etc. Also remove duplicated lines, navigation, cookie, legal, application instructions. The posting includes "We are KBR" etc. That's generic company description; we need to preserve substantive info? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The company description may be considered substantive? It's about KBR, but not directly about the role. Might be considered boilerplate? It's not navigation/legal/EEO, but it's generic marketing. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description is not explicitly listed to remove, but we might keep it? However typical job posting reformatting often includes a brief "About the company" but not required. The instruction says "Prefer a few substantive sections over many thin ones." Could include an "About KBR" section? Not in allowed headings list. Allowed headings are only those listed. So we should not create extra headings beyond those. So we likely ignore the generic company description unless we can fit it into a section like "About the role"? No, that's about role. The company description could be omitted as not required. The instruction says preserve ALL substantive information; but if we omit company description, are we losing substantive info? It's about the company, not the role. Might be considered not essential for the job posting? However they said "Preserve ALL substantive information; do NOT invent or summarize away detail." That suggests we should keep everything that is not boilerplate. The company description is not boilerplate per se, but it's generic marketing. However it's still substantive info about the employer. But we have no heading for it; we could put it in a

before the first heading? The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. It didn't forbid having stray paragraphs before headings. So we could include a

with the company description. Then headings for sections. We need to decide which sections to include based on content. We have: - About The Role: paragraph(s). We'll make

About the role

then

with that paragraph. - Key Responsibilities: list. We'll make

Responsibilities

then

• each. - Basic Qualifications: includes Education & Experience and Technical & Functional Skills & Expertise. Could be split into Requirements and Skills sections. The allowed headings: Requirements, Qualifications, Skills. We need to decide. We have Education & Experience (Bachelor's degree, 5+ years). That's qualifications. Then Technical & Functional Skills & Expertise: list of skills. That could be Skills. We could also have a Requirements section for education/experience, and Skills section for the skill list. We also have Location info, Additional Compensation, Benefits. Benefits we have a section. Pay? Not specific salary; only "Additional Compensation: KBR may offer bonuses, commissions, or other forms of compensation..." That's vague but mentions possible bonuses etc. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits is stated: "Benefits: KBR offers a selection of competitive lifestyle benefits which could include a 401K plan with company match, medical, dental, vision, life insurance, AD&D, flexible spending account, disability, paid time off, or flexible work schedule." So we should include Benefits section. Pay: Not specific salary; only mention of additional compensation forms. The instruction says never create Pay section unless posting actually states them. It does mention "Additional Compensation: KBR may offer bonuses, commissions, or other forms of compensation..." That's not a specific pay range, but it's about compensation. Could we treat that as Pay? The heading "Pay" is allowed. The posting does mention compensation, albeit not specific numbers. Is that enough to include Pay section? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state additional compensation, so we could include Pay section with that info. However it's vague; but we must preserve all substantive info, not invent or summarize away detail. So we can include Pay section with that paragraph. Schedule: The posting mentions flexible working arrangements, hybrid, remote, virtual delivery. That's schedule info. So we can include Schedule section. Location: Not a heading allowed; we could incorporate into a paragraph maybe under About the role? Or we could add a

  after headings. But we should not create a heading for location. We'll just include location info in a

  maybe after About the role or as part of Benefits? Better to add a

  with location info. We also have "Additional Compensation" paragraph separate from Benefits. We'll put that under Pay. We also have "Belong, Connect and Grow at KBR" etc. That's more company culture; could be considered boilerplate? Not EEO but still generic. Might be okay to keep as a

  before headings? But we already have company description earlier. Might be redundant. We could keep it as a

  after the company description. However to keep sections few, maybe we combine them into an introductory paragraph. But we must not repeat job title as heading. Already not. We must not put Job ID/requisition numbers as headings; we have R2126807 at end; we should drop it. We must remove duplicated lines: there may be none. Now construct HTML. We'll start with an introductory

  containing the company description paragraphs (the "We are KBR" and "We are Finance" maybe). Then location paragraph? Could combine. Better: Intro

  with the two paragraphs: "We are KBR ..." and "We are Finance ...". Then location

  . Then headings. Let's extract the exact text. Company description: "We are KBR When you become part of our KBR team, your opportunities are endless. Through internal collaboration, and with our partners and customers, we’re defining tomorrow’s challenges, then providing the innovative solutions to overcome those challenges, always maintaining our commitment to Zero Harm and our Sustainability Platform. Working with us means being rewarded for your contributions. In addition to competitive benefits and professional development, our people are empowered to use all their potential, creating meaningful change for themselves and our clients. We attract the best minds in the world because our expertise thrives on creativity, resourcefulness and collaboration. That is how we supply our clients with cutting-edge solutions. As the needs of the world change, we’re ready to respond and guide the way forward with strategic, sustainable, and technological advancements grounded in more than a century of practical application and execution." Then "We are Finance We are strategic partners to the business, providing financial leadership and insight that drives disciplined growth and long-term value creation. We operate across global markets, navigating complex regulatory environments and partnering cross-functionally to deliver practical, data-driven solutions. Our agility, commercial acumen, and commitment to operational excellence enable us to support the business at every stage of its evolution." We'll keep them as separate sentences but combine into one

  maybe. Location paragraph: "Location: The ideal candidate will be located in the Houston, TX or greater Washington D.C.-Baltimore area. While KBR strives to maintain a global, flexible, diverse, and sustainable work environment for our people, we currently offer flexible working arrangements, including hybrid, remote working, and virtual delivery to help reinforce and strengthen our strong commitment to becoming a more socially sustainable company, allowing us to provide greater work-life balance and flexibility." We could split location and schedule but schedule section will cover flexible arrangements. However location includes mention of flexible arrangements; we could keep location paragraph just about location, and schedule paragraph about flexible arrangements. But the text mixes both. We could separate: location sentence: "Location: The ideal candidate will be located in the Houston, TX or greater Washington D.C.-Baltimore area." Then schedule sentence: "While KBR strives to maintain a global, flexible, diverse, and sustainable work environment for our people, we currently offer flexible working arrangements, including hybrid, remote working, and virtual delivery to help reinforce and strengthen our strong commitment to becoming a more socially sustainable company, allowing us to provide greater work-life balance and flexibility." We'll make two

  s: one for location, one for schedule (though schedule section will also have that). To avoid duplication, maybe put location in a

  before headings, and schedule section will contain the flexible arrangements text. Now sections: About the role: paragraph(s) from "About The Role". Let's extract: "About The Role As a Corporate FP&A Analyst, you will support the company’s financial planning, reporting, and analytical activities, helping to deliver insights that drive business performance and decision-making. As part of the Corporate FP&A team, you will work closely with finance and business partners to support planning cycles, enhance reporting capabilities, and contribute to process improvement initiatives. This role will also serve as a resource across the broader finance function (e.g, Accounting, Treasury, Tax, Audit), driving transformation initiatives through the application of automation, AI, and system integrations to improve efficiency, scalability, and overall effectiveness." We'll put that in

  . Responsibilities: list items from "Key Responsibilities". Let's list them exactly: - Support annual budgeting, long-range planning, and periodic forecasting processes - Prepare financial models, variance analyses, and management reporting packages - Analyze financial performance and provide insights on trends, risks, and opportunities - Assist in developing and maintaining KPIs, dashboards, and reporting tools - Contribute to the design and improvement of internal financial reporting - Deliver timely, accurate, and actionable analysis to finance leadership and business partners - Support ad hoc financial analysis and business decision-making, leveraging advanced tools and automation where applicable - Identify opportunities to improve processes, enhance efficiency, and increase automation - Act as a resource across the finance function to identify and develop automation solutions, including Robotic Process Automation (RPA), AI-enabled tools, and system-to-system integrations - Partner with Finance and IT teams to design and implement smarter, scalable solutions that improve efficiency, data flow, and overall effectiveness - Evaluate existing workflows and drive the adoption of advanced technologies to streamline reporting, forecasting, and data management processes - Assist with implementation and enhancement of financial systems and reporting tools - Collaborate with finance and business stakeholders across the organization We'll make

  • each. Requirements: Education & Experience: "Bachelor’s degree in Finance, Accounting, Economics, Data Analytics, or a related field required" and "5+ years of experience in FP&A, corporate finance, accounting, or a related analytical role". We'll put in

    maybe as a list? Could be

    but not required. We'll just put in

    . Skills: Technical & Functional Skills & Expertise list: - Strong analytical and problem-solving skills with high attention to detail - Solid understanding of financial statements, budgeting, and forecasting processes - Advanced proficiency in Microsoft Excel; strong working knowledge of Microsoft Office suite - Experience with financial planning systems and ERP platforms (e.g., Oracle EPM, Hyperion, SAP, or similar) preferred - Experience or exposure to RPA tools, AI-driven solutions, or automation technologies within finance functions preferred - Understanding of system integrations and data flow optimization across financial platforms is a plus