Senior Artificial Intelligence/Machine Learning Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Benefits (maybe also Skills? The posting includes "Core Skills" list. Also "What’s in it for you?" includes benefits. Also maybe "Pay" and "Schedule" not present, so omit. Also "Qualifications" maybe not separate; we have Requirements. Also "Skills" maybe we can include Core Skills as a section? The instruction: use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Include a section only when posting has real specific content. So we have About the role (present), Responsibilities (present), Requirements (present), Skills (Core Skills list), Benefits (What's in it for you?). Also maybe "Qualifications" not separate; we can skip. Also "Pay"/"Schedule" not present, omit. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like navigation, EEO, application instructions. The posting includes "Interested already? We would love to get to know you! Submit your application. We can’t wait to see you at Ciklum." That's application instruction; remove. Also "About Us" maybe not needed? It's not a required heading; could be omitted or maybe we could include as a paragraph? The instruction: preserve ALL substantive information; do not invent or summarize away detail. "About Us" is substantive but not a required heading; we could include as a

after sections? The instruction says output only HTML fragment; we can include any content as

not under headings if not matching headings. But better to keep it as a section? There's no heading for About Us in list; we could just put as a

after sections. However, we must not include boilerplate like navigation/legal/EEO etc. "About Us" is not boilerplate; it's substantive. So we should keep it. We need to preserve all substantive information: The role description includes many details. We must not lose any. We'll need to copy the responsibilities list exactly as given (but maybe we can keep bullet points). The responsibilities section currently has a weird formatting: "L ead automation initiatives..." with a space after L? Probably a typo; we should preserve as is? The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should keep the text exactly, including the typo? Might be okay to keep as is. However, we could correct obvious typo? That would be altering content. Better to keep as is. Similarly, requirements list includes many bullet points; we need to preserve. We also have "Core Skills:" list. We need to format as

• for any list of duties/requirements/benefits. So each bullet becomes
• . For responsibilities, each line starting with a capital verb? We'll need to split. Let's extract responsibilities block: "Responsibilities L ead automation initiatives for enterprise GenAI, Data Science, Metadata, Data Quality, Event Streaming, and Analytics platformsDesign and implement self-service automation capabilities that streamline onboarding, environment provisioning, deployment, governance, monitoring, and operational workflowsBuild automated platform services supporting the complete AI and analytics lifecycle including data preparation, experimentation, model training, deployment, inferencing, observability, and lifecycle managementDevelop Infrastructure-as-Code (IaC) solutions using Terraform and related automation frameworks to enable repeatable, scalable, and compliant infrastructure deploymentsDesign and implement enterprise CI/CD pipelines, automated testing frameworks, deployment automation, and release management processes using Atlassian and related DevOps toolchainsPartner with platform engineering and cloud teams to automate Kubernetes, container, serverless, and distributed computing environmentsBuild automation solutions supporting agentic AI applications, MCP-enabled services, event-driven architectures, and enterprise AI workflowsDrive operational excellence through platform monitoring, observability, automated remediation, performance optimization, and reliability engineering practicesCollaborate with architecture, engineering, governance, security, and business stakeholders to ensure platforms meet enterprise standards and compliance requirementsConduct technical design reviews, automation assessments, code reviews, and establish engineering best practices across teamsProvide technical leadership, mentorship, and guidance to engineering teams adopting automation-first development and operational practicesSupport key business initiatives including Consumer AML Analytics and other strategic AI platform adoption efforts" It seems there is no punctuation between items; they are concatenated. We need to split into separate responsibilities. Likely each responsibility starts with a verb capitalized (except the first "L ead" has a space). We can manually split based on capital letters at start of each responsibility after a lowercase? This is messy. Perhaps we can keep as a single

  preserving the text? But instruction says use

  • for any list of duties/requirements/benefits. This is a list of duties, so we should make
    • . However, the source lacks clear delimiters. We could still make each sentence as a
    • by splitting at periods. Let's insert periods where appropriate: The text seems to have missing periods; we can add them? That would be altering content. Better to keep as a single

      maybe? But instruction says use

      • for any list of duties/requirements/benefits. If we don't split, we violate. However, we could treat the whole block as a single duty? Not ideal. Given the ambiguity, maybe we can preserve as

        and note that it's not a list? But the instruction is strict. However, the source is flawed; we might still output

        • with each responsibility as a separate
        • by splitting at capital letters that start a new responsibility (like "Design", "Build", "Develop", "Design", "Partner", "Build", "Drive", "Collaborate", "Conduct", "Provide", "Support"). We'll need to insert appropriate punctuation. Let's attempt to split: 1. Lead automation initiatives for enterprise GenAI, Data Science, Metadata, Data Quality, Event Streaming, and Analytics platforms 2. Design and implement self-service automation capabilities that streamline onboarding, environment provisioning, deployment, governance, monitoring, and operational workflows 3. Build automated platform services supporting the complete AI and analytics lifecycle including data preparation, experimentation, model training, deployment, inferencing, observability, and lifecycle management 4. Develop Infrastructure-as-Code (IaC) solutions using Terraform and related automation frameworks to enable repeatable, scalable, and compliant infrastructure deployments 5. Design and implement enterprise CI/CD pipelines, automated testing frameworks, deployment automation, and release management processes using Atlassian and related DevOps toolchains 6. Partner with platform engineering and cloud teams to automate Kubernetes, container, serverless, and distributed computing environments 7. Build automation solutions supporting agentic AI applications, MCP-enabled services, event-driven architectures, and enterprise AI workflows 8. Drive operational excellence through platform monitoring, observability, automated remediation, performance optimization, and reliability engineering practices 9. Collaborate with architecture, engineering, governance, security, and business stakeholders to ensure platforms meet enterprise standards and compliance requirements 10. Conduct technical design reviews, automation assessments, code reviews, and establish engineering best practices across teams 11. Provide technical leadership, mentorship, and guidance to engineering teams adopting automation-first development and operational practices 12. Support key business initiatives including Consumer AML Analytics and other strategic AI platform adoption efforts Note the first responsibility had a typo "L ead". We'll keep as "L ead automation initiatives..." (preserving the space). We'll keep the typo. Now Requirements block: "Requirements Bachelor’s or Master’s degree in Computer Science, Engineering, Information Technology, or a related technical field10+ years of hands-on experience in platform engineering, automation engineering, cloud engineering, DevOps, or large-scale distributed systemsProven experience building self-service enterprise platforms supporting AI/ML, Data Science, Data Engineering, and advanced analytics workloadsStrong expertise in automation frameworks, DevOps methodologies, CI/CD pipelines, Infrastructure-as-Code, and software delivery lifecycle automationDeep understanding of modern open-source Generative AI and Data Science platform architectures including storage and compute separation, interactive development environments, virtual environments, containers, Jupyter, VSCode, and developer productivity toolingHands-on experience implementing enterprise CI/CD automation using Atlassian ecosystem tools including Bitbucket, Bamboo, Jira, and ConfluenceExperience designing and implementing Infrastructure-as-Code solutions using Terraform and cloud-native automation frameworksStrong understanding of metadata management, data lineage, governance frameworks, and semantic layer concepts supporting enterprise AI and data platformsExperience building scalable cloud-native solutions utilizing distributed computing architectures and modern platform engineering principlesExperience automating deployments and operations for Kubernetes, containerized, YARN, serverless, and distributed processing environmentsExperience designing and supporting event-driven architectures leveraging technologies such as Kafka and streaming data platformsWorking knowledge of agentic AI architectures, MCP frameworks, API integrations, workflow automation, and enterprise AI enablement platformsStrong Python development experience for automation, orchestration, scripting, tooling, and operational engineering use casesKnowledge of cloud engineering principles including networking, infrastructure management, security, resilience, scalability, and cost optimizationExperience implementing observability frameworks including logging, monitoring, tracing, alerting, automation, and operational dashboardsAbility to communicate effectively with engineers, architects, product owners, and business stakeholders across varying technical levels" We need to split into items. Likely each requirement starts after a period? There are no periods. We'll split by capital letters at start of each requirement after a lowercase? Let's attempt: 1. Bachelor’s or Master’s degree in Computer Science, Engineering, Information Technology, or a related technical field 2. 10+ years of hands-on experience in platform engineering, automation engineering, cloud engineering, DevOps, or large-scale distributed systems 3. Proven experience building self-service enterprise platforms supporting AI/ML, Data Science, Data Engineering, and advanced analytics workloads 4. Strong expertise in automation frameworks, DevOps methodologies, CI/CD pipelines, Infrastructure-as-Code, and software delivery lifecycle automation 5. Deep understanding of modern open-source Generative AI and Data Science platform architectures including storage and compute separation, interactive development environments, virtual environments, containers, Jupyter, VSCode, and developer productivity tooling 6. Hands-on experience implementing enterprise CI/CD automation using Atlassian ecosystem tools including Bitbucket, Bamboo, Jira, and Confluence 7. Experience designing and implementing Infrastructure-as-Code solutions using Terraform and cloud-native automation frameworks 8. Strong understanding of metadata management, data lineage, governance frameworks, and semantic layer concepts supporting enterprise AI and data platforms 9. Experience building scalable cloud-native solutions utilizing distributed computing architectures and modern platform engineering principles 10. Experience automating deployments and operations for Kubernetes, containerized, YARN, serverless, and distributed processing environments 11. Experience designing and supporting event-driven architectures leveraging technologies such as Kafka and streaming data platforms 12. Working knowledge of agentic AI architectures, MCP frameworks, API integrations, workflow automation, and enterprise AI enablement platforms 13. Strong Python development experience for automation, orchestration, scripting, tooling, and operational engineering use cases 14. Knowledge of cloud engineering principles including networking, infrastructure management, security, resilience, scalability, and cost optimization 15. Experience implementing observability frameworks including logging, monitoring, tracing, alerting, automation, and operational dashboards 16. Ability to communicate effectively with engineers, architects, product owners, and business stakeholders across varying technical levels Now Desirable Experience section: It's under "Desirable Experience". Could be considered as part of Requirements or separate? The instruction: include a section only when posting has real specific content. We could add a "Desirable Experience" subsection under Requirements? But headings list doesn't include Desirable Experience. Could treat as part of Requirements (maybe as a

          note). However, we could also create a "Preferred Qualifications" but not in list. Safer to include as a

          after Requirements, maybe as a paragraph. But we also have "Core Skills:" list. That's a list of skills; we can make a Skills section. Now Benefits: "What’s in it for you?" includes bullet points: Strong community..., Growth focus..., Tailored learning..., Endless opportunities..., Care: Healthcare