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. More on reddit.com

lmao are you the guy I am interviewing in 4 days?

if so, you should know enough Docker to dockerize a low-effort json microservice in some language of your choice, and then enough kubernetes to create a k8s manifest to let us test your results with a simple kubectl apply, and for extra credit know how to use terraform, and above all else demonstrate the ability to document your work intelligently (briefly, concisely) and communicate with coworkers and client engineers

More on reddit.com

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. More on reddit.com

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. More on reddit.com