Automation and Scripting Questions

Covers practical and architectural skills for writing production safe automation and operational scripts as well as building reusable automation systems. Topics include designing idempotent automation, safe retries, robust error handling, structured logging and observability, argument parsing and command line interface design, configuration management, and secure credential handling. Emphasis on testing and validation of scripts and automation code, packaging, documentation, deployment, and maintainability so automation can be operated by other team members. Includes integration with schedulers such as cron and systemd timers, continuous integration and continuous delivery pipelines, orchestration and configuration management systems, and common operational patterns such as log processing, backups, polling, multi step orchestration, provisioning, configuration changes, and routine maintenance. Also assesses language selection and trade offs among Python, Go, Bash and other tooling, concurrency and performance considerations, and at senior levels the design and architecture of reusable automation frameworks and strategies for scaling automation to reduce toil.

HardTechnical

0 practiced

You need to build a high-throughput automation worker to process ~10k small tasks per minute. Compare implementing this worker in Go (goroutines and channels), Python (asyncio or multiprocessing), and Bash orchestrating external tools. Discuss startup latency, memory footprint, concurrency safety, packaging, observability, error-handling and developer ergonomics.

EasyTechnical

0 practiced

Provide a Bash command or short script to find files under /var/log that are larger than 100MB and older than 30 days, printing human-readable size and full path in a way that safely handles filenames with spaces or newlines. Explain why it is safe to run from cron.

HardTechnical

0 practiced

A CI/CD pipeline credential was compromised and an attacker injected a malicious automation job that executed across production nodes. As SRE, outline the incident response steps: containment, secrets rotation, forensic evidence collection (CI artifacts, logs), rollback of affected systems, remediation to prevent recurrence, and stakeholder communication.

MediumTechnical

0 practiced

You are building automation that calls an external payment API. Describe a robust error-handling strategy: include timeouts, retries with exponential backoff and jitter, idempotency keys for non-idempotent endpoints, circuit-breaker logic, alerting thresholds, and how to surface incidents to operators without causing noise.

EasyTechnical

0 practiced

Describe the principle of least privilege as applied to automation agents and scripts. Provide at least two concrete tactics (e.g., scoped service accounts with minimal roles, short-lived credentials via OIDC or vault-issued tokens) and explain how to validate and audit that privileges are minimized.

Unlock Full Question Bank

Get access to hundreds of Automation and Scripting interview questions and detailed answers.

Join thousands of developers preparing for their dream job.