Tell me about yourself and your experience as a Linux administrator

Start with your current role and the most relevant recent experience, focusing on the systems and scale you manage and the outcomes you drove. Summarize the last 5 to 10 years, highlighting specific responsibilities such as configuration management, monitoring, backups, and incident response. Close by connecting that experience to the role you are interviewing for and one or two skills you want to grow in this job, and avoid reciting your entire resume or unrelated early career details.

Which Linux distributions have you worked with and how do you choose one for a project?

Explain the distributions you have used and why they were chosen, mentioning RHEL/CentOS, Debian/Ubuntu, or SUSE where applicable and the factors that drove the choice. Discuss practical considerations such as vendor support, package availability, compatibility with tooling, and existing team expertise. When choosing a distro for a project, prioritize support and ecosystem needs, and avoid picking based on personal preference alone without assessing operational impact.

How do you manage users, groups, and permissions on a Linux system?

Describe your approach to account lifecycle, including creating users with minimal privileges, using groups for role-based access, and applying correct file permissions and ACLs where needed. Give a concrete example such as creating a deploy group, setting directory ownership with chown, and applying setgid bits so new files inherit group ownership. Mention common pitfalls like giving sudo to too many users and storing passwords insecurely, and recommend using centralized authentication like LDAP or AD where scale requires it.

How do you troubleshoot a server that fails to boot?

Outline a structured troubleshooting process: check console/serial output, review bootloader configuration, inspect kernel messages, and use rescue media if necessary. Provide a specific technique, for example booting into single-user mode by editing grub to add 'systemd.unit=rescue.target', then examining journalctl -xb and /etc/fstab for mounting issues. Advise documenting each step and restoring from backups only after isolating cause, and avoid making wide filesystem changes without a backup.

How do you monitor system performance and diagnose high CPU or memory usage?

Start with foundational tools such as top, htop, vmstat, iostat, and free to get a fast view of CPU, memory, and IO, then drill deeper with ps, perf, or pmap for process-level detail. Give an example workflow: use top to identify the offending process, pidstat to view per-thread stats, and strace or perf to inspect system calls or hotspots. Warn against guessing root cause from a single snapshot, and recommend collecting metrics over time with Prometheus, Grafana, or similar tools for trend analysis.

Explain how you handle patching and package management in production environments.

Describe a controlled patching process that includes staging, automated testing, a maintenance window, and rollback plans, plus using tools like apt, yum/dnf, or subscription management for patch application. Offer a concrete example such as testing kernel and library upgrades in a staging cluster, applying patches using Ansible playbooks, and monitoring for regressions for 24 to 72 hours before rolling to production. Emphasize maintaining current security patches and avoid running ad hoc updates directly on critical production nodes without change control.

How do you secure a Linux server against common threats?

Explain layered security steps such as minimizing installed packages, configuring a host firewall, enforcing SSH key-based access, and keeping systems patched, plus using file integrity checks and centralized logging. Provide a specific measure like hardening SSH by disabling root login, changing the default port if appropriate, and enforcing strong key policies and two-factor authentication for admin accounts. Mention common mistakes such as relying solely on obscurity or weak firewall rules, and recommend regular audits and automated compliance checks.

Describe your approach to backups and disaster recovery for critical Linux services.

Outline a backup strategy that defines Recovery Time Objective and Recovery Point Objective, includes full and incremental backups, verifies integrity, and stores copies offsite or on separate cloud storage. Give an example backup flow such as using rsync or Borg for filesystem backups, mysqldump or physical snapshots for databases, and periodic test restores to validate procedures. Stress the importance of automation and testing, and avoid keeping only a single recent backup without versioning or verification.

How do you use shell scripting to automate routine sysadmin tasks?

Describe writing small, well-documented scripts that handle idempotent tasks, check for errors, and log actions, and explain choosing shell, Python, or Perl based on complexity and maintainability. Provide a concrete example like a daily disk usage report script that runs df, parses output, and emails alerts if thresholds are crossed, or an Ansible task that performs the same at scale. Suggest keeping scripts in version control and avoid hard-coded paths or credentials inside scripts.

Explain filesystems, swap, and LVM and when you would use logical volumes.

Summarize filesystems like ext4 and XFS, swap usage for memory pressure, and LVM for flexible volume management and snapshot support, describing trade-offs for performance and recoverability. Give a specific example such as creating an LVM volume group across two disks, carving a logical volume for /var, and taking snapshots before major upgrades with commands like pvcreate, vgcreate, lvcreate, and lvcreate --size 1G --snapshot. Warn about common pitfalls like snapshot space exhaustion and not monitoring free space in volume groups, and recommend monitoring and periodic maintenance.

