Applied AI Engineer

We need to output HTML fragment with sections: About the role? The posting includes a paragraph about ERCOT environment, then Job Summary, Job Duties, Experience, Required Skills And Knowledge, Preferred (maybe separate), EDUCATION, TOOLS & TECHNOLOGY, CERTIFICATION, WORK LOCATION, Expected Salary Range. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections when posting has real specific content. We need to map content to these headings. We have: - About the role: could be the introductory paragraph about ERCOT environment and mission. That's a prose. - Responsibilities: Job Duties list. - Requirements: Experience Requires minimum 5 years... maybe also Education. - Qualifications: maybe Education and Certifications. - Skills: Required Skills And Knowledge and Preferred. - Benefits: Not mentioned. - Pay: Expected Salary Range. - Schedule: WORK LOCATION: Hybrid schedule in Taylor, TX 2 days per week. That's schedule info. We should not repeat job title. No Job ID. We need to remove boilerplate: EEO etc. Remove equal opportunity lines. Also remove "ERCOT is firmly committed to equal employment..." etc. We need to preserve all substantive info. We need to output only HTML fragment, no /, no markdown fences. We need to use

for each section heading. Use

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

  for prose. We need to decide which sections to include. Let's extract content: Intro paragraph: "At ERCOT, our diverse and dynamic work environment provides a platform on which employees can work together to build the future of the Texas power grid and wholesale market utilizing the latest technologies and resources. We encourage you to join our talented, dedicated workforce to develop world-class solutions for today and tomorrow’s energy challenges while learning new skills and growing your career. ERCOT is committed to fostering inclusion at all levels of our company. It is the cornerstone of our corporate values of accountability, leadership, innovation, trust, and expertise. We know that individuals with a wide variety of talents, ideas, and experiences propel the innovation that drives our success. An inclusive and diverse workforce strengthens us and allows for a collaborative environment to solve the challenges that face our industry today and in the future." That's About the role. Job Summary: "Applies knowledge of generative AI application development, agent orchestration, retrieval architecture, and evaluation methodology to deliver production AI solutions. Follows established AI governance, security review, and evaluation processes to deploy reliable, auditable systems. Operates in a regulated environment where delivery speed is balanced against required governance and review gates." That could be part of About the role or separate? Could be under Responsibilities? But we have Job Duties separate. We could treat Job Summary as part of About the role or maybe as a brief overview. Since we need sections only when content exists, we could include a section "About the role" covering the intro + Job Summary? Or we could split: About the role (intro), Responsibilities (Job Duties), Requirements (Experience + Education + Certifications), Skills (Required Skills And Knowledge + Preferred), Pay (Salary Range), Schedule (Work location/hybrid). Benefits not present, omit. We need to use

  • for any list of duties/requirements/benefits. So for Responsibilities we need a list. Job Duties are a series of sentences separated by periods; we can turn each into a list item. Similarly, Requirements could be a list: Experience (5 years), Education (Bachelor's), Certification (preferred). But we need to decide if we want separate sections for Requirements and Qualifications. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have Requirements (experience) and Qualifications (education/certifications). Or we could combine. Let's map: - About the role: intro paragraph + Job Summary? Might be too much but okay. - Responsibilities: Job Duties list. - Requirements: Experience Requires minimum 5 years job related work experience in AI/ML or software engineering in excess of degree requirements. - Qualifications: EDUCATION (Bachelor's Degree...), CERTIFICATION (Cloud or AI/ML certification preferred). Also maybe Preferred items? But Preferred is more like nice-to-have; could go under Skills or Qualifications. We'll treat Preferred as part of Skills. - Skills: Required Skills And Knowledge list, plus Preferred items (Solution and system architecture..., Large-scale data platforms..., Experience in regulated industry..., Multi-agent orchestration...). Also maybe Tools & Technology? That's a list of tools; could be under Skills as well. But we have a separate heading for Skills; we can include tools there. - Pay: Expected Salary Range. - Schedule: WORK LOCATION: Hybrid schedule in Taylor, TX 2 days per week. We must not include filler like "commensurate with experience". Not present. We need to ensure we don't repeat content. Let's extract each piece. Intro paragraph (About the role) we have. Job Summary: we could include in About the role as a second paragraph. Responsibilities: list each duty. Duties sentences: 1. Translates ambiguous business problems into scoped technical roadmaps, and identifies constraints (data access, compliance, latency, cost) before development begins. 2. Designs and builds production agentic systems, covering planning, tool-calling, multi-step reasoning, memory, and error recovery, using modern orchestration frameworks such as LangGraph or Microsoft Agent Framework. 3. Implements production RAG pipelines, including chunking, embeddings, hybrid search, reranking, retrieval-quality evaluation, and content freshness. 4. Builds and extends connectors that give agents secure, standardized access to enterprise tools and data. 5. Deploys applications onto managed cloud platforms and integrates them with enterprise systems and collaboration tools. 6. Builds evaluation suites, tracing, and rollback paths so agents are reliable in production rather than demonstrations. 7. Monitors, debugs, and improves deployed applications against evaluation metrics. 8. Applies sound system-design principles. Defines application architecture, data flows, and integration boundaries, and designs for scalability, reliability, latency, and cost. 9. Codifies repeatable patterns, turning successful builds into reusable components and reference architecture the team can leverage. 10. Works directly with non-technical business owners to understand their workflows, and maintains current knowledge of evolving LLM capabilities, implementation patterns, and AI development stacks. Note: Some sentences have two sentences combined (like #8). We'll keep as one item. Requirements: Experience Requires minimum 5 years job related work experience in AI/ML or software engineering in excess of degree requirements. Qualifications: - EDUCATION: Bachelor's Degree: Computer Science, Data Science, Information Systems, Engineering, or related field (Required) or a combination of education and experience that provides equivalent knowledge to a major in such fields is required - CERTIFICATION: Cloud or AI/ML certification (Azure AI Engineer, AWS Machine Learning, or Databricks) (Preferred) We could also include that certification is preferred. Skills: Required Skills And Knowledge list: - Proven record of building and deploying production-grade autonomous agents, not prototypes. - Agent orchestration frameworks (LangGraph, Microsoft Agent Framework, or comparable). - Production RAG with vector search and vector databases (pgvector, Azure AI Search, Databricks Vector Search) - Strong Python and hands-on LLM API integration. - System-design fundamentals: scalable, reliable, maintainable services, API and integration-boundary design, and trade-offs across latency, throughput, and cost. - Building or extending tool and data connectors for LLM applications. - Deploying and operating applications on a managed cloud platform. - AI governance, model lifecycle, and evaluation methodology. - Stakeholder and discovery skills. Works directly with non-technical business owners, scopes ambiguity, and operates autonomously. Preferred items: - Solution and system architecture across multiple applications, with security-by-design and reference architecture. - Large-scale data platforms (Databricks) for retrieval, feature, or pipeline work. - Experience in a regulated industry (energy, finance, healthcare) or an audit-driven environment. - Multi-agent orchestration and context engineering. Tools & Technology list: we could include under Skills as well, but maybe better to include as part of Skills. However the instruction says use headings like Skills; we can put all skills-related content there, including tools. Thus Skills section will contain two lists: Required Skills And Knowledge (list), Preferred (list), Tools & Technology (list). Could combine into one list but better to separate with subheadings? But we cannot add extra headings beyond the allowed ones? The instruction only says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections. It doesn't say we cannot have other headings, but to be safe we stick to those. So we can't add subheadings like "Tools & Technology". We could incorporate tools into the Skills list as items. Thus Skills section will have a list that includes required skills, preferred skills, and tools. We need to ensure we don't lose any info. Let's compile Skills list items: Required Skills And Knowledge: - Proven record of building and deploying production-grade autonomous agents, not prototypes. - Agent orchestration frameworks (LangGraph, Microsoft Agent Framework, or comparable). - Production RAG with vector search and vector databases (pgvector, Azure AI Search, Databricks Vector Search) - Strong Python and hands-on LLM API integration. - System-design fundamentals: scalable, reliable, maintainable services, API and integration-boundary design, and trade-offs across latency, throughput, and cost. - Building or extending tool and data connectors for LLM applications. - Deploying and operating applications on a managed cloud platform. - AI governance, model lifecycle, and evaluation methodology. - Stakeholder and discovery skills. Works directly with non-technical business owners, scopes ambiguity, and operates autonomously. Preferred: - Solution and system architecture across multiple applications, with security-by-design and reference architecture. - Large-scale data platforms (Databricks) for retrieval, feature, or pipeline work. - Experience in a regulated industry (energy, finance, healthcare) or an audit-driven environment. - Multi-agent orchestration and context engineering. Tools & Technology: - Agent & LLM Frameworks: LangGraph, Microsoft Agent Framework, LangChain, LlamaIndex - LLM Platforms & APIs: Claude API, Azure OpenAI, OpenAI API, model routing and evaluation frameworks - AI Coding Assistants: Claude Code, OpenAI Codex, GitHub Copilot, Microsoft Copilot Studio - Retrieval & Vector Search: Azure AI Search, Databricks Vector Search, pgvector - Data & Analytics: Databricks, Power BI, SQL, Oracle DB, PostgreSQL - Connectors & Integration: MCP (Model Context Protocol), REST APIs, enterprise system connectors, Teams integration - Cloud & Deployment: Azure, OpenShift (Private Cloud / On-Premises), Docker, Kubernetes, Helm - CI/CD & Source Control: GitHub, GitHub Actions, Git and pull-request workflows - Observability & Evaluation: Tracing, evaluation harnesses, LLM observability, logging and monitoring - ITSM & Agile Tooling: ServiceNow, Jira - Scripting & Languages: Python, PowerShell We need to include all. Pay: Expected Salary Range $145,000 - $200,000 Schedule: Hybrid schedule in Taylor, TX 2 days per week. Now produce HTML. Structure:

    About the role

    Intro paragraph...

    Job Summary...