
Wrike Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 16 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Wrike.
Software Engineer
The company reached out twice, first rejecting me due to salary, then asking me back. The interview was online. Technical issues happened but got fixed. It was poorly prepared, the interviewer didn't know the company reached out, and the audio/video was bad. They didn't present the company or its value. The interviewer kept saying my salary expectations were too high and I'd only fit one team. They also couldn't explain growth opportunities and were strict about the tech stack. It was a bad experience overall, they even questioned why I showed up. I got a rejection later.
- What motivated you to attend this interview?
Senior Software Engineer
So first there was an HR call where I got some java sql objective questions. Then the first round had 10 questions to answer, covering sql composite index, order by and group by clauses, and the difference between Integer and String equals. There was also a code review part where I had to refactor code to move service and repository logic to separate classes and implement batch operations to avoid the n+1 problem. Lastly, they asked about Prometheus and Grafana dashboard analysis. The second round had 3 interviewers (IC, manager, product owner) and involved a design problem where I had to write code to implement validation rules for department hierarchy changes in an IDE.
- Could you answer some java sql objective questions?
- What is a sql composite index?
- Can you explain order by and group by?
Software Engineer
The whole thing had 4 parts: first a recruiter call, then a technical interview, then some IQ test which was a silly requirement but not too hard, and finally a culture fit interview. The technical interview was 3 hours long and included talking about my experience, a technical problem, and then talking with the recruiter again. The culture fit was about 1.5 hours. Overall it was a great experience, though exhausting.
- Can you explain your previous work experience?
- Implement some functionality in an existing data model by writing a couple of methods. You will have 30 minutes for coding and then a code review where you explain your approach and suggest improvements for a broader scope.
Wrike Software Engineer Interview Questions
Quoted word for word from Wrike interview reports.
“What is a sql composite index?”
Read reports →“What's the difference between Integer and String equals?”
Read reports →“Apart from useEffect, which React hook is suitable for side operations during layout rendering?”
Read reports →“Could you explain why React renders twice during development?”
Read reports →“Implement a basic counter, focusing on code optimization.”
Read report →“Design a system to validate department hierarchy changes based on the given requirements and implement the validation logic in code.”
Read report →“How would you refactor code to move service and repository logic to different classes and implement batch operations to solve the n+1 problem?”
Read report →“How can data be synchronized from the backend to the front end in various ways?”
Read report →“Considering a scenario where numerous threads interact with multiple shared resources, what strategies can be employed to avoid deadlocks?”
Read report →Formats, difficulty and experience
Across all 16 Wrike interview reports.