Getting an Interview
Getting an Interview
Interviews for Top Jobs at Fidessa
- Software Developer (18)
- Software Engineer (7)
- Graduate Developer (5)
- Support Specialist (3)
- Software Support Analyst (2)
- Consultant (2)
- Technical Writer (1)
- Data Quality Analyst (1)
- Production Support (1)
- Java Developer (1)
- Intern (1)
- C++ Developer (1)
- Implementation Consultant (1)
- Implementation Specialist (1)
- Systems Specialist (1)
- Helpdesk (1)
- QA Team Lead (1)
- C# GUI Software Developer (1)
- Graduate Analyst Programmer (1)
- Graduate Connectivity Engineer (1)
- Central Operations (1)
- Regional Developer (1)
- TA Manager (1)
- Junior Trade Support (1)
- Client Delivery Management Intern (1)
- Trading Platform Engineer (1)
- Software Developer (Fidessa Japan) (1)
- No OfferPositive ExperienceAverage Interview
I applied through a recruiter. The process took 4 weeks – interviewed at Fidessa (London, England (UK)) in March 2011.
First stage of interview process was Logical reasoning test. After clearing that test, i was called for F2F interview in London office. First there was 20 mins HR interview which was quite easy (usual stuff like why did you leave last company? what are your strengths/weaknesses?..etc). After that there was 1 hr C++ test, questions where mostly based on key concepts like inheritance, templates, polymorphism and data structure. After clearing that test, I went for 1:1 interview. Interviewers were very friendly. Questions included core c++ concepts and few behavioral questions. Interview went well, but after a week i was told that they want a more senior person.
- what is semaphore? how does it work? Answer Question
- No OfferNegative ExperienceAverage Interview
The process took 1 day – interviewed at Fidessa (Woking, England (UK)) in June 2010.
The interview process started off with an on-line psychometric test that takes about 30 mins. Once that was passed, a face-to-face interview was arranged for a couple of weeks later.
The interview started off with a 20 minute talk with an HR representative. This was fairly pointless, involved filling in a couple of forms, and being told about the company in general - normally the kind of thing that is done if and when you have passed the main interview.
Then there was a technical test. This consisted of approx 20 general c# questions, which require written answers, not multiple choice. Finally, there were 2 "problem solving" questions which were more open ended and carried a much higher points balance. The main issue with this test is that they have an answer sheet that it is marked against, and if you don't have the exact words written down as is on their answer sheet, then you get marked down, even if your answer is in fact correct. Also, the questions can be quite poorly worded and ambiguous.
There is no common sense or flexibility in the marking. For example, with one of the problem solving questions, even though I'd presented a new way of answering the question that they'd not seen before, due to a spelling error, I lost marks, even though they knew that it was a mistake.
I'm sure it may be a good company to work for, but they don't seem to value logic, initiative or creativity, only text book learning, which personally, I don't think makes for great coding.