I guess is more like a smoke test to see if the candidate know some linux basics or not. I think it's a good idea. We made a mistake one time to hire a mid level that was ok in term of theory, but was terrible at using a computer. It took a while to try to train him, but it was not satisfying at all, and the company ended up firing him. It could had saved a lot of pain for everyone with a quick test like that. I will prefer that as well. I don't think some deep algorithm knowledge is really relevant, compare to some actual troubleshooting work. We (my team) wrote only simple scripts / pipelines, with some functions and loops, parsing some json files, some apis calls and that's it. If we end up with too much complex code, that's probably mean that an existing solution already exist out there ready to be deployed. Answer from temitcha on reddit.com
🌐
Reddit
reddit.com › r/devops › devops engineer live coding interview
r/devops on Reddit: DevOps engineer live coding interview
May 14, 2025 -

Hey guys! I've never had a live coding interview for devops engineering roles. Anyone has experience on what questions might be asked? I was told it won't be leetcode style not algo. Any experience you can share would be greatly appreciated!

Top answer
1 of 5
81
We do a 3-part tech segment that spans 2h max. It consists of: Architecture discussion: describe a stack or app you have experience with, explain network routes and deployment. Looking for some understanding of security practices, DNS, OSI model, and knowledge of how and where things can be scaled in any direction. Good candidates often naturally start drawing diagrams. Live troubleshooting in a broken app, either Terraform or Docker or a K8s cluster depending on the role. Looking for understanding of how scheduling and labels and annotations work, ability to navigate the CLI, ability to probe granular pieces (curl container/service/ingress) and knowledge of where to find logs when things crash. Programming: not leetcode, but write in any language a very basic script (with some goal/task) that involves loops and conditionals. The candidates that struggle the most are those that get locked into their own heads. This interview isn't just about being technically competent - it's also about the candidates ability to communicate and ask questions, and for the interviewers to get a sense of what the candidate might be like to work with. Asking questions or admitting that you don't know something isn't a fail - it's acknowledgement of a boundary and a demonstration that you won't spin your wheels in silence. This role requires people to learn on their feet, and we look for that from day 0.
2 of 5
34
Ask them directly. Since the definition of a “DevOps/SRE/Platform” roles is so wide, it can be anything: from creating a couple of resources with Terraform to solving some LeetCode challenges.
🌐
Reddit
reddit.com › r/devops › devops interview coding questions
r/devops on Reddit: Devops interview coding questions
December 28, 2024 -

I have an upcoming interview for a Senior DevOps Engineer position. Does anyone have experience with the types of coding questions typically asked? Are there any websites or resources specifically tailored for DevOps preparation? I’ve practiced some easy-to-medium problems on LeetCode, but I’m looking for resources more focused on DevOps.

Top answer
1 of 5
41

What cloud platforms are you familiar with?

How do go about making an aws s3 bucket/azure blob storage (assuming that’s your jam) (looking for how you answer … as there are multiple ways)

What shell languages are you familiar with?

What cicd platforms are you familiar with?

Have you ever created a cicd pipeline?

When would you bring security into a development cycle? (What can you do as a devops person to help achieve that goal)

Have you mentored a team in processes you have created so that they may utilize your processes? What were the steps that you did to accomplish this?

What infrastructure as code programming languages are you familiar with?

Are you familiar with kubernetes?

What are some things to look out for when upgrading a kubernetes cluster?

(Some of the questions I occasionally ask) not completely focused on coding - but generally trying to get a feel of skill levels and how much training is needed to onboard them

2 of 5
23

I guess as a senior devops I would rather prepare for the other non-devops questions.

Like why did you choose our company? What are your weaknesses? Tell me about yourself. And that crap.

Seriously if you need to prepare basic stuff for a senior role, I guess you are applying for the wrong job.

I would not even look at stuff like LeetCode if I would try to find a job now.

