Vice President Finance
Eastside Catholic School · Sammamish, WA · 1 wk ago
On-siteFinance$28.3/hrFull-time
The user wants me to reformat this job posting into clean semantic HTML. Let me analyze the content and structure it according to the rules.
First, I need to identify the sections:
1. About the role / Position Overview (but not the job title as heading)
2. Essential Responsibilities - with sub-sections
3. Qualifications & Experience
The posting has:
- "Who We Are" - this is about the organization, could be "About the Organization" or similar
- "Position Overview" - this is about the role
- "Essential Responsibilities" with multiple sub-sections
- "Qualifications & Experience"
Rules:
- Use for section headings
- Use
for section headings
- Use - for lists
- Use
for prose
- Don't repeat job title as heading
- Don't put Job ID/requisition numbers as headings
- Preserve ALL substantive information
- Remove boilerplate (cookie/navigation/legal/EEO/scam-warning)
- Remove duplicated lines and application instructions
- Include section ONLY when real specific content exists
- No filler/placeholder text
- No Pay/Schedule/Benefits unless stated
- Output ONLY HTML fragment
Looking at the content:
- "Who We Are" - substantive content about the school
- "Position Overview" - substantive description of the role and its specific mandate
- "Essential Responsibilities" - has multiple sub-sections with bullet points
- "Qualifications & Experience" - list of qualifications
The application instructions at the end should be removed (candidates must submit..., applications accepted until..., interviews begin...).
Also note: "This is an in-office position with an anticipated start date of November 30, 2026..." - this could go in a Schedule section? But the rules say only include Schedule if posting actually states them. It does state "in-office position" and "anticipated start date". But Schedule typically means work schedule (hours, days). This is more about work arrangement and start date. Could fold into a short paragraph in Position Overview or a separate small section. But rules say prefer few substantive sections over many thin ones. I'll include it in Position Overview.
Also "The position will provide leadership for the areas outlined above, with the potential for additional departments..." - this is part of responsibilities.
Now, structure:
About the Organization
(for Who We Are)
...
About the Role
(for Position Overview)
...
Responsibilities
- but there are sub-sections. The rules say use for section headings like Responsibilities, Requirements, etc. But here we have sub-sections under Essential Responsibilities. Should I make each sub-section an ? The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So Responsibilities is a section heading. But the content has sub-sections: Budgeting & Strategic Financial Planning, Financial Management, Debt & Risk Mitigation, Team Leadership & Organizational Collaboration, Investment Management, Accounting & Financial Reporting, Payroll & Human Resources Coordination, Tuition Administration & Financial Aid.
These are sub-sections of Responsibilities. I could make them but the rules only mention . However, the rules don't forbid other heading levels, but they say "use for section headings". It might be okay to use for sub-sections. But to be safe, I'll keep them as ? That would make many headings. The example includes "Responsibilities" as a section heading. The sub-sections are part of Responsibilities. I think using for each sub-section is acceptable as they are distinct responsibility areas. The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say you can't have multiple for sub-sections. But "Responsibilities" is listed as an example. However, the content has clear sub-sections with bullet points. I'll make each sub-section an with the sub-section title, and then list the bullet points. That seems most semantic.
Alternatively, I could have one Responsibilities
and then each sub-section as but the rules don't mention . The output is HTML fragment, so using is fine. But the instruction says "use for section headings". It doesn't say "only use ". I'll use for main sections and for sub-sections? But the user might expect only . Let's see: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This suggests that the top-level sections should be . The sub-sections under Responsibilities are not in that list. I think it's better to treat each responsibility area as a separate section with . That would be consistent with "Responsibilities" being a section heading, but here we have multiple responsibility categories. I'll make each a .
But then we have "Qualifications & Experience" as another .
Also "About the Organization" and "About the Role" as .
Let's outline:
About the Organization
Eastside Catholic School is a Catholic, faith-based educational community...
About the Role
The Vice President of Finance serves as a key strategic leader...
This is a hands-on financial leadership role with a specific, time-bound mandate...
This is an in-office position with an anticipated start date of November 30, 2026, with flexibility based on the selected candidate’s availability.
Budgeting & Strategic Financial Planning
- Lead financial planning efforts to align with operational needs and long-term goals.
- Lead the development of the annual budget, engaging Leadership Team members, Department Chairs, and Managers in the process.
- Present budget recommendations to the Finance Committee and Board of Trustees.
- Maintain and update the long-term financial forecast, ensuring alignment with strategic goals and realistic tuition, enrollment, and discount-rate assumptions.
- Oversee the school’s capital budget and compensation strategies, integrating financial planning with school priorities and facilities reserve requirements.
Financial Management, Debt & Risk Mitigation
- Ensure financial stability by managing resources, banking relationships, debt covenant compliance, and risk.
- Develop cash forecasts and manage liquidity strategies.
- Own the school’s relationship with its bond lender, including ongoing debt service coverage covenant testing, required financial reporting under the loan agreement, and any waiver, amendment, or restructuring negotiations.
- Report proactively and candidly to the President, Finance Committee, and Board of Trustees on covenant status and financial risk, well ahead of compliance testing dates, not after.
- Oversee risk management policies, including insurance coverages, funding sources, and financial reserves, including the facilities reserve.
- Negotiate and maintain debt agreements, ensuring compliance with all financial covenants.
Team Leadership & Organizational Collaboration
- Foster a culture of financial stewardship, service, and excellence within the Finance Team and the school community.
- Lead and mentor the VP Finance Office staff, including the Senior Accountant, Tuition Assistance Administrator and Business Office Associate.
- Promote teamwork, accountability, and professional development within the department.
- Collaborate with school departments, including Advancement, Admissions, Athletics, Registrar, and the Leadership Team, to support school-wide initiatives and financial planning.
Investment Management
- Oversee investment and endowment fund management to ensure financial sustainability.
- Develop and manage budgets and projections for endowment and other invested assets.
- Prepare and present quarterly investment reports to the Board of Trustees (or its designated Finance/Investment Committee).
- Ensure accurate classification of contributions and adherence to donor restrictions, including named and restricted endowment funds.
- Manage investment distributions and oversee adherence to the Investment Policy Statement in coordination with the Board of Trustees.
- Work with external investment managers and monitor portfolio performance.
- Oversee and file any required tax forms related to invested funds.
Accounting & Financial Reporting
- Ensure accurate financial reporting and compliance to support strategic decision-making and steward financial resources.
- Establish, implement, and oversee accounting policies that safeguard the school’s financial integrity and ensure compliance with GAAP, nonprofit regulations, and best practices.
- Oversee all accounting functions, including accounts payable, cash disbursements, cash receipts, fixed assets, and restricted fund accounting.
- Prepare timely and accurate financial reports for school leadership, the Board of Trustees, and external stakeholders, ensuring clarity in financial data and emerging trends, including a clear, non-adjusted (GAAP) view of operating results alongside any supplemental metrics presented to the board.
- Manage external financial audits and coordinate with the CPA firm for the annual financial statement audit.
- Oversee the preparation and submission of all required state and federal tax filings.
Payroll & Human Resources Coordination
- Oversee payroll administration and partner closely with Human Resources, which reports to the President.
- Oversee payroll processing, ensuring accurate and compliant payroll tax filings.
- Ensure compliance with all federal, state, and local payroll regulations.
- Serve as fiduciary trustee for the 401(k) plan, ensuring compliance and proper administration.
- Partner with the Human Resources Manager on compensation structures, benefits budgeting, and staffing plans, ensuring HR policy and practice remain aligned with the school’s financial plan, mission, and regulatory requirements.
Tuition Administration & Financial Aid
- Manage the school’s tuition program to balance affordability for families while ensuring sustainable revenue for the school.
- Oversee tuition and financial aid administration processes in collaboration with the Tuition Assistance Administrator, Admissions Office, and Registrar.
- Monitor the tuition discount rate against budget and long-term sustainability targets, and report trends to the President and Board.
- Develop and update communication materials for tuition policies, including written and online resources.
The position will provide leadership for the areas outlined above, with the potential for additional departments or functions to be added to its scope of responsibility as the organization’s needs evolve.
Qualifications & Experience
- Bachelor’s degree in accounting, finance, or a related field required.
- CPA license or master’s degree in a relevant field preferred.
- 7+ years of experience in a senior financial leadership role, with direct P&L or balance-sheet accountability, preferred.
- Demonstrated experience managing institutional debt, lender relationships, or covenant compliance — experience navigating a waiver, amendment, restructuring, or turnaround is strongly preferred given the school’s current debt covenant posture.
- Working knowledge of non-profit fund accounting standards, restricted gifts, and endowment management.
- Experience in payroll management preferred.
- Strong commitment to the mission and values of
for prose - Don't repeat job title as heading - Don't put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/scam-warning) - Remove duplicated lines and application instructions - Include section ONLY when real specific content exists - No filler/placeholder text - No Pay/Schedule/Benefits unless stated - Output ONLY HTML fragment Looking at the content: - "Who We Are" - substantive content about the school - "Position Overview" - substantive description of the role and its specific mandate - "Essential Responsibilities" - has multiple sub-sections with bullet points - "Qualifications & Experience" - list of qualifications The application instructions at the end should be removed (candidates must submit..., applications accepted until..., interviews begin...). Also note: "This is an in-office position with an anticipated start date of November 30, 2026..." - this could go in a Schedule section? But the rules say only include Schedule if posting actually states them. It does state "in-office position" and "anticipated start date". But Schedule typically means work schedule (hours, days). This is more about work arrangement and start date. Could fold into a short paragraph in Position Overview or a separate small section. But rules say prefer few substantive sections over many thin ones. I'll include it in Position Overview. Also "The position will provide leadership for the areas outlined above, with the potential for additional departments..." - this is part of responsibilities. Now, structure:
About the Organization
(for Who We Are)...
About the Role
(for Position Overview)...
Responsibilities
- but there are sub-sections. The rules say use for section headings like Responsibilities, Requirements, etc. But here we have sub-sections under Essential Responsibilities. Should I make each sub-section an ? The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So Responsibilities is a section heading. But the content has sub-sections: Budgeting & Strategic Financial Planning, Financial Management, Debt & Risk Mitigation, Team Leadership & Organizational Collaboration, Investment Management, Accounting & Financial Reporting, Payroll & Human Resources Coordination, Tuition Administration & Financial Aid.
These are sub-sections of Responsibilities. I could make them but the rules only mention . However, the rules don't forbid other heading levels, but they say "use for section headings". It might be okay to use for sub-sections. But to be safe, I'll keep them as ? That would make many headings. The example includes "Responsibilities" as a section heading. The sub-sections are part of Responsibilities. I think using for each sub-section is acceptable as they are distinct responsibility areas. The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say you can't have multiple for sub-sections. But "Responsibilities" is listed as an example. However, the content has clear sub-sections with bullet points. I'll make each sub-section an with the sub-section title, and then list the bullet points. That seems most semantic.
Alternatively, I could have one Responsibilities
and then each sub-section as but the rules don't mention . The output is HTML fragment, so using is fine. But the instruction says "use for section headings". It doesn't say "only use ". I'll use for main sections and for sub-sections? But the user might expect only . Let's see: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This suggests that the top-level sections should be . The sub-sections under Responsibilities are not in that list. I think it's better to treat each responsibility area as a separate section with . That would be consistent with "Responsibilities" being a section heading, but here we have multiple responsibility categories. I'll make each a .
But then we have "Qualifications & Experience" as another .
Also "About the Organization" and "About the Role" as .
Let's outline:
About the Organization
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So Responsibilities is a section heading. But the content has sub-sections: Budgeting & Strategic Financial Planning, Financial Management, Debt & Risk Mitigation, Team Leadership & Organizational Collaboration, Investment Management, Accounting & Financial Reporting, Payroll & Human Resources Coordination, Tuition Administration & Financial Aid.
These are sub-sections of Responsibilities. I could make them but the rules only mention . However, the rules don't forbid other heading levels, but they say "use for section headings". It might be okay to use for sub-sections. But to be safe, I'll keep them as ? That would make many headings. The example includes "Responsibilities" as a section heading. The sub-sections are part of Responsibilities. I think using for each sub-section is acceptable as they are distinct responsibility areas. The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say you can't have multiple for sub-sections. But "Responsibilities" is listed as an example. However, the content has clear sub-sections with bullet points. I'll make each sub-section an with the sub-section title, and then list the bullet points. That seems most semantic.
Alternatively, I could have one Responsibilities
and then each sub-section as but the rules don't mention . The output is HTML fragment, so using is fine. But the instruction says "use for section headings". It doesn't say "only use ". I'll use for main sections and for sub-sections? But the user might expect only . Let's see: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This suggests that the top-level sections should be . The sub-sections under Responsibilities are not in that list. I think it's better to treat each responsibility area as a separate section with . That would be consistent with "Responsibilities" being a section heading, but here we have multiple responsibility categories. I'll make each a .
But then we have "Qualifications & Experience" as another .
Also "About the Organization" and "About the Role" as .
Let's outline:
About the Organization
. However, the rules don't forbid other heading levels, but they say "use for section headings". It might be okay to use for sub-sections. But to be safe, I'll keep them as ? That would make many headings. The example includes "Responsibilities" as a section heading. The sub-sections are part of Responsibilities. I think using for each sub-section is acceptable as they are distinct responsibility areas. The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say you can't have multiple for sub-sections. But "Responsibilities" is listed as an example. However, the content has clear sub-sections with bullet points. I'll make each sub-section an with the sub-section title, and then list the bullet points. That seems most semantic.
Alternatively, I could have one Responsibilities
and then each sub-section as but the rules don't mention . The output is HTML fragment, so using is fine. But the instruction says "use for section headings". It doesn't say "only use ". I'll use for main sections and for sub-sections? But the user might expect only . Let's see: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This suggests that the top-level sections should be . The sub-sections under Responsibilities are not in that list. I think it's better to treat each responsibility area as a separate section with . That would be consistent with "Responsibilities" being a section heading, but here we have multiple responsibility categories. I'll make each a .
But then we have "Qualifications & Experience" as another .
Also "About the Organization" and "About the Role" as .
Let's outline:
About the Organization
for sub-sections. But to be safe, I'll keep them as ? That would make many headings. The example includes "Responsibilities" as a section heading. The sub-sections are part of Responsibilities. I think using for each sub-section is acceptable as they are distinct responsibility areas. The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say you can't have multiple for sub-sections. But "Responsibilities" is listed as an example. However, the content has clear sub-sections with bullet points. I'll make each sub-section an with the sub-section title, and then list the bullet points. That seems most semantic.
Alternatively, I could have one Responsibilities
and then each sub-section as but the rules don't mention . The output is HTML fragment, so using is fine. But the instruction says "use for section headings". It doesn't say "only use ". I'll use for main sections and for sub-sections? But the user might expect only . Let's see: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This suggests that the top-level sections should be . The sub-sections under Responsibilities are not in that list. I think it's better to treat each responsibility area as a separate section with . That would be consistent with "Responsibilities" being a section heading, but here we have multiple responsibility categories. I'll make each a .
But then we have "Qualifications & Experience" as another .
Also "About the Organization" and "About the Role" as .
Let's outline:
About the Organization
headings. The example includes "Responsibilities" as a section heading. The sub-sections are part of Responsibilities. I think using for each sub-section is acceptable as they are distinct responsibility areas. The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say you can't have multiple for sub-sections. But "Responsibilities" is listed as an example. However, the content has clear sub-sections with bullet points. I'll make each sub-section an with the sub-section title, and then list the bullet points. That seems most semantic.
Alternatively, I could have one Responsibilities
and then each sub-section as but the rules don't mention . The output is HTML fragment, so using is fine. But the instruction says "use for section headings". It doesn't say "only use ". I'll use for main sections and for sub-sections? But the user might expect only . Let's see: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This suggests that the top-level sections should be . The sub-sections under Responsibilities are not in that list. I think it's better to treat each responsibility area as a separate section with . That would be consistent with "Responsibilities" being a section heading, but here we have multiple responsibility categories. I'll make each a .
But then we have "Qualifications & Experience" as another .
Also "About the Organization" and "About the Role" as .
Let's outline:
About the Organization
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say you can't have multiple for sub-sections. But "Responsibilities" is listed as an example. However, the content has clear sub-sections with bullet points. I'll make each sub-section an with the sub-section title, and then list the bullet points. That seems most semantic.
Alternatively, I could have one Responsibilities
and then each sub-section as but the rules don't mention . The output is HTML fragment, so using is fine. But the instruction says "use for section headings". It doesn't say "only use ". I'll use for main sections and for sub-sections? But the user might expect only . Let's see: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This suggests that the top-level sections should be . The sub-sections under Responsibilities are not in that list. I think it's better to treat each responsibility area as a separate section with . That would be consistent with "Responsibilities" being a section heading, but here we have multiple responsibility categories. I'll make each a .
But then we have "Qualifications & Experience" as another .
Also "About the Organization" and "About the Role" as .
Let's outline:
About the Organization
with the sub-section title, and then list the bullet points. That seems most semantic.
Alternatively, I could have one Responsibilities
and then each sub-section as but the rules don't mention . The output is HTML fragment, so using is fine. But the instruction says "use for section headings". It doesn't say "only use ". I'll use for main sections and for sub-sections? But the user might expect only . Let's see: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This suggests that the top-level sections should be . The sub-sections under Responsibilities are not in that list. I think it's better to treat each responsibility area as a separate section with . That would be consistent with "Responsibilities" being a section heading, but here we have multiple responsibility categories. I'll make each a .
But then we have "Qualifications & Experience" as another .
Also "About the Organization" and "About the Role" as .
Let's outline:
About the Organization
. The output is HTML fragment, so using is fine. But the instruction says "use for section headings". It doesn't say "only use ". I'll use for main sections and for sub-sections? But the user might expect only . Let's see: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This suggests that the top-level sections should be . The sub-sections under Responsibilities are not in that list. I think it's better to treat each responsibility area as a separate section with . That would be consistent with "Responsibilities" being a section heading, but here we have multiple responsibility categories. I'll make each a .
But then we have "Qualifications & Experience" as another .
Also "About the Organization" and "About the Role" as .
Let's outline:
About the Organization
for section headings". It doesn't say "only use ". I'll use for main sections and for sub-sections? But the user might expect only . Let's see: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This suggests that the top-level sections should be . The sub-sections under Responsibilities are not in that list. I think it's better to treat each responsibility area as a separate section with . That would be consistent with "Responsibilities" being a section heading, but here we have multiple responsibility categories. I'll make each a .
But then we have "Qualifications & Experience" as another .
Also "About the Organization" and "About the Role" as .
Let's outline:
About the Organization
for main sections and for sub-sections? But the user might expect only . Let's see: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This suggests that the top-level sections should be . The sub-sections under Responsibilities are not in that list. I think it's better to treat each responsibility area as a separate section with . That would be consistent with "Responsibilities" being a section heading, but here we have multiple responsibility categories. I'll make each a .
But then we have "Qualifications & Experience" as another .
Also "About the Organization" and "About the Role" as .
Let's outline:
About the Organization
. Let's see: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This suggests that the top-level sections should be . The sub-sections under Responsibilities are not in that list. I think it's better to treat each responsibility area as a separate section with . That would be consistent with "Responsibilities" being a section heading, but here we have multiple responsibility categories. I'll make each a .
But then we have "Qualifications & Experience" as another .
Also "About the Organization" and "About the Role" as .
Let's outline:
About the Organization
. The sub-sections under Responsibilities are not in that list. I think it's better to treat each responsibility area as a separate section with . That would be consistent with "Responsibilities" being a section heading, but here we have multiple responsibility categories. I'll make each a .
But then we have "Qualifications & Experience" as another .
Also "About the Organization" and "About the Role" as .
Let's outline:
About the Organization
.
But then we have "Qualifications & Experience" as another .
Also "About the Organization" and "About the Role" as .
Let's outline:
About the Organization
.
Let's outline:
About the Organization
Eastside Catholic School is a Catholic, faith-based educational community...
About the Role
The Vice President of Finance serves as a key strategic leader...
This is a hands-on financial leadership role with a specific, time-bound mandate...
This is an in-office position with an anticipated start date of November 30, 2026, with flexibility based on the selected candidate’s availability.
Budgeting & Strategic Financial Planning
- Lead financial planning efforts to align with operational needs and long-term goals.
- Lead the development of the annual budget, engaging Leadership Team members, Department Chairs, and Managers in the process.
- Present budget recommendations to the Finance Committee and Board of Trustees.
- Maintain and update the long-term financial forecast, ensuring alignment with strategic goals and realistic tuition, enrollment, and discount-rate assumptions.
- Oversee the school’s capital budget and compensation strategies, integrating financial planning with school priorities and facilities reserve requirements.
Financial Management, Debt & Risk Mitigation
- Ensure financial stability by managing resources, banking relationships, debt covenant compliance, and risk.
- Develop cash forecasts and manage liquidity strategies.
- Own the school’s relationship with its bond lender, including ongoing debt service coverage covenant testing, required financial reporting under the loan agreement, and any waiver, amendment, or restructuring negotiations.
- Report proactively and candidly to the President, Finance Committee, and Board of Trustees on covenant status and financial risk, well ahead of compliance testing dates, not after.
- Oversee risk management policies, including insurance coverages, funding sources, and financial reserves, including the facilities reserve.
- Negotiate and maintain debt agreements, ensuring compliance with all financial covenants.
Team Leadership & Organizational Collaboration
- Foster a culture of financial stewardship, service, and excellence within the Finance Team and the school community.
- Lead and mentor the VP Finance Office staff, including the Senior Accountant, Tuition Assistance Administrator and Business Office Associate.
- Promote teamwork, accountability, and professional development within the department.
- Collaborate with school departments, including Advancement, Admissions, Athletics, Registrar, and the Leadership Team, to support school-wide initiatives and financial planning.
Investment Management
- Oversee investment and endowment fund management to ensure financial sustainability.
- Develop and manage budgets and projections for endowment and other invested assets.
- Prepare and present quarterly investment reports to the Board of Trustees (or its designated Finance/Investment Committee).
- Ensure accurate classification of contributions and adherence to donor restrictions, including named and restricted endowment funds.
- Manage investment distributions and oversee adherence to the Investment Policy Statement in coordination with the Board of Trustees.
- Work with external investment managers and monitor portfolio performance.
- Oversee and file any required tax forms related to invested funds.
Accounting & Financial Reporting
- Ensure accurate financial reporting and compliance to support strategic decision-making and steward financial resources.
- Establish, implement, and oversee accounting policies that safeguard the school’s financial integrity and ensure compliance with GAAP, nonprofit regulations, and best practices.
- Oversee all accounting functions, including accounts payable, cash disbursements, cash receipts, fixed assets, and restricted fund accounting.
- Prepare timely and accurate financial reports for school leadership, the Board of Trustees, and external stakeholders, ensuring clarity in financial data and emerging trends, including a clear, non-adjusted (GAAP) view of operating results alongside any supplemental metrics presented to the board.
- Manage external financial audits and coordinate with the CPA firm for the annual financial statement audit.
- Oversee the preparation and submission of all required state and federal tax filings.
Payroll & Human Resources Coordination
- Oversee payroll administration and partner closely with Human Resources, which reports to the President.
- Oversee payroll processing, ensuring accurate and compliant payroll tax filings.
- Ensure compliance with all federal, state, and local payroll regulations.
- Serve as fiduciary trustee for the 401(k) plan, ensuring compliance and proper administration.
- Partner with the Human Resources Manager on compensation structures, benefits budgeting, and staffing plans, ensuring HR policy and practice remain aligned with the school’s financial plan, mission, and regulatory requirements.
Tuition Administration & Financial Aid
- Manage the school’s tuition program to balance affordability for families while ensuring sustainable revenue for the school.
- Oversee tuition and financial aid administration processes in collaboration with the Tuition Assistance Administrator, Admissions Office, and Registrar.
- Monitor the tuition discount rate against budget and long-term sustainability targets, and report trends to the President and Board.
- Develop and update communication materials for tuition policies, including written and online resources.
The position will provide leadership for the areas outlined above, with the potential for additional departments or functions to be added to its scope of responsibility as the organization’s needs evolve.
Qualifications & Experience
- Bachelor’s degree in accounting, finance, or a related field required.
- CPA license or master’s degree in a relevant field preferred.
- 7+ years of experience in a senior financial leadership role, with direct P&L or balance-sheet accountability, preferred.
- Demonstrated experience managing institutional debt, lender relationships, or covenant compliance — experience navigating a waiver, amendment, restructuring, or turnaround is strongly preferred given the school’s current debt covenant posture.
- Working knowledge of non-profit fund accounting standards, restricted gifts, and endowment management.
- Experience in payroll management preferred.
- Strong commitment to the mission and values of