Director, Enterprise Data Architecture

We need to output HTML fragment with headings

for sections present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. Let's parse the posting. We have: - Req ID, Location, Areas of Interest, Pay Transparency Salary Range, Application Deadline: these are metadata; we should not make headings for them, fold minor metadata into short

or drop it. So we can include a short paragraph with location, salary range maybe? But Pay section only if posting actually states them. It does state Salary Range: $130,000 - $205,000. So we can include a Pay section with that info. Also maybe Benefits? Not mentioned explicitly besides "excellent training and development". That's a benefit? Could be considered benefits but not explicit list. The instruction: never create Benefits section unless posting actually states them. It mentions "excellent training and development". That's a benefit but not a list. Might be okay to include a Benefits section with that detail? However they said "Prefer a few substantive sections over many thin ones." Might be better to incorporate that into About the role or Requirements. Probably not create Benefits. Schedule: not mentioned. So omit. About the role: we have summary paragraph: "Build data that matters at a bank with deep roots and bold plans..." That's about the role. Also "Job Description" paragraph. Could combine. Responsibilities: The bullet list under "How You'll Spend Your Time" is responsibilities. Requirements: Education & Experience Requirements paragraph includes requirements. Qualifications: Might be overlapping with requirements; but we can treat "Education & Experience Requirements" as Qualifications. However we need to follow headings: we can have Requirements and Qualifications separate if content distinct. The posting has "Education & Experience Requirements" which includes both education and experience and a list of competencies. That could be Qualifications. We could have Requirements (maybe minimal) and Qualifications (the list). But to avoid thin sections, maybe combine into one Qualifications section. However the instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to include. We have: - About the role: summary and job description paragraphs. - Responsibilities: the list of "How You'll Spend Your Time" items. - Qualifications: the Education & Experience Requirements paragraph plus the list of competencies (Deep expertise..., Proven ability..., etc). That is qualifications. - Skills: maybe we could extract skills from the list (e.g., data management, data integration, etc). But the qualifications already cover skills; we could create a Skills section listing specific skills like data management, data integration, manipulation, governance, master data management, architecture strategies, blueprints, roadmaps, strategic thinking, data lifecycle, emerging tech trends, problem solving, product management, agile methodologies, navigating organizational dynamics, communication, leadership. That would be a thin section but maybe okay if we have content. However we already have those in qualifications; splitting may create thin sections. Better to keep Qualifications and not create Skills. - Pay: Salary Range. - Benefits: not explicit list; we have "excellent training and development". Could be a benefit but not a list. Might be okay to include a Benefits section with that sentence. However they said never create Benefits unless posting actually states them. It does state "excellent training and development". That's a benefit. So we can include Benefits section with that sentence. - Schedule: none. Thus sections: About the role, Responsibilities, Qualifications, Pay, Benefits. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information; do not invent or summarize away detail. Remove boilerplate etc. We need to include location maybe in About the role? Could add a short paragraph with location and maybe requisition ID? But they said fold minor metadata into a short

  or drop it. So we can include a short paragraph at top with location and maybe salary? But salary we put in Pay section. Location we could put in About the role as a short paragraph. Let's extract content: About the role: - "Build data that matters at a bank with deep roots and bold plans. Our team is advancing a cloud, data, and AI transformation—creating an enterprise data lake, governed products, and scalable analytics. By connecting data across the bank, we help teams make smarter decisions, manage risk, and better serve clients. Our work drives stronger performance, more efficient operations, and more consistent experiences enterprise‑wide." - Also maybe "Job Description The Director, Enterprise Information Architecture will lead an expert team of diverse, highly skilled data professionals including Enterprise Data Architects, Data Modelers and Data Product Managers. This team will be responsible for modernizing and managing the enterprise data architecture including structured and unstructured data, advancing data technology and data products in alignment with the Enterprise Data Vision and Strategy. The Director, Enterprise Information Architecture will collaborate with the Chief Data Officer, Data Management team directors, Data Governance, and Enterprise Architecture to produce, and advance strategic playbooks and roadmaps to grow and mature the Enterprise Information Architecture practice at BOKF." We can combine these into About the role prose. Responsibilities: list from "How You'll Spend Your Time": - develop and execute the enterprise data strategy and architecture aligned with business goals. - create strategic roadmaps and business cases to modernize data platforms. - identify opportunities to improve data accessibility, usability, and performance. - lead and develop a team delivering enterprise data solutions and products. - enhance and evolve the enterprise data model to support organization-wide data usage. - ensure projects align with enterprise data architecture principles and standards. - provide data architecture leadership, solution planning, and delivery cost estimates. Each as

