Cloud Solutions Developer - Integrations & Platforms

The user wants me to extract only the actual job information and return it in a clean, readable format. Let me analyze the text: 1. The first paragraph has a link "Here" - this is a navigation/application instruction, not actual job info. I should remove this. 2. The job title is "Cloud Solutions Developer - Integrations & Platforms" 3. The company is PATH 4. Location is not explicitly mentioned, but it mentions "PATH country office location" in the skills section, so the location is the PATH country office location (not specified which country) 5. The description and responsibilities are clear 6. Requirements and qualifications are present 7. Preferred experience is present 8. Skills and attributes are present 9. There's no salary mentioned 10. No deadline mentioned 11. No contract type mentioned explicitly 12. The last paragraph about PATH's mission is promotional content - should I remove it? It's not strictly job info but it's part of the description. The instructions say to REMOVE promotional content and category labels. This is more of an intro/about section. I think I should keep the core job description but remove the promotional footer about PATH's mission. Actually, looking at the instructions again: - REMOVE: Social sharing text, author bylines, "You may also like", navigation text, comments, advertisements, cookie notices, duplicate text, category labels, stray numbers - KEEP: Job title, company, location, description, requirements, how to apply, salary, deadline, Job ID, contract type The "PATH current employees - please log in and apply Here" is application instructions - keep it? It's a bit odd but it's application instructions. Actually, it seems like a navigation element that was scraped. I'll remove it as it's not clean job info. The last paragraph about PATH's mission is promotional - remove it. Let me structure the HTML: - Job title: Cloud Solutions Developer - Integrations & Platforms - Company: PATH - Location: Not explicitly stated, but mentioned as "PATH country office location" in skills - Description: The paragraphs before Responsibilities - Responsibilities:

• ...

- Required experience:

• ...

- Preferred experience:

• ...

- Skills and attributes:

• ...

- How to apply: The first paragraph with the link - actually this is application instructions. But it's messy. Let me include a cleaned version. Wait, the instructions say to return ONLY the cleaned job text. And for HTML formatting, use specific tags. Let me re-read: "Return ONLY the cleaned job text. Do not add any commentary, headers like 'Here is the cleaned version', or markdown formatting." So I need to output just the HTML. For the application link, I should probably keep it as it's application instructions. But the original had "PATH current employees - please log in and apply Here" which is confusing. I'll keep the link but clean it up. Actually, looking more carefully, the first paragraph is: "PATH current employees - please log in and apply [link Here]" This seems like a navigation artifact. But it does contain application instructions. I'll keep a cleaned version of it. Let me also note: the location isn't explicitly stated in the main text. It says "PATH country office location" in the skills section. So I'll note that as the location. No salary, no deadline, no contract type mentioned explicitly. Let me write the HTML: ```html

PATH is seeking a Cloud Solutions Developer - Integrations & Platforms to strengthen PATH’s internal capability across enterprise integrations, cloud-hosted services, deployment automation, and shared technical platforms. This role is intended to expand our capacity in cloud-first solutions development, reduce concentration risk in critical integration and platform work, and help PATH automate legacy solutions toward more secure, and scalable cloud-first services.

This role requires a developer with 3–5 years of experience in cloud solutions development who can quickly understand the current integrations landscape, work alongside existing technical team members, and progressively take shared ownership of selected production integrations, platform services, and modernization initiatives, including the transition of selected legacy solutions to cloud-first patterns.

The successful candidate will help support business-critical integrations and shared services across PATH’s enterprise systems, improve operational resilience, reduce operational risk, and contribute to a more secure, supportable, and maintainable cloud-first technical environment.

Responsibilities

• Design, develop, enhance, and support cloud-based solutions that enable enterprise integrations, application interoperability, and automation across PATH’s business-critical platforms.
... etc

``` Wait, the instructions say to use

for introductory paragraphs and general text,

for section headers,

