My experience is mainly in analytics and observability pipeline once the tool is deployed. This involves data onboarding, knowledge extraction (KVs out of poorly structured or unstructured data) and creating and maintaining knowledge objects (alerts, reports, dashboards, etc.). My experience with AWS or GCP, containers, CM and devops in general is light. Familiar with all of them, took classes, did projects with them - but they're not part of my daily routines as my team is still fully on prem. So this seemingly was the case of misunderstanding: they were looking for someone who'd be good in DEPLOYING tools in the cloud, not someone who'd MAINTAIN them and use them to extract actionable knowledge. I think it was on them to figure this out early on rather than put me through 3+ hours of interviews (they were getting paid for their time - I was not) - yet somehow this didn't happen. I'll be the wiser from it, hopefully. :) Overall, a negative interview experience: what they were looking for isn't on my resume - so why spend 3+ hours of their time of around 8 people pursuing something that was clear from the get go that it wouldn't work? I think they're also in for a surprise: observability devops != observability engineer and analyst. They will need the latter one soon, and it seems they're even looking for one thinking that devops would take care of it. (It wouldn't.)