The live coding exercise involved a deep clone of a simple object: its properties were filled with primitives and object values. Some questions were: how would you distribute traffic in a load balancer? how many records have the biggest DB you've worked with?
They drilled me on a number of real-world scenarios, can't remember the questions specifically.
HR interview includes basic questions like : Why Raisin ? What is your goal ? What is one task you are proud of ? In the end a simple coding task.
What your expectations from the company?
How would you know your writing clean code.
How would you design a scalable RESTful API using Node.js? What to Look For: The candidate's understanding of REST principles, knowledge of Express.js or other frameworks, experience with middleware, handling of different HTTP methods, and ability to ensure security and performance. Follow-Up Questions: How would you handle authentication and authorization? What strategies would you use to ensure the API can scale effectively as traffic increases?
1. Optimize a hypothetical backend system 2. Implement LFU cache
In the system design interview, how would you design a banking app.
Implement program to read file input, validate according to defined rules and produce output in a specific format
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.
Viewing 51 - 60 interview questions