iManage Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 15 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at iManage.
iManage
Software Engineer
Mid Average Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical Coding
There were two rounds for the interview. The first round was with the hiring manager and another developer, mostly for a non-technical chat to see if I would be a good fit. The second round involved two senior engineers who tested my coding skills with problems. It was pretty straightforward. HR was really helpful and accommodating at first, but after the interviews, I got no response. I sent several follow-up emails, but still nothing. It's disappointing because other reviews said the opposite.
Confirmed questions2 questions
- How would you refactor this piece of bad code?
- Write code to create an http call and then filter the results from the JSON response.
iManage
Software Engineer
Senior Easy Positive experience No offer 3 rounds
Interview process
Recruiter call Phone screen Technical screen
Interview formats
Behavioral Technical
The hiring manager or interviewer was super rude and impatient, and it felt like they had already made up their mind before the interview even started. They just kept asking about things on my resume like 'You did this?' and then immediately moved on to the next thing, 'you did that?', without giving any feedback even after I walked them through it technically.
Confirmed questions1 question
- Can you tell me about the work experiences listed on your resume?
iManage
Software Developer
Entry Average Neutral experience No offer 2 rounds
Interview process
Recruiter call Phone screen
Interview formats
Behavioral Technical Coding
So I had this interview, first with a recruiter, then with a senior dev, and that was it. Each chat was around 30 mins. The recruiter asked basic stuff like where I went to school and if I knew Java. Then the senior dev wanted to know about my experience and projects. We got into some tech questions after that, which were pretty easy if you know Java stacks and databases. The guy was super chill, totally cool if I didn't know something and helped me figure it out. He kept asking if I had questions at the end, but I didn't, plus I had class. It felt like he really wanted me to ask more, but I wasn't sure what else to ask.
Confirmed questions5 questions
- Could you explain what a transaction is?
- Can you describe how a stack operates in Java?
- Tell me about your general experience.
iManage Software Engineer Interview Questions
Quoted word for word from iManage interview reports.
“How much memory does the stack have?”
Read reports →“What is the memory capacity of the stack?”
Read reports →“Write code to create an http call and then filter the results from the JSON response.”
Read reports →“Could you sort a list of numbers, which might include duplicates, without using greater than, less than, greater than or equal to, or less than or equal to operators?”
Read reports →“Can you explain the differences between Python and Java?”
Read report →“How would you refactor this piece of bad code?”
Read report →“Can you describe how a stack operates in Java?”
Read report →“Could you explain what a transaction is?”
Read report →“What does clean code mean to you?”
Read report →Formats, difficulty and experience
Across all 15 iManage interview reports.