Tell me about a time you handled a major production outage

Situation: Our web cluster experienced cascading failures during a deployment window, causing service degradation for several hours. Task: As the on-call Linux administrator, you had to identify the root cause, restore service quickly, and prevent recurrence. Action: You triaged logs across multiple nodes, reverted the deployment using orchestration tooling, and isolated a faulty configuration change by comparing recent commits and rollout timing, then applied a tested rollback and scaled up healthy instances. Result: Service was restored within the SLA window, incident postmortem identified process gaps, and the team implemented a pre-deploy checklist that reduced similar incidents by measurable frequency.

Describe a time you disagreed with a team decision and how you handled it

Situation: The team decided to delay patching to avoid downtime during a busy quarter despite known security advisories. Task: You needed to convince stakeholders to balance risk and availability without creating conflict. Action: You gathered concrete data on the vulnerability impact, presented a mitigated patching schedule with staged canaries and rollback plans, and suggested short maintenance windows with communication plans to minimize impact. Result: Leadership approved a phased patching plan, critical vulnerabilities were remediated during low-traffic hours, and the team adopted your staged approach for future updates.

Give an example of when you improved an operational process

Situation: Incident response lacked consistent runbooks, leading to slow and inconsistent recovery actions across engineers. Task: You were asked to standardize response procedures for common Linux service failures. Action: You authored clear runbooks with step-by-step checks, automated initial triage scripts to gather logs and metrics, and ran tabletop drills to validate the process with the team. Result: Incident MTTR dropped, on-call stress decreased, and new engineers could follow runbooks to resolve issues faster with fewer escalations.

What is systemd and how does it differ from traditional init systems?

Explain that systemd is an init system and service manager that uses unit files to manage services and dependencies, offering parallel startup and socket activation. Give a practical example like using systemctl to start, stop, enable, or inspect services with commands such as 'systemctl status sshd' and 'journalctl -u sshd' for logs. Note common gotchas such as complex unit dependencies and masking services accidentally, and recommend reading unit files and journals instead of guessing service behavior.

How do you configure SSH for key-based authentication and harden it?

Describe creating an SSH key pair with 'ssh-keygen', copying the public key to the server's ~/.ssh/authorized_keys, and setting correct permissions on .ssh and authorized_keys. Provide a concrete hardening checklist such as disabling root login by setting 'PermitRootLogin no' in /etc/ssh/sshd_config, disabling password authentication with 'PasswordAuthentication no', and restricting access with AllowUsers or by using SSH certificates for large environments. Mention pitfalls like incorrect file permissions preventing key auth and forgetting to restart sshd after config changes, and always keep a recovery method like console access when changing SSH settings.

How do you set up LVM and create a new logical volume with commands?

Explain the LVM workflow: create physical volumes, create a volume group, then create logical volumes and format them for use. Give exact commands as an example such as 'pvcreate /dev/sdb', 'vgcreate vg_data /dev/sdb', 'lvcreate -L 50G -n lv_var vg_data', then 'mkfs.xfs /dev/vg_data/lv_var' and mounting with 'mount /dev/vg_data/lv_var /var'. Warn about resizing snapshots and ensuring you have adequate free extents before expanding logical volumes, and always backup important data before major volume changes.

How would you diagnose a process making many system calls using strace?

Describe using strace to attach to a running PID with 'strace -p ' or to run a command under strace to capture syscalls and signals. Provide a practical example like 'strace -f -o /tmp/trace.log myservice' to capture child processes and inspect the log for repeated failing syscalls such as open or connect errors. Note common pitfalls such as performance impact when tracing busy processes and the need to filter output with '-e' flags to avoid overwhelming logs.

How do you set up a basic firewall with nftables or iptables and what are common rules?

Summarize creating a default deny policy and allowing specific services, for example setting default input policy to drop and allowing established connections and SSH. Provide example nftables commands such as 'nft add table inet filter', 'nft add chain inet filter input { type filter hook input priority 0 \\; }', 'nft add rule inet filter input ct state established,related accept', and 'nft add rule inet filter input tcp dport 22 accept' to allow SSH. Point out common mistakes like locking yourself out by not allowing your current SSH connection, and recommend testing rules in a non-blocking mode or using a rollback timer.

How do you use rsync for backups, including an example command and gotchas?

Explain that rsync efficiently transfers changed files and can preserve permissions, links, and ownership, making it suitable for incremental backups. Offer a concrete command example like 'rsync -aHAX --delete --info=progress2 /srv/ /mnt/backup/srv/' which preserves attributes and removes files deleted on the source if desired. Warn about the '--delete' risk of accidental data loss, the need to test restores regularly, and handling open files on live systems either by using filesystem snapshots or database dumps for consistency.

