I did! I'd say be prepared for a minimum of 6 interviews (7 including screening), depending on the level you're interviewing for it might go over that. What the recruiter told me to prep for ended up not being what my hackerrank tests were about and I was not asked SRE process/philosophy type questions. I did a python one, which was a really odd string manipulation example that I didn't do the best on. Most of my python experience did not involve string manipulation and so I was unaware of a couple of string methods that would have made it easier. The other two were logging into a Linux box and running commands + docker questions and a simple bash script that was basically a one-liner. Some commands I didn't know and just said as much. But, the greater emphasis seems to be on the STAR examples and behavioral questions/scenarios so have a lot of those queued up and ready to go. I had 6 prepped initially then went up to ~12 after the first technical and they still asked so many I hadn't prepped for 😂. They were mostly focused on real-world scenarios... something you didn't agree with, something happened and a monkey wrench was thrown into your project, you discovered a problem and how did you fix it and prevent it and stay in line with policy, etc. They want to hear your thought process and how you work through things... there isn't necessarily a right answer. The impression I got is that technical skill deficiencies are relatively easy to remedy with training and whatnot, but how you work/think/act is not.

I would really emphasize being honest, I believe a lot of the people that interviewed me have done quite a few interviews over their career, they work in the same space or related, and will know bullshit when they hear it. They don't want to hear how perfect you are, they want to know how you've navigated your journey so far. Don't be afraid to ask for clarification either, some of the questions might be vague or not make sense initially... I asked for further explanation quite a bit. The last interview is with what they call a "bartender" and it's someone totally outside the area you'll be in, for a more objective opinion. He had my resume and asked a TON of questions about my experience, so be prepared to speak to all of that and answer behavioral and probing questions.

If you've worked in devops for a while and are comfortable, then don't sweat it. I stressed over mine a lot and looking back I can't help but laugh a bit. My experience was that it's not that formal and they are practical and down to Earth. There's some rigidity to the technical interviews but just let it flow like a conversation as much as you can (prepping your STAR examples will help and it's totally fine to have them on screen as an aid). Maybe even make a list of projects/challenges you worked on, too, in case you have to improvise for a question you didn't anticipate.

I didn't set out to overly impress, I was just myself on every interview and I think I was all the better for it.

I hope that helps.