• . Qualifications: Education & Experience Requirements paragraph plus list of competencies. Paragraph: "This level of knowledge is normally acquired through completion of Bachelor's degree in computer science, information-technology, engineering, system analysis or a related study with a minimum of 10+ years of experience in at least two data related disciplines, including data management, data governance, data product development, database administration and management or equivalent combination of education and experience. Experience working in a relevant industry is preferred." Then list of competencies (starting with "Broad exposure to diverse data technologies, platforms, and processing environments." and then each sentence ends with a period). Let's extract each as separate bullet maybe? They are sentences separated by periods. We'll treat each as a bullet under Qualifications (or maybe under Skills). But we can keep them as part of Qualifications prose? The instruction: Use
  • for any list of duties/requirements/benefits. The qualifications list is a list of requirements, so we should make a
    • . So we need to split into items. List items: - Broad exposure to diverse data technologies, platforms, and processing environments. - Deep expertise in data management, including data integration, manipulation, governance, and master data management. - Proven ability to develop architecture strategies, blueprints, and roadmaps. - Strategic thinker with the ability to balance long-term vision and short-term execution. - Strong understanding of data lifecycle—generation, flow, management, and usage across the enterprise. - Awareness of emerging technology trends and their practical application to evolving business models. - Innovative problem-solver with a results-driven mindset. - Solid grasp of product management and agile methodologies; able to guide agile teams on technical opportunities, risks, and architectural considerations. - Skilled in navigating complex organizational dynamics, building strategic relationships, and influencing stakeholders. - Effective communicator, capable of presenting technical concepts to both executive and technical audiences. - Demonstrated leadership in guiding diverse teams toward ambitious goals and leveraging networks to drive outcomes. Also maybe include "BOK Financial Corporation Group is a stable and financially strong organization that provides excellent training and development to support building the long term careers of employees. With passion, skill and partnership you can make an impact on the success of the bank, customers and your own career! Apply today and take the first step towards your next career opportunity!" That's more like a closing marketing; could be considered Benefits? But we already have Benefits for training and development. Might incorporate that into Benefits. Benefits: "excellent training and development" plus maybe "stable and financially strong organization", "opportunity to make impact". We'll keep it simple: "excellent training and development" as benefit. Pay: Salary Range: $130,000 - $205,000. We also have location: Tulsa -TUL, Dallas -DAL, Denver -DEN. Could be a short paragraph. We must not repeat job title as heading. Not include Job ID/requisition numbers as headings. We'll output HTML fragment:

      Location: Tulsa (TUL), Dallas (DAL), Denver (DEN)

      About the role

      Build data that matters at a bank with deep roots and bold plans. Our team is advancing a cloud, data, and AI transformation—creating an enterprise data lake, governed products, and scalable analytics. By connecting data across the bank, we help teams make smarter decisions, manage risk, and better serve clients. Our work drives stronger performance, more efficient operations, and more consistent experiences enterprise‑wide. The Director, Enterprise Information Architecture will lead an expert team of diverse, highly skilled data professionals including Enterprise Data Architects, Data Modelers and Data Product Managers. This team will be responsible for modernizing and managing the enterprise data architecture including structured and unstructured data, advancing data technology and data products in alignment with the Enterprise Data Vision and Strategy. The Director, Enterprise Information Architecture will collaborate with the Chief Data Officer, Data Management team directors, Data Governance, and Enterprise Architecture to produce, and advance strategic playbooks and roadmaps to grow and mature the Enterprise Information Architecture practice at BOKF.

      Responsibilities

      • Develop and execute the enterprise data strategy and architecture aligned with business goals.
      • Create strategic roadmaps and business cases to modernize data platforms.
      • Identify opportunities to improve data accessibility, usability, and performance.
      • Lead and develop a team delivering enterprise data solutions and products.
      • Enhance and evolve the enterprise data model to support organization-wide data usage.
      • Ensure projects align with enterprise data architecture principles and standards.
      • Provide data architecture leadership, solution planning, and delivery cost estimates.

      Qualifications

      This level of knowledge is normally acquired through completion of Bachelor's degree in computer science, information-technology, engineering, system analysis or a related study with a minimum of 10+ years of experience in at least two data related disciplines, including data management, data governance, data product development, database administration and management or equivalent combination of education and experience. Experience working in a relevant industry is preferred.

      • Broad exposure to diverse data technologies, platforms, and processing environments.
      • Deep expertise in data management, including data integration, manipulation, governance, and master data management.
      • Proven ability to develop architecture strategies, blueprints, and roadmaps.
      • Strategic thinker with the ability to balance long-term vision and short-term execution.
      • Strong understanding of data lifecycle—generation, flow, management, and usage across the enterprise.
      • Awareness of emerging technology trends and their practical application to evolving business models.
      • Innovative problem-solver with a results-driven mindset.
      • Solid grasp of product management and agile methodologies; able to guide agile teams on technical opportunities, risks, and architectural considerations.
      • Skilled in navigating complex organizational dynamics, building strategic relationships, and influencing stakeholders.
      • Effective communicator, capable of presenting technical concepts to both executive and technical audiences.
      • Demonstrated leadership in guiding diverse teams toward ambitious goals and leveraging networks to drive outcomes.