New interview

Candidate name Candidate email Roadmap

Questions

1. Service lifetimes in DI 2. Working with async/await and the Thread Pool 3. The N+1 problem in EF Core 4. Caching with Redis 5. Messaging with Kafka: lost messages and duplicate messages 6. Fixing slowness in Production 7. Choosing between Monolith and Microservices 8. System design: Flash Sale 9. Changing one record at the same time: Lost Update 10. Paging on a big table 11. Safe shutdown in Kubernetes 12. Hot Path code and memory 13. A Job that runs again on several Pods 14. Retry storm 15. Retrying requests in a payment system 16. A database with a Read Replica 17. Changing the database schema without Downtime 18. Exporting a large amount of data 19. Request limiting (Rate Limiting) on several servers 20. Revoking access with JWT 21. Two concurrent requests with one Idempotency Key 22. Event order from several servers 23. Hot partition in Kafka 24. Data that lives in another service 25. When compensation fails in a Saga 26. Scaling in Kubernetes: horizontal and vertical 27. How Kafka partitions relate to pods 28. Using Task or Thread 29. Moving to Redis Cluster 30. Deadlock in the database 31. When the user cancels a request 32. Changing message structure (Schema Evolution) 33. Deadlock in Orleans Grains 34. Following one request across several services (Observability) 35. Memory leak in .NET 36. Aggregates and keeping domain rules 37. Anemic or Rich domain model 38. Bounded Context and shared language 39. The Mediator pattern and the MediatR library 40. The Strategy pattern instead of a big switch 41. The Decorator pattern and a Repository on EF Core

1. Nested loop and Big O 2. Finding duplicate emails 3. Rebase on a shared branch 4. HTTP status codes in an API 5. Building SQL with an f-string 6. A function with flag parameters 7. Storing money as float 8. Reviewing a big pull request 9. A test that depends on the system clock 10. An if/elif chain that keeps growing 11. Hidden dependencies and dependency injection 12. A shared counter across threads 13. An index that is not used 14. Returning every row from an API 15. Duplicate orders from retried requests 16. Storing passwords with SHA-256 17. A stale cache after a profile change 18. Logs that do not help 19. A test suite that takes 70 minutes 20. Storing appointment times without a time zone 21. Estimating a task with one number 22. A binary search in code review 23. Money transfer with two locks 24. Withdraw money from a wallet 25. A cache for user profiles 26. Retrying calls to a payment provider 27. A test that fails sometimes in CI 28. Checkout errors at 2 a.m. 29. Design an LRU cache 30. Design a large file upload service

1. What does a software architect decide? 2. Starting the architecture from a feature list 3. A controller that skips the service layer 4. The debate that comes back every few months 5. One small change across 7 modules 6. Stock and likes during a network split 7. A 24-hour cache for product pages 8. A five-service chain in checkout 9. Two services sharing the same tables 10. Renaming a field in a public API 11. A message consumer and duplicate messages 12. A slow dependency and the product page 13. "Checkout is sometimes slow" 14. "We have no time for refactoring" 15. Build it ourselves or buy it? 16. Saving an order and publishing an event 17. A transaction across order, payment and inventory 18. A full rewrite of a 10-year-old monolith 19. One Customer class for everyone 20. Microservices with layered teams 21. When is Event Sourcing worth it? 22. A reporting dashboard on the main database 23. Data design for a multi-tenant SaaS 24. Checking the user's token in every service 25. Capacity estimate for a photo app 26. A plan for going multi-region 27. Design a URL shortener 28. Design a notification system (email, SMS, push) 29. Design a simple chat app 30. Design the payment part of an online shop

Not saved in this browser.

Levelwise · Open SourceContribute