The exercise of technical interview seemed invented 2 min after interview started. Two interviewers have jumped in without preparing anything. Finally after a wee pause the one of them asked me to provide Scala implementation of a list. When I asked to precise what kind of list he meant, his answer was - immutable linked list.
A fairly average js question to get all the github pullrequest and it's reviewers and create an api to give it back in the response.
Have you heard about Zalando?
Find the minimum value greater than a certain given value in a sorted array.
interview process is not hard . crack it very easily if you have background skill
Practical task to design REST API client in one hour.
Since I don't currently use Ruby I've warned them of that. It's been a laid-back chat where they asked some general tech questions and other behavioral ones, focusing on: - What languages I've learnt lately - How do I test, if I do TDD - How do I get my hands on a new project with its own language and architecture - How do I work on legacy code (they have a monolith) - How do I give feedback - What do I do if someone is "against" your point of view - Why backend in place of frontend Basically, they look for someone putting the hands under the hood the first minute by maintaining the monolith "as-is" at the moment, no major changes on the monolith will take place, according to what they told me. Then, expect questions related to that: they heavily depend on ruby on rails and super skilled on that, and no other technologies or architectures are about to come. I'd recommend ask yourself, because this could change.
Are you familiar with agile practices?
Can you tell us what it means SOLID principles?
Design customer care system
Viewing 541 - 550 interview questions