Could you tell us about a time in which you had to solve a complex problem with a simple solution? Describe the context, the situation you were in, the steps you took to deal with it and the outcome. It would be helpful if you can explain this in a way in which non-technical people can follow and understand it.
A coding challenge question was nice. I received a SpringBoot application with maven project. It also had integration tests. The question was to create 3 Rest endpoints with straight forward logic. The challenging part is not to implement the requirements but to implement it in a codility environment. Codility is the worst platform to implement a modular application, it works for small algorithmic problems. Despite I was able to run full problem in my IDE (Which they also recommend), I was not able to detect why it failed to compile and run on the codility. It is difficult to implement, copy to codility and make it run on codility within 2 hrs.
Mainly questions on how architect a backend API for very large user base with burst requests in specific time.
To be successful you need to master concurrency in golang
Technical Stage was a code review exercise. You had 5 mins to read the code explain what it does and find ways to improve it. Would help if you've used Django previously.
Live coding, typical leetcode exercise
- Implement a function to filter data. I liked that it was not a basic leet code problem. - Basic leet code problem string compression/decompression exercise. - System's design problem related to a potential feature used at Affirm. - Standard behavioral interview questions.
What are your takes on monolith vs. microservice architecture?
Live coding questions about building a binary tree.
Questions about : data structure : Array vs linked List Java: memory management Spring boot, design decisions, scalability issues etc
Viewing 1181 - 1190 interview questions