Data Architecture & Engineering Manager

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. First, there is a long intro about Accenture, but that is not part of the job description? The posting includes "We Are Accenture ..." then "Our AI and Data practice ..." then "You Are ..." then "The Work ..." then "Here’s What You Need ..." then "Bonus Points If You ..." then "Compensation at Accenture varies ..." then benefits list, then location salary ranges. We need to extract sections: - About the role: maybe the description of role and responsibilities. The "You Are" and "The Work" sections describe responsibilities. Could be "Responsibilities" heading. - Requirements: the "Here’s What You Need" list of minimum experience. - Qualifications: maybe the "Bonus Points If You" could be qualifications or preferred qualifications. - Skills: maybe combine some skill sets? But we can treat "Requirements" as skills and experience. - Benefits: there is a paragraph about benefits and a link. - Pay: there is compensation range per location. So we need a Pay section with that info. - Schedule: travel may be required varying 0-100% depending on business need. That's schedule info. We must not include headings with filler text. So we need to ensure each heading has substantive content. We must not repeat job title as heading. Not include Job ID. We must remove boilerplate: EEO, accommodation request, legal statements, etc. We must preserve all substantive information; do not invent or summarize away detail. We need to output only HTML fragment: use

for headings,

• for lists,

  for prose. We need to include sections only when posting has real specific content. Let's extract content. First, "About the role": maybe a short paragraph summarizing role: "You are a data architect who designs enterprise data fabric solutions that provide unified, intelligent, automated access to distributed data across on-prem and multi-cloud environments. You bring together data virtualization, active metadata, knowledge graphs, cataloging, and automated integration into a connected data layer that powers analytics and AI — and you can define the reference architectures and integration patterns that make it real." That's from "You Are". Could be placed under About the role or Responsibilities. Let's decide: Use "About the role" for a brief overview, and "Responsibilities" for detailed duties. But we need to avoid duplication. We could put the overview in About the role, and then list responsibilities under Responsibilities. Let's extract responsibilities from "The Work": bullet-like sentences each starting with a verb. List: - 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. That last one is schedule/travel. We'll put travel under Schedule section. Now Requirements: "Here’s What You Need" list: - Minimum of 7 years of experience in data architecture or enterprise data engineering (in a AWS, Microsoft, Google (preferred), etc. environment) - Minimum of 4 years of experience architecting data fabric solutions (data virtualization, active metadata, knowledge graphs, automated integration) - Minimum of 4 years of experience with cloud data platforms (e.g., Snowflake, Databricks, Azure Synapse, BigQuery) - Minimum of 3 years of experience with data integration/ETL/ELT and metadata & lineage tooling - Minimum of 3 years of experience with API and streaming architectures - Bachelor's degree or equivalent (minimum 12 years' work experience). If Associate’s Degree, must have equivalent minimum 6-year work experience We should keep each as list items. Now Bonus Points If You: (preferred qualifications) - 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 can put these under Qualifications or Skills. Since we have a Qualifications heading, we can put bonus points there. Now Benefits: paragraph: "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 need to keep the link as is. Now Pay: compensation ranges per location. We need to include that info. The posting includes a table-ish list: "Role Location Annual Salary Range California $94,400 to $293,800 Cleveland $87,400 to $235,000 Colorado $94,400 to $253,800 District of Columbia $100,500 to $270,300 Illinois $87,400 to $253,800 Maine $80,400 to $216,200 Maryland $94,400 to $253,800 Massachusetts $94,400 to $270,300 Minnesota $94,400 to $253,800 New York $87,400 to $293,800 New Jersey $100,500 to $293,800 Virginia $87,400 to $270,300 Washington $100,500 to $270,300" Then a list of many cities: "Seattle, WA Albany, NY Arlington, VA Atlanta, GA Austin, TX Beaverton, OR Bentonville, AR Boston, MA Carmel, IN Charlotte, NC Chicago, IL Cincinnati, OH Cleveland, OH Columbus, OH Culver City, CA Denver, CO Detroit, MI Hartford, CT Houston, TX Irving, TX Kirkland, WA Miami, FL Milwaukee, WI Minneapolis, MN Morristown, NJ Mountain View, CA Nashville, TN New York City, NY Oklahoma City, OK Overland Park, KS Philadelphia, PA Pittsburgh, PA Raleigh, NC Sacramento, CA San Diego, CA San Francisco, CA Scottsdale, AZ St. Louis, MO St. Petersburg, FL Walnut Creek, CA" Probably those are locations where the salary ranges apply? The earlier list gave ranges per state/region; then the city list maybe just additional locations. We need to preserve all substantive information. So we should include both the state ranges and the city list. We can format as a

  list of items each location with its range, but we don't have ranges for each city; only for states. The city list may be just locations where the role is available; we can list them as separate items without range. Better: Provide Pay section with two parts: a paragraph describing that compensation varies by location, then a list of location-based salary ranges (state/region) and then a list of specific cities. We must not invent or summarize away detail; we need to preserve the exact text? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the exact wording as much as possible, but we can reformat into HTML lists. We need to avoid adding extra info not present. Thus for Pay we can output:

  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.

  • California $94,400 to $293,800
  • Cleveland $87,400 to $235,000
  • Colorado $94,400 to $253,800
  • District of Columbia $100,500 to $270,300
  • Illinois $87,400 to $253,800
  • Maine $80,400 to $216,200
  • Maryland $94,400 to $253,800
  • Massachusetts $94,400 to $270,300
  • Minnesota $94,400 to $253,800
  • New York $87,400 to $293,800
  • New Jersey $100,500 to $293,800
  • Virginia $87,400 to $270,300
  • Washington $100,500 to $270,300

  Additional locations include: Seattle, WA; Albany, NY; Arlington, VA; Atlanta, GA; Austin, TX; Beaverton, OR; Bentonville, AR; Boston, MA; Carmel, IN; Charlotte, NC; Chicago, IL; Cincinnati, OH; Cleveland, OH; Columbus, OH; Culver City, CA; Denver, CO; Detroit, MI; Hartford, CT; Houston, TX; Irving, TX; Kirkland, WA; Miami, FL; Milwaukee, WI; Minneapolis, MN; Morristown, NJ; Mountain View, CA; Nashville, TN; New York City, NY; Oklahoma City, OK; Overland Park, KS; Philadelphia, PA; Pittsburgh, PA; Raleigh, NC; Sacramento, CA; San Diego, CA; San Francisco, CA; Scottsdale, AZ; St. Louis, MO; St. Petersburg, FL; Walnut Creek, CA

  We need to ensure we didn't add any info not present. The original had "Role Location Annual Salary Range" then list. We kept that. Now Schedule: travel may be required varying 0-100% depending on business need and client requirements. That's from responsibilities list. We'll put under Schedule.

  Schedule

  Travel may be required for this role, varying from 0 to 100% depending on business need and client requirements.

  Now Responsibilities: we have list of duties. We'll put under

  Responsibilities

  with
  • each duty (excluding travel line). Let's list the six duties. Now About the role: we could give a short paragraph summarizing role: maybe combine the "You Are" paragraph. Let's use that as About the role.

    About the role