Cron is designed to run jobs on a schedule specified in minutes. While it is technically possible to run a job every 30 seconds by running a command similar to the ones I provided earlier, it would be highly inadvisable to do so because it can put a significant load on the system. Cron will run the command repeatedly every 30 seconds causing high system resource usage and can cause stability issues.
A better approach would be to use a script that checks the current time and sleeps until the next 30 second interval, and then runs the desired command. This way, the script will only run every 30 seconds, but it will not be consuming resources when it is not running.
It is important to consider the impact of running a job every 30 seconds on your system, and whether or not it is necessary.