Собеседование DevOps: специально завалил все тех вопросы

Are you afraid of going to a DevOps technical interview? I conducted an experiment: I went to a real tech interview and intentionally flunked all the questions to show there was absolutely nothing to be afraid of. In this video, I intentionally answer "I don't know," say I haven't worked with the necessary tools, and deliberately get confused when answering technical questions about infrastructure. And you know what happened? The interviewer himself starts telling me the right solutions! This interview shows that even if you go in with absolutely zero knowledge, an IT interview is the most useful and free way to learn. You don't just develop resilience, you get direct answers and understand what the market is currently demanding. Stop fearing rejection, watch how technical interviews actually go, and use this life hack to improve your skills. ⚡️ My work record, resume samples, and lifestyle: https://t.me/tylnyi_blog #devops #interview #techjobs #ITperson #entervitity 00:00 Experiment: deliberately failing the DevOps techjob 00:40 How a completed task is evaluated and what is GitOps 02:04 Basic Git questions: what's the difference between git pull and git fetch 03:32 Team development: how to merge a branch if master is way ahead 07:39 Candidate's honest answer: "I can Google it in 5 minutes" 10:12 Fatal error: accidentally leaked a database password to an open repository 11:29 The interviewer suggests a solution: git reset and push --force 12:08 What to do next? Security (IS) Incident Interview 23:02 Troubleshooting: Nginx Log Disk Full 24:39 Linux Trap: Deleted Log Files, But Disk Space Still Remains 25:39 lsof Command: Finding Open File Descriptors 27:57 Who's Maintaining the Files? Finding a Hanging Filebeat Process 28:26 Logic Question: Why Do We Soft-Restart Nginx, But Kill Filebeat with Kill -9?