Cloud Engineer

This is not a DevOps role. If you spend most of your day writing pipelines, building CI/CD workflows, or owning infrastructure-as-code, this probably is not for you. If you thrive keeping cloud environments stable, handling L2/L3 incidents, and making sure things run well day and night, keep reading. You will join the cloud operations team of a major digital services company with real technological depth. Your core job is reliability: monitoring multi-cloud infrastructures across OVH, OCI, AWS, and GCP, managing incidents, maintaining Linux systems, and making sure clients can count on you when things go wrong. What the role actually involves: L2/L3 technical support and incident management across multi-cloud environments Linux system maintenance in cloud contexts Participating in technical committees and client steering meetings Collaborating across design, deployment, evolution, and run phases Potentially joining a 24/7 on-call rotation (this will be discussed in the process) You need at minimum: 3 years in a cloud operations or cloud run/MCO role Hands-on experience with at least two of: OVH, OCI, AWS, GCP Azure experience is a genuine plus and will strengthen your candidacy Familiarity with ITIL processes and ITSM tools Strong written communication, clear documentation is part of the job What has already gotten candidates rejected: Less than 3 years of relevant cloud ops experience A profile that is purely DevOps oriented No Azure exposure (not disqualifying on its own, but it adds up) The process is straightforward. Three interviews, no technical test. The client accepts candidates still on notice period, so do not wait until you are free to apply.