Cloud Engineering Advisor
headings for each section, and - for lists,
for prose.
We should not repeat job title as heading.
We need to include only sections with real content.
Let's craft:
maybe not needed; just headings and content.
We'll produce:
About the role
As a Cloud Engineer, you will be responsible for the deployment, integration, and management of private, public, and/or hybrid cloud platform services supporting the development of complex analytical applications at enterprise scale. You will demonstrate networking and security protocol knowledge to ensure safe and scalable environment provisioning while protecting accessibility to data assets. You will be comfortable developing infrastructure as code using scripts, templates, blueprints, workflows, CI/CD orchestration tools, and other automation technologies in the spirit of speed and consistency. Continuous collaboration with architects and peer engineering teams will be essential to ensure deployed services meet the highest levels of scalability, reliability, and performance while balancing security, maintainability, and operational excellence.
But we need to preserve all substantive information; we can paraphrase? The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should not paraphrase to lose detail, but we can rephrase as long as we keep all details. However, we must not invent or summarize away detail. Summarizing may be okay if we keep all details? Safer to keep the original sentences but maybe combine.
We could keep the original text but remove duplication.
Let's extract responsibilities list:
- Deployment, integration, and management of private, public, and/or hybrid cloud platform services supporting development of complex analytical applications at enterprise scale.
- Demonstrating networking and security protocol knowledge to ensure safe and scalable environment provisioning while protecting accessibility to data assets.
- Developing infrastructure as code using scripts, templates, blueprints, workflows, CI/CD orchestration tools, and other automation technologies in the spirit of speed and consistency.
- Continuous collaboration with a variety of architects and peer engineering teams ensuring deployed services meet the highest levels of scalability, reliability, and performance while balancing security, maintainability, reliability, and operational excellence.
- Design, integrate and monitor cloud computing systems.
- Manage deployment, all integration and troubleshoot platform services.
- Collaboration with engineers, architects building systems to meet all needs.
We need to ensure we didn't miss any.
Now requirements:
- Minimum Education: Bachelor's Degree/equivalent in computer science, engineering, or information systems and/or equivalent formal training or work experience.
- Minimum Experience: Five to seven (5 - 7) years’ experience in cloud engineering or related field.
- Experience providing leadership in a general planning or consulting setting.
- Experience as a leader or a senior member of multi-function project teams.
- A related advanced degree may offset the related experience requirements.
Skills/Knolwedge:
- Strong leader / mentorship
- Strong oral and written communication skills
- Must have: Terraform, Yaml configurations, Shell scripting, Kubernetes
- Nice to have: Java or Python, Databricks, Azure services such as Event Hubs, ADF, ADLS, Synapse
Preferred Qualifications: maybe none else.
Pay: as listed.
We need to avoid duplication: "Strong leader / mentorshipStrong oral and written communication skills" appears as concatenated; we need to split.
Now we need to decide which heading for skills vs qualifications. The posting has "Knolwedge, Skills And Abilities" then list, then "Preferred Qualifications". We could combine skills and qualifications under one heading "Skills and Qualifications" or separate. The instruction says use headings for section headings (e.g
for prose. We should not repeat job title as heading. We need to include only sections with real content. Let's craft: maybe not needed; just headings and content. We'll produce:
About the role
As a Cloud Engineer, you will be responsible for the deployment, integration, and management of private, public, and/or hybrid cloud platform services supporting the development of complex analytical applications at enterprise scale. You will demonstrate networking and security protocol knowledge to ensure safe and scalable environment provisioning while protecting accessibility to data assets. You will be comfortable developing infrastructure as code using scripts, templates, blueprints, workflows, CI/CD orchestration tools, and other automation technologies in the spirit of speed and consistency. Continuous collaboration with architects and peer engineering teams will be essential to ensure deployed services meet the highest levels of scalability, reliability, and performance while balancing security, maintainability, and operational excellence.
But we need to preserve all substantive information; we can paraphrase? The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should not paraphrase to lose detail, but we can rephrase as long as we keep all details. However, we must not invent or summarize away detail. Summarizing may be okay if we keep all details? Safer to keep the original sentences but maybe combine. We could keep the original text but remove duplication. Let's extract responsibilities list: - Deployment, integration, and management of private, public, and/or hybrid cloud platform services supporting development of complex analytical applications at enterprise scale. - Demonstrating networking and security protocol knowledge to ensure safe and scalable environment provisioning while protecting accessibility to data assets. - Developing infrastructure as code using scripts, templates, blueprints, workflows, CI/CD orchestration tools, and other automation technologies in the spirit of speed and consistency. - Continuous collaboration with a variety of architects and peer engineering teams ensuring deployed services meet the highest levels of scalability, reliability, and performance while balancing security, maintainability, reliability, and operational excellence. - Design, integrate and monitor cloud computing systems. - Manage deployment, all integration and troubleshoot platform services. - Collaboration with engineers, architects building systems to meet all needs. We need to ensure we didn't miss any. Now requirements: - Minimum Education: Bachelor's Degree/equivalent in computer science, engineering, or information systems and/or equivalent formal training or work experience. - Minimum Experience: Five to seven (5 - 7) years’ experience in cloud engineering or related field. - Experience providing leadership in a general planning or consulting setting. - Experience as a leader or a senior member of multi-function project teams. - A related advanced degree may offset the related experience requirements. Skills/Knolwedge: - Strong leader / mentorship - Strong oral and written communication skills - Must have: Terraform, Yaml configurations, Shell scripting, Kubernetes - Nice to have: Java or Python, Databricks, Azure services such as Event Hubs, ADF, ADLS, Synapse Preferred Qualifications: maybe none else. Pay: as listed. We need to avoid duplication: "Strong leader / mentorshipStrong oral and written communication skills" appears as concatenated; we need to split. Now we need to decide which heading for skills vs qualifications. The posting has "Knolwedge, Skills And Abilities" then list, then "Preferred Qualifications". We could combine skills and qualifications under one heading "Skills and Qualifications" or separate. The instruction says use headings for section headings (e.g