Can you tell about the approaches to designing data warehouse architecture you have used? At least theoretically.
System Analyst
Calculate the load: 1000 active users, 50% make payments every day, each makes 5 requests per day. How many requests per hour should the service support?
Have you had experience integrating with NGX (Nginx)?
Who drew the architecture after moving to microservices?
What will the server respond if a GET method is sent with a request body?
What is meant by passing parameters in the request body?
Should a separate database be built or use a common Ozon assets database? Which technology to choose?
What is the difference between validation and verification of requirements?
Tell about the main components of Kafka.
Was the data loading itself written directly in Python?
What date formats are used in JSON Schema in practice?
Tell about yourself — who you are, what is your experience?
Comment on the latest conditions for the SQL query — what does WHERE co.operation_date >= DATE_SUB(NOW(), INTERVAL 3 MONTH) mean?
Do you have extensive experience communicating with factory workers (production staff)?
How to transmit the attachment itself (file/document) in the request?
Are you a team player or do you prefer to work independently?
What qualities should a product have to make it comfortable for you to work with?
Give an example of when it is better to store data in a register of information, and when in a register of accumulation.
Вы работали с системами Machine Learning? Имеете базовое представление о том, что это такое и чем отличается?
Have you worked with microservice or monolithic architecture?