Azure Databricks Admin

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Cognizant" and then "Azure Databricks Administrator". The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include. The posting includes: - About Cognizant (company description) - Azure Databricks Administrator (role description) - Work Model Remote - United States (maybe part of location) - Responsibilities (long list) - Required Qualifications - Preferred Qualifications - Salary And Other Compensation (Pay) - Benefits - Why Choose Cognizant? (maybe not needed) - Equal Opportunity Employer (boilerplate, remove) - etc. We need to produce sections: maybe "About the role", "Responsibilities", "Qualifications" (could combine required and preferred?), "Benefits", "Pay". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which are present. We have About Cognizant description; could be "About the role" maybe includes role summary. The posting includes a paragraph after role title: "Cognizant is seeking a highly skilled Azure Databricks Administrator...". That's role summary. So we can put that under

About the role

. Responsibilities: we have a big list; we can put under

Responsibilities

with

• each bullet. Qualifications: we have Required Qualifications and Preferred Qualifications. Could combine under

  Qualifications

  with two sublists? Or separate Required and Preferred? The instruction says we can have Qualifications heading. We could put Required under

  Qualifications

  and maybe Preferred under another heading like "Preferred Qualifications"? But they said prefer few substantive sections over many thin ones. Could combine both under Qualifications with two
  maybe with headings inside? But we cannot add extra headings besides h3? We could embed Required etc inside

  . Simpler: have

  Qualifications

  then a

  with required qualifications list as

  and then another

  for preferred. That's okay. Benefits: we have Benefits section with list. Pay: we have Salary And Other Compensation with salary range and incentive. So we can have

  Pay

  with that info. Schedule: not mentioned; we have Work Model Remote - United States. That's not a schedule but location/work model. Could be placed under About the role or maybe a separate section? There's no Schedule heading content; we should not create Schedule unless present. So omit. We must remove boilerplate: Equal Opportunity Employer, etc. Also remove "Why Choose Cognizant?" maybe not needed but could be considered substantive? It's more marketing; but we could keep under About the role? The instruction says remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Why Choose Cognizant?" is not boilerplate but could be considered fluff; but it's substantive? It's marketing; but we could keep as part of About the role? Safer to omit because it's not required and may be considered filler. The instruction: Prefer a few substantive sections over many thin ones. So we could omit Why Choose Cognizant. Also remove "Applications will be accepted until 08/30/2026." That's application instruction? It's a date; maybe considered application instruction; we should remove per instruction: remove application instructions. So drop that line. Also remove "Equal Opportunity Employer" etc. Now produce HTML. Structure:

  About the role

  Cognizant is seeking a highly skilled Azure Databricks Administrator to join our growing Cloud, Data & AI practice. This role is responsible for the administration, governance, security, optimization, and operational support of enterprise-scale Azure Databricks environments. The ideal candidate will possess deep expertise in Azure Databricks, Unity Catalog, Azure networking, security, data governance, and platform operations. This individual will serve as a technical leader and trusted advisor, partnering with engineering, infrastructure, security, and operations teams to ensure a scalable, secure, and high-performing data platform.

  Work Model: Remote - United States

  Then Responsibilities:

  Responsibilities

  • Azure Databricks Administration & Optimization: Design, deploy, and administer Azure Databricks workspaces utilizing VNet injection, private endpoints, and secure cluster connectivity. Configure and maintain cluster policies, Databricks Runtime versions, autoscaling, and workload management standards. Optimize platform performance through cluster tuning, Spark configuration management, and Delta Lake best practices. Perform capacity planning and resource forecasting to support enterprise growth. Drive cost optimization initiatives including right-sizing, auto-termination policies, reserved instances, and spot instance utilization. Troubleshoot and resolve complex platform, cluster, job execution, and connectivity issues.
  ... but we need each duty as separate
  • . The original bullet list is grouped under headings like "Azure Databricks Administration & Optimization", "Data Governance & Unity Catalog", etc. We could keep each heading as part of the li text, or we could split into multiple li each with heading. Probably better to keep each bullet as a separate li with the heading bold. Let's parse. Original responsibilities sections: - Azure Databricks Administration & Optimization - Design, deploy, and administer Azure Databricks workspaces utilizing VNet injection, private endpoints, and secure cluster connectivity. - Configure and maintain cluster policies, Databricks Runtime versions, autoscaling, and workload management standards. - Optimize platform performance through cluster tuning, Spark configuration management, and Delta Lake best practices. - Perform capacity planning and resource forecasting to support enterprise growth. - Drive cost optimization initiatives including right-sizing, auto-termination policies, reserved instances, and spot instance utilization. - Troubleshoot and resolve complex platform, cluster, job execution, and connectivity issues. - Data Governance & Unity Catalog - Design, implement, and administer Unity Catalog metastores, catalogs, schemas, external locations, and volumes. - Establish and enforce fine-grained access controls across enterprise data assets. - Support data lineage tracking, auditing, and governance requirements. - Govern managed and external data assets while promoting best practices for data management. - Security & Identity Management - Integrate Azure Databricks with Microsoft Entra ID for authentication and Single Sign-On (SSO). - Configure and manage SCIM provisioning for automated user and group lifecycle management. - Implement secure secret management using Azure Key Vault-backed secret scopes. - Define and manage access controls across Unity Catalog, Databricks workspaces, and Azure Data Lake Storage Gen2. - Support security audits, compliance reviews, and governance initiatives. - Networking & Connectivity - Architect and maintain secure networking solutions utilizing VNets, NSGs, private endpoints, and firewall controls. - Ensure secure connectivity between Databricks, Azure services, and on-premises environments. - Manage DNS resolution, routing configurations, and network security best practices. - Data Integration & Automation - Design and implement Azure Data Factory (ADF) integration patterns with Azure Databricks. - Support orchestration of enterprise data pipelines and notebook execution workflows. - Partner with DevOps teams to establish and maintain CI/CD pipelines. - Utilize Databricks REST APIs and automation frameworks to streamline platform administration. - Storage Management - Provide guidance on Azure Data Lake Storage Gen2 architecture and configuration. - Implement secure access patterns using service principals, credential passthrough, and Microsoft Entra ID integration. - Troubleshoot storage connectivity and access management issues. - Operations & Platform Reliability - Implement monitoring and alerting using Azure Monitor, Log Analytics, and Databricks native monitoring tools. - Monitor service availability, platform health, resource utilization, and job performance. - Support disaster recovery, business continuity, and resiliency planning efforts. - Plan and coordinate Databricks Runtime upgrades and platform maintenance activities. - Communicate service impacts and operational risks to stakeholders. - Documentation & Enablement - Develop and maintain architecture documentation, diagrams, standards, and operational runbooks. - Establish best practices for platform governance, security, cost optimization, and performance management. - Provide technical guidance, training, and knowledge transfer to internal teams. - Stakeholder Engagement - Collaborate with data engineering, data science, infrastructure, networking, security, and operations teams. - Act as the subject matter expert for Databricks platform administration and governance. - Participate in architecture reviews and provide technical leadership for strategic initiatives. We need to convert each of these bullet points into
  • . Could keep the heading as part of the first sentence or as a inside li. Simpler: each main bullet group could be a
  • containing multiple sentences; but that would lose granularity. However instruction: Use
    • for any list of duties/requirements/benefits. It doesn't forbid having multiple sentences inside a li. So we could keep each group as a li with the heading bold and then the sub-bullets as sentences separated by semicolons. But we could also flatten each sub-bullet into its own li. That would be many li but still okay. Probably better to flatten each sub-bullet to preserve detail. Thus we will produce a long
      with each sub-bullet as
      • . We'll keep the heading as plain text maybe not bold. Eg:
      • Design, deploy, and administer Azure Databricks workspaces utilizing VNet injection, private endpoints, and secure cluster connectivity.
      And so on. We'll need to list all sub-bullets. Let's extract them: Azure Databricks Administration & Optimization: 1. Design, deploy, and administer Azure Databricks workspaces utilizing VNet injection, private endpoints, and secure cluster connectivity. 2. Configure and maintain cluster policies, Databricks Runtime versions, autoscaling, and workload management standards. 3. Optimize platform performance through cluster tuning, Spark configuration management, and Delta Lake best practices. 4. Perform capacity planning and resource forecasting to support enterprise growth. 5. Drive cost optimization initiatives including right-sizing, auto-termination policies, reserved instances, and spot instance utilization. 6. Troubleshoot and resolve complex platform, cluster, job execution, and connectivity issues. Data Governance & Unity Catalog: 1. Design, implement, and administer Unity Catalog metastores, catalogs, schemas, external locations, and volumes. 2. Establish and enforce fine-grained access controls across enterprise data assets. 3. Support data lineage tracking, auditing, and governance requirements. 4. Govern managed and external data assets while promoting best practices for data management. Security & Identity Management: 1. Integrate Azure Databricks with Microsoft Entra ID for authentication and Single Sign-On (SSO). 2. Configure and manage SCIM provisioning for automated user and group lifecycle management. 3. Implement secure secret management using Azure Key Vault-backed secret scopes. 4. Define and manage access controls across Unity Catalog,