How do you find and fix disk space issues caused by deleted files still held open by processes?

Describe identifying the issue by checking disk usage with 'df -h' and then finding deleted-but-open files with 'lsof +L1' which lists files unlinked from the filesystem but held by processes. Give a specific remediation example such as restarting the offending process gracefully to release the file descriptor, or truncating the file with '>' redirection like '> /proc/ /fd/ ' when restart is not feasible. Mention the pitfall of blindly killing critical processes, and recommend planning maintenance windows for restarts on production services.

How do you schedule tasks and when would you use a systemd timer instead of cron?

Explain cron for simple, recurring schedules and systemd timers for more integrated service-triggered tasks, calendar events, and precise dependency control with unit files. Provide an example like creating a service unit and timer that runs a backup.service with a timer unit containing 'OnCalendar=daily' and manage it with 'systemctl enable --now backup.timer'. Note that systemd timers offer better logging and failure handling, while cron remains simple and ubiquitous, and recommend choosing based on needs for dependencies and monitoring.

linux administrator Interview Questions: Complete Guide

Expect a mix of technical problems, scenario questions, and behavioral questions in linux administrator interview questions. Interviews often include a phone screen, a live technical exercise or whiteboard, and a behavioral round, so prepare for hands-on tasks as well as discussion of past incidents. Be confident, pragmatic, and ready to explain your troubleshooting process step by step.

Common Interview Questions

Behavioral Questions (STAR Method)

STAR Method: Structure your answers using Situation, Task, Action, and Result to tell compelling stories about your experience.

Technical Questions

Questions to Ask the Interviewer

Show your interest by asking thoughtful questions

•What does success look like in this role after the first 6 months, and what are the top priorities you want solved?
•Can you describe the team structure, who I would work with daily, and how on-call responsibilities are shared?
•What are the most frequent types of incidents or performance issues this infrastructure faces today?
•What tools do you currently use for configuration management, monitoring, and CI/CD, and are there plans to change them?
•How do you measure and track professional development for system administrators on the team?

Interview Preparation Tips

1
Practice live troubleshooting on a VM lab, and record your terminal session so you can review how you explain each step under pressure.
2
When answering technical questions, narrate your thought process clearly, state assumptions, and check in with the interviewer before making changes.
3
Prepare one or two concise incident postmortems you can explain in STAR format to demonstrate your operational maturity.
4
Study the stack mentioned in the job description, and set up a small environment that matches it so you can give specific examples during the interview.

linux administrator Interview Questions: Complete Guide

Michael Rodriguez

Common Interview Questions

Behavioral Questions (STAR Method)

Technical Questions

Questions to Ask the Interviewer

Interview Preparation Tips

Related guides

linux Interview Questions: Complete Guide

database administrator Interview Questions: Complete Guide

education administrator Interview Questions: Complete Guide

hospital administrator Interview Questions: Complete Guide

linux administrator Interview Questions: Complete Guide

Michael Rodriguez

Common Interview Questions

Q1Tell me about yourself and your experience as a Linux administrator

Q2Which Linux distributions have you worked with and how do you choose one for a project?

Q3How do you manage users, groups, and permissions on a Linux system?

Q4How do you troubleshoot a server that fails to boot?

Q5How do you monitor system performance and diagnose high CPU or memory usage?

Q6Explain how you handle patching and package management in production environments.

Q7How do you secure a Linux server against common threats?

Q8Describe your approach to backups and disaster recovery for critical Linux services.

Q9How do you use shell scripting to automate routine sysadmin tasks?

Q10Explain filesystems, swap, and LVM and when you would use logical volumes.

Behavioral Questions (STAR Method)

B1Tell me about a time you handled a major production outage

B2Describe a time you disagreed with a team decision and how you handled it

B3Give an example of when you improved an operational process

Technical Questions

T1What is systemd and how does it differ from traditional init systems?

T2How do you configure SSH for key-based authentication and harden it?

T3How do you set up LVM and create a new logical volume with commands?

T4How would you diagnose a process making many system calls using strace?

T5How do you set up a basic firewall with nftables or iptables and what are common rules?

T6How do you use rsync for backups, including an example command and gotchas?

T7How do you find and fix disk space issues caused by deleted files still held open by processes?

T8How do you schedule tasks and when would you use a systemd timer instead of cron?

Questions to Ask the Interviewer

Interview Preparation Tips

Related guides

linux Interview Questions: Complete Guide

database administrator Interview Questions: Complete Guide

education administrator Interview Questions: Complete Guide

hospital administrator Interview Questions: Complete Guide