If the role asks let's say for AWS and Kubernetes you may want to look what the latest hot stuff for Kubernetes and AWS. And maybe try that new feature out. Or something regarding security and code quality is also always welcomed, for example maybe look into Snyk and Sonarqube.

Coding questions for Devops are rather unusual I believe.You are not applying as a backend programmer who has to implement the most efficient sorting algorithm in the world. In my experience devops interviews are more tell us about your knowledge of technology X and how you used that technology in your past projects.

🌐
Reddit
reddit.com › r/devops › how would you prepare for this devops technical interview (coding test)?
r/devops on Reddit: How would you prepare for this DevOps Technical Interview (Coding test)?
July 2, 2022 -

I'm currently on my 2nd interview for a Sr. DevOps role at a startup company and I'm struggling with how to properly interpret this next step in the process.

The in-house recruiter scheduled me for a 45 minute "coding screen", which to me would imply solving some basic algorithms with the language of my choice. Pretty standard right? However when I asked him to clarify what kind of coding test it would be, he replied "you'll be doing basic file system navigation/manipulation. Please use Bash or an alternative shell for this interview." So I'm guessing instead that this is more of a practical focused on Linux OS commands. Things like changing file permissions, creating links, etc. Do you think I'm interpreting this correctly?

For my current role (DevOps Engineer), I had to do an AWS practical AND a coding test similar to how I mentioned earlier. I'm a little surprised that neither of these would be covered, which is why I was hoping for a 2nd opinion? I'm guess that since this is a startup, maybe they don't quite know how to interview for this kind of role yet?

Top answer
1 of 8
26
As someone who’s been in the more CI/CD and Ops side of DevOps for the last 5 years, who hasn’t had a reason to do any heavy coding since I stopped being a web Dev (I was a dev for 5 years prior to moving to DevOps) I wish more interviews had a Bash/Linux/Infrastructure component. I’ve been interviewing for a bit, and it seems like everywhere I apply I make it 2-3 rounds and they spring some sort of leetcode thing on me where I have to solve some problem while another dude stares at me. I am terrible at those sorts of exercises, but really don’t want to invest a ton of time on building skills I’ll never use outside of interviews(I’m already burned out enough). I also don’t retain information I don’t use regularly, so even if I can read and quickly find bugs in 3 or 4 languages, it takes me a while to remember what I need to do when writing code from scratch. When I started out most interviews were a technical discussion and maybe some whiteboarding, then people wanted to see a GitHub portfolio, then it was take home tests, now it’s all the real-time coding exercises. When I was a straight up dev, I could at least understand some of those requirements (whiteboard, GitHub, the take home stuff was pushing the limit of my patience), but now half the stuff I’m asked about in interviews isn’t relevant to the job description or any of the ostensible work I would be doing.
2 of 8
14
I guess is more like a smoke test to see if the candidate know some linux basics or not. I think it's a good idea. We made a mistake one time to hire a mid level that was ok in term of theory, but was terrible at using a computer. It took a while to try to train him, but it was not satisfying at all, and the company ended up firing him. It could had saved a lot of pain for everyone with a quick test like that. I will prefer that as well. I don't think some deep algorithm knowledge is really relevant, compare to some actual troubleshooting work. We (my team) wrote only simple scripts / pipelines, with some functions and loops, parsing some json files, some apis calls and that's it. If we end up with too much complex code, that's probably mean that an existing solution already exist out there ready to be deployed.
🌐
Reddit
reddit.com › r/devops › what are devops interviews like?
r/devops on Reddit: What are devops interviews like?
January 25, 2024 -

I am a software engineer with 3 years of experience and applying to some Devops engineer roles. What are the differences between software engineer interviews and devops engineer interviews? What should I study? I have a good amount of experience doing CI/CD pipelines and managing deployments, troubleshooting bugs in production, and working with security and cloud teams to resolve issues. I have an interview next week and have no idea what to expect.

🌐
Reddit
reddit.com › r/devops › devops interviews coding questions?
r/devops on Reddit: DevOps interviews coding questions?
December 31, 2023 -

