Eze Castle Software Interview Questions & Reviews

Interview Details Met with a representative at our career fair. He took my resume and sort of left me at dark spot. I got an email a couple weeks later saying they wanted to to have a phone interview with me. Pretty basic, just a conversation to get to know you. Few behavioral questions as well. After that is the grueling task. They asked me to come in for an interview to meet with 3 managers. Each meeting lasted about 30-45 min and was absolutely grueling. I thought I tanked it but they gave me the opportunity to come in for one more interview, to meet with three other managers. I did not know what to expect. The job seemed pretty interesting and it seemed like a cool place to work, so I went in again. This time I thought I nailed the interviews, answered there tough questions in detail and enthusiasm. I left thinking I had this one in the bag.

Interview Details Phone interview 1 week after applying. 2 weeks after made appt for 1st interview. Interview consisted of conversations with HR rep, and individuals from QA and CC- took about 2 hrs.

Interview Details I worked with a headhunter to get the interview and become prepared. I met with the leads of a few different consulting teams. The interview was very standard--reviewed resume, asked about intention to switch jobs, and such. I was also asked a few specific questions about their business to test if I had done my research homework. It is a pretty high stress job at times, and I came off a little too relaxed for their culture. I was not offered the job, so presumably a more agressive personality would fit better.

Interview Details I applied through my college career website. I was contacted by Eze's HR and there was an initial phone screen. After this I moved on to a second round interview which was conducted via Skype because I was an out of state candidate. I interviewed with two Eze employees, one from the quality assurance side and one from the connectivity consultant side. After a few days I was contacted that I wasn't invited to Boston for a final round.

Interview Details First round was on OOPS concepts. Difference between C and Java. About resume and tell logic for printing 'a' if given number is divisible by 5 and 'b' if it is divisible by 15. Second interview was scheduled for 1 hr but interview went on for only 10 minutes asking about projects which I did.

Interview Details Three-round interview. First was by phone with a lead developer at HQ, second in-person with managers at local office, third by phone with hiring manager at local office. Initial phone interview questions mostly focused on definitions of terms involved with object-oriented programming, plus writing a short program to solve an easy problem. In-person interview was a bit tougher, asking more technical questions about the problems involved with multiple inheritance and also questions about object-oriented design (e.g., drawing a proposed system on the whiteboard). Knowing SQL beforehand is a plus but not required, especially if you have a strong math background. Researching the company beforehand is also recommended. Third interview (second phone round) was mostly a discussion of past experience and what I hoped to get out of the internship. Office culture seems nice but quiet: there are cubicles with short walls; attire was mostly business casual; they have a nice break room with a beer tap (for Fridays after the market closes); I was also able to talk with some of the employees in the break room between the two rounds of the in-person interview. Had a bit of difficulty communicating with one of the HR people by email; I overcame this by copying in another HR contact with all of my emails and by following up within a couple days if I got no response.

Interview Details For campus recruiting it was only one thirty minute interview with several logic questions. Kind of halfway between a case interview and personality interview.

Negotiation Details – They tell you the salary, then you have a few weeks to accept or decline.

Interview Details I just gave a phone interview. They first ran down my resume and asked me to explain my project. Then I was given a random question on changing some parameters in the project. After this, he asked me about object oriented programming concepts like inheritance and polymorphism.

Interview Details Applied through my University. Two telephonic screenings. First one was very easy. All questions are already on Glassdoor like why there is no multiple inheritance in C#. inheritance, polymorphism, encapsulation etc. example of polymorphism. Second round - some more OOPS concepts ...now in depth .... no more definitions.. asked me to write prototype for a class stack.... like function (typename T) void push(T t); etc
Another question related to polymorphism - We have an interface Ianimal with a function eat() and three classes derive from it - Class Tiger, Class jellyfish and class Zebra. All these classes implement eat(). Now we have another class zooKeeper which implements a function feed(). Now using feed() call eat() function. Finally it was the Onsite interview. First round is a one hour test with one question - you have 3 presorted very large arrays. Find the first common element amongst them. No duplicates in each of the array. I gave an answer using hash table and it had a time complexity of O(3n) and space complexity of O(n) but the interviewer wanted a solution in O(n) time and O(1) space. Together we worked the solution and he contributed most to the solution. I would tell you the answer but then this question will no longer remain in the test. The only reason why this question is still on the exam since 2009 is that nobody wrote the answer to it on the web. Rest of the rounds were easy mostly pertaining to my resume and other behavioral questions. And yes you will have to pay for onsite interview expenses yourself. In the last round I was interviewed by a guy with strong accent and he asked me a to right code for binary search. I know it is fairly simple but I messed up as I made a mistake in calculating the mid and that was it when I lost my confidence and started messing up.

Overall the interview was very I easy if I hadn't messed up and lost my confidence and started making mistakes. All interviews will be on board.