6 Signs You Sound Junior (And Don’t Even Know It)

Summary

The speaker argues that engineers can undermine their credibility in meetings not because of weak technical skills, but because of how they communicate. Senior-sounding communication is direct, responsive to the actual question, and prepared in advance.

Six Communication Practices

• Speak without apologizing first. Skip self-deprecating preambles and state the point. Apologetic introductions can make useful contributions easier to overlook.
• Ask informed questions instead of lecturing. Build experience into a question that surfaces a key fact, checks assumptions, and helps others reach a conclusion. For example, rather than declaring a launch date impossible, ask when the security review will begin.
• Listen instead of rehearsing your turn. Focus on what the other person wants to know and why it matters to them. Answering a different question—even with accurate technical detail—can signal that you did not hear the concern.
• Use a deliberate pause. Wait about three seconds before answering so you can formulate a considered response and avoid filler words or rushed answers.
• Lead with the answer (BLUF). Give the shortest accurate response first—such as yes, no, a number, or “I don’t know; I’ll find out.” Add context only when it is relevant or requested.
• Prepare before important meetings. Anticipate likely questions, concerns, and objections. Write concise answers and clarify owners and dates in advance.

Frameworks and Practical Playbooks

• Experience-backed question: Start with the conclusion you want to convey, identify the fact that supports it, and ask about that fact.
• Listen for intent: Determine both the question being asked and why it matters to the person asking.
• BLUF / answer-first pyramid: Put the answer at the top and supporting context below it. Give the answer, pause, and add detail as needed.
• Meeting preparation: Spend 30 minutes identifying likely questions and drafting one-sentence answers. For action items, clarify the task, owner, and deadline.

Examples and Business Implications

• In a system-design review, lead engineer Peter Washall asked a junior engineer where a supposedly reliable transaction queue was hosted. The queue was on the same machine as the database, so a host failure could take out both. The question exposed the design flaw while helping the engineer understand it, rather than simply handing over the fix.
• In a launch discussion, a senior engineer repeatedly explained a cache issue when a VP was asking about the launch date. The lesson: address the stakeholder’s concern—in this case, schedule and commitments—before giving technical background.
• An Amazon director repeatedly asked whether deadlines were being met, what the tasks were, who owned them, and when they would be completed. Preparing those answers in advance could make the meeting shorter and avoid follow-up meetings.
• Clear, direct answers and visible preparation can increase confidence that someone is ready to represent a team or take on greater responsibility.

Metrics and Timelines Mentioned

• The speaker says he spent 20 years at Amazon, attended thousands of meetings, and has trained hundreds of engineers.
• The suggested pause is three seconds.
• The speaker estimates that filler words arise from discomfort with silence in 99 out of 100 cases.
• He says that in nine cases out of ten, a concise answer will prompt a clarifying question that indicates what context is needed.
• Meeting preparation: 30 minutes; a well-prepared recurring meeting could potentially finish in five minutes.
• In the illustrative launch scenario, a security review was described as at least six weeks away.

Sources and Presenters

• Presenter: Steve, who describes his experience attending meetings and mentoring engineers at Amazon.
• Named example: Peter Washall, a lead engineer in the system-design review anecdote.
• Other sources referenced: Unnamed Amazon colleagues, a vice president, and communications coaches.