Build: Your technical response
Use this workspace to practise responding to a piece of technical feedback. Choose one scenario below that fits your role. Write your response in bullet points using the four-part structure.
- Acknowledge — Show you heard the feedback
- Clarify — Ask a short question if needed
- Adapt — Change your approach or explain your original choice
- Reflect — What do you think now?
Use this workspace to practise responding to a piece of technical feedback. Choose one scenario below that fits your role. Write your response in bullet points using the four-part structure.
- Acknowledge — Show you heard the feedback
- Clarify — Ask a short question if needed
- Adapt — Change your approach or explain your original choice
- Reflect — What do you think now?
Choose one: "That is a good start — but what if millions of users log in at the same time?" / "Could you explain how you checked the quality of your input data?" / "Have you thought about a rollback plan if something goes wrong?" / "Do you think this flow works well for mobile users?"
What is your first reaction? Show the interviewer you heard them.
Do you need more information? Ask one short question.
How will you change your approach? Or why did you make your original choice?
What do you think now? What would you do differently?
e.g. That is a good point / You are right, I had not thought about that e.g. Are you thinking about peak load specifically, or sustained traffic over time? e.g. I would add a load balancer / use a queue to handle spikes / separate the auth service to scale independently e.g. My original design was simpler but not production-ready / scalability should be part of the initial design, not an afterthought
Get started
Create a free account
Track your progress, complete exercises, and prepare your own interview answers.
No credit card needed
See it in practice
All case studies →How a Java Engineer New to London Prepared System Design English
A Java backend engineer who moved from Korea to London prepared system design and live-coding English - vocabulary, phrases and structure first.
Read storyHow a Backend Engineer in Sydney Prepared for Microsoft in English
A Sydney backend engineer from China prepared Microsoft competency stories and system design in English: outages, metrics, AI agents. No offer claimed.
Read story