Hey guys two questions:

First is - are you guys getting tasked with coding questions (like leet code) in your interviews for DevOps roles? If so what have they consisted of?

Second is - my current role as a devops engineer primarily consists of Terraform, bash scripting, yaml files for workflows and few ansible playbooks (in terms of scripting/coding). I have Python knowledge (intermediate at best) but never really use it in my day to day, so my question is - is it worth enhancing my knowledge of python, or is it worth picking up Go and learning that? If so what are use cases in your current role of using something like Go? As the title DevOps is very wide and mine leans more towards the cloud infra side of responsibilities (most of my day to day revolves around AWS).

Thanks in advance!

Top answer
1 of 12
12
If an interview requires live coding i just nope out of it because I have not written serious code in like 5 years. I would get better with python, but Go is often used for writing kubernetes admission controllers, so if that is something you want to get into then Go would be a good option.
2 of 12
8
We don't require live-coding during our interviews, primarily because we're not software developers, and they're intimidating for people being interviewed. We offer candidates an option of live-coding interview if they want it, or a take-home assignment instead which most people take. We need some way to know that people applying can do what they're talking about (i.e. they have practical knowledge not just theoretical knowledge), so that's why some form of coding is required during the interview process. Our take-home / live coding is generally terraform / ansible / bash, maybe some minimal python. On my team, most engineers can't write well-optimized python code, since they have an IT background (not a CS background) and didn't learn things like time and space complexity, multithreading / multiprocessing and advanced data structures. It's going to depend on where you work if you need more than just basic python knowledge to land a job, depending generally on how much automation your team needs to write. I do most of the python automation on our team since I have both IT and programming background, and we don't have enough automation workload that multiple engineers are required. We would rather have additional engineers that can do more common tasks for our org, such as advanced networking, kubernetes, etc. Not every engineer is going to know everything.
🌐
Reddit
reddit.com › r/devops › devops and interviewing
r/devops on Reddit: DevOps and interviewing
April 4, 2019 -

Hello,

I’m testing the interview waters in my area and am noticing a pattern that DevOps and SRE interviews are starting to incorporate more software engineer practices into their interviews. How do you feel about having to start grinding out leetcode problems to prep and pass interviews?

I usually don’t have to whiteboard or code solutions to problems in interviews especially as someone who has been doing this since 2011 and held titles as Senior Ops Engineer, Senior Cloud Engineer and DevOps engineer (I know, shouldn’t be a title).

I’m an Ops person who can code and I automate things daily with git, bash, python, groovy using Jenkins but what I am not is a software engineer with a CompSci background.

🌐
Reddit
reddit.com › r/devops › need guidance for devops coderpad interview
Need guidance for Devops coderpad interview : r/devops
February 14, 2026 - And rattled is a terrible way to interview. ... Yes, I studied using chatGPT, my prompt was “ask me medium challenge devops coding questions”, and I prepped for two weeks · Coderpad has a “try it out” sandbox that I coded in to prep in the actual environment too, by the time I got to the interview I was not too worried.
🌐
Reddit
reddit.com › r/devops › is there a devops equivalent of "cracking the coding interview" ?
r/devops on Reddit: Is there a devOps equivalent of "Cracking the coding interview" ?
November 3, 2023 -

I've found "Cracking the Coding Interview" without much value for entry level / beginner devOps interview questions . Is there a comparable go-to resource for DevOps jobs? I'm on the lookout for a book or resource that covers technical skills, best practices, and real-world scenarios specific to DevOps, akin to how "Cracking the Coding Interview" prepares software engineers for technical interviews. Any recommendations or insights into a comprehensive DevOps guide would be greatly appreciated. Thank you!

Find elsewhere
🌐
Reddit
reddit.com › r/devops › devops interviews and coding tasks...
r/devops on Reddit: DevOps interviews and coding tasks...
July 31, 2024 -

