Have you worked on projects from scratch or did you join an already running project?
System Analyst
Have you participated in analyzing and troubleshooting industrial environment (production) incidents?
Why is scalability in a microservices architecture better than in a monolith?
What changes are required in the API when adding promo codes?
What rule was applied for ATM write-offs, and was the ATM's economy considered?
What is the difference between GET and POST methods?
Is it possible to design services so that all methods use only POST?
What data will be transferred from one bank to another?
Do you have to independently design integrations or is it done jointly with a developer/architect? What kind of integrations: internal or external?
There is a task to split a monolith into microservices. One of the services may not respond, leading to data inconsistency. How to safeguard?
Write the physical database tables for a catalog service (books, authors, genres, price).
Who is responsible for functional requirements, and who for non-functional ones?
Do you have more experience in run activities or in change? Specifically in software development and production?
Where are we sending the event from and to, and how to determine if it is valid (has passed)?
What did you enjoy doing on the last project with unified accounting and inventories?
Is there anything else about caching that needs to be considered?
Have there been sprints in your work?
What ways of scaling databases do you know?
* No centralized notification history; * Users complain about duplicates and delays; * No unified SLA, metrics, or control center. Goal Design a new Notification Platform that: * Aggregates events from various sources (CRM, Support, Security); * Routes them by type and channel (email, SMS, Telegram, push); * Ensures uniform templates, logging, and observability; * Supports SLA (p95 ≤ 3 seconds for delivery); * Allows for future scaling and channel expansion. Candidate task 1. Define the functional requirements of the system. 2. Describe the non-functional requirements (reliability, performance, error handling). 3. Create a context diagram (C4 Level 2). 4. Add a sequence diagram, for example, sending a message from a source.
Can you hear me?