A cron job is a task that runs on a timer. You tell the system when, say every night at 2 AM or every 15 minutes, and from then on it runs by itself without anyone pressing a button. The name comes from a long-standing Unix tool, but the idea applies anywhere: it is automation driven by the clock rather than by an event.
Think of a programmable coffee machine. You set it once to brew at 6:45 every morning, and from then on the coffee is ready when you walk into the kitchen, no matter how tired you are. A cron job is that timer for your software. It might pull a sales report at 7 AM so it sits in your inbox before the team logs on, or tidy up temporary files at midnight when nobody is working. This makes it a kind of scheduled trigger, one that fires on time rather than on an action.
The schedule is written in a compact format, but most modern tools let you pick it from a plain menu instead. The key thing to understand is that cron runs whether or not anything has changed, which is exactly what you want for routine, time-based work. When you instead need a job to wake up and check for new data, that is closer to polling.
At TopDevs we use cron jobs for the steady background tasks a client relies on, so backups, reports and syncs happen on time without anyone remembering to start them.
