Yep. Time honored tradition, every cron is edited at least twice. Once to put it there, again to fix PATH.
Everyone who does this enough knows it, everyone else [hopefully] rediscovers. Honest to goodness decades-long cargo culture.
I prefer not having this problem, using "systemd timers" instead. The job and any forked work have a reasonable default path, and observability is worlds better.
Did the last run succeed? When is the next? One command with timers, a guess with cron.
Seems very bad to me (SysAdmin/Generalist Engineer).
Of the few interviews I've done this year, they've been rather HR centric and lacking in technical content. I usually get a follow-up interview, followed by an unspecific rejection (or 'culture-fit') even after a seemingly positive discussion.
