AutoSys Interview Questions and Answers — Complete Guide
- Master the ON_HOLD vs ON_ICE difference cold — it is tested in almost every AutoSys interview
- Know the autorep flags: default (status), -d (detail), -q (JIL dump), -s (filter by status)
- Be ready for scenario questions: EOD workflow design, PEND_MACH recovery, failed box recovery
AutoSys knowledge is tested in depth at companies that depend on it — financial institutions, insurance companies, healthcare organisations. Interviewers know the tool well and ask specific questions. Vague answers about 'scheduling jobs' won't get you far. This guide covers every category of AutoSys questions with complete, accurate answers.
The questions are organised from foundational to advanced. If you've worked through the rest of this AutoSys track, you know these answers already — this article is your review and consolidation.
Architecture and concepts
These questions test whether you understand what AutoSys actually is and how it works internally.
Q: What is AutoSys and what problem does it solve? A: AutoSys is Broadcom's enterprise workload automation platform for scheduling, monitoring, and orchestrating batch jobs across multiple servers. It solves the scalability problems of cron: dependency management, centralised visibility, alerting, audit trails, and multi-server coordination. Q: What are the main components of AutoSys architecture? A: Event Server (database storing all definitions and events), Event Processor (scheduling daemon that evaluates conditions and triggers agents), Remote Agents (lightweight processes on each target machine), and Clients (CLI tools + WCC web UI). Q: What happens when the Event Processor goes down? A: Job triggering stops. Jobs that are currently RUNNING continue to completion (the agent handles execution independently), but no new jobs will be triggered until the Event Processor is restarted.
JIL and job operations
These test practical JIL knowledge — what interviewers really want to know is whether you've actually used the tool.
Q: What is the difference between insert_job and update_job? A: insert_job creates a new job definition — fails if the job already exists. update_job modifies an existing job (partial update, only changed attributes). Fails if the job doesn't exist. Q: What is the difference between delete_job and delete_box? A: delete_job on a box removes only the box, leaving inner jobs as standalone. delete_box removes the box AND all its inner jobs. Q: How do you back up AutoSys job definitions? A: autorep -J % -q > backup_$(date +%Y%m%d).jil This dumps all job definitions in JIL format to a file. Q: How do you view the JIL definition of an existing job? A: autorep -J jobname -q Q: What does FORCE_STARTJOB do differently from STARTJOB? A: FORCE_STARTJOB starts the job immediately bypassing all conditions (date_conditions, start_times, condition attribute). STARTJOB only triggers if conditions are currently met.
Status codes and troubleshooting
These test operational knowledge — have you actually been on-call for an AutoSys environment?
Q: What does PEND_MACH mean and what usually causes it? A: PEND_MACH (PE) means the Remote Agent on the target machine is unavailable. Most common cause: the agent machine's filesystem is 100% full, stopping the agent service. Check disk space first: ssh machine01 'df -h' Q: What is the difference between ON_HOLD and ON_ICE? A: ON_HOLD: releasing (OFF_HOLD) starts the job immediately if conditions are currently met. ON_ICE: releasing (OFF_ICE) makes the job wait for conditions to reoccur in the next scheduling cycle — it does not start immediately. Q: A job was failing every night for a week. What's your troubleshooting approach? A: 1. Check std_err_file for the error pattern 2. Check if it's always the same exit code (consistent root cause) 3. Check autorep -J jobname -run 7 to compare recent runs 4. Check if it correlates with system events (deployments, maintenance) 5. Engage the application team who owns the script Q: How do you unblock downstream jobs after manually fixing a failed job? A: sendevent -E CHANGE_STATUS -J fixed_job -s SUCCESS This marks the job SUCCESS so all downstream success() conditions are met.
Advanced and scenario questions
These test whether you can reason about AutoSys in complex real-world situations.
Q: Design an AutoSys workflow for end-of-day batch processing. A: Use a 3-level hierarchy: master box (overall schedule) → section boxes (logical groupings: extract, transform, load, report) → CMD jobs inside each section box. Include a pre-check job as box_terminator, n_retrys on I/O jobs, alarm_if_fail on all critical jobs, and a post-check job to validate output. Q: What is box_terminator and when would you use it? A: box_terminator: 1 on a job means if that job fails, the entire parent box immediately moves to FAILURE and all remaining inner jobs are skipped. Use it on validation/pre-check jobs whose failure makes all downstream processing pointless. Q: How do you handle a scenario where an upstream file sometimes arrives late? A: Use a File Watcher job (job_type: FW) with a run_window covering the expected arrival period and an appropriate min_file_size. The downstream jobs condition on success(file_watcher_job). This way processing starts as soon as the file arrives rather than at a fixed time that may be too early. Q: How do you pass data between AutoSys jobs? A: Using global variables: the upstream script runs sendevent -E SET_GLOBAL -G "VAR_NAME=value". Downstream jobs read it via autostatus -G VAR_NAME or reference it in JIL conditions with variable(VAR_NAME).
| Topic area | Key questions to prepare | Depth expected |
|---|---|---|
| Architecture | Components, HA, what fails when each component goes down | Conceptual |
| JIL commands | insert/update/delete, backup with autorep -q, override_job | Practical — know syntax |
| Job types | CMD vs BOX vs FW, when to use each, box_name attribute | Practical |
| Status codes | All abbreviations, PEND_MACH causes, ON_HOLD vs ON_ICE | Must know cold |
| Scheduling | date_conditions, start_times, run_calendar, run_window | Practical |
| Fault tolerance | n_retrys, box_terminator, HA setup | Conceptual + practical |
| Troubleshooting | Failure investigation workflow, error log location, recovery | Scenario-based |
🎯 Key Takeaways
- Master the ON_HOLD vs ON_ICE difference cold — it is tested in almost every AutoSys interview
- Know the autorep flags: default (status), -d (detail), -q (JIL dump), -s (filter by status)
- Be ready for scenario questions: EOD workflow design, PEND_MACH recovery, failed box recovery
- Connect your answers to real examples from your experience — specificity wins interviews
⚠ Common Mistakes to Avoid
- ✕Memorising answers without understanding the reasoning — interviewers probe with follow-up questions
- ✕Not knowing the autorep command — every practical question about status checking involves autorep
- ✕Confusing ON_HOLD and ON_ICE — this is the most common wrong answer in AutoSys interviews
- ✕Being vague about troubleshooting — 'I would check the logs' is not enough; describe the exact commands and workflow
Interview Questions on This Topic
- QWhat is AutoSys and what makes it better than cron for enterprise batch processing?
- QExplain the AutoSys architecture and the role of each component.
- QWhat is the difference between ON_HOLD and ON_ICE? What happens when you release each?
- QA job is in PEND_MACH status. Walk me through how you diagnose and fix it.
- QWhat does date_conditions do and what is its default value?
- QWhat is box_terminator and when would you use it?
- QHow do you design an AutoSys workflow for a complex end-of-day batch run?
- QWhat is the difference between FORCE_STARTJOB and STARTJOB?
- QHow would you pass a record count from one AutoSys job to the next?
- QWalk me through how you recover from a BOX job that went to FAILURE at 3 AM.
Frequently Asked Questions
What AutoSys questions come up most in interviews?
The most common: ON_HOLD vs ON_ICE difference, PEND_MACH causes and resolution, date_conditions explanation, FORCE_STARTJOB vs STARTJOB, box_terminator, and scenario questions about designing an EOD batch workflow.
What is the most commonly asked AutoSys interview question?
The ON_HOLD vs ON_ICE question appears in almost every AutoSys interview. The key answer: releasing from ON_HOLD starts the job immediately if conditions are met; releasing from ON_ICE makes the job wait for conditions to reoccur in the next cycle.
Do I need hands-on AutoSys experience to pass the interview?
For operational roles, yes — interviewers ask specific command syntax, troubleshooting workflows, and scenario questions that require real experience. Studying the concepts is necessary but not sufficient. If you don't have direct experience, setting up a trial AutoSys environment or practising with a colleague who has access is valuable.
What is the PEND_MACH answer in AutoSys interviews?
PEND_MACH means the Remote Agent on the target machine is unavailable. Causes: agent service stopped (most commonly due to full disk), machine is offline, or network issue. Diagnosis: ssh to the machine, check df -h for disk usage, check the agent process with ps -ef | grep autosys. Fix: clear disk space, restart the agent service.
How do I explain AutoSys to a non-technical interviewer?
AutoSys is an enterprise scheduling and orchestration tool. Think of it like a very sophisticated alarm clock for a company's servers — it wakes up programs at specific times, in a specific order, watches for them to finish, and alerts the team immediately if anything goes wrong. Large banks and insurance companies use it to run thousands of overnight processes that can't fail.
Developer and founder of TheCodeForge. I built this site because I was tired of tutorials that explain what to type without explaining why it works. Every article here is written to make concepts actually click.