Finance - Corporate FP&A Business Analyst, Assistant Vice President

We need to output HTML fragment with sections: About the role? The posting includes Position Summary, Key Responsibilities, Qualifications, Success Measures, Expected annual base salary range, Additional compensation and benefits. Also maybe "About Blackstone" intro but we should not repeat job title. We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. We have content for Responsibilities (Key Responsibilities), Requirements/Qualifications (Qualifications), Benefits (Additional compensation and benefits), Pay (Expected annual base salary range). Also maybe "About the role" could be Position Summary. That is substantive. Also maybe "Success Measures" could be a section but not in prescribed headings; we could incorporate into Responsibilities or Qualifications? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples; we can use those headings if appropriate. We should not create sections like Success Measures unless we map to one of those. Could we treat Success Measures as part of Responsibilities? Probably better to include as a separate section? But the instruction says prefer a few substantive sections over many thin ones. We could combine Success Measures into Responsibilities or Qualifications. However, we have enough sections: About the role (Position Summary), Responsibilities (Key Responsibilities), Requirements (Qualifications), Benefits (Additional compensation and benefits), Pay (Expected annual base salary range). That's five sections. We should not include Schedule (no info). Skills maybe part of Qualifications; we could embed skills within Qualifications. So we will not create a separate Skills section. We need to use

