The use case was a dumb one: forecasting of the future operations, in the retail bank application, with the very same accuracy as the historical operations (for instance, the application should forecast that you will buy some cake at Albert Heijn in ten days from now, on a Tuesday morning at 10:12, for an amount of 1.27 Euros). When I tried to transform the use case so that it makes more sense business-wise (for instance, a budget planning exercise, where we still keep the analysis of time series), the interviews were dumb and wanted to stick to the original formulation of the use case.
Lead Support Engineer Interview Questions
53,730 lead support engineer interview questions shared by candidates
All the question are real time scenerio based and one needs to have good experence to understand them and answer them
Behavioral/ situation questions.
Questions very easy. But in cv also mentioned we don't have c# experience. But they asked questions in C # also
Basics on C# WPF c++
Round 1: 1) Duplicates in an array in O(n) time and O(1) space. 2) Left-view of a binary tree. 3) Kafka producer-consumer lag. 4) Convert list to map using streams. and others I dont remember, but they were on basic concepts. Round 2: 1) kafka working and architecture. 2) Design patterns as above. and some other basic questions.
Design patterns in java with examples
Architectural solutions for ETL technology
Do you have experience with Python?
- OOPS/ C#/ Design patterns/ SQL - Database managment system, - Application Architecture - Roles and responsiblity.
Viewing 2311 - 2320 interview questions