• for lists. Also, I need to preserve ALL original content word-for-word. So I shouldn't change "3–5 years" to "3-5 years" - keep the en-dash. Let me also check: the first paragraph with the link - should I keep it? It's application instructions. I'll keep a cleaned version. Actually, re-reading the rules: "REMOVE all of the following: ... Navigation text (Previous, Next, Read more, Back to)" - the first paragraph is kind of navigation. But it also contains application instructions. Hmm. I think the safest approach is to keep the application link since it's relevant, but remove the "PATH current employees - please log in and apply" prefix which seems like navigation noise. Or I could keep it as is since it's application instructions. Actually, let me reconsider. The first line says "PATH current employees - please log in and apply Here" followed by a link. This is clearly application instructions. I'll keep it but clean it up slightly. Hmm, but the instructions say "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". So I should keep the link. Let me structure it properly: ```html

  PATH is seeking a Cloud Solutions Developer - Integrations & Platforms to strengthen PATH’s internal capability across enterprise integrations, cloud-hosted services, deployment automation, and shared technical platforms. This role is intended to expand our capacity in cloud-first solutions development, reduce concentration risk in critical integration and platform work, and help PATH automate legacy solutions toward more secure, and scalable cloud-first services.

  This role requires a developer with 3–5 years of experience in cloud solutions development who can quickly understand the current integrations landscape, work alongside existing technical team members, and progressively take shared ownership of selected production integrations, platform services, and modernization initiatives, including the transition of selected legacy solutions to cloud-first patterns.

  The successful candidate will help support business-critical integrations and shared services across PATH’s enterprise systems, improve operational resilience, reduce operational risk, and contribute to a more secure, supportable, and maintainable cloud-first technical environment.

  Responsibilities

  • Design, develop, enhance, and support cloud-based solutions that enable enterprise integrations, application interoperability, and automation across PATH’s business-critical platforms.
  ...
  ``` Wait, should I keep the bold tags? The original has tags. The instructions say to preserve content word-for-word. I think keeping is fine since they're semantic enough. But actually, the instructions say "Use

  for introductory paragraphs and general text" and don't mention . However, preserving original content means keeping the tags if they were there. Actually, looking at the original text, there are several tags used for emphasis (job title, years of experience, etc.). I should preserve them as they were in the original. Let me also handle the application link. The original first paragraph: "

  PATH current employees - please log in and apply Here
  
  

  " This is application instructions. I'll keep it but without the styling. Actually, wait. The instructions say to REMOVE navigation text. This first paragraph is kind of navigation/application instruction. But it does tell you how to apply. I think I should keep it because it's application instructions, not navigation. Hmm, but "PATH current employees - please log in and apply" sounds like it might be a filter/navigation thing. Let me keep it since it's application instructions. Actually, I'll keep it minimal - just the link without the "PATH current employees" prefix which seems like navigation noise. But the instructions say preserve all content... OK, I'll keep the first paragraph as is (cleaned of styles), since it contains application instructions. Let me now write the full HTML output. For the location: it's not explicitly stated in the main body. The skills section mentions "Must have legal authorization to work in the PATH country office location." So the location is the PATH country office location. I'll note this. No salary, no deadline, no contract type mentioned. Let me draft the complete HTML: ```html

  PATH current employees - please log in and apply Here

  PATH is a global nonprofit dedicated to achieving health equity. With more than 40 years of experience forging multisector partnerships and with expertise in science, economics, technology, advocacy, and dozens of other specialties, PATH develops and scales up innovative solutions to the world’s most pressing health challenges.

  PATH is seeking a Cloud Solutions Developer - Integrations & Platforms to strengthen PATH’s internal capability across enterprise integrations, cloud-hosted services, deployment automation, and shared technical platforms. This role is intended to expand our capacity in cloud-first solutions development, reduce concentration risk in critical integration and platform work, and help PATH automate legacy solutions toward more secure, and scalable cloud-first services.

  This role requires a developer with 3–5 years of experience in cloud solutions development who can quickly understand the current integrations landscape, work alongside existing technical team members, and progressively take shared ownership of selected production integrations, platform services, and modernization initiatives, including the transition of selected legacy solutions to cloud-first patterns.

  The successful candidate will help support business-critical integrations and shared services across PATH’s enterprise systems, improve operational resilience, reduce operational risk, and contribute to a more secure, supportable, and maintainable cloud-first technical environment.

  Responsibilities

  • Design, develop, enhance, and support cloud-based solutions that enable enterprise integrations, application interoperability, and automation across PATH’s business-critical platforms.
  • Work closely with technical team members, business system owners, and stakeholders to understand existing integration patterns, application dependencies, operational risks, and opportunities to migrate legacy solutions to cloud-first services.
  • Support and enhance Azure-based integration and application components, including services used for scheduled jobs, automation, messaging, configuration, identity, monitoring, and deployment.
  • Build and maintain integrations using API-based, queue-based, file-based, and scheduled processing patterns.
  • Strengthen CI/CD, deployment reliability, and environment management practices, including source control, build pipelines, release processes, secrets/configuration handling, and secure promotion across environments.
  • Troubleshoot and resolve issues across application, integration, deployment, data, and platform layers, and participate in operational support and continuity planning for production services.
  • Improve technical documentation, monitoring, support readiness, service ownership, and knowledge transfer for key services and solutions to reduce operational risk and improve team resilience.
  • Partner with internal stakeholders, platform owners, and vendors to translate business and operational requirements into practical, secure, and maintainable technical solutions.
  • Contribute to medium-term modernization efforts that reduce manual effort, retire or reduce dependency on legacy solutions, and move critical services toward more sustainable cloud-first patterns and enterprise standards.
  • Provide support for related platform and integration work as assigned, including handover of selected legacy responsibilities, transition planning, and progressive ownership of cloud-first replacements or improvements.
  • Identify opportunities to use automation, modern engineering tools, and AI-enabled capabilities where appropriate to improve developer productivity, operational efficiency, and supportability.
  • Work closely with the PATH IT Infrastructure and Support team to understand, support, and transition integrations or services that rely on server-hosted, hybrid, or on-premises components.

  Required experience

  • Bachelor’s degree in computer science, information systems, software engineering, or a related field, or equivalent combination of education and experience.
  • 3–5 years of professional experience in cloud solutions development, software engineering, application integration, or a related technical role.
  • Hands-on experience building, supporting, and improving solutions in Microsoft Azure, including cloud-hosted integration or application services, websites, databases, Python based functions, etc.
  • Experience with CI/CD and release automation, ideally including Azure DevOps or similar tooling, with attention to reliability, traceability, and controlled deployment practices.
  • Experience with enterprise system integration patterns such as REST APIs, scheduled processing, messaging/queues, file-based exchange, data transformation, and service-to-service connectivity.
  • Experience with SQL Server, database objects, ETL, or enterprise data pipelines.
  • Strong troubleshooting and problem-solving skills across application, integration, deployment, and platform layers in production environments.
  • Experience working with source control, deployment processes, environment promotion practices, and secure handling of configuration, credentials, and secrets.
  • Ability to document technical solutions clearly, support knowledge transfer, and communicate effectively with both technical and non-technical stakeholders.
  • Strong organizational skills and ability to manage multiple priorities in a collaborative team environment.

  Preferred experience

  • Experience working in environments that integrate business applications such as Business World / Unit4, Salesforce, Workday, reporting, identity, or document management platforms, particularly where those systems are operationally critical.
  • Experience with Salesforce-integrated environments, especially where Salesforce exchanges data with other enterprise systems and shared services.
  • Working knowledge of scripting or development languages such as Python, particularly for automation, integration support, data processing, or migration tasks.
  • Experience with authentication, service connections, or identity-related integrations such as SSO, service principals, and secure application-to-application connectivity.
  • Gain knowledge of existing integration patterns and support their gradual transition to Azure-native solutions, balancing operational continuity with modernization goals.
  • Experience supporting, stabilizing, and modernizing legacy or on-premises processes into cloud-first solutions.
  • Experience applying integration standards, reusable design patterns, and maintainable architecture in enterprise environments.
  • Experience working in a nonprofit, international, or mission-driven environment.
  • Experience using AI tools and building AI-enabled solutions.

  Skills and attributes

  • Strong technical curiosity and the ability to quickly understand complex existing systems.
  • Comfortable working in environments where documentation gaps, legacy dependencies, and operational realities must be balanced with modernization goals and a cloud-first direction.
  • Practical, solutions-oriented mindset with sound judgment, a strong sense of ownership, and an ability to balance business continuity with technical improvement.
  • Ability to work independently while also collaborating effectively across teams and functions.
  • Strong written and verbal communication skills.
  • Commitment to knowledge sharing, documentation and service support readiness
  • Fluency in English.
  • Must have legal authorization to work in the PATH country office location.

  PATH is a diverse nonprofit organization that creates a culture of collaboration and partnership. Learn more about the impact you can make globally here.

  ``` Wait, I removed the last paragraph about PATH's mission. Is that correct? The instructions say to remove "Category labels that aren't part of the job" and promotional content. The last paragraph is promotional. But it's also part of the job description context. Hmm. Actually, looking at the rules again: "REMOVE all of the following: ... Advertisements or promotions". The last paragraph about PATH's mission is promotional. I'll remove it. But wait, the instructions also say "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". This is a conflict. The