Director, AI & Data Platforms

We need to output HTML fragment with sections: About the role? Actually the posting includes "Who We Are" and description. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections that have real content. The posting includes: Who We Are (description of division), then "The Director of AI & Data Platforms is responsible for leading..." That's about the role. Then "WHAT WILL YOU DO:" with bullet-like paragraphs (leadership, enterprise enablement, etc). That's responsibilities. Then "WHAT WILL YOU BRING" includes Required Education, Required Experience, Required Registration, Certification, or Licensure, Knowledge, Skills, and Abilities. That's qualifications/requirements/skills. There's no explicit Benefits, Pay, Schedule. So we should not include those sections. We need to preserve all substantive info, no boilerplate like Requisition ID, Employment Type, etc. We can fold minor metadata into a short

or drop it. Probably we can include a short

with location and maybe requisition ID? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include a

with location and maybe requisition ID? It says minor metadata, we can include location and maybe requisition ID in a paragraph. But we could drop it entirely. Safer to include a short paragraph with location and requisition ID? It says fold minor metadata into a short

or drop it. So we can include a

containing location and requisition ID. Not as heading. We must not repeat job title as heading. The page already shows it, so we don't add heading for title. We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We'll decide which sections to include: About the role (maybe from "Who We Are" and description), Responsibilities (WHAT WILL YOU DO), Requirements (maybe Required Education/Experience), Qualifications (maybe same as Requirements?), Skills (Knowledge, Skills, and Abilities). We need to avoid duplication. Could combine Requirements and Qualifications? But we need to follow instruction: Use headings only when posting has real specific content. We have content for About the role, Responsibilities, Required Education/Experience (requirements), Knowledge, Skills, and Abilities (skills). Could also include Qualifications (maybe same as requirements). To avoid thin sections, we could merge Education/Experience into Requirements, and Skills into Skills section. Qualifications maybe not needed if we have Requirements and Skills. But we could include Qualifications as a heading covering Required Education/Experience and maybe certifications. However we have no certifications. Might be okay to have Requirements and Skills only. Let's decide sections: - About the role: includes "Who We Are" paragraph and the description of the Director role. - Responsibilities: the "WHAT WILL YOU DO:" sections (Leadership, Enterprise Enablement & Adoption, Enterprise AI & Data Platform Strategy, Architecture, and Governance, Platform Engineering, Operations, and Enablement). We'll turn each bullet into