• for any list of duties/requirements/benefits. So for Responsibilities we have bullet points; we need to convert each duty into
• . For Qualifications we have required and preferred; we can list as
  . For Benefits we have list: comprehensive health benefits..., paid time off; life insurance; 401(k) plan; discretionary bonuses; equity and other incentive compensation. We'll list as
  . We need to preserve ALL substantive information; do not invent or summarize away detail. Must not repeat job title as heading. Must not put Job ID/requisition numbers as headings (none present). Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the EEO statement, the accommodation contact, securities license note, application instructions (To submit your application...), etc. Also remove the "Further information is available at www.blackstone.com. Follow @blackstone on LinkedIn, X (Twitter), and Instagram." That's boilerplate? It's not EEO but maybe considered navigation? It's not essential to role; but it's not duplicated lines; but it's not substantive about role. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Further information is available at www.blackstone.com. Follow @blackstone on LinkedIn, X (Twitter), and Instagram." is like navigation/footer; likely should be removed. Also the initial paragraph about Blackstone being world's largest alternative asset manager etc. That's company overview; is that substantive? It's not about the role but maybe considered boilerplate? It's not navigation/legal/EEO; it's company description. Might be considered okay to keep? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Company overview is not those; but it's not directly about the role. However, we might keep it as part of "About the role"? The Position Summary already describes role. The company overview could be considered filler but not prohibited. However, to be safe, we could include a brief About the role section that includes the Position Summary only. The company overview could be omitted as not directly about role. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. The company overview is substantive about Blackstone but not about the role; but it's still part of posting. Might be considered boilerplate? Not sure. I'd keep it maybe as a short paragraph under About the role? But the heading "About the role" expects role description; we could include company overview as part of that? Might be okay. Better to follow the example: they gave headings like About the role, Responsibilities, etc. So we can put Position Summary under About the role. We'll omit the generic Blackstone description. Now we need to format. Let's extract Position Summary: "We are seeking a highly analytical and collaborative Business Analyst to join the Corporate FP&A team. This individual will serve as the primary liaison between Finance and Technology, developing a deep understanding of financial planning, forecasting, reporting, and submission processes while driving the successful delivery of strategic technology initiatives. The role will partner closely with Corporate FP&A stakeholders, Business Unit FP&A teams, data owners, and technology teams to identify process improvement opportunities, gather and document business requirements, coordinate project execution, support user adoption, and ensure technology solutions align with business objectives. This position is ideal for someone who enjoys combining business process expertise, stakeholder management, and project coordination to modernize finance operations through automation, data integration, and digital transformation initiatives." That's the summary. Key Responsibilities bullet points: - Business Process Analysis & Improvement - Develop a comprehensive understanding of Corporate FP&A processes, including: Forecasting and budgeting Financial reporting Management and executive reporting Data submissions and approvals Planning system workflows - Document current-state and future-state processes, identifying opportunities for efficiency, automation, and improved controls. - Analyze business challenges and translate them into actionable process and technology recommendations. - Facilitate working sessions with finance stakeholders to gather requirements and validate solutions. - Requirements Management - Gather, document, and prioritize business requirements. - Ensure requirements are clearly communicated to development teams and aligned with business objectives. - Support solution design reviews and validate that delivered functionality meets business needs. - Support prioritization and management of the Corporate FP&A projects. - Testing & User Adoption - Perform User Acceptance Testing (UAT) activities and create test scenarios. (Note typo "Preform" but we keep as is? Should we correct? Probably keep as posted but we could keep "Perform". The instruction: preserve ALL substantive information; do not invent or summarize away detail. Changing typo could be considered altering? Might be okay to keep as is but we could correct? I'd keep as "Perform" to be correct but that's altering. I'd keep original "Preform". However, it's a typo; preserving it means we keep the typo. I'll keep "Preform". - Partner with end users to validate functionality and document defects or enhancement requests. - Support training, documentation, and rollout activities to drive adoption of new solutions. Qualifications Required: - Bachelor's degree in Finance, Accounting, Economics, Information Systems, Business, or a related field. - 7+ years of experience in: - Business Analysis - FP&A - Finance Transformation - Financial Systems - Project Coordination - Strong understanding of financial planning, forecasting, and reporting processes. - Experience gathering business requirements and translating them into technology solutions. - Excellent communication and stakeholder management skills. - Strong analytical and problem-solving capabilities. - Advanced Excel and PowerPoint skills. Preferred: - Experience supporting FP&A, Accounting, or Corporate Finance functions. - Exposure to planning and reporting platforms such as: - Anaplan - Essbase - Power BI - Sigma - Tableau - Microsoft Power Platform - Knowledge of data governance, hierarchy management, and financial reporting processes. - Familiarity with AI, Copilot, workflow automation, and finance transformation initiatives. Success Measures: we could embed into Responsibilities or Qualifications but maybe better to add a section "Success Measures" but not in allowed headings. Could we treat as part of Responsibilities? Might be okay to add a section "Success Measures" but the instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It might be safer to stick to those headings. So we can incorporate Success Measures into Responsibilities or Qualifications. I'd add them as bullet points under Responsibilities maybe as a separate subsection "Success Measures". But that would be a heading inside Responsibilities, not a top-level heading. Could be okay but might be considered creating a heading not listed. Safer to just incorporate into Responsibilities as additional bullet points: "In the first 12 months, success would include: ..." We'll turn that into a

  under Responsibilities. Pay: Expected annual base salary range: $135,000 - $200,000. Additional note about actual base salary determined by components, location, etc. We'll keep that as prose under Pay. Benefits: Additional compensation and benefits offered in connection with the role consist of comprehensive health benefits, including but not limited to medical, dental, vision, and FSA benefits; paid time off; life insurance; 401(k) plan; and discretionary bonuses. Certain employees may also be eligible for equity and other incentive compensation at Blackstone’s sole discretion. We'll list as
  . Now we need to remove boilerplate: EEO statement, accommodation contact, securities license note, application instructions, company overview, social media follow, further information link. Also remove "The duties and responsibilities described here are not exhaustive..." that's boilerplate; remove. Also remove "Assignments, duties, and responsibilities may be changed at any time..." boilerplate; remove. Also remove "Depending on the position, you may be required to obtain certain securities licenses..." boilerplate; remove. Also remove "Note: The above list is not the exhaustive list..." boilerplate; remove. Also remove "Please speak with your Blackstone Recruiting contact..." boilerplate; remove. Also remove "To submit your application please complete the form below...." boilerplate; remove. Now we need to output only HTML fragment. Let's craft:

  About the role

  We are seeking a highly analytical and collaborative Business Analyst to join the Corporate FP&A team. This individual will serve as the primary liaison between Finance and Technology, developing a deep understanding of financial planning, forecasting, reporting, and submission processes while driving the successful delivery of strategic technology initiatives. The role will partner closely with Corporate FP&A stakeholders, Business Unit FP&A teams, data owners, and technology teams to identify process improvement opportunities, gather and document business requirements, coordinate project execution, support user adoption, and ensure technology solutions align with business objectives. This position is ideal for someone who enjoys combining business process expertise, stakeholder management, and project coordination to modernize finance operations through automation, data integration, and digital transformation initiatives.

  Responsibilities

  • Business Process Analysis & Improvement
    • Develop a comprehensive understanding of Corporate FP&A processes, including:
      • Forecasting and budgeting
      • Financial reporting
      • Management and executive reporting
      • Data submissions and approvals
      • Planning system workflows
    • Document current-state and future-state processes, identifying opportunities for efficiency, automation, and improved controls.
    • Analyze business challenges and translate them into actionable process and technology recommendations.
    • Facilitate working sessions with finance stakeholders to gather requirements and validate solutions.
  • Requirements Management
    • Gather, document, and prioritize business requirements.
    • Ensure requirements are clearly communicated to development teams and aligned with business objectives.
    • Support solution design reviews and validate that delivered functionality meets business needs.