FP&A Manager
Pinnacle Fertility · Scottsdale, AZ · 3 wk ago
On-siteFinanceFull-time
We need to output HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: About the Role (we can use About the role). Responsibilities (Key Responsibilities). Requirements (Education, Experience). Qualifications? Might be overlapping; but we have "Position Requirements" includes Education, Experience, Technical Skills, Core Skills & Competencies. Could map to Requirements and Qualifications and Skills. The instruction: Use headings for those specific labels. We need to decide which sections to include based on content.
We have content for:
- About the Role: yes.
- Responsibilities: yes (Key Responsibilities with subpoints).
- Requirements: Education, Experience (maybe also Technical Skills? but they'd go under Skills). We'll put Education and Experience under Requirements.
- Qualifications: maybe we can include "Preferred qualifications" like Master's preferred, etc. The posting includes "Master of Science in Mathematical Finance & Financial Technology or Financial Engineering preferred." That's a qualification. Also "Experience with budgeting, forecasting, financial modeling, and financial performance analysis preferred." etc. Could be under Qualifications.
- Skills: Technical Skills (Python, SQL, Excel, PowerPoint) and Core Skills & Competencies.
- Benefits: Yes, there is a "Compensation & Benefits" section describing benefits.
- Pay: Not specified (no salary). So we should NOT include Pay section.
- Schedule: Not specified (full-time, onsite). Could we include Schedule? The posting says "This is a full-time, salaried, onsite position based in Scottsdale, Arizona." That indicates schedule: full-time, onsite. That's specific enough? It says full-time, onsite. That is schedule info. The rule: include Schedule section only if posting actually states them. It does state full-time, onsite. So we can include Schedule with that info.
We must not include boilerplate like EEO etc. Remove Diversity & Inclusivity etc.
We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format as lists.
We need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: About the Role (we can use About the role). Responsibilities (Key Responsibilities). Requirements (Education, Experience). Qualifications? Might be overlapping; but we have "Position Requirements" includes Education, Experience, Technical Skills, Core Skills & Competencies. Could map to Requirements and Qualifications and Skills. The instruction: Use headings for those specific labels. We need to decide which sections to include based on content.
We have content for:
- About the Role: yes.
- Responsibilities: yes (Key Responsibilities with subpoints).
- Requirements: Education, Experience (maybe also Technical Skills? but they'd go under Skills). We'll put Education and Experience under Requirements.
- Qualifications: maybe we can include "Preferred qualifications" like Master's preferred, etc. The posting includes "Master of Science in Mathematical Finance & Financial Technology or Financial Engineering preferred." That's a qualification. Also "Experience with budgeting, forecasting, financial modeling, and financial performance analysis preferred." etc. Could be under Qualifications.
- Skills: Technical Skills (Python, SQL, Excel, PowerPoint) and Core Skills & Competencies.
- Benefits: Yes, there is a "Compensation & Benefits" section describing benefits.
- Pay: Not specified (no salary). So we should NOT include Pay section.
- Schedule: Not specified (full-time, onsite). Could we include Schedule? The posting says "This is a full-time, salaried, onsite position based in Scottsdale, Arizona." That indicates schedule: full-time, onsite. That's specific enough? It says full-time, onsite. That is schedule info. The rule: include Schedule section only if posting actually states them. It does state full-time, onsite. So we can include Schedule with that info.
We must not include boilerplate like EEO etc. Remove Diversity & Inclusivity etc.
We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format as lists.
We need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
About the role
... text ...
Responsibilities
- ... ...
. Now Responsibilities: list under "Key Responsibilities" with subheadings: Financial Planning, Budgeting & Forecasting; Financial Analysis & Business Partnership; Financial Modeling & Data Analytics; Executive, Board & Stakeholder Reporting; Process Improvement. We need to capture each bullet under those subheadings. The posting lists bullet points under each subheading. We'll combine them into a flat list? The instruction: Use
- for any list of duties/requirements/benefits. So we can make a list for responsibilities, each duty as
- . We could also keep subheadings inside
- but better to just list all duties.
Let's extract each duty:
Under Financial Planning, Budgeting & Forecasting:
- Collaborate with department heads and business stakeholders to prepare annual budgets, forecasts, and long-term financial plans.
- Monitor and evaluate financial performance metrics by comparing actual results to budget and forecast.
- Analyze financial performance, trends, and business drivers to identify risks, opportunities, and areas requiring management attention.
- Provide meaningful financial insights and recommendations to management to support business growth and profitability.
- Support leadership in understanding the financial implications of business decisions, initiatives, and investments.
Under Financial Analysis & Business Partnership:
- Conduct ad-hoc financial analysis to support strategic and operational decision-making.
- Partner with department leaders and business stakeholders to understand financial performance and underlying business drivers.
- Evaluate the financial impact of various initiatives and investment opportunities.
- Identify trends and relationships within financial and operational data and translate findings into actionable recommendations.
- Collaborate with Finance, Accounting, and cross-functional teams to ensure financial analysis supports organizational objectives.
- Serve as a trusted financial partner by helping stakeholders connect financial results with operational performance.
Under Financial Modeling & Data Analytics:
- Develop and maintain financial models to support business planning, forecasting, investment opportunities, and strategic decision-making.
- Analyze financial and operational data to identify trends, opportunities, risks, and potential areas for improvement.
- Utilize Python and SQL to perform financial and data analysis and support data-driven decision-making.
- Leverage advanced Excel capabilities to analyze data and develop financial models.
- Develop analytical approaches that improve the accuracy, efficiency, and effectiveness of financial reporting and analysis.
- Support the continued development of data-driven financial analysis and reporting practices within the Finance organization.
Under Executive, Board & Stakeholder Reporting:
- Prepare key financial metrics, analyses, and presentations for senior management, the Board of Directors, and external stakeholders.
- Monitor and communicate financial performance against budget and forecast.
- Develop clear and concise presentations that highlight key financial trends, business drivers, risks, and opportunities.
- Translate complex financial information into actionable insights and recommendations for executive-level audiences.
- Ensure financial reporting and presentations are accurate, timely, and aligned with organizational priorities.
Under Process Improvement:
- Identify process improvement opportunities within the Finance department.
- Contribute to the development and implementation of enhanced financial reporting and analysis practices.
- Identify opportunities to improve reporting efficiency, data quality, accuracy, and accessibility.
- Help improve processes and analytical tools used to support financial planning and decision-making.
- Participate in other finance-related duties and projects as assigned.
Now Requirements: Education and Experience.
Education:
- Bachelor's degree in Accounting or Finance required.
- Master of Science in Mathematical Finance & Financial Technology or Financial Engineering preferred.
Experience:
- 4-5 years of experience in finance and/or accounting required.
- Demonstrated experience performing financial analysis and working with financial data.
- Experience with budgeting, forecasting, financial modeling, and financial performance analysis preferred.
- Experience collaborating with cross-functional teams and business stakeholders preferred.
We could also include Technical Skills under Skills, not Requirements.
Now Qualifications: maybe we can include "Preferred qualifications" like Master's preferred, experience with budgeting etc. But we already have those under Requirements (Education preferred, Experience preferred). Could also include "Ideal candidate combines strong FP&A fundamentals with advanced analytical capabilities and is comfortable leveraging Excel, Python, and SQL to analyze data, identify trends, improve reporting, and support data-driven decision-making." That's more Skills.
We could treat Qualifications as the combination of Education and Experience (both required and preferred). But we already have Requirements heading; maybe we should split: Requirements = required items; Qualifications = preferred items. However the instruction says use headings for those specific labels if there is real specific content. We have content for both required and preferred. We could put required under Requirements, preferred under Qualifications. Let's do that.
Thus:
Requirements
- Bachelor's degree in Accounting or Finance required.
- 4-5 years of experience in finance and/or accounting required.
- Demonstrated experience performing financial analysis and working with financial data.
Qualifications
- Master of Science in Mathematical Finance & Financial Technology or Financial Engineering preferred.
- Experience with budgeting, forecasting, financial modeling, and financial performance analysis preferred.
- Experience collaborating with cross-functional teams and business stakeholders preferred.