Director/Senior Director, Office of the CFO Finance Transformation

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. We must not repeat job title. No Job ID etc. Remove boilerplate like EEO, accommodations, etc. Also remove navigation, cookie, legal, duplicated lines. We need to parse the posting. Content: - Intro: "Ankura is a team of excellence founded on innovation and growth." etc. That's about the company/practice overview. Could be "About the role"? Actually "About the role" maybe includes overview of role. The posting has "Practice Overview", "Role Overview". We can combine into About the role section. - Responsibilities: bullet list. - Requirements: bullet list. - Qualifications: maybe overlapping with requirements. The posting includes "Requirements" section with bullet items. Also "Qualifications" maybe not separate. Could treat "Requirements" as qualifications. But we have both sections possible. We need to decide based on content: The posting has "Requirements" heading with bullet list. Also there is "Qualifications" not explicit. Could combine. - Skills: maybe list of tools: ERP and EPM platforms, Process and automation tooling, Project-delivery tooling; SQL or Python a plus. Could be a Skills section. - Benefits: Not mentioned explicitly. There's mention of compensation range but not benefits. So we should not create Benefits section unless posting actually states them. It does not list benefits like health, 401k, etc. So omit Benefits. - Pay: The posting includes compensation range: "A reasonable estimate of the current base pay range is between $110,000 to $200,000;". Also mentions pay transparency. So we can include Pay section with that info. - Schedule: Not mentioned explicitly. There's hybrid-based position ideally based in Chicago, NYC, LA. Travel up to 80%. That's more about location/travel, not schedule. No explicit schedule like full-time, part-time. So we should not create Schedule section unless posting actually states them. It does not. So omit Schedule. We must not include placeholder text like "commensurate with experience". The compensation range is specific, okay. We need to preserve all substantive information, not invent or summarize away detail. So we need to include all details from the posting, but we can format them. We must remove boilerplate: EEO statement, accommodations, etc. Also remove duplicated lines. We need to decide headings: About the role, Responsibilities, Requirements, Skills, Pay. Possibly also Qualifications if we separate. But we have Requirements already covering qualifications. Could also include Qualifications as separate if there is distinct content. The posting under Requirements includes education, experience, certifications, tools, travel, work authorization, professionalism. That's essentially qualifications. So we can just have Requirements section and maybe not Qualifications. But the instruction says use headings for those categories if content exists. We can include Qualifications as a heading if we have content distinct from Requirements. However we risk duplication. Better to follow the posting: they have a "Requirements" heading. So we will use that. No separate Qualifications. Skills: we can extract tools and technical skills into a Skills section. About the role: combine practice overview and role overview. Let's draft. About the role (

About the role

): include paragraphs summarizing Ankura, OCFO, focus, role overview, hybrid location, typical experience for Director/Senior Director. We must not invent or summarize away detail; we can paraphrase but must preserve all substantive info. Paraphrasing is okay as long as we keep meaning. We'll try to keep details. Responsibilities (

Responsibilities

): list bullet points from the responsibilities paragraph. Requirements (

Requirements

): list bullet points from requirements. Skills (

Skills

): list technical skills: ERP and EPM platforms (SAP, Oracle, Workday, NetSuite; Hyperion, Anaplan); Process and automation tooling (Microsoft Power Platform, Alteryx); Project-delivery tooling; SQL or Python a plus. Pay (

Pay

): paragraph about compensation range: $110,000 to $200,000 base pay range, note about pay transparency, not adjusted for geographic differential, does not include benefits, typical not hired at top, etc. We must not include boilerplate like "Ankura is an Affirmative Action and Equal Opportunity Employer." etc. Remove. Also remove the line about accommodations email/phone. Also remove the line about "For individuals assigned and/or hired to work in California, Colorado, New York or other states with relevant pay transparency laws, Ankura is required to include a reasonable estimate of the compensation range for this role." That's part of pay explanation; we can keep that as part of Pay section because it's substantive about pay range disclosure. But we must ensure not to include EEO etc. We should also remove the sentence about "At Ankura, it is not typical for an individual to be hired at or near the top of the range for their role and compensation decisions are dependent on the facts and circumstances of each role." That's part of pay details, keep. Now ensure we don't repeat job title. Now produce HTML fragment: only the sections, each with

