Is It Normal to Rely on Documentation as a Sysadmin?
Asked by
MellowCedar42
I've been a Linux administrator at a small-to-medium-sized company for about two years. I'm comfortable troubleshooting issues with documentation and occasional help from AI, especially for tedious tasks, syntax, or unfamiliar concepts. However, I still struggle to remember basic Linux commands and write Bash scripts without checking notes or guides.
I narrowly missed passing the RHCSA last year, scoring about 10 points below the passing mark. Since then, I've helped deploy four large projects serving more than 200,000 users, including PostgreSQL clusters, MongoDB replication, multisite failover, load balancing, Docker applications, performance tuning, and security hardening. Those systems have remained stable since launch.
Despite these results, I often feel like I don't really know Linux because I need to look up even simple procedures. Is this normal? How would this typically be viewed for an L2 sysadmin role at a large multinational company? Should I be concerned, or is being able to find, understand, and safely apply the right information the more important skill?
Answers
The real skill is adaptability. You don’t need to remember every command, but you should know what kind of tool or concept to look for, how to read the documentation, and how to test the result safely. Focus on broad fundamentals—files, permissions, processes, networking, storage, and shell logic—then let references fill in the exact syntax.
A little uncertainty can even be useful in operations because it encourages you to double-check before changing production. Just make sure it motivates careful learning rather than preventing you from taking on new work.
Reply to this answer
Your results are evidence that you’re not an impostor. You’ve already designed or deployed complex systems and kept them stable. Feeling uncertain is common in infrastructure work because there is always another technology, failure mode, or environment to learn.
Keep building hands-on experience, write down what you learn, and avoid comparing your command recall to people who use the same tools every day. The goal isn’t to know everything—it’s to solve problems reliably and keep improving.
Reply to this answer
The projects you described are significant and say much more about your ability than a certification score. Certifications test a narrow set of skills under exam conditions, while real administration involves research, testing, change control, and knowing how to recover safely.
For an L2 role, employers will usually care about your troubleshooting process, judgment, communication, and ability to learn. Needing documentation is not a red flag unless you refuse to verify things or cannot understand what you’re reading.
MellowCedar42: I think focusing on RHCSA, RHCE, and Kubernetes certifications has made me judge myself too much by exam performance.
Reply to this answer
Yes, this is completely normal. Even people with decades of experience still look up commands, syntax, and obscure procedures—especially if they don’t use them every day. In production, correctness and verification matter much more than proving you can memorize every flag.
Your ability to understand documentation, troubleshoot unfamiliar problems, and deliver stable systems is far more valuable than being a command-line trivia expert. Your project experience is especially strong for someone with two years in the field.
MellowCedar42: That’s reassuring. I’ve been trying to focus more on understanding documentation instead of feeling bad that I don’t remember every command.
Reply to this answer
Try separating the process from the procedure. The process is the underlying goal—such as diagnosing a network problem, checking storage, or safely changing a service. The procedure is the exact set of commands, which can vary by distribution, version, and environment.
If you understand the process, finding the correct commands becomes much easier. For routine work, keep notes, use command history, and document reliable procedures. In well-run environments, automation and documented runbooks are preferable to improvising commands from memory anyway.
Reply to this answer
Add your answer
Answers are reviewed before publication.
RiverCandle63: A bit of “I might be wrong, let me verify that” is much safer than being overconfident and breaking production. As long as the doubt doesn’t paralyze you, it can make you a better administrator.