Step one, of course, would be to define what you mean by "getting stuck".  Is it the job that's getting stuck because of something wonky on the server or is it the code in the job that's getting stuck?  Did someone mess up and shrink the database which will cause these types of symptoms?  Does the code have a "spill to disk"  somewhere because the system is underpowered compared to the production box?  Like Lynn asked, does the code in the job run correctly if you run it from SSMS without the job?  Are stats up to date?  Etc, etc, etc.  Start somewhere and expand.  First thing to do is make sure that the code the job is running runs fine without the job.