Imagine you join a project where the solution has already been partly developed but there is almost no documentation and stakeholders keep changing their minds. How would you quickly establish clarity on requirements and get the project back under control?

Question

VirtualInterview.AI · Accepted Answer

I’d start by stabilizing what’s already in motion. In the first week, I’d sit with the dev lead and QA to reverse‑engineer what’s built so far into a lightweight spec: core workflows, data model, and known constraints. In parallel, I’d run a short “requirements reset” workshop with the key stakeholders to agree on a concise problem statement, success metrics, and a 6–8 week outcome (for example, MVP that serves 80% of current users with \u003c2% defect rate). From there, I’d translate that into a prioritized backlog, explicitly flagging assumptions and open questions. To manage the changing minds, I’d introduce a simple change-control approach: any new ask gets sized, impact-assessed, and either slotted into a future release or traded against existing scope. I’d also set up weekly 30‑minute demos so stakeholders see progress and we constantly validate that what’s being built still aligns to the agreed goals.

Sample Answer

Keywords