Job Environment
By default, Qube! will execute the job in the job owner's environment as defined on the Worker. The Worker can also be instructed to use the current environment to execute the job as well. (Keep in mind that the job owner may be the user who submits the job, or it may be the generic 'qubeproxy' user, depending on how your installation is configured)
In fact, what happens is that the Worker runs setuid to the job's owner. This isn't the same as loading the user's .cshrc or .bashrc file, so variables defined in those files may not get set. You can control the job's execution environment explicitly by defining environment variables into the /etc/init.d Worker scripts, or by setting them as part of the package of job commands that land on the Worker.
Example
% qbsub --flags export_environment sleep 10
...