Technical screening questions
Ask for one example per question and listen for specifics.
- How do you troubleshoot a server that is slow? A good answer: CPU, memory, disk and network checks in order.
- How do you manage permissions? A good answer: Users, groups, file modes and sudo.
- How do you patch production servers safely? A good answer: Staging, maintenance windows and rollback.
- How do you harden a server? A good answer: Minimal services, SSH settings and firewall.
- How do you automate repetitive tasks? A good answer: Scripts and configuration management.
Quick screening questions
Use these when you have only a few minutes.
- How many servers did you manage?
- How do you automate patching?
- Walk me through diagnosing a server that is slow.
What separates the levels
Match the level to the requirement before you submit.
- Junior: handles routine tasks.
- Mid: manages servers and automation.
- Senior: designs infrastructure and standards.
Red flags
Any of these is a reason to probe further.
- Only used a desktop Linux.
- Cannot troubleshoot performance.
- No scripting.
Tools you should hear mentioned
A Linux administrator with real experience usually names several of these without prompting.
- Red Hat or Ubuntu
- Bash scripting
- systemd
- SSH and networking tools
- Ansible
- Monitoring tools
Run the call well
Ask for the last project first, then dig into the second or third question. Take notes on versions, team size and outcomes, and record them with the submission so the vendor’s later technical interview does not surprise you.
Frequently asked questions
How long should a Linux administrator screening call take?
Fifteen to twenty minutes is enough to cover the project, three technical questions and availability, rate and work authorization.
Do recruiters need to know the technology?
Working vocabulary is enough. Use the sourcing guide for the role and listen for specifics instead of judging technical depth yourself.