How do you answer honestly about a technology you haven't used in production?
Answer out loud or in your head first, then compare.
Answer
I name the boundary and move on to the problem. For example: “I haven't deployed ECS myself. I've worked with Workers and queues, so I understand the need for a separate worker, durable state and protection against repeats. I'd have to check ECS configuration and permissions in the documentation.”
That doesn't pretend to equivalent experience, but it shows transferable knowledge. I can ask about the requirements and propose a way to verify the risk. You don't need to know every parameter by heart. But you do need to tell knowing the principles apart from deployment practice. If practical AWS is a requirement for the company, it may remain a real gap — a clever phrasing won't hide it.
Why it matters: Protects your credibility without ending the answer at “I don't know”.
Possible follow-ups: What can you already do on your own, and where do you need checking or support?
How did it go? Be honest — “Not yet” puts the question on your review list.
Start with
- B-P14 · How do unit, integration and end-to-end tests differ? — JavaScript, TypeScript and Node.js
- I-P04 · How does a coding agent differ from a chat that suggests code? — Harness, MCP and coding agents
Further reading
- AWS Decision Guides: Fargate or Lambda?(opens in a new tab)Updated 21.08.2026. Choosing compute by how long the workload runs and what kind it is.