In UX (User eXperience) design, responsible for: - interface operational testing - acquiring new user experience from interface use - compliance of interface with corporate style - ease and clarity of the interface - interface work speed
System Analyst
Logging can be used for: - Protecting the system from malicious software - Increasing data encryption level - Ensuring uninterrupted server operation - Increasing network bandwidth - Identifying causes of failures and malfunctions - Debugging software and troubleshooting issues
Have you had to conduct acceptance tests and demos for clients?
Did you receive a ready topic with JSON or did you work out message contracts, partitions, consumers yourself?
Tell me about the technical assignment — how did you work with it?
Have you ever had a client add new requirements and comments during a demo — how did you handle it?
Have you only worked with microservices architecture?
Fix the JSON User profile [ "user_id": "6F9619FF-8B86-D011-B42D-00CF4FC964FF", "age": "30", "user_name": "Test User", "user_name": "Ivanov Ivan Ivanovich", "emails": { [ "email": "[email]", "main": true, ] [ "email": "[email]", "main": "false" ] } "city": "Sochi", "categories": {news, cars, it} ]
Do you know the configs/settings for microservices that are pulled through Docker environment variables?
What is important to you when choosing a job? What do you pay attention to?
Will there be work related to LLM, vibe coding, or own microservices in the project, or is it about a full-fledged product?
What does business have to do with API design? What will they tell you?
Will there be a business component and direct communication with the customer in the role of a systems analyst?
Can FE only work in a browser? Why? (Provide a brief justification for your answer)
Key advantages of using NoSQL databases: - Strict data schema and support for complex SQL queries - Support for strict data integrity constraints - Ability for relatively fast processing and analysis of large data volumes - Scalability and flexibility in working with unstructured data
Tell us about the project you worked on recently: what was it, its goals, tasks, and your role?
The distinctive feature of relational databases compared to non-relational ones is: - storing data in tables as columns and rows - the ability to explicitly type data: string, integer, boolean, etc. - access rights distribution function for accounts - using primary and foreign keys to establish relationships - having an indexing function to speed up data search
When integrating with an external CRM system (SOAP), the response can include: - Fault AUTH_FAILED - Fault VALIDATION_ERROR (e.g., incorrect phone) - timeout The task is to create a crm-adapter (REST inside the contour) Best mapping: AUTH_FAILED → 403, VALIDATION_ERROR → 400, timeout → 504 AUTH_FAILED → 500, VALIDATION_ERROR → 500, timeout → 200 AUTH_FAILED → 403, VALIDATION_ERROR → 404, timeout → 409 AUTH_FAILED → 401, VALIDATION_ERROR → 400, timeout → 504 Can return code 200, with body {"error": }
Through what tools did you look at logs?
Have you ever designed an API from scratch without developer assistance?