Data Architecture & Engineering Senior Manager
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to decide sections: About the role (maybe combine company overview and role description). Responsibilities (the Work bullet list). Requirements (the "Here’s What You Need" bullet list). Bonus Points could be part of Requirements or separate "Preferred Qualifications". Could make a section "Preferred Qualifications". Benefits: list of benefits. Pay: include compensation statement and salary ranges. Schedule: travel may be required.
We must not create sections with filler. Ensure each heading has real content.
Let's extract content.
Company overview paragraph: "We Are Accenture is a leading global professional services company...". That's substantive.
AI and Data practice paragraph: "Our AI and Data practice sits at the intersection...". Also substantive.
Role description: "You Are You are a senior data architect who designs enterprise data fabric solutions..." That's a bit duplicated "You Are You". We'll keep as is but maybe clean? We must preserve substantive info, not invent. The text includes duplication but we should keep as is? Probably we should keep the sentence as given but maybe remove duplicate "You Are". However that would be altering content. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't say we must keep exact wording, but we should not change meaning. Removing duplicate words could be considered editing but not inventing. Might be okay. Safer to keep as is? It reads weird but it's the original. We'll keep exactly as appears: "You Are You are a senior data architect who designs enterprise data fabric solutions that provide unified, intelligent, automated access to distributed data across on-prem and multi-cloud environments." That's weird but it's what they wrote.
Then responsibilities bullet list: each line starts with a bold heading? In text: "The Work Architect enterprise data fabric — design data fabric solutions that deliver unified, intelligent, automated access to distributed data across on-prem and multi-cloud environments.Integrate the connected data layer — design the integration of data virtualization, active metadata, knowledge graphs, cataloging, and automated data integration into a connected data layer for analytics and AI.Define reference architectures — establish reference architectures, integration patterns, and governance integration that scale across the enterprise.Enable data products and self-service — support self-service consumption, data products, and real-time data delivery through the fabric.Apply modern data paradigms — bring data mesh and data product concepts, cloud data platforms (Snowflake, Databricks, Azure Synapse, BigQuery), and streaming/API architectures to bear on client problems.Advise and shape solutions — engage client architects and leaders as a trusted advisor and shape solutions for major data modernization pursuits. Travel may be required for this role, varying from 0 to 100% depending on business need and client requirements."
We need to split into list items. Each bullet separated by a period? Actually they are separated by periods but no line breaks. We'll parse each sentence before an em dash? The pattern: "Architect enterprise data fabric — design ..." then "Integrate the connected data layer — design ..." etc. We'll make each as
- .
We'll need to separate travel sentence maybe as its own bullet? It's after a period: "Travel may be required for this role, varying from 0 to 100% depending on business need and client requirements." We'll include as a bullet under Responsibilities or maybe under Schedule. Since Schedule section is for travel, we could put travel sentence there. But the instruction: Use Schedule section only if posting actually states them. It does state travel may be required varying 0-100%. So we can put that in Schedule section. However the responsibilities bullet list includes that sentence; we could keep it there but better to move to Schedule to avoid duplication. But we must preserve all substantive information; moving is okay as long as we keep the info. We'll put travel sentence in Schedule section.
Thus Responsibilities bullets: Architect enterprise data fabric — design data fabric solutions that deliver unified, intelligent, automated access to distributed data across on-prem and multi-cloud environments. Integrate the connected data layer — design the integration of data virtualization, active metadata, knowledge graphs, cataloging, and automated data integration into a connected data layer for analytics and AI. Define reference architectures — establish reference architectures, integration patterns, and governance integration that scale across the enterprise. Enable data products and self-service — support self-service consumption, data products, and real-time data delivery through the fabric. Apply modern data paradigms — bring data mesh and data product concepts, cloud data platforms (Snowflake, Databricks, Azure Synapse, BigQuery), and streaming/API architectures to bear on client problems. Advise and shape solutions — engage client architects and leaders as a trusted advisor and shape solutions for major data modernization pursuits.
Now Requirements bullet list: "Minimum of 10 years of experience in data architecture or enterprise data engineering (in a AWS, Microsoft, Google (preferred), etc. environment) Minimum of 6 years of experience architecting data fabric solutions (data virtualization, active metadata, knowledge graphs, automated integration) Minimum of 5 years of experience with cloud data platforms (e.g., Snowflake, Databricks, Azure Synapse, BigQuery) Minimum of 4 years of experience with data integration/ETL/ELT and metadata & lineage tooling Minimum of 3 years of experience with API and streaming architecture Bachelor's degree or equivalent (minimum 12 years' work experience). If Associate’s Degree, must have equivalent minimum 6-year work experience". We'll split each as
- .
Bonus Points: "Bonus Points If You have a minimum of 1 year of experience serving utilities clients (electric, gas, or water) or in a utilities finance, controllership, or regulatory function. You have a Master’s degree in a relevant field You have hands-on experience applying data mesh and data product operating models You have Cloud or data platform architecture certifications". We'll make a section "Preferred Qualifications" with those bullets.
Benefits: "Accenture offers a market competitive suite of benefits including medical, dental, vision, life, and long-term disability coverage, a 401(k) plan, bonus opportunities, paid holidays, and paid time off. See more information on our benefits here: U.S. Employee Benefits | Accenture". We'll keep the link as is inside
.
Pay: "Compensation at Accenture varies depending on a wide array of factors, which may include but are not limited to the specific office location, role, skill set, and level of experience. As required by local law, Accenture provides a reasonable range of compensation for roles that may be hired as set forth below. We anticipate this job posting will be posted until 08/25/2026." Then the salary ranges table: list of locations with ranges. We'll keep that as a
maybe each location as - . Or we could keep as paragraphs. Better to use
- for list.
Schedule: "Travel may be required for this role, varying from 0 to 100% depending on business need and client requirements."
We must remove boilerplate: EEO statements, accommodation request, legal statements, etc. Also remove navigation, cookie, etc. Also remove the "Requesting an Accommodation" paragraph and everything after that until end? Actually after that there is EEO statement etc. We'll cut off before "Requesting an Accommodation". So we stop before that heading.
Also remove the line "Visit us at accenture.com." maybe keep? It's part of company overview; it's substantive? It's just a URL; could keep but it's not essential. Might keep as part of overview.
We must not include the link to benefits inside a
but it's okay.
Now produce HTML fragment.
Structure:
About the role
We Are Accenture is a leading global professional services company that helps the world’s leading businesses, governments and other organizations build their digital core, optimize their operations, accelerate revenue growth and enhance citizen services—creating tangible value at speed and scale. We are a talent- and innovation-led company with approximately 790,000 people serving clients in more than 120 countries. Technology is at the core of change today, and we are one of the world’s leaders in helping drive that change, with strong ecosystem relationships. We combine our strength in technology and leadership in cloud, data and AI with unmatched industry experience, functional expertise and global delivery capability. Our broad range of services, solutions and assets across Strategy & Consulting, Technology, Operations, Industry X and Song, together with our culture of shared success and commitment to creating 360° value, enable us to help our clients reinvent and build trusted, lasting relationships. We measure our success by the 360° value we create for our clients, each other, our shareholders, partners and communities. Visit us at accenture.com. Our AI and Data practice sits at the intersection of deep industry knowledge and applied AI and data engineering. We help the world’s leading Resources and Utilities organizations reinvent how they run — designing the data foundations, AI platforms, and governance models that turn data into trusted, production-grade intelligence. We are not looking for generalists who advise on AI in the abstract. We need practitioners who understand how enterprises actually operate, where the friction lives, and how to engineer smarter solutions using AI and data to fundamentally transform business processes and outcomes. You Are You are a senior data architect who designs enterprise data fabric solutions that provide unified, intelligent, automated access to distributed data across on-prem and multi-cloud environments.
Responsibilities
- Architect enterprise data fabric — design data fabric solutions that deliver unified, intelligent, automated access to distributed data across on-prem and multi-cloud environments.
- Integrate the connected data layer — design the integration of data virtualization, active metadata, knowledge graphs, cataloging, and automated data integration into a connected data layer for analytics and AI.
- Define reference architectures — establish reference architectures, integration patterns, and governance integration that scale across the enterprise.
- Enable data products and self-service — support self-service consumption, data products, and real-time data delivery through the fabric.
- Apply modern data paradigms — bring data mesh and data product concepts, cloud data platforms (Snowflake, Databricks, Azure Synapse, BigQuery), and streaming/API architectures to bear on client problems.
- Advise and shape solutions — engage client architects and leaders as a trusted advisor and shape solutions for major data modernization pursuits.
Requirements
- Minimum of 10 years of experience in data architecture or enterprise data engineering (in a AWS, Microsoft, Google (preferred), etc. environment)
- Minimum of 6 years of experience architect
for prose. We need to decide sections: About the role (maybe combine company overview and role description). Responsibilities (the Work bullet list). Requirements (the "Here’s What You Need" bullet list). Bonus Points could be part of Requirements or separate "Preferred Qualifications". Could make a section "Preferred Qualifications". Benefits: list of benefits. Pay: include compensation statement and salary ranges. Schedule: travel may be required. We must not create sections with filler. Ensure each heading has real content. Let's extract content. Company overview paragraph: "We Are Accenture is a leading global professional services company...". That's substantive. AI and Data practice paragraph: "Our AI and Data practice sits at the intersection...". Also substantive. Role description: "You Are You are a senior data architect who designs enterprise data fabric solutions..." That's a bit duplicated "You Are You". We'll keep as is but maybe clean? We must preserve substantive info, not invent. The text includes duplication but we should keep as is? Probably we should keep the sentence as given but maybe remove duplicate "You Are". However that would be altering content. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't say we must keep exact wording, but we should not change meaning. Removing duplicate words could be considered editing but not inventing. Might be okay. Safer to keep as is? It reads weird but it's the original. We'll keep exactly as appears: "You Are You are a senior data architect who designs enterprise data fabric solutions that provide unified, intelligent, automated access to distributed data across on-prem and multi-cloud environments." That's weird but it's what they wrote. Then responsibilities bullet list: each line starts with a bold heading? In text: "The Work Architect enterprise data fabric — design data fabric solutions that deliver unified, intelligent, automated access to distributed data across on-prem and multi-cloud environments.Integrate the connected data layer — design the integration of data virtualization, active metadata, knowledge graphs, cataloging, and automated data integration into a connected data layer for analytics and AI.Define reference architectures — establish reference architectures, integration patterns, and governance integration that scale across the enterprise.Enable data products and self-service — support self-service consumption, data products, and real-time data delivery through the fabric.Apply modern data paradigms — bring data mesh and data product concepts, cloud data platforms (Snowflake, Databricks, Azure Synapse, BigQuery), and streaming/API architectures to bear on client problems.Advise and shape solutions — engage client architects and leaders as a trusted advisor and shape solutions for major data modernization pursuits. Travel may be required for this role, varying from 0 to 100% depending on business need and client requirements." We need to split into list items. Each bullet separated by a period? Actually they are separated by periods but no line breaks. We'll parse each sentence before an em dash? The pattern: "Architect enterprise data fabric — design ..." then "Integrate the connected data layer — design ..." etc. We'll make each as
. Pay: "Compensation at Accenture varies depending on a wide array of factors, which may include but are not limited to the specific office location, role, skill set, and level of experience. As required by local law, Accenture provides a reasonable range of compensation for roles that may be hired as set forth below. We anticipate this job posting will be posted until 08/25/2026." Then the salary ranges table: list of locations with ranges. We'll keep that as a
- maybe each location as
- . Or we could keep as paragraphs. Better to use
- for list.
Schedule: "Travel may be required for this role, varying from 0 to 100% depending on business need and client requirements."
We must remove boilerplate: EEO statements, accommodation request, legal statements, etc. Also remove navigation, cookie, etc. Also remove the "Requesting an Accommodation" paragraph and everything after that until end? Actually after that there is EEO statement etc. We'll cut off before "Requesting an Accommodation". So we stop before that heading.
Also remove the line "Visit us at accenture.com." maybe keep? It's part of company overview; it's substantive? It's just a URL; could keep but it's not essential. Might keep as part of overview.
We must not include the link to benefits inside a
but it's okay. Now produce HTML fragment. Structure:
About the role
We Are Accenture is a leading global professional services company that helps the world’s leading businesses, governments and other organizations build their digital core, optimize their operations, accelerate revenue growth and enhance citizen services—creating tangible value at speed and scale. We are a talent- and innovation-led company with approximately 790,000 people serving clients in more than 120 countries. Technology is at the core of change today, and we are one of the world’s leaders in helping drive that change, with strong ecosystem relationships. We combine our strength in technology and leadership in cloud, data and AI with unmatched industry experience, functional expertise and global delivery capability. Our broad range of services, solutions and assets across Strategy & Consulting, Technology, Operations, Industry X and Song, together with our culture of shared success and commitment to creating 360° value, enable us to help our clients reinvent and build trusted, lasting relationships. We measure our success by the 360° value we create for our clients, each other, our shareholders, partners and communities. Visit us at accenture.com. Our AI and Data practice sits at the intersection of deep industry knowledge and applied AI and data engineering. We help the world’s leading Resources and Utilities organizations reinvent how they run — designing the data foundations, AI platforms, and governance models that turn data into trusted, production-grade intelligence. We are not looking for generalists who advise on AI in the abstract. We need practitioners who understand how enterprises actually operate, where the friction lives, and how to engineer smarter solutions using AI and data to fundamentally transform business processes and outcomes. You Are You are a senior data architect who designs enterprise data fabric solutions that provide unified, intelligent, automated access to distributed data across on-prem and multi-cloud environments.
Responsibilities
- Architect enterprise data fabric — design data fabric solutions that deliver unified, intelligent, automated access to distributed data across on-prem and multi-cloud environments.
- Integrate the connected data layer — design the integration of data virtualization, active metadata, knowledge graphs, cataloging, and automated data integration into a connected data layer for analytics and AI.
- Define reference architectures — establish reference architectures, integration patterns, and governance integration that scale across the enterprise.
- Enable data products and self-service — support self-service consumption, data products, and real-time data delivery through the fabric.
- Apply modern data paradigms — bring data mesh and data product concepts, cloud data platforms (Snowflake, Databricks, Azure Synapse, BigQuery), and streaming/API architectures to bear on client problems.
- Advise and shape solutions — engage client architects and leaders as a trusted advisor and shape solutions for major data modernization pursuits.
Requirements
- Minimum of 10 years of experience in data architecture or enterprise data engineering (in a AWS, Microsoft, Google (preferred), etc. environment)
- Minimum of 6 years of experience architect
- for list.
Schedule: "Travel may be required for this role, varying from 0 to 100% depending on business need and client requirements."
We must remove boilerplate: EEO statements, accommodation request, legal statements, etc. Also remove navigation, cookie, etc. Also remove the "Requesting an Accommodation" paragraph and everything after that until end? Actually after that there is EEO statement etc. We'll cut off before "Requesting an Accommodation". So we stop before that heading.
Also remove the line "Visit us at accenture.com." maybe keep? It's part of company overview; it's substantive? It's just a URL; could keep but it's not essential. Might keep as part of overview.
We must not include the link to benefits inside a