Quick answers
- How do engineers give status updates?
- Name the task, status, and blockers. Be specific: 'I completed X. I'm working on Y. Blocked on Z.'
Key takeaways
- Use task names and status in standups.
- Be specific in code reviews.
- Describe incidents with timeline and impact.
- Explain technical tradeoffs in plain language.
Instead of → Say
| Instead of | Say |
|---|---|
| I coded it | I completed the auth middleware and added unit tests. |
| The PR is ready | The PR is ready for review. I've addressed the comments from the last round. |
| It crashed | We saw a spike in 5xx errors. Root cause was the unindexed query. We've rolled back. |
| We need to refactor | The module is getting hard to maintain. I'd suggest we extract the validation logic. |
Example dialogue
You: Yesterday I merged the auth PR and fixed the flaky test. Today I'm starting the payment integration. Blocked on the API schema—I've requested it from backend.
Common mistakes
- Too technical for mixed audiences.
- Vague status.
Frequently asked questions
- How do I describe my work in standup?
- Name the task, the status, and any blockers. Avoid deep technical detail unless asked.
- How do I explain a technical decision?
- State the problem, options, and why you chose this approach. Use plain language.
Related
Ready to practice?
Try a scenario with AI and get feedback on your communication.
Start practicing