The interview was pretty much one-sided with the interviewer consuming about 95% of the conversational bandwidth describing their Titan product, which happens to be pretty good with very few, if any, competing products in the marketplace. A Java coding test is part of the initial interview. There is not a lot of raw code to write but some thought has to put into how a couple or three small classes you need to write fit into a relatively small existing framework of classes. The coding test can take up to an hour. The test gets a positive nod because it is more realistic than other coding tests where, for example, you're asked to do something stupid like write an algorithm for reversing the characters in a string. If you are invited back for a 2nd interview, you may be asked to provide an example or two of your past Java code prior to that interview. Do not do this!! These people apparently have very strict, righteous, sanctimonious ideas of what code should look like and given that most programmers don't like the code of most other programmers for any one of a large variety of reasons whether they're justified or not, it is highly likely your 2nd interview will be cancelled if they don't think your code is saintly enough. Just say you can't show them any code because of an NDA you signed with prior employer(s). If you want to work here, it is apparently in your best interests to keep these people guessing.
