# Speaking up in meetings when you are the quiet engineer

> Quiet engineers often have the best point in the room and no way in. Prepare one contribution, speak in the first ten minutes, and turn a doubt into a question people can answer.

Source: https://hintvo.com/blog/speak-up-in-meetings-as-an-engineer | Last updated: November 20, 2026 | Reviewed: 2026-11-20

The engineer who says the least in a meeting often has the most useful thing to say, and leaves without saying it. Being quiet is not the problem. The problem is that meetings reward people who talk first and fast. A few habits make it much easier to get your point in without changing who you are.

## Prepare one thing

Before the meeting, write down one point you want to make or one question you want answered. Just one. It is much easier to speak when you already know what you will say, and one contribution per meeting is enough to change how people see you.

## Speak in the first ten minutes

The longer you wait, the harder it gets, and the more the conversation moves past your point. Say something early, even something small: agreeing with someone and adding one fact counts. After that, the second time is easy.

## Turn a doubt into a question

| Instead of saying nothing about | Ask |
| --- | --- |
| I think this will break refunds | Does this change affect the refunds path as well? |
| This estimate seems low | Does the estimate include the migration for existing rows? |
| I do not understand the plan | Can I check I have it right? First we add the key, then the retry? |

A question is easier to say than a disagreement, and people answer it instead of defending against it. Often it makes the same point.

## Getting in when people talk over each other

- Use the raise hand button in the call. Most facilitators watch for it.
- Start with the person's name: "Sam, can I add one thing to that?"
- Write it in the chat. Many points that are hard to say out loud are easy to type.
- Ask the person running the meeting beforehand to bring you in on a topic you know well.

## Use writing

Quiet people often write better than they speak in the moment. Send your view before the meeting, or a short note after it with the point you did not get to make. Teams that read are often fairer to quiet people than teams that only talk.

## If you are the one who talks a lot

Ask the quietest person directly, by name, with an open question: "Priya, you know this code best. What are we missing?" Then wait, and do not fill the silence. It is the cheapest way to make your meetings better.

> **Where Hintvo fits:** the Ask this card suggests a question worth raising from your own code, such as a missing idempotency key before retries are added. Live captions for both sides of the call in 9 languages (English, Turkish, German, French, Spanish, Portuguese, Italian, Dutch and Polish) help when the pace is fast. See the moment in the sample meeting on the [home page](https://hintvo.com/#replay).

## Related

- [Design reviews: ten questions worth asking](https://hintvo.com/blog/design-review-questions-worth-asking.md): What questions should I ask in a design review?
- [Interviewing in your second language](https://hintvo.com/blog/interviewing-in-a-second-language.md): How do I do well in a job interview that is not in my first language?
- [How to say "I don't know" in a technical meeting](https://hintvo.com/blog/how-to-say-i-do-not-know-in-a-technical-meeting.md): How do I say I don't know in a technical meeting without losing credibility?
