Desafios abertos: raciocine em voz alta, como na entrevista real

"Walk me through a project you're proud of" (in English)

Context (1 line) → your role (1 line) → one technical decision + why → outcome with a number. Not a tech stack dump.

Explain a technical trade-off you made (in English)

Two options → the constraint that decided it → what you gave up → whether it held. Trade-off first, backstory second.

Design a URL shortener — thinking out loud in English

Clarify in English → state assumptions → core flow → name trade-offs out loud. Narration structure matters more than the diagram.

"Tell me about a time you disagreed with a teammate" (in English)

STAR, heavy on Action. Pick a story where the disagreement was resolved with evidence — bonus if you were the one who updated your view.

Phrases for clarifying and buying time in English

"Just to make sure I understand...", "Let me think about that for a second.", "I haven't used that directly, but I'd approach it by..."

Explain how you'd debug a slow endpoint (in English)

Observability first (scope + timing + recent changes) → narrow with logs/traces → hypothesis → confirm before fixing. Narrated in English.

Idiomatic phrasing: which sentence sounds natural?

"The payment service went down in production." — "is down" / "went down" is the set phrase.

Explain a technical concept to a non-technical stakeholder (in English)

Analogy they already know (shortcut / tax) → one concrete number → the choice in their terms. No jargon. Success = they could re-explain it.

Writing a code review comment in English that doesn't sound rude

Ask don't command, label severity (nit/suggestion/blocking), give the why, say "the code"/"we" not "you", drop "obviously"/"just"/sarcasm. Direct about the code is fine; direct at the person isn't.

Giving a daily standup update in English

Done / doing / blocked-on (name who you need). ~30 seconds. Bad: vague "same as yesterday", implementation deep-dive, activity not progress, hiding a blocker.

Pushing back on scope or a deadline in English

Acknowledge the goal → name the constraint factually → offer 2 options with trade-offs → ask which they prefer. "Here's what I can commit to...", "The risk I see is...". Not just "no" / "impossible".

Technical false friends: PT→EN traps

atualmente→currently (not 'actually'), eventualmente→occasionally, pretender→intend (not 'pretend'), library=biblioteca, 'attend' a meeting, 'ask' a question, 'explain to me'.

Narrating a coding problem out loud in English

Restate + confirm the problem → ask edge cases/constraints → brute force + its cost → name the pattern → walk a small example → then code, narrating. Connectors: "Let me start with...", "One edge case is...".