Senior Software Engineer applicants have rated the interview process at Manhattan Associates with 3.1 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 63% positive. To compare, the company-average is 67.6% positive. This is according to Glassdoor user ratings.
Candidates applying for Senior Software Engineer roles take an average of 14 days to get hired, when considering 8 user submitted interviews for this role. To compare, the hiring process at Manhattan Associates overall takes an average of 18 days.
Common stages of the interview process at Manhattan Associates as a Senior Software Engineer according to 8 Glassdoor interviews include:
One on one interview: 26%
Phone interview: 21%
Skills test: 16%
Background check: 11%
Personality test: 11%
Presentation: 5%
Group panel interview: 5%
IQ intelligence test: 5%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 1 day. I interviewed at Manhattan Associates
Interview
I recently interviewed in Manhattan Associates(R&D). It was for a java back end developer role in Bangalore Location.
Finding the building where the interview was taking place was a pain.
It was a scheduled drive. First round was a written test with MCQ on Java , Hibernate and few problems on SQL queries and Strings.
I cleared the first round and had to wait there. They provided lunch. I did ask few others who completed the second round and they told me all the questions were technical on Core Java, Spring, Hibernate and Web services.
I went for the second round and explained stuff about previous project. He didn't ask me anything technical on Core Java, Hibernate or even spring. He just asked all about designing a project, ways to improve the design . He was more concerned on the Design Patterns stuff in real time projects. He asked 2 questions from Hash Map and exception for name sake. I couldn't get through the second round.
Interview questions [3]
Question 1
What Design Patterns have you used to solve problems in your previous project.
Scenario : We have a method with type as parameter, based on the type we have to do different functions. Currently it is having to do this by using If else conditions.
In future there might be many types coming into picture and the code can get very long.
What will you do so that I do not have to modify the original method.
Very professional and smooth process. Questions were all what you would expected for a java developer interview. Interviewer was patient and friendly.
Learn your basic OOPS, multi threading and some code optimisation and you're good
Interview questions [1]
Question 1
How will you improve db performance if slowness if observed
Basic of Java , ops concept, multiple threading, collection
Basic of Sql-
Sql queries ( joins, groupby , update)
Should have knowledge of procedure, triggers
Hibernate and spring boot
Hibernate queries, mapping , spring ioc container and some annotation
Consisted of 4 rounds- 2 technical, 1 director and an hr round.
Technical round consisted of coding problem around strings and maps, java8 streams, multithreading and collections
Director round was 45 min discussion focused on experience and past projects, standard managerial round questions.
Interview questions [1]
Question 1
Longest substring without repeating character, leetcode