• . - Requirements: Required Education and Required Experience (including substitution notes). We'll list as
  • . - Skills: Knowledge, Skills, and Abilities section. We'll break into Knowledge, Skills, Ability sublists? Could just list as
    • each item. We must not include Benefits, Pay, Schedule. We need to preserve all substantive information: ensure we don't lose any details. Let's extract text. Who We Are: "The Information Technology (IT) Division lays the foundation for TRS to deliver excellent service experiences across the organization and with our members. We serve with purpose through mentorship and collaboration across a broad variety of teams unified by innovation to create technology and information solutions that have a positive impact on our members’ lives. We invite you to join one of Austin’s Top Workplaces. TRS offers a best-in-class combination of technology and continuous learning opportunities to equip you to solve problems, expand your knowledge, and create impact for 1 in 20 Texans." Then role description: "The Director of AI & Data Platforms is responsible for leading the enterprise strategy, architecture, engineering, and operations of TRS’s artificial intelligence and data platforms. The incumbent will own the shared AI and data foundations that enable scalable, secure, and compliant analytics and AI capabilities across the organization, and ensure that platform capabilities, governance enforcement, and architecture standards are consistently applied to support business-driven data delivery and AI initiatives. This role is a key member of IT leadership and serves as the enterprise point of accountability for AI and data platform execution." Now Responsibilities sections: Leadership: paragraphs: - Builds and leads a high-performing team of platform engineers, architects, AI engineers, and governance specialists. - Develops workforce capabilities in AI and data platform engineering. - Partners with IT leadership on organizational strategy and staffing growth. - Directs department staff, directly and through team leaders, including hiring, directing, monitoring, evaluating, and motivating staff. - Establishes clear career paths and role specialization within AI and data platform domains. - Provides direction, monitors team work loads and work processes, and takes corrective actions as needed to ensure that all operations are covered, and productivity, customer service, and quality goals are met. - Ensures compliance with applicable federal, state, agency, and department policies, procedures, rules, and regulations. - Assesses training needs of team members and arranges for or provides training, coaching, and technical assistance. Enterprise Enablement & Adoption: - Serves as the enabling technology partner for Data Delivery and LOB teams. - Provides “paved roads” for AI and data delivery teams. - Supports developer experience, onboarding, and platform adoption. - Reduces duplication and tool sprawl across the enterprise. - Partners closely with Enterprise Technology Services to achieve enablement goals. Enterprise AI & Data Platform Strategy, Architecture, and Governance: - Defines and execute the strategy for enterprise AI and data platforms (e.g., Fabric, Databricks, Azure AI services). - Oversees platform architecture, engineering, and lifecycle management. - Ensures scalability, reliability, performance, and cost optimization (FinOps). - Establishes and maintains enterprise AI and data platform architecture standards. - Ensures the platform provides the infrastructure and tooling to support AI-ready data patterns (e.g., semantic layers, RAG, data integration patterns). - Drive consistency in interoperability and platform alignment. - Owns platform architecture across the AI and data estate; sets architectural direction for how AI capabilities are built, deployed, and governed on shared infrastructure. - Owns enterprise data governance tooling and enforcement mechanisms, including data catalog (Purview or equivalent), data classification and sensitivity labeling, access controls and policy enforcement. - Ensure governance is implemented through platform capabilities, not manual processes. - Partner with enterprise governance bodies to align policy with technical enforcement. Platform Engineering, Operations, and Enablement: - Leads platform operations including monitoring, incident management, and reliability. - Owns environment strategy (sandbox, development, testing, production). - Establishes DevOps practices including CI/CD, version control, and deployment standards. - Ensures secure, compliant, and auditable platform usage. - Leads development of reusable AI capabilities (e.g., agents, copilots, orchestration frameworks). - Supports AI experimentation, R&D, and transition to production-ready capabilities. - Delivers shared services and patterns that enable downstream delivery teams. - Performs related work as assigned. Now WHAT WILL YOU BRING: Required Education: - Bachelor’s degree from an accredited college or university in Computer Science, Information Systems, Engineering, or a closely related field. - High school diploma or equivalent and additional full-time experience in data platforms, cloud architecture, IT enterprise or related experience may be substituted on an equivalent year-for-year basis. Required Experience: - Eight (8) years of full-time directly related, progressively responsible experience in data platforms, cloud architecture, IT enterprise or related experience. - Four (4) years of experience leading, or supervising the work of others, required. - Experience with enterprise AI platforms and agentic frameworks (e.g., Azure AI Foundry, Azure OpenAI Service, Copilot Studio, Databricks Model Serving). - Experience in enterprise AI adoption practices through agentic frameworks (LangChain, Semantic Kernel/Microsoft Agent Framework, Azure AI Agent Service), RAG pipeline design, MCP integrations, prompt engineering and responsible AI frameworks, AI guardrails and content safety. - A master's degree or doctoral degree in a closely related field may be substituted on an equivalent year-for-year basis. Required Registration, Certification, or Licensure: - None. Knowledge, Skills, and Abilities: Knowledge of: - Data governance, security, and compliance frameworks. - Modern data platforms (e.g., Databricks, Azure, Fabric, Snowflake). - People leadership in the data platform, data engineering and data operations space. - A diverse base of knowledge that allows you to help your team solve complex technical problems. - The principles, practices, and techniques of computer programming and systems analysis and design; all phases of software development and project management; and computing standards and development methodologies, including Systems Development Life Cycle methodologies. - Varying technological architectures, security, and technology trends. - Agency computing standards, security, and development methodologies. Skills in: - Leading large-scale data and AI platform initiatives - Multi-agent orchestration patterns (sequential, concurrent, handoff) and agent governance/observability tooling. - Leading analytics project teams; and organizing, managing, and motivating staff to meet project goals and objectives. - Analyzing problems and devising innovative and effective solutions, including collecting and analyzing complex data, evaluating information and business processes, and drawing logical conclusions. - Designing complex computer programs. - Project planning and management; planning, organizing, and coordinating work assignments to effectively meet frequent and/or multiple deadlines; handling multiple tasks simultaneously; and managing conflicting priorities and demands. - Communicating complex technical information to people of varying technical backgrounds. Ability to: - Establish and maintain harmonious working relationships with co-workers, agency staff, and external contacts. - Work effectively in a professional team environment. - Plan strategically and align with peers in complex technical and operating environments. Also there is a MOS Codes paragraph about veterans; that's maybe minor metadata? It's not boilerplate but it's a note encouraging veterans. Could be included under Requirements or maybe as a note. It's substantive? It's about eligibility. Might be considered minor metadata? It's not boilerplate but it's a note. I'd include it maybe under Requirements as a note. But we can also drop it as minor metadata? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The MOS Codes paragraph is not exactly boilerplate; it's about veterans. Might be considered EEO? It's referencing a crosswalk. Could be considered EEO-related. Safer to drop it? The instruction says remove EEO/equal-opportunity boilerplate. This is about veterans, which is a type of EEO. So we should drop that paragraph. Also there is a line: "Please contact Talent Acquisition at careers@trs.texas.gov with questions or for additional information. To view all job vacancies, visit www.trs.texas.gov/careers or www.trs.csod.com/careersite. For more information, visit www.trs.texas.gov." That's application instructions, should be removed. Also there is "Requisition ID: req1420Employment Type: Unclassified Regular Full-Time (URF)Division: Enterprise AI & Data MgmtCompensation: Depends on Qualification Job Closing: 10/10/2026 at 11:59 CSTLocation: TRS Headquarters Building 2 1900 Aldrich StreetAustin, Texas, 78723United States". That's metadata; we can fold location into a short

      . We'll include location maybe. We must not repeat job title as heading. We'll not include any heading for title. Now produce HTML