Principal, Finance Data Governance & Strategy

We need to output HTML fragment with sections: About the role? The posting includes Overview, The Role, Responsibilities, Candidate Profile, Qualifications, Preferred Experience, Pay info. We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We must include sections only when posting has real specific content. We have content for Overview (maybe "About the role" or "Overview"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we map sections accordingly. We have Overview (mission, role description). Could be "About the role". Then Responsibilities section. Then Qualifications (maybe "Qualifications" heading). Also Candidate Profile could be part of Qualifications or maybe "Requirements"? The instruction says use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Qualifications and Preferred Experience (maybe part of Qualifications). We have Pay info (Expected Base Pay Range). No Benefits or Schedule specifics. So we should not create Benefits or Schedule sections because no specific content. We also have "Overview" maybe we can treat as "About the role". Provide a paragraph summarizing mission and role. We need to preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, navigation, etc. Remove duplicated lines. We need to output only HTML fragment, no /, no markdown fences. Let's extract content: Overview: "Intuit's mission is powering prosperity around the world. We do this by attracting the world's top talent, delivering innovative solutions for consumers, small businesses, self-employed professionals, and accounting experts. Every day we innovate with our flagship products: TurboTax, QuickBooks, Mailchimp, and Credit Karma. For over 100 million customers, we deliver more money, more time, and more confidence." The Role: "Reporting to the Director, Finance Data, Automation and AI, the Principal, Finance Data Governance & Strategy will own the data foundation that Intuit's Finance transformation is built on. As Finance modernizes its planning, reporting, and ERP platforms under the Unified Plan to Perform program, and as AI moves from pilots into production Finance workflows, the value of that work depends on data that is defined once, owned clearly, traceable to source, and safe to use. This is a senior individual contributor role for someone who is equally comfortable setting policy and building the technical foundation that makes it real. You will stand up and scale Finance's governance and stewardship model, ensure governance is designed into our platform modernization rather than retrofitted afterward, and lead emerging capabilities such as synthetic data that let Finance test, develop, and train models without exposing sensitive data. The role sits at the intersection of control and innovation. You will partner across Finance, Technology, Enterprise Data, Risk and Compliance, Legal, and Security, and represent Finance in shaping Intuit's enterprise data strategy" Responsibilities: list bullet points: - Own Finance's data governance framework: Define and operate data definitions, quality standards, stewardship, and access controls across Finance data domains, with accountable owners and clear decision rights for every critical dataset. - Build lineage and the Finance data map: Establish and maintain a living inventory of Finance data sources, systems, flows, and transformations, so every metric traces back to source and the map serves as the reference for access, risk, audit, and architecture decisions. - Embed governance in platform modernization: Lead the data governance, mapping, and reconciliation strategy for Finance's ERP and planning platform migration, ensuring ownership, lineage, and SOX-relevant controls are re-established in the target state rather than replicated as-is. - Lead Finance's synthetic data strategy: Define where synthetic data can replace production data for testing, development, model training, and analytics; set fidelity and validation standards; and partner with Engineering and AI/ML teams on reusable pipelines and tooling. - Design controls with partners: Work with Technology, Enterprise Data, Risk and Compliance, Legal, and Security on access controls and sensitive-data handling that meet SOX and privacy requirements without slowing the business. - Represent Finance in enterprise data strategy: Sit on enterprise data governance forums, align Finance standards with Intuit-wide policy, and ensure Finance's needs are reflected in company-wide data decisions. - Shape what comes next: Build and own the roadmap for Finance's data capability maturity, evaluating emerging capabilities (AI-driven data quality, automated lineage, federated access) and acting as a thought partner to Finance leadership on where to invest. Candidate Profile: paragraphs describing ideal candidate. Qualifications: list bullet points: - 8+ years in data governance, data strategy, or data architecture, including 2 to 3 years operating at a principal or strategic level. - Demonstrated experience standing up or scaling a data governance and stewardship program. - Experience governing data through a large legacy-to-cloud platform migration, with a focus on lineage, ownership, and controls rather than technical migration execution alone. - Experience building or owning enterprise data maps, catalogs, and lineage tooling. - Strong technical fluency, including SQL and modern data warehouse environments (Snowflake, BigQuery, or similar). - Experience in a regulated or controls-sensitive environment (SOX/ICFR exposure preferred). - Track record of influencing enterprise-level data strategy and senior stakeholders across business and technology. - Bachelor's degree in Information Systems, Computer Science, Finance, Business, or a related field; advanced degree or relevant certifications a plus. Preferred Experience: bullet points: - Hands-on experience with synthetic data generation and validation techniques. - Experience with Oracle ERP or EPM environments and Finance data models (Chart of Accounts, master data). - Experience supporting Finance, Accounting, or FP&A functions in a large, matrixed enterprise. - Exposure to AI/ML data readiness, data products, or federated data governance models. Pay: "Intuit provides a competitive compensation package with a strong pay for performance rewards approach. This position may be eligible for a cash bonus, equity rewards and benefits, in accordance with our applicable plans and programs (see more about our compensation and benefits at Intuit®: Careers | Benefits). Pay offered is based on factors such as job-related knowledge, skills, experience, and work location. To drive ongoing fair pay for employees, Intuit conducts regular comparisons across categories of ethnicity and gender. The Expected Base Pay Range For This Position Is Mountain View $215,000 - $291,000" We need to include Pay section with that info. Benefits: we have mention of benefits but not specific details; we should not create Benefits section unless posting actually states them. It mentions "cash bonus, equity rewards and benefits" but not specifics. Probably we should not create Benefits section because no specific benefit details. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Pay range, so we include Pay. Benefits: they mention benefits generically but not specific; maybe we could include a Benefits section with that generic statement? The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits in a sentence: "This position may be eligible for a cash bonus, equity rewards and benefits, in accordance with our applicable plans and programs". That is a statement about benefits eligibility. Could be considered stating benefits. However they also say "see more about our compensation and benefits at Intuit®: Careers | Benefits". That is a reference. Might be considered stating benefits. But to be safe, we could include a Benefits section with that sentence. However the instruction also says "Prefer a few substantive sections over many thin ones." So maybe we combine Pay and Benefits? But they want separate headings for Pay, Benefits, Schedule. If we include Benefits, we need to have content. The content is generic but still substantive? It says "cash bonus, equity rewards and benefits". That's somewhat vague but still mentions benefits. I'd include a Benefits section with that sentence. Schedule: no info, so omit. We also need to include maybe a "Requirements" section? The qualifications could be considered Requirements. But we already have Qualifications heading. The instruction includes Requirements as a possible heading. We could map Qualifications to Requirements? But they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we have both Requirements and Qualifications as separate headings. We need to decide where to put content. The posting has "Qualifications" and "Preferred Experience". Could treat "Qualifications" as Requirements (mandatory) and "Preferred Experience" as Qualifications? Or we could treat "Qualifications" as Requirements and "Preferred Experience" as Qualifications. But the instruction says we should not invent sections; we should include a section only when posting has real specific content for it. So we need to map the content to appropriate headings. The posting explicitly uses "Qualifications" heading for the list of 8+ years etc. And "Preferred Experience" heading for additional desired experience. So we can use

Qualifications

for the mandatory qualifications list, and

Preferred Experience

is not in the allowed headings list. The allowed headings list does not include "Preferred Experience". So we need to decide: either we treat Preferred Experience as part of Qualifications (maybe under Qualifications we include both mandatory and preferred). Or we could create a "Skills" section for preferred experience? Not ideal. Better to follow the instruction: Use headings from the list. So we have: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content: - About the role: Overview + The Role description (mission and role). - Responsibilities: the responsibilities list. - Requirements: maybe the Qualifications list (mandatory). - Qualifications: maybe the Preferred Experience list? Or we could treat Qualifications as the mandatory and Requirements as something else? But we have both headings; we need to decide which content goes where. The posting has "Qualifications" (mandatory) and "Preferred Experience". So we could map "Qualifications" to the mandatory list, and "Preferred Experience" to the "Qualifications" heading? That would be confusing. Perhaps we treat "Requirements" as the mandatory qualifications, and "Qualifications" as the preferred experience. That seems plausible: Requirements = must-have; Qualifications = nice-to-have. The instruction didn't define semantics, just gave headings. So we can assign accordingly. Thus:

Requirements

with the mandatory qualifications list (8+ years, etc.)

Qualifications

with the Preferred Experience list. Skills: we could maybe include technical fluency (SQL, Snowflake, etc.) but that's already in Requirements. Could create Skills section for technical fluency? But we already used that in Requirements. Might be redundant. Better to omit Skills if no distinct content. Benefits: include the sentence about cash bonus, equity rewards and benefits. Pay: include the pay range and description. Schedule: none. We must not repeat job title as heading. Not include Job ID etc. We must preserve all substantive information. Ensure we don't lose any detail. Let's craft HTML: maybe not needed; just headings and content. We'll output:

About the role

Intuit's mission is powering prosperity around the world. We do this by attracting the world's top talent, delivering innovative solutions for consumers, small businesses, self-employed professionals, and accounting experts. Every day we innovate with our flagship products: TurboTax, QuickBooks, Mailchimp, and Credit Karma. For over 100 million customers, we deliver more money, more time, and more confidence.

Reporting to the Director, Finance Data, Automation and AI, the Principal, Finance Data Governance & Strategy will own the data foundation that Intuit's Finance transformation is built on. As Finance modernizes its planning, reporting, and ERP platforms under the Unified Plan to Perform program, and as AI moves from pilots into production Finance workflows, the value of that work depends on data that is defined once, owned clearly,