Katkat
Back

Explain OOP design and API rollout

MicrosoftSoftware Engineer · Technical Screen
HardSoftware EngineerTechnical ScreenSoftware Engineering Fundamentals

Last updated

This question evaluates object-oriented design and API release engineering competencies, covering identification of core domain objects, separation of orchestration from business rules, testability and extensibility of backend logic, and safe modification of public APIs including backward compatibility, versioning, testing, rollout, monitoring, and client communication, and it is categorized under Software Engineering Fundamentals. It is commonly asked because employers need assurance that engineers can both conceptually design maintainable, extensible systems and practically apply release processes and testing strategies to evolve public interfaces without disrupting clients.

In one interview round, the discussion focused on practical backend engineering rather than pure algorithms.

Discuss both of the following:

  1. You are asked to implement a new piece of business logic for an existing backend service using object-oriented design. How would you identify the core domain objects, define responsibilities, separate orchestration from business rules, and make the implementation testable and extensible?
  2. You need to modify an existing public API that is already used by clients. What release process would you follow to ship the change safely? Cover backward compatibility, versioning, testing, rollout, monitoring, and communication with clients.