Last time I switched jobs was 3 years ago, and yeah, its job hunting season again. Now, the difference between 3 years ago and now is that no one had leetcode shit on their devops interviews, while I see everyone around me complaining about them now. Really? Apart from having to memorize a billion of network/infra/etc shit, now I have to grind python/bash leetshit in the age of gpt? What's your experience with that, and where would you recommend I start? Is there some collection of really nice devops flashcards I could use, and regarding python/bash, I assume basic level of knowledge is enough?

🌐
Reddit
reddit.com › r/devops › my top 20 devops interview questions (from about 80 interviews)
r/devops on Reddit: my top 20 DevOps Interview questions (from about 80 interviews)
February 4, 2024 -

Hi Gents, had lot of interview during past 3 years..some companies I interviewed for were Apple, Elastic, Orange, DeliveryHero, CGI, etc.

Took me whole weekend to remember questions and write them, hope it will be useful:

Updated for 2026:

https://www.linkedin.com/pulse/20-devops-interview-questions-every-engineer-should-know-alex-muradov-wtome

EDIT: fixed link

If you liked it, please press like so I could do more of devops content, thank you

🌐
Reddit
reddit.com › r/devops › i have a devops interview tomorrow. can someone give me some tips?
r/devops on Reddit: I have a DevOps Interview tomorrow. Can someone give me some tips?
December 4, 2023 -

Been hunting for a tech job for 4 months now, and started applying to DevOps jobs because I wasn't getting SE hits. (I have 8 years in the industry overall, but this current market is crazy!)

I haven't been DevOps per say, but a lot of my experience has me doing DevOps related stuff, such as running terraform, creating monitors, doing deployments, etc.

Anything in particular I should do to prep for an interview? The place uses Microsoft Azure, and it seems like they use terraform specifically. One thing I've done is started an azure account and made some resources via terraform, but I really am not sure what to expect in the interview. Usually I would do coding problems in a software engineer interview, but I don't think that's the case here.

Job description doesn't have a whole lot to go on. Just says its entry level, Azure, would likely be doing deployment pipelines, running terraform, assisting with monitoring and logging, and working in an Agile environment.

🌐
Reddit
reddit.com › r/devops › my devops interview experience, are they all like this?
r/devops on Reddit: My devops interview experience, are they all like this?
December 5, 2018 -

So I'm a developer that used ansible, terraform, docker and dabbled work a little bit of kubernetes and aws. I figured that I'd try to interview for a devops because it seemed interesting. I'm not a Linux system administrator, but I know about infrastructure as code and can figure my way around.

So I go for this devops engineer interview where the guys want to use openshift. They make the claim that they want to move to infrastructure as code and so on. Then the interview starts going downhill fast because I didn't know any Linux sysadmin and openshift theory. One example is to explain the differences between the different hdd formats and how does IP tables work and so on.

No questions on containers, infrastructure as code or anything devops in my mind.

Are all the devops interviews like this? Do people expect you to know Linux at this advanced level?

🌐
Reddit
reddit.com › r/devops › i collected devops interview questions and interview labs, for faang and other major companies.
r/devops on Reddit: I collected DevOps Interview Questions and Interview Labs, for FAANG and other major companies.
December 29, 2024 -

Hi Folks,

I posted before about my site where I collected and post DevOps interview questions.

Its mainly FAANG and other major companies like Amazon, Google, Meta, Netflix, Yahoo, Cloudflare, Accenture etc.. 

site is prepare.sh
I already explained how I get them (scraping major interview review platforms, certain forums, certain repos)

I have a major update for interview questions - I added new questions + Runtimes, so its not text based but rather IDE e.g. executable Python, Kubernetes, Terraform, questions in the code Editor + for cloud e.g. AWS questions you get AWS temporary Login/Password with infrastructure for the question deployed.

Added Labs... I realized from scrapes that most of the devops interview reviews were not programming languages questions but asking to do something in devops tooling for that I added Labs: .. Currently about 100 labs.. It was not just me but other folks who reached out to me after my last post 4 months ago and volunteered to help. It will take lot of space to name each of them but they are mentioned in the website leaderboard.

