Senior Cloud Solutions Engineer
Humana · Louisville, KY · 1 mo ago
RemoteRemoteEngineering$107k–$147k/yrFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the posting.
Content:
- Opening paragraph: "Become a part of our caring community The Senior Cloud Solutions Engineer participates in the design and development of cloud-based solutions and applications in the big data space within Humana’s Digital & Data organization primarily using Microsoft Azure and related technologies. The Senior Cloud Solutions Engineer work assignments involve moderately complex to complex issues where the analysis of situations or data requires an in-depth evaluation of variable factors. The Senior Cloud Solutions Engineer Implements the organization's cloud strategy from a technical perspective, including design, planning, integration, and maintenance for big data solutions using Microsoft Azure. This will involve participating in the design and development of cloud-based solutions and applications within Humana’s Digital & Data organization primarily using Microsoft Azure."
That's basically description of role. Could be "About the role" section.
- Then "Responsibilities Include" bullet list: "Work with stakeholders across organization to evaluate cloud systems and identify appropriate solutions. Collaborates with product managers and engineers to develop specifications for new cloud-based products/services, applications and solutions.Drives the roll-out of cloud management platforms, evaluates its performance and implements enhancements. Begins to influence department’s strategy.Makes decisions on moderately complex to complex issues regarding technical approach for project components, and work is performed without direction. Exercises considerable latitude in determining objectives and approaches to assignments."
These are sentences; we can treat each as list items.
- Then "Required Qualifications" heading: list: "Use your skills to make an impact Bachelor's Degree in Computer Science or related field or equivalent work experienceExperience building Cloud Solutions in big data with Azure, AWS or GCP5 or more years of experience designing, developing, and testing of software applicationsStrong SQL skillsExperience with Azure Functions including Azure Data Factory, Azure Data Lake, and Azure Logic AppsCI/CD experience creating Azure DevOps pipelineMust be passionate about contributing to an organization focused on continuously improving consumer experiences"
We need to separate into list items.
- Then "Preferred Qualifications": "Master's DegreeDatabricks experiencePython experience"
- Then "Work at Home Requirements": details about internet speed, dedicated space, travel, etc. This could be a section maybe "Work Requirements" or "Remote Work Requirements". The allowed headings list includes Schedule, Benefits, Pay, etc. Not specifically "Work at Home Requirements". But we could put under "Schedule"? Not appropriate. Could create a custom heading? The instruction says use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the posting.
Content:
- Opening paragraph: "Become a part of our caring community The Senior Cloud Solutions Engineer participates in the design and development of cloud-based solutions and applications in the big data space within Humana’s Digital & Data organization primarily using Microsoft Azure and related technologies. The Senior Cloud Solutions Engineer work assignments involve moderately complex to complex issues where the analysis of situations or data requires an in-depth evaluation of variable factors. The Senior Cloud Solutions Engineer Implements the organization's cloud strategy from a technical perspective, including design, planning, integration, and maintenance for big data solutions using Microsoft Azure. This will involve participating in the design and development of cloud-based solutions and applications within Humana’s Digital & Data organization primarily using Microsoft Azure."
That's basically description of role. Could be "About the role" section.
- Then "Responsibilities Include" bullet list: "Work with stakeholders across organization to evaluate cloud systems and identify appropriate solutions. Collaborates with product managers and engineers to develop specifications for new cloud-based products/services, applications and solutions.Drives the roll-out of cloud management platforms, evaluates its performance and implements enhancements. Begins to influence department’s strategy.Makes decisions on moderately complex to complex issues regarding technical approach for project components, and work is performed without direction. Exercises considerable latitude in determining objectives and approaches to assignments."
These are sentences; we can treat each as list items.
- Then "Required Qualifications" heading: list: "Use your skills to make an impact Bachelor's Degree in Computer Science or related field or equivalent work experienceExperience building Cloud Solutions in big data with Azure, AWS or GCP5 or more years of experience designing, developing, and testing of software applicationsStrong SQL skillsExperience with Azure Functions including Azure Data Factory, Azure Data Lake, and Azure Logic AppsCI/CD experience creating Azure DevOps pipelineMust be passionate about contributing to an organization focused on continuously improving consumer experiences"
We need to separate into list items.
- Then "Preferred Qualifications": "Master's DegreeDatabricks experiencePython experience"
- Then "Work at Home Requirements": details about internet speed, dedicated space, travel, etc. This could be a section maybe "Work Requirements" or "Remote Work Requirements". The allowed headings list includes Schedule, Benefits, Pay, etc. Not specifically "Work at Home Requirements". But we could put under "Schedule"? Not appropriate. Could create a custom heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we can use others? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings only. So we need to map content to those headings.
We have:
- About the role: description paragraph.
- Responsibilities: bullet list.
- Requirements: maybe combine Required Qualifications? Could be "Requirements" heading.
- Qualifications: maybe Preferred Qualifications? Or we could have both Required and Preferred under Qualifications? But we need to avoid duplication. Could have "Requirements" for required qualifications, and "Qualifications" for preferred? Or we could combine both under "Qualifications" with subheadings? But only allowed headings list includes Qualifications. Could treat "Requirements" as separate heading (allowed). Then "Qualifications" for preferred? Might be okay.
- Skills: maybe list specific skills like SQL, Azure Functions, etc. Could extract from required qualifications.
- Benefits: description of benefits.
- Pay: pay range.
- Schedule: scheduled weekly hours 40.
We also have Work at Home Requirements and Travel info. Could fit under "Schedule"? Not really. Could be part of "About the role" or maybe we omit as not fitting headings? But we must preserve ALL substantive information; cannot drop. So we need to include that info somewhere. Perhaps we can include under "About the role" as additional paragraph. Or create a section "Work Requirements" but not in allowed list; risk. However instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. So we could add other headings like "Work at Home Requirements". Safer to follow examples but not strictly limited. I'd include a heading "Work at Home Requirements". It's substantive.
Also "Travel" info could be under same.
Thus sections:
- About the role (description)
- Responsibilities (list)
- Requirements (required qualifications)
- Qualifications (preferred qualifications)
- Skills (maybe extract specific skills: Strong SQL skills, Experience with Azure Functions including Azure Data Factory, Azure Data Lake, Azure Logic Apps, CI/CD experience creating Azure DevOps pipeline, etc.)
- Benefits
- Pay
- Schedule (weekly hours 40)
- Work at Home Requirements (internet speed, dedicated space, travel)
We must not repeat job title as heading. Not include Job ID.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. At end there is EEO statement; we must remove that.
Also remove "About Us" maybe? It's substantive? It describes company; could be considered boilerplate? It's about Humana; maybe we can keep as part of About the role? But it's not about the role; it's about company. Could be considered boilerplate but it's not EEO. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Us" is not explicitly listed; could keep but maybe it's not needed. However we must preserve ALL substantive information; "About Us" is substantive about company. Might be okay to keep under About the role or separate section "About Humana". But not in headings list; we could add "About the company". But maybe we can incorporate into About the role as a brief note. Safer to keep as a paragraph under About the role.
We need to output only HTML fragment, no /, no markdown fences.
Let's craft.
Structure:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings only. So we need to map content to those headings.
We have:
- About the role: description paragraph.
- Responsibilities: bullet list.
- Requirements: maybe combine Required Qualifications? Could be "Requirements" heading.
- Qualifications: maybe Preferred Qualifications? Or we could have both Required and Preferred under Qualifications? But we need to avoid duplication. Could have "Requirements" for required qualifications, and "Qualifications" for preferred? Or we could combine both under "Qualifications" with subheadings? But only allowed headings list includes Qualifications. Could treat "Requirements" as separate heading (allowed). Then "Qualifications" for preferred? Might be okay.
- Skills: maybe list specific skills like SQL, Azure Functions, etc. Could extract from required qualifications.
- Benefits: description of benefits.
- Pay: pay range.
- Schedule: scheduled weekly hours 40.
We also have Work at Home Requirements and Travel info. Could fit under "Schedule"? Not really. Could be part of "About the role" or maybe we omit as not fitting headings? But we must preserve ALL substantive information; cannot drop. So we need to include that info somewhere. Perhaps we can include under "About the role" as additional paragraph. Or create a section "Work Requirements" but not in allowed list; risk. However instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. So we could add other headings like "Work at Home Requirements". Safer to follow examples but not strictly limited. I'd include a heading "Work at Home Requirements". It's substantive.
Also "Travel" info could be under same.
Thus sections:
- About the role (description)
- Responsibilities (list)
- Requirements (required qualifications)
- Qualifications (preferred qualifications)
- Skills (maybe extract specific skills: Strong SQL skills, Experience with Azure Functions including Azure Data Factory, Azure Data Lake, Azure Logic Apps, CI/CD experience creating Azure DevOps pipeline, etc.)
- Benefits
- Pay
- Schedule (weekly hours 40)
- Work at Home Requirements (internet speed, dedicated space, travel)
We must not repeat job title as heading. Not include Job ID.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. At end there is EEO statement; we must remove that.
Also remove "About Us" maybe? It's substantive? It describes company; could be considered boilerplate? It's about Humana; maybe we can keep as part of About the role? But it's not about the role; it's about company. Could be considered boilerplate but it's not EEO. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Us" is not explicitly listed; could keep but maybe it's not needed. However we must preserve ALL substantive information; "About Us" is substantive about company. Might be okay to keep under About the role or separate section "About Humana". But not in headings list; we could add "About the company". But maybe we can incorporate into About the role as a brief note. Safer to keep as a paragraph under About the role.
We need to output only HTML fragment, no /, no markdown fences.
Let's craft.
Structure:
About the role
About the role
...
Responsibilities
- ... ...
Requirements
- Bachelor's Degree in Computer Science or related field or equivalent work experience
- Experience building Cloud Solutions in big data with Azure, AWS or GCP
- 5 or more years of experience designing, developing, and testing of software applications
- Strong SQL skills
- Experience with Azure Functions including Azure Data Factory, Azure Data Lake, and Azure Logic Apps
- CI/CD experience creating Azure DevOps pipeline
- Must be passionate about contributing to an organization focused on continuously improving consumer experiences
Qualifications
- Master's Degree
- Databricks experience
- Python experience
Skills
- Strong SQL skills
- Experience with Azure Functions (Azure Data Factory, Azure Data Lake, Azure Logic Apps)
- CI/CD experience creating Azure DevOps pipelines