BarCap Technology AC

#1

Has anyone been to a BarCap Technology AC?

I know the basic format to expect (i.e. group exercise, some individual interviews, …?), but I would be grateful for any info regarding how much non-technical BarCap/IB-specific knowledge you are supposed to present (probably mostly at the level of individual interviews), i.e. is the ability to answer the telephone interview kind of competency questions, roughly in corresponding length, sufficient?

Or are you expected to be able to talk for say 15 minutes when asked questions like “What does BARX offer for clients?”

Thanks.

#2

hey irquas, ive had my telephone interview for barcap and still waiting to hear for further news, when did you have yours? and what day is your ac?

#3

Hi,

I previously attended a BarCap Tech AC and was unsuccessful due to lack of technical knowledge (my CV actually screams business analyst, been years since I did programming, fair enough mind, they stated at the start of the AC they were looking for front office developers…), so make sure you are sharp when it comes to your technical knowledge, reviewing a bit on Data Structures/Alogrithms/Performance Enhancement would be my advice, just to ensure you can speak about that area comfortably even if you are not 100%. Mind you, some of the others I spoke to didn’t get questions on data structures etc. but certainly programming concepts were mentioned and are important. I actually get the feeling I would have got through this interview having re-read an old textbook on data structures and algorithms/basic java programming, I would encourage you to do the same if you have the time…

The interviewers for technical actually specifcally said “so we see you have experience in Java” when there is actually no mention of Java on my CV/application at all, so make sure you know one language as even though you might select a “general” technical interview you will be quized on programming. Having said all that, it sounds like your technical knowledge is probably up to scratch anyhow, so moving on…

In terms of competency - you have two interviews, one technical and one competency based. The competency interview is very similar to the telephone interview, but there are no questions on why BarCap etc. at least not for me - one or two got asked who the CEO was I think, so make sure you know that stuff just in case. But generally you are looking at examples of being in a team, how did you work, leadership, when you failed, innovation, how did you cope with team mate issues, how you deal with money (this is a strange one, think they are looking to see how careful you are with money or something similar) etc. I got very decent marks (one of the graduate guys gave me a phone with feedback, really great there for that kinda thing) for this, mainly because I stuck to work experience examples and have done 12031232 of these interviews before… Just be confident, speak clearly and get to the point, don’t go off on a tangent. You can view this as an extension of the telephone interview, although it varies from interviewer to interviewer as to the exact questions you will be asked.

As for IB knowledge (having just read your post again :D) I did not get one question about IB, nor did anyone I spoke to - nothing about what they do etc. I would still advise you know your stuff there though, perhaps even a few current events which are not hard to work out. Actually - thinking about it, they did ask about current technology trends and it would obviously look better if you linked that back to IB. There was a guy in my group who went off on a tangent about HFT, clearly not really knowing what it is, so if you do read up on something make sure you have a decent understanding on it. I won’t tell you what I spoke about, but generally it is not difficult to discuss current issues in IBanking and how technology can help (or is actually supposed to help with regulations etc.).

The group exercise was a nightmare for me, in a group with people who appeared to think it was a contest in getting heard, constantly talking over people etc. I would advise you to make decisions quickly and develop good reasoning behind those decisions, they will question you no matter what you say and expect you to speak up for yourself and not get bullied, same for the individual task. No point in saying more about those two areas, make sure you do the usual time keeping thing, put forward a few decent points and listen to others, standard stuff.

I got the impression the group project was just making sure you are not an arehole (I think they have a “no-jerk” policy, seen that advertised around on Vault) and the individual exercise was assessing your logic, again making sure you stuck by your decisions… I was only satisfactory in the group project as apparently I became flustered when asked questions (was actually embarrassed at how sht we were, although time is VERY limited so most teams struggled from what I heard), which was fair enough overall, had a 'mare.

Individual I did fine, just make sure you have logical reasons as to why you made certain decisions and stick by them. It is a strange exercise as the scenario is supposed to be meeting your manager, which presumably means you should take their advice and adapt, but they are expecting you to stand up for yourself too. You get 15 minutes to make the decisions, make notes next to each item to say why you would leave it (it is a basic task prioritisation exercise, pick 5 from 20 etc.) and then why you would select the 5…

It was a strange experience in a way - it is the first banking AC I have been to, previously I went to a Cisco AC which was very similar only EVERY interviewer saw EVERY candidate which I personally think works better. Hard to judge candidates when you only see a couple each and the questions appear to vary. Having said that it was a positive experience, even though I did not get the offer I felt I got a decent amount out of it and will use that knowledge (i.e. my weaknesses) going into the next couple of ACs I have coming up.

Additional tips - there is a networking dinner thing toward the end, DO NOT go for the lasagne, it is rock hard and makes you look silly trying to eat it with a fork and getting no where :D. I do encourage you to go around and talk to as many people as possible, be polite and discuss the day, be positive throughout too, I made the mistake of telling one of them I felt the group thing did not go as well (which is true, but if it comes to them deciding your fate you don’t want to give them something…).

Usual closing advice - be yourself (unless you are a jerk :D), be polite, be calm, do not rush, do not become flustered. They are not looking to catch you out, they are decent folks and you should be fine if you follow the advice on this forum!

Good luck buddies

#4

Thanks a lot for the info.

#5

i got an invite for BarCap AC on 12 Oct…is there anyone else going for AC on that day?

#6

Hey mdrs12, I’m heading to that AC aswell.

I’ve been trying to find info on the technical questions mostly, wondering if they are going to be really in depth q’s or more basic.

#7

@PeaTear: I think that it’ll mostly be basic qns than in-depth.
Do you know what all exercises will be there?

#8

Hopefully anyway.

From what I understand anyway, what timmymagic07 said is what we can expect.

I think it’s 2 competency interviews though. Along with the tech interview, prioritisation exercise and team exercise.

The competency’s will be just like the phone interview I think. Prioritisation and team will be mostly organisation and how well you work with people so I don’t think there is much to do to prepare for them.

#9

Hi guys

I like how timmymagic07 has described his whole experience but what I want to find out is what kind of technical questions they might ask during the technical interview. I understand what timmymagic07 has said about data structure and algorithms but they are huge topics. I am confused. HELP!!!

#10

In my experience and that of 1 my friend, the technical side of the interviews was really weak. During the “technical” interview, we both got asked “What data structure/algorithm have you recently created?” and then talked about its efficiency (make sure you know, and talk about, the O notation!), etc., for about 5 minutes. Neither of us got anything about e.g. threads in Java or any advanced topic like that.

So based on these 2 experiences, you wouldn’t think you would have much to worry about. However, I massively stress that I am only basing this on 2 experiences and so it may well be that that of the others, yours included, might be different. You’d probably want to brush up on general algo stuff, such as the mentioned O notation, but don’t spend ages on this – spend most of the time brushing up your competencies, your teamwork and your business knowledge.

#11

thanks irquas.

I have just read up on searching and sorting algorithms. Don’t no much about notations though. I am going to read up on that now. Is there anything else I should be worried about or any other tips. Thanks