heading and content. For About the role: maybe two paragraphs. Let's craft. About the role: Paragraph 1: Ankura is a team of excellence founded on innovation and growth. The Ankura Office of the CFO™ (Ankura OCFO™) was established to support the strategic vision and evolving demands of the finance organization. Its focus is on enabling the CFO's success by delivering holistic, tailored solutions that drive business performance, improve operational efficiency and effectiveness, transform data into insights, and position the finance function as a strategic partner to the business. Ankura OCFO professionals serve as trusted partners to a diverse clientele — from middle-market enterprises to Fortune 500 companies, and across private equity firms and their portfolio companies in every industry — bringing a collaborative spirit and an entrepreneurial mindset as they sustain rapid growth and constant innovation. Paragraph 2: This role sits within the Finance Transformation focus area, helping clients redesign finance processes and operating models and implement the systems, data, and automation that make the finance function more effective. Depending on candidate experience and qualifications, the role could be filled at the Director or Senior Director level. A Director owns day-to-day engagement delivery and client leadership, managing teams and engagement economics (typical experience: 6‑10 years). A Senior Director owns delivery across multiple engagements or larger accounts, serves as a subject‑matter authority, and drives business development (typical experience: 10‑15 years). This is a hybrid‑based position ideally based in Chicago, New York City, or Los Angeles. Now Responsibilities: list bullet points. From posting: - Lead finance process redesign and ERP/EPM-enabled implementations end to end. - Assess operating models, org design, processes, and technology; build execution plans. - Drive data and automation to improve efficiency and reporting. - Serve as day-to-day client leader across transformation workstreams and advise senior stakeholders through complex transformation. - Manage program delivery, scope, and risk; lead teams. - Contribute to pursuits. - Architect target operating models and drive large-scale change programs (Senior Director) - Own delivery across programs and accounts (Senior Director) - Develop directors and teams (Senior Director) - Generate opportunities and own scoping and pricing (Senior Director) We need to keep all. Could combine senior director specifics as separate bullet points. Now Requirements bullet list: - Undergraduate degree in a relevant field; Master's or MBA preferred. - Experience: Director = 6‑10+ years of relevant experience, including 2‑3 years in client‑facing consulting. Senior Director = 10‑15+ years of experience. - Track record leading engagement delivery and developing teams. - Experience leading finance transformation — operating‑model design, ERP/EPM implementation, and change management. - PMP, Six Sigma, or equivalent delivery certification preferred. - ERP and EPM platforms (SAP, Oracle, Workday, NetSuite; Hyperion, Anaplan). - Process and automation tooling (Microsoft Power Platform, Alteryx). - Project‑delivery tooling; SQL or Python a plus. - Willingness and ability to travel extensively (up to ~80%) as client engagements require. - Must be legally authorized to work in the United States without the need for employer sponsorship, now or at any time in the future. - Demonstrates the highest standards of professionalism, ethics, quality, and integrity. Now Skills section: we could extract the tools and technical skills. But note that many of these appear also in Requirements. To avoid duplication, we could keep them in Requirements and not repeat in Skills. However the instruction says we can have Skills section if posting has real specific content for it. The posting does mention tools under Requirements. Could we create a Skills section that lists those tools? That would duplicate content. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is not prohibited explicitly, but we should avoid redundant sections? It says "Prefer a few substantive sections over many thin ones." Duplication could be considered thin. Better to keep tools within Requirements and not create separate Skills section unless there is distinct skills content not already covered. However the instruction includes Skills as a possible heading. The posting does have a list of tools under Requirements; we could still create a Skills section that lists them, but that would be repeating. Might be okay but could be considered thin. I'd rather not create Skills section to avoid duplication and keep sections substantive. But we need to decide: The instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's just examples; we can omit Skills if not needed. The posting does have specific technical skills, but they are already in Requirements. Could we move them to Skills and keep Requirements more about experience/education? That would split content but still preserve all info. That might be better: Requirements focusing on education, experience, certifications, travel, work authorization, professionalism. Skills focusing on technical tools. That avoids duplication and gives each section substantive content. Let's do that. Thus: Requirements: - Undergraduate degree in a relevant field; Master's or MBA preferred. - Experience: Director = 6‑10+ years of relevant experience, including 2‑3 years in client‑facing consulting. Senior Director = 10‑15+ years of experience. - Track record leading engagement delivery and developing teams. - Experience leading finance transformation — operating‑model design, ERP/EPM implementation, and change management. - PMP, Six Sigma, or equivalent delivery certification preferred. - Willingness and ability to travel extensively (up to ~80%) as client engagements require. - Must be legally authorized to work in the United States without the need for employer sponsorship, now or at any time in the future. - Demonstrates the highest standards of professionalism, ethics, quality, and integrity. Skills: - ERP and EPM platforms (SAP, Oracle, Workday, NetSuite; Hyperion, Anaplan). - Process and automation tooling (Microsoft Power Platform, Alteryx). - Project‑delivery tooling; SQL or Python a plus. Now Pay section: include the compensation range details. Pay: Paragraph: For individuals assigned and/or hired to work in California, Colorado, New York or other states with relevant pay transparency laws, Ankura is required to include a reasonable estimate of the compensation range for this role. This compensation range is specific to the said markets and considers a broad range of factors including but not limited to skill sets, experience and training, licensure and certifications, and other business and organizational needs. The disclosed range estimate has not been adjusted for the applicable geographic differential associated with the location at which the position may be filled. The range does not include additional benefits outside of salary. At Ankura, it is not typical for