--- title: "Bash / Shell Scripting Interview Questions (2026): By Level, With Model Answers" url: https://weworkworldwide.com/bash-shell-scripting-interview-questions/ description: "Bash and shell scripting interview questions for junior, mid and senior engineers — variables, quoting, exit codes and safe scripting — with answers and red flags." date: 2026-07-04T16:00:42+00:00 source: https://weworkworldwide.com/llms.txt --- # Bash / Shell Scripting Interview Questions (2026): By Level, With Model Answers How to use this Shell scripts run critical automation and fail silently when written carelessly. These questions check whether a candidate writes robust, safe scripts. Hiring a Bash / Shell developer is easy. Telling a real one from a convincing résumé is the hard part — and it’s most of what we do. These are grouped by level, because the same question that stretches a junior is a warm-up for a senior. ## Junior Bash / Shell interview questions 0–2 years Fundamentals. ### What is the shebang line? What a strong answer covers The `#!/bin/bash` (or `/usr/bin/env bash`) at the top telling the system which interpreter to run. Red flag Omits it and the script runs under the wrong shell. ### How do variables work in shell? What a strong answer covers Assigned with no spaces (`x=1`) and referenced with `$x`; everything is a string by default. Red flag Adds spaces around `=` and it breaks. ### Why must you quote variables? What a strong answer covers Unquoted variables undergo word-splitting and globbing, breaking on spaces or special characters; quote with `"$var"`. Red flag Uses unquoted variables and scripts break on spaces in paths. ### What are exit codes? What a strong answer covers A command’s numeric status: 0 for success, non-zero for failure, checkable via `$?` and used in conditionals. Red flag Ignores exit codes and assumes commands succeed. ### What is the difference between `$@` and `$*`? What a strong answer covers `"$@"` preserves each argument as a separate quoted word; `"$*"` joins them into one — `"$@"` is almost always what you want. Red flag Uses `$*` and mangles arguments with spaces. ### How do you write a conditional? What a strong answer covers `if` with `[[ ... ]]` tests, checking strings, numbers or files; understand the difference from `[ ]`. Red flag Mismatched test syntax causes silent bugs. ### How do loops work in bash? What a strong answer covers `for` over lists/globs and `while` reading input; quoting and IFS matter when iterating. Red flag Iterates over unquoted command output and splits wrongly. ### What is the difference between single and double quotes? What a strong answer covers Single quotes are literal; double quotes allow variable and command expansion. Red flag Expects variables to expand inside single quotes. ## Mid-level Bash / Shell interview questions 2–5 years Robust scripting. ### What does `set -euo pipefail` do? What a strong answer covers Exit on error, treat unset variables as errors, and fail a pipeline if any stage fails — a safer default for scripts. Red flag Writes scripts that plough on after failures. ### What is command substitution? What a strong answer covers Capturing a command’s output with `$(...)` for use in variables or arguments. Red flag Uses backticks and nests them badly. ### How do pipes and redirection work? What a strong answer covers Pipes feed stdout to the next command; redirection sends streams to files, with `2>&1` combining stderr and stdout. Red flag Loses error output by redirecting only stdout. ### How do you handle errors and cleanup? What a strong answer covers Check exit codes, use `trap` for cleanup on exit/signals, and fail fast rather than continuing in a bad state. Red flag No cleanup; leaves temp files and partial state. ### What is the difference between `[[ ]]` and `[ ]`? What a strong answer covers `[[ ]]` is a bash builtin with safer parsing and pattern matching; `[ ]` is the older POSIX test with more pitfalls. Red flag Uses `[ ]` and hits word-splitting bugs. ### How do you read input safely in a loop? What a strong answer covers `while IFS= read -r line` to avoid trimming whitespace and mangling backslashes. Red flag Uses `for line in $(cat file)` and splits on spaces. ### What is the difference between sourcing and executing a script? What a strong answer covers Executing runs it in a subshell; sourcing (`. script`) runs it in the current shell, affecting its environment. Red flag Expects a sub-script to change the parent’s variables. ### How do you make scripts portable? What a strong answer covers Target a specific shell, avoid bashisms if POSIX sh is needed, and don’t assume GNU-specific tool options. Red flag Assumes bash and GNU tools everywhere. ## Senior Bash / Shell interview questions 5+ years Reliability and maintainability. ### When should you stop using bash and switch languages? What a strong answer covers When a script grows complex, needs data structures, robust error handling or testing — a real language becomes safer and clearer. Red flag Writes thousand-line unmaintainable bash. ### How do you make scripts idempotent? What a strong answer covers Check current state before acting so re-running is safe (e.g. create-if-not-exists), important for automation. Red flag Scripts that fail or duplicate work on a second run. ### How do you lint and test shell scripts? What a strong answer covers Static analysis with ShellCheck and testing frameworks (bats), catching quoting and logic bugs early. Red flag Ships untested scripts and debugs in production. ### How do you handle secrets in scripts? What a strong answer covers Read from environment or a secrets manager, avoid passing them on the command line (visible in process lists), and never hardcode. Red flag Hardcodes credentials or passes them as visible arguments. ### How do you write scripts safe for automation/cron? What a strong answer covers Absolute paths, explicit environment, robust error handling, logging, and locking to prevent overlapping runs. Red flag Relies on interactive environment assumptions that fail in cron. ### What are common security pitfalls in shell scripts? What a strong answer covers Unquoted input, `eval` on untrusted data, insecure temp files, and command injection via unsanitised variables. Red flag Uses `eval` on user input. ### How do you structure larger shell scripts for maintainability? What a strong answer covers Functions, clear naming, `set -euo pipefail`, usage/help, and separating logic from configuration. Red flag One long flat script with no functions. ### How do you debug a failing shell script? What a strong answer covers `set -x` for tracing, checking exit codes at each step, and ShellCheck for latent issues. Red flag Adds echo statements everywhere with no tracing. **Skip the screening entirely.**We vet Bash / Shell engineers so you don’t have to — embed one in your team, or have us build it. [Hire Bash / Shell developers](https://weworkworldwide.com/hire-remote-devops-developers/)[Compare us](https://weworkworldwide.com/compare/) Build and score a full interview with our free [interview scorecard tool](https://weworkworldwide.com/developer-interview-scorecard/), browse the [full question hub](https://weworkworldwide.com/interview-questions/), or see [how we interview engineers](https://weworkworldwide.com/how-we-interview-engineers/).