Explain a technical concept to a non-technical stakeholder (in English)
Pergunta
Scenario: in English, explain what 'technical debt' is to a product manager who has no engineering background. Keep it under a minute.
Resposta esperada
Lead with an analogy the listener already understands, then connect it to a decision they care about. For technical debt: "It's like taking a shortcut to hit a deadline — the shortcut gets us there faster now, but every future change in that area costs extra time until we go back and clean it up. Right now, work touching the checkout code takes about twice as long because of shortcuts we took last quarter." Then offer the choice in their terms: "We can spend two days paying it down and get that speed back, or keep paying the tax on every checkout feature." Avoid jargon (no 'refactor', 'coupling'), use one concrete number, and end with a decision they can make. The grade is on whether the PM could now explain it to someone else.
Por que perguntam isso
Desafio de comunicação em inglês. Conecta com a pergunta de dívida técnica (arquitetura). O erro a evitar em inglês: traduzir o jargão em vez de trocar por analogia.