Manager, Finance Analytics
Meriton · Dallas, TX · 1 mo ago
HybridFinanceInternship
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. No job title heading. No metadata like Job ID. Remove boilerplate, EEO, etc. Keep substantive info.
We need to parse the posting.
Content:
- Intro paragraph: "Meriton is a national team of experts driving HVAC innovation through a network of high-performing companies. From strategy and support to systems and solutions, we work behind the scenes to strengthen operations and build value—for our partners and our people.If you’re looking to make an impact, we’re glad you’re here. At Meriton, you’ll join a team that believes in big ideas, doing great work, and building careers that matter—every step of the way."
That's about the company/role. Could be "About the role" or "About Meriton". We'll use "About the role" heading.
- Then description of role: "The Manager, Finance Analytics is a key member of the FP&A team responsible for developing financial and operational insights, standardizing performance reporting, and improving the scalability of FP&A across the organization. Reporting to the VP, Finance, this role partners closely with FP&A leadership and operating company finance teams to analyze project performance, bookings and backlog, margins, operational KPIs, and other key business drivers. The ideal candidate combines strong financial acumen with data analytics and business intelligence capabilities, translating complex data into actionable insights for leadership. This person is analytically rigorous, comfortable working across finance and operational teams, and motivated to build scalable reporting capabilities that strengthen decision-making enterprise-wide."
That's more about role responsibilities. Could go under Responsibilities.
- Then "Essential Duties and Responsibilities:" with subheadings: Business Intelligence & Reporting, Project & Margin Analytics, Customer & Vendor Analytics, Performance Benchmarking & Cross-Functional Partnership, Other Duties.
We need to turn these into
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No metadata like Job ID. Remove boilerplate, EEO, etc. Keep substantive info.
We need to parse the posting.
Content:
- Intro paragraph: "Meriton is a national team of experts driving HVAC innovation through a network of high-performing companies. From strategy and support to systems and solutions, we work behind the scenes to strengthen operations and build value—for our partners and our people.If you’re looking to make an impact, we’re glad you’re here. At Meriton, you’ll join a team that believes in big ideas, doing great work, and building careers that matter—every step of the way."
That's about the company/role. Could be "About the role" or "About Meriton". We'll use "About the role" heading.
- Then description of role: "The Manager, Finance Analytics is a key member of the FP&A team responsible for developing financial and operational insights, standardizing performance reporting, and improving the scalability of FP&A across the organization. Reporting to the VP, Finance, this role partners closely with FP&A leadership and operating company finance teams to analyze project performance, bookings and backlog, margins, operational KPIs, and other key business drivers. The ideal candidate combines strong financial acumen with data analytics and business intelligence capabilities, translating complex data into actionable insights for leadership. This person is analytically rigorous, comfortable working across finance and operational teams, and motivated to build scalable reporting capabilities that strengthen decision-making enterprise-wide."
That's more about role responsibilities. Could go under Responsibilities.
- Then "Essential Duties and Responsibilities:" with subheadings: Business Intelligence & Reporting, Project & Margin Analytics, Customer & Vendor Analytics, Performance Benchmarking & Cross-Functional Partnership, Other Duties.
We need to turn these into - lists. Probably each bullet is a duty.
Let's extract bullet points:
Under Business Intelligence & Reporting:
- Own the development of scalable dashboards and analytical tools that integrate financial, project, customer, labor, bookings, backlog, and operational data across the organization.
- Drive the design and standardization of consistent KPIs across operating companies, including gross margin, project margin, service utilization, labor productivity, backlog conversion, bookings, and pricing.
- Champion the automation of recurring FP&A reporting to reduce manual effort and expand Finance's capacity for analysis and business partnership.
Project & Margin Analytics:
- Own the analysis of project-level financial and operational data to surface trends in profitability, margin erosion, execution, and customer/project concentration.
- Drive deep-dive analyses of bookings and backlog by end market, customer, project type, geography, and operating company to build leading indicators of future revenue and margin performance.
Customer & Vendor Analytics:
- Own the analysis of customer and vendor data to identify concentration, business mix, purchasing trends, cost exposure, and emerging risks and opportunities.
Performance Benchmarking & Cross-Functional Partnership:
- Develop scorecards and benchmarking across operating companies to identify performance outliers, best practices, and opportunities for operational improvement.
- Partner with operating company finance teams, operations, and IT/data teams to ensure data quality, reporting consistency, and adoption of analytical tools.
Other Duties:
- Regular, consistent and necessary to meet the needs of the business
- Assists the leadership team and other team members with various research projects and/or special projects
- Performs other duties and responsibilities as assigned
- Must conduct self in an ethical, legal, and responsible manner at all times
- Must adhere to the policies, principles, and guidance within the Employee Handbook and Code of Conduct
We need to decide if we include "Other Duties" as part of Responsibilities or separate. Probably include under Responsibilities as a list.
Now Education/Experience section:
Required:
- Bachelor's degree in Finance, Accounting, Economics, Business Analytics, Data Analytics, or a related field
- 7+ years of experience in FP&A, finance analytics, business analytics, strategic finance, or a related role
- Strong financial acumen with experience analyzing P&L, margins, profitability, and operational performance
- Strong proficiency with Power BI, Tableau, or comparable business intelligence tools
- Advanced Excel and financial modeling skills
- Demonstrated ability to analyze large financial and operational datasets and translate findings into actionable business insights
- Strong communication skills with the ability to present complex analysis clearly to finance, operational, and executive audiences
Preferred:
- SQL experience and ability to independently query and manipulate large datasets
- Experience automating financial reporting and analytical processes
- Must be proficient in the Microsoft Office Suite, including Outlook, Excel, PowerPoint and Word
We can separate into Requirements (education/experience) and Skills (tools). The instruction: Use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where.
"Education/Experience" could be Requirements or Qualifications. Usually Requirements = education/experience. Qualifications could be similar. But we have both Required and Preferred. Could put Required under Requirements, Preferred under Qualifications or Skills? However Skills heading is for technical skills. Let's map:
- Requirements: Education and experience (Bachelor's degree, 7+ years, strong financial acumen, etc.) maybe also include strong communication skills? That's a skill.
- Qualifications: Could be the Preferred items? Or we could combine Required and Preferred under Requirements and Qualifications respectively.
- Skills: Technical skills: Power BI, Tableau, Advanced Excel, financial modeling, SQL, Microsoft Office Suite, ability to analyze large datasets, automation experience.
We need to avoid filler like "commensurate with experience". Not present.
We also have Work Environment and Physical Demands sections. Those could go under maybe "Work Environment" but not in allowed headings list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should not create extra headings. So we need to decide where to place Work Environment and Physical Demands info. The instruction: "Prefer a few substantive sections over many thin ones." We could incorporate Work Environment and Physical Demands into About the role or Responsibilities? Probably not appropriate. But we must preserve ALL substantive information; we cannot omit it. However we cannot create headings not listed. We could embed that info in a
under an existing heading like About the role or Responsibilities. 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 to use those for section headings. It might be okay to add other headings if needed, but better to stick to those. However we need to preserve info; we could put Work Environment and Physical Demands under a
within About the role or Responsibilities. But that might be odd.
Alternatively, we could create a section "Work Environment" as a heading, but not in the list. The instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. But later: "IMPORTANT: 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 create any heading as long as it's substantive. But they gave examples; we can still use others if needed. However to be safe, we could incorporate Work Environment and Physical Demands into a "Work Environment" heading (h3). That seems reasonable.
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 they gave examples. I'd assume we can use other headings if needed, but better to stick to those. However we have no Benefits, Pay, Schedule info. The posting does not mention benefits, pay, or schedule. So we should not create those sections. So we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Work Environment (maybe). But we need to decide if we need Qualifications separate from Requirements. The posting has Required and Preferred. We could treat Required as Requirements, Preferred as Qualifications. That seems logical.
Skills: we can list technical skills: Power BI, Tableau, Advanced Excel, financial modeling, SQL, Microsoft Office Suite, ability to analyze large datasets, automation experience.
Now let's extract content for each.
About the role: combine intro paragraph and role description.
Paragraph: "Meriton is a national team of experts driving HVAC innovation through a network of high-performing companies. From strategy and support to systems and solutions, we work behind the scenes to strengthen operations and build value—for our partners and our people. If you’re looking to make an impact, we’re glad you’re here. At Meriton, you’ll join a team that believes in big ideas, doing great work, and building careers that matter—every step of the way."
Then role description: "The Manager, Finance Analytics is a key member of the FP&A team responsible for developing financial and operational insights, standardizing performance reporting, and improving the scalability of FP&A across the organization. Reporting to the VP, Finance, this role partners closely with FP&A leadership and operating company finance teams to analyze project performance, bookings and backlog, margins, operational KPIs, and other key business drivers. The ideal candidate combines strong financial acumen with data analytics and business intelligence capabilities, translating complex data into actionable insights for leadership. This person is analytically rigorous, comfortable working across finance and operational teams, and motivated to build scalable reporting capabilities that strengthen decision-making enterprise-wide."
We can combine into one or two
under About the role.
Responsibilities: list of duties from Essential Duties and Responsibilities.
We'll create a
with - for each bullet. Could group by subheadings? Not required but could keep as flat list. However we might want to keep subheadings for readability but not required. The instruction: Use
- for any list of duties/requirements/benefits. So we can just list all duties as
- . Might be long but okay.
We need to include all duties:
- Own the development of scalable dashboards and analytical tools that integrate financial, project, customer, labor, bookings, backlog, and operational data across the organization.
- Drive the design and standardization of consistent KPIs across operating companies, including gross margin, project margin, service utilization, labor productivity, backlog conversion, bookings, and pricing.
- Champion the automation of recurring FP&A reporting to reduce manual effort and expand Finance's capacity for analysis and business partnership.
- Own the analysis of project-level financial and operational data to surface trends in profitability, margin erosion, execution, and customer/project concentration.
- Drive deep-dive analyses of bookings and backlog by end market, customer, project type, geography, and operating company to build leading indicators of future revenue and margin performance.
- Own the analysis of customer and vendor data to identify concentration, business mix, purchasing trends, cost exposure, and emerging risks and opportunities.
- Develop scorecards and benchmarking across operating companies to identify performance outliers, best practices, and opportunities for operational improvement.
- Partner with operating company finance teams, operations, and IT/data teams to ensure data quality, reporting consistency, and adoption of analytical tools.
- Regular, consistent and necessary to meet the needs of the business
- Assists the leadership team and other team members with various research projects and/or special projects
- Performs other duties and responsibilities as assigned
- Must conduct self in an ethical, legal, and responsible manner at all times
- Must adhere to the policies, principles, and guidance within the Employee Handbook and Code of Conduct
Now Requirements: Required education/experience.
List:
- Bachelor's degree in Finance, Accounting, Economics, Business Analytics, Data Analytics, or a related field
- 7+ years of experience in FP&A, finance analytics, business
under an existing heading like About the role or Responsibilities. 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 to use those for section headings. It might be okay to add other headings if needed, but better to stick to those. However we need to preserve info; we could put Work Environment and Physical Demands under a
within About the role or Responsibilities. But that might be odd. Alternatively, we could create a section "Work Environment" as a heading, but not in the list. The instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. But later: "IMPORTANT: 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 create any heading as long as it's substantive. But they gave examples; we can still use others if needed. However to be safe, we could incorporate Work Environment and Physical Demands into a "Work Environment" heading (h3). That seems reasonable.
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 they gave examples. I'd assume we can use other headings if needed, but better to stick to those. However we have no Benefits, Pay, Schedule info. The posting does not mention benefits, pay, or schedule. So we should not create those sections. So we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Work Environment (maybe). But we need to decide if we need Qualifications separate from Requirements. The posting has Required and Preferred. We could treat Required as Requirements, Preferred as Qualifications. That seems logical.
Skills: we can list technical skills: Power BI, Tableau, Advanced Excel, financial modeling, SQL, Microsoft Office Suite, ability to analyze large datasets, automation experience.
Now let's extract content for each.
About the role: combine intro paragraph and role description.
Paragraph: "Meriton is a national team of experts driving HVAC innovation through a network of high-performing companies. From strategy and support to systems and solutions, we work behind the scenes to strengthen operations and build value—for our partners and our people. If you’re looking to make an impact, we’re glad you’re here. At Meriton, you’ll join a team that believes in big ideas, doing great work, and building careers that matter—every step of the way."
Then role description: "The Manager, Finance Analytics is a key member of the FP&A team responsible for developing financial and operational insights, standardizing performance reporting, and improving the scalability of FP&A across the organization. Reporting to the VP, Finance, this role partners closely with FP&A leadership and operating company finance teams to analyze project performance, bookings and backlog, margins, operational KPIs, and other key business drivers. The ideal candidate combines strong financial acumen with data analytics and business intelligence capabilities, translating complex data into actionable insights for leadership. This person is analytically rigorous, comfortable working across finance and operational teams, and motivated to build scalable reporting capabilities that strengthen decision-making enterprise-wide."
We can combine into one or two
under About the role. Responsibilities: list of duties from Essential Duties and Responsibilities. We'll create a
- with
- for each bullet. Could group by subheadings? Not required but could keep as flat list. However we might want to keep subheadings for readability but not required. The instruction: Use
- for any list of duties/requirements/benefits. So we can just list all duties as
- . Might be long but okay. We need to include all duties: - Own the development of scalable dashboards and analytical tools that integrate financial, project, customer, labor, bookings, backlog, and operational data across the organization. - Drive the design and standardization of consistent KPIs across operating companies, including gross margin, project margin, service utilization, labor productivity, backlog conversion, bookings, and pricing. - Champion the automation of recurring FP&A reporting to reduce manual effort and expand Finance's capacity for analysis and business partnership. - Own the analysis of project-level financial and operational data to surface trends in profitability, margin erosion, execution, and customer/project concentration. - Drive deep-dive analyses of bookings and backlog by end market, customer, project type, geography, and operating company to build leading indicators of future revenue and margin performance. - Own the analysis of customer and vendor data to identify concentration, business mix, purchasing trends, cost exposure, and emerging risks and opportunities. - Develop scorecards and benchmarking across operating companies to identify performance outliers, best practices, and opportunities for operational improvement. - Partner with operating company finance teams, operations, and IT/data teams to ensure data quality, reporting consistency, and adoption of analytical tools. - Regular, consistent and necessary to meet the needs of the business - Assists the leadership team and other team members with various research projects and/or special projects - Performs other duties and responsibilities as assigned - Must conduct self in an ethical, legal, and responsible manner at all times - Must adhere to the policies, principles, and guidance within the Employee Handbook and Code of Conduct Now Requirements: Required education/experience. List: - Bachelor's degree in Finance, Accounting, Economics, Business Analytics, Data Analytics, or a related field - 7+ years of experience in FP&A, finance analytics, business