Welcome to your interview.
The question is on your right: Write User Stories and Acceptance Criteria. Take a moment with it first.
Talk your thinking through with me if you like - when you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes). Discussion and graded submissions share your five interviewer interactions, so spend them well.
You're preparing work for an upcoming product build and want engineering, design, QA, and business stakeholders to interpret requirements the same way. You need a consistent way to write user stories and define acceptance criteria so delivery doesn't drift or get debated mid-sprint.
What specific structure do you use for writing user stories, and how do you define acceptance criteria?