Most of the labs are free, the logic here is simple - if it doesn't cost me much to deploy and run it will be free, same goes for questions. As I promised before, previous text based questions will also remain free.

if anyone wants to help build it further - let me know.

(btw scraping process is explained in footer if anyones curious...)

🌐
Reddit
reddit.com › r/devops › devops interview questions
r/devops on Reddit: DevOps Interview questions
October 24, 2022 -

What are some common interview questions for devops in aws and python? I have an interview coming up and need to prepare for it….anything helpful is much appreciated!

Top answer
1 of 5
10
Google has a very nice video on doing interview with them - https://www.youtube.com/watch?v=XKu_SEDAykw Note that the most important part is not to give the right answer right away, but to talk through how you are thinking about the problem. Also keep in mind that in most of the places it's totally acceptable to ask interviewer a question if you forgot something, some places are even totally cool with you googling your way through the question. If interview is remote (which it most likely is), you will be doing with peer programming site - like codeshare or something similar, make sure you are familiar with how it works. Some of them have quite good web editors with support for common shortcuts, some will run your code for you - just make sure you are comfortable with technology before the interview.
2 of 5
5
The best interview questions are conversational. Tell me about an infrastructure, deployment process, etc. you setup and what trade offs you made and what you’d do differently had you had to start over and do it again today. I may butt in with a clarifying question here or there, but otherwise I let the interviewee speak through the process. It’s great because it gives them the chance to talk about something they know. It also lets me dig deep into their logic process and critical thinking skills. Their knowledge on trade offs is great because anyone in DevOps knows there’s 10 ways to do the same thing and what you did a year ago may be completely different than what you’d do today. If they are brief in their answer I may interject challenges into their answer to see how they’d navigate through. I may also bring up weighing cost (time or dollar) against their answer and see their thought process through that. I concede this requires the interviewer to also know a bit about DevOps to run an interview this way. But by in large this has been the best interview process, smoothest, and clearest identifier of someone’s depth of knowledge so far
🌐
Reddit
reddit.com › r/devops › devops interview questions/code tests.
r/devops on Reddit: DevOps interview questions/code tests.
June 20, 2018 -

Guys hi,

We will be adding DevOps person to our small team. What are some good questions/code challenges we can ask to weed out bad candidates?

Task Details:

We will need to develop set-up similar to one described here, but using Deployer instead of Capsitrano.

Ideally to add deployer into this docker-image we already using and which have lots of useful tools preinstalled.


p.s. Something simple but on the point, for example this simple CSS question

What is the difference between following CSS lines

T1 T2 {};

T1, T2 {};

T1 > T2 {};

T1 + T2 {};

Helped weed out lots of so called front end gurus. Something similar for DevOps.

IMPORTANT: The example question is not for DevOps candidate - it's just a sample of what we use to ask FE candidates. So looking for suggestion for something similar for DevOps.


UPDATE1: Since linux knowledge is important for out task i think it's good idea to include couple of questions from here.


UPDATE2: Thank you guys for all your great suggestions. Lots of you mentioned importance of open ended / big picture questions.

I've just searches passed similar threads on the topic and gathered some good ones:

Tell me about a time when you saved your production environment. How did you identify the problem? How did you fix the problem? What did you do to make sure it didn't reoccur?

.

What's the worst clusterfuck of a project you ever worked on? Was it a success or failure? What part did you play? Where did it all go wrong? How would you do it all over again?

.

Diagram the system you currently run. Do you have any criticism of the architecture you just outlined?

Also i really liked that one

That's actually how we conduct (a large part) our interview. We draw up a basic lamp stack from the early 2000's and then ask them to draw and discuss how they would scale it to modern days standards. We ask them to talk about various pieces and parts along the way, why they chose this over that, how are they securing things, important metrics, etc. There's no PASS/FAIL here, just a sense of how proficient someone is. I've found this approach VASTLY superior then launching a bunch of various textbook linux questions/scenarios at them.

