How to assess · For hiring teams
How to Assess Linux Administration Skills When Hiring
The test formats that actually work for Linux Administration, what a strong answer looks like, sample questions and a scoring rubric you can use as-is.
The short answer
Assess Linux Administration with a task, not a conversation: broken-system troubleshooting, paper diagnosis, ai-scored assessment (e.g. cohesyve) or scripting task. Score it against written criteria you fix before you see any submissions, and weight the criteria that the role actually depends on.
- Troubleshoots methodically: logs and journal, process state, resources, network, permissions — in an order that narrows quickly
- Understands processes, signals, users and permissions well enough to reason about what a system will do
- Reads and writes shell competently, and knows when a script should become something more robust
- Diagnoses networking with the standard tools and can explain what each layer is telling them
Paste a job description; Cohesyve generates a role-specific assessment and rubric. Ten candidates free, no card.
Linux administration is mostly diagnosis: a service that will not start, a disk that is full, a process eating memory, a permission that is wrong. The skill is knowing where to look and in what order, and having enough understanding of the system to interpret what you find. It cannot be read off a certification list, and it shows within minutes when a candidate is handed a broken box. This page covers how to assess Linux administration for infrastructure, SRE and support roles: troubleshooting method, the process and filesystem model, networking, security basics, and automation.
Why Linux Administration is worth testing
The cost of weak Linux skill is time: an outage that takes two hours instead of ten minutes because the administrator did not know to check the journal, a security exposure from a permission set to 777 to make an error go away. Testing shows whether a candidate has a method and a mental model, and a broken-system exercise reveals it faster than any conversation.
What strong Linux Administration looks like
- Troubleshoots methodically: logs and journal, process state, resources, network, permissions — in an order that narrows quickly
- Understands processes, signals, users and permissions well enough to reason about what a system will do
- Reads and writes shell competently, and knows when a script should become something more robust
- Diagnoses networking with the standard tools and can explain what each layer is telling them
- Applies security basics: least privilege, no unnecessary services, patched, logged
- Manages services with systemd and can read a unit file
- Automates repeated work and documents what is not automated
Ways to assess Linux Administration
Broken-system troubleshooting
Provide access to a VM or container with three planted faults — a service failing due to a bad config, a full disk, a permission problem on a directory it needs. Ask the candidate to get the service running and explain each fix. Forty-five minutes.
Pros
Cons
Best for Any level; scale via fault subtlety.
Paper diagnosis
Provide command outputs — `systemctl status`, journal excerpts, `df`, `ls -l`, `ss` — for a failing system and ask for diagnosis and fix.
Pros
Cons
Best for Screening before a practical.
AI-scored assessment (e.g. Cohesyve)
Generate a Linux scenario from the job description — a troubleshooting case, a security review, a script task — with a rubric. Each candidate receives a different variant; reasoning is scored in writing.
Pros
Cons
Best for Screening a large pool.
Scripting task
Ask for a script that rotates logs, checks disk usage and alerts, with error handling. Thirty minutes.
Pros
Cons
Best for Roles with automation responsibility.
Cohesyve
Run a Linux Administration assessment on your next opening
Cohesyve generates a unique Linux Administration task per candidate from your job description, with the scoring rubric attached. Questions are different for every applicant, so they cannot be shared or looked up.
What to test
Troubleshooting method
Whether they narrow a problem quickly.
System model
Whether they understand what the system is doing.
Networking
Whether they can diagnose connectivity.
Security and automation
Whether the system is safe and maintainable.
Sample Linux Administration questions
A service fails to start. What are the first three commands you run?
EntryLook for systemctl status, journalctl for the unit, then check its config or dependencies; method over guessing.
The disk is full but `du` does not account for it. What might be happening?
MidLook for A deleted file held open by a process; find with lsof; restart or truncate.
A web service is running and listening, but clients cannot connect. Diagnose.
MidLook for Check the bind address, firewall, security groups, then network path; use ss, curl from localhost, then from outside.
Someone set a directory to 777 to fix a permission error. What do you do?
MidLook for Revert, find the actual user the service runs as, grant the minimum, explain the risk.
How would you make fifty servers consistent and keep them that way?
SeniorLook for Configuration management or images, drift detection, patch process, and a way to rebuild rather than repair.
Red flags
- Guesses instead of reading logs
- Uses 777 permissions or runs everything as root
- Cannot explain what systemd does
- Has never diagnosed a network problem beyond ping
- Fixes things by hand with no record
Scoring rubric
| Criterion | Weight | What strong looks like |
|---|---|---|
| Diagnostic method | 35% | Narrows quickly using the right tools in the right order. |
| System understanding | 25% | Processes, permissions and services are understood, not memorised. |
| Networking | 15% | Can locate a connectivity problem by layer. |
| Security | 15% | Least privilege and hardening by habit. |
| Automation | 10% | Repeated work is scripted robustly. |
Mistakes hiring teams make
- Testing command trivia instead of diagnosis
- Not planting real faults — the ones that cause outages
- Accepting a fix that works but is insecure
- Confusing certification with troubleshooting ability
- Skipping networking because "that is a different team"
Roles that need Linux Administration
Common questions
Do I need a live environment to assess Linux skill?
It is best, and a disposable container makes it cheap. Paper diagnosis from command outputs works well for screening and tests the same interpretation skill.
What is the most telling Linux question?
A failing service with the journal available. Method, tools and understanding all show in five minutes.
Should I test a specific distribution?
Test the one you run, but the fundamentals — systemd, permissions, networking — are common to modern distributions.
How much Linux should a developer know?
Enough to read logs, find a process, check disk and memory, and understand permissions. Administration beyond that is an infrastructure role.
Cohesyve · Skill assessments for hiring
Test Linux Administration before the first interview
Generate a role-specific Linux Administration assessment from your job description and see who can do the work before you spend interview time on them.
1,500+
assessments completed
50%
faster time-to-hire
90%
completion rate
5 min
from JD to assessment
No credit card · 10 free candidates · Plans sized to your hiring volume
From the blog