info

Christchurch Court, 10-15 Newgate Street,
Round2
5.20 - 6.00pm - Chris Kohle - tech test
6.00 - 6.30pm - Chris Kohle and Subhash Vaddiparty
6.30 - 7.00pm - Chris Littler
7.00 - 7.30pm - Syed Atif Abbas
Round3 (if R2 successful)
7.30 - 8pm - Paul Hill

You will be called by Subhash Vaddiparty, he is a Senior Analyst Developer in the team.

Please make sure that you are familiar with your own CV as he may go through this and ask you questions based on previous projects. Any skills or experience that you have mentioned on your CV they will expect you to have a decent understanding of to the degree that you have explained. Please be aware of this, have a look over your CV before hand and anything that maybe rusty have a look over.

Please also make sure that you are familiar with the job specs attached.

The skills required for the role are as follows:

·   5+ years of industry JAVA experience.

·   1+ years of industry .NET winforms experience

·   Knowledge of OO design and experience and application of design patterns.

·   Experience of the following technologies – Java 1.5/1.6, Hibernate, JMS (EMS and RV), Log4j, RMI, Linux, Eclipse, JDBC, Distributed Transaction Management, J2EE (Servlets)

·   4+ years of industry Database experience– preferably UDB.

·   Experience in incremental and test-driven development

  

If you don’t know any of the technologies above please look them up before the interview. Not so you can claim you have experience with them but so that you can say you have looked them up and interested in learning them.

I have had a candidate interviewed previously for this role and he was asked a question about “dealing with distributed transactions and C# to java communication using bridges?”  

At Goldman Sachs they like all candidates to been keen and enthusiastic, you must portray that you are interested in working for GS.

If you don’t know the answers or the subject matter to any questions whether they are technical or business, all interviewers prefer it if you say you don’t really know as you haven’t had the exposure to it but you are confident you could pick it up. This is better than trying to bluff your way through at any interview and being found out, it also demonstrates a positive attitude.

This role will involve some support like most development roles, so they will try and gauge your willingness to help out with some support and team fit in general. I have seen on many occasions candidates being rejected after first interview just because the manager “got the impression” they weren’t keen on support. As with most Dev roles an element of support is required in the role. They just want people to be willing to muck in.

These interviews usually focus on 4 key areas (listed below but not in any order of importance):

Analytical Thinking  

Technical Knowledge

Communication

Business Knowledge

One final point, on occasion interviewers will ask if you enjoyed your previous roles and what the main reasons were for you to like that role. If you did have a bad experience at a past position or company please be diplomatic in your answer as no employer will want to hire someone who speaks negatively of a past employer.