Thanks for the effort.

These type of questions are OK for a filter phone interview or entry-level Linux job imho as in they rely on "what is" questions (which can be memorized or replied without much experience) rather than "how would you" questions (the "demo time" at the end, that's the good part). You want to ask scenario and troubleshooting questions rather than trivia for jobs other than basic ones. (You can certainly ask more advanced non-scenario -still relatable or practical- questions about things like system calls, interrupts, CPU scheduling etc, "system internals" stuff that I don't see at all or barely in these questions. A Linux questionnaire without mentioning strace or perf hurts my heart.)

I can basically nit-pick, find a fault or find a better way of asking in pretty much every question.

The Expert section can be dropped (only one question).

Mysql section can be dropped, maybe replace with basic SQL section.

DevOps section can be dropped, we can see here how definition of DevOps is still fluid, just add Linux/Networking/General questions to their respective sections (also "GIT", really?).

One reference link at the bottom doesn't work.

----

Examples of issues with questions and how to improve them:

- What commands do you know that can be used to check DNS records?: instead ask how to troubleshoot DNS issues, like how to check if a name server has an entry. How does local DNS work? (as in what's the order in which files/servers are checked to resolve a name, where is that stored) how does DNS in general works? (as in you ask for a record to a name server and it doesn't have it, now what). How much TTL would you set in a record and why. Why does DNS run on UDP and TCP?

- "tac", (really? and no "grep" "sort", "uniq" or "sum"?), rather ask how to print a field from a command like 'df' or 'free' or how to add column values from a text file (basically if they can slice horizontally with grep and vertically with awk / cut and then count occurrences or sum numbers.

- What does & disown after a command do?: rather ask when you would use 'disown', or better, inversely how to de-attach a running command from terminal

- What is Virtual Memory? : not sure what you want them to answer here, maybe rather ask about a server with most of its total memory used, what does Linux cache (there's buffer and inode/dir caching besides files but only two memory caching areas), how to find that, when does the OS write stuff in RAM to disk (what are dirty pages), how do you change that frequency, when is better to do it more/less frequently or what's the tradeoff etc

- What is swap and what is it used for?: this is more advanced but you can ask if a server can have no swap, is it possible for a server with plenty of free RAM to page (write to swap)? can you reduce/increment tendency to swap? why would you do that, how much swap partition would you set up (OK these are a bit of tricky questions, more to gauge experience)

- How to search for the string "my konfi is the best" in files of a directory recursively? : I actually like this one

- How to connect to a remote server or what is SSH? : you can split in "list all the possible ways you can think of so you can communicate (or send message/file) between two servers on a network" and a question about how SSH works from Linux point of view (not protocol), sshd settings (idea, not memorized params), how to set up passwordless (key-based) SSH, hardening tips, how to troubleshoot if you can't ssh to a server (no firewall, you can telnet/whatever), what does it mean when you get a message "key has changed etc", what's a private and public key...

- What is the sticky bit? : this depends on OS, I guess explaining different behaviours is good.

- What does the immutable bit do to a file?: this is not part of linux VFS but of particular filesystem implementations, btw no questions about what's a filesystem, what's a journaled one, difference between ext4 and xfs for ex. Also what about LVM?

- What is the difference between hardlinks and symlinks?: while a good question I'd rather ask when to use one or the other, also just to confuse, ask how to "link/map" a directory in a partition that is running out of space to a directory in a new partition with plenty of space, so that it works transparently.

- What is MAJOR and MINOR numbers of special files?: I guess device files, rather or besides ask difference between block and character devices, about pseudo dirs in file system: /dev /proc /sys , how to find hardware or process info (everything is pretty much in /proc or /sys , also dmesg )

- Describe a scenario when deleting a file, but 'df' not showing the space being freed. : this is good but it can be better built into a scenario: there's an "no space left on device" error, how to find biggest files/dirs. You find it's a huge web server access.log file, now you delete it and disk space doesn't seem to shrink, why (the df vs du), what can you do?, can you close the open file?

- Instead of "how does ps/top work?" ask something specific or scenario based, like how do you find if there's a disk I/O problem by looking at 'top' (there's at least two possible indicators). Zero questions about I/O, or for the matter, for server utilization metrics, which ones are they, how to measure each, how to find if they reached saturation, what happens in that case for each, how to look for errors in each. If a server is using 80% CPU is that good or bad?

OK I got tired here.

If you have read until this dear reader, would you be interested in my trying to create a Docker container or Amazon image with a Linux box and have these types of scenarios set up?