I wonder what is good reply to that " basic lamp stack from the early 2000's" question?

🌐
Reddit
reddit.com › r/devops › coding prep for devops & sre interviews - request guidance
r/devops on Reddit: Coding prep for DevOps & SRE Interviews - Request Guidance
October 20, 2023 -

I have a few interviews coming up for DevOps Engg and SRE positions(Mid Senior Levels). I have been trying to find info on what kind of questions are usually asked but most of the data out there seems to be generic & vague.

It would be helpful if you could provide some clarity on the kind of preparation needed and the kind of usual questions to expect(few examples will be great). I've been brushing my python concepts for the past few days.

Top answer
1 of 3
8
Coding exercises are pretty much basic. Here is a template, parse it and replace some key values with a prefix derived from some rule. E.G. use the folder name of the repo. Real world use case is to dynamically create a helm chart. Parse these logs for only 5x0 errors. There will be some 5xx littered for things in the log like USER agent and size, the 5x0 we want are between the METHOD and user agent in a regular Apache or NGINX http server log.Then pipe those referrer IP to a CSV so you can auto-ban those people and call an API to get geolocation to block BRIC countries (non friendly countries). The second script should consume that CSV and call the Firewall to with payload of which IPs/Subnet to ban. A lof of reading files, parsing, manipulating, and calling a regular API (to get geo location).So basically a mid-level developer. They can choose BASH, Python or Go. We don't do Powershell as we are not a Window shop. Those are fairly basic type questions. I may even do something like I want a password strength validator base on this logic. 8 chars, special characters, and mix of upper/lowercase. Walk me through how you tackle this. Choose any language you want. A more experience engineer would just write a oneline regex versus someone who writes 60 line code with a lot of if-thens. And you can tell who uses ChatGPT because we are not looking for the code but how they think.
2 of 3
2
Hey, Python most definitely and throw in some Golang as well. I don’t know whether your company does leetcode or not, but being familiar with these two languages is always a plus. Apart from that, I’d mostly expect a conversation about your past projects and maybe some mock code review. Also, if they use K8S revise some typical troubleshooting scenarios, but if you’ve used it then I think you’ll be just fine. Same with cloud concepts. Unfortunately it’s highly dependent on the company. Best of luck!
🌐
Reddit
reddit.com › r/devops › coding interviews for sre/devops
r/devops on Reddit: Coding interviews for SRE/DevOps
September 19, 2020 -

So I am a Sr. SRE and am curious how others in this space deal with coding interviews? I mean I code day to day and automate stuff but that is mostly Jenkins, Terraform, Python and some Bash but I am by no means a Software Engineer.

I do know that for SRE it is basically taking a Software Engineer and having them do an operations job or task however a lot of titles that were DevOps Engineer ( I know shouldn't be a title), are now SRE.

What kind of prep can I do because like I said I can code and automate stuff but I am far from a SWE, have no CompSci degree yet I'm being asked to do LeetCode type challenges in interviews?

Thanks for any suggestions or feedback.

🌐
Reddit
reddit.com › r/devops › programming interview for a devops position - why?
r/devops on Reddit: Programming interview for a DevOps position - Why?
March 19, 2019 -

Hey all,

I've applied to a DevOps Engineering position and I made it to the third round of interviews. However, this is supposed to be a programming interview and I don't have a clue A) what they're expecting of me or B) why there's a programming interview in the first place. The job posting states that proficiency in a language is a bonus my conversations with the recruiter and the hiring manager didn't seem to indicate that programming would really be part of the job.

I'm brushing up on my Python to prepare but I haven't been exposed to a whole lot of programming in my very young career (started with DevOps positions out of the gate and I was a non-CS major).

So my question is - what should I expect out of this interview? How much are they going to expect me to know? I plan on being honest with them about my skill level and have a conversation about the actual job, but I'd still like to do well with the actual programming.