Brandon, it really matters on what technologies are required for the job and whether the questions are given as written or oral.
Regardless, I recommend starting out with some easier questions like "What packages should be imported when programming a Servlet?", "What is the difference between the use of a PrintWriter and an OutputStream?", "Tell me what you know about MVC.", and "Why might a JSP page run slow the first time it is run?".
I would then move into more detailed questions about frameworks or IDEs or application servers or whatever will be required of the applicant to know or to learn for the job. Start with easy questions first. If UML is required, draw a stick figure on a whiteboard and ask what it represents in UML. If the applicant doesn't respond with "an actor", you could probably assume that UML is a dead end topic with the candidate.
Giving the exam orally will allow you to get a better feel for what the candidate really knows. Also, if they don't know anything you can stop asking after the first few questions and cut the interview a bit shorter to keep from wasting time.
By the way, do you know of any places in the Midwest that are hiring entry-level Java programmers eager to show their worth?
