Dutch Feedback Survival Guide

Stop reading blunt Dutch feedback as an attack, and learn how to give it back without sounding rude or scared.

Who this is for

Filipino devs already living and working in the Netherlands, a few weeks to a few years in, who keep flinching when a Dutch colleague says something straight to your face in standup, code review, or a 1-on-1.

What this helps you decide or do

This helps you tell the difference between “Dutch direct” and “actually rude”, respond in the moment instead of freezing, and start giving honest feedback yourself so your team stops seeing you as the quiet one who always agrees.

Quick checklist

1. When a Dutch colleague says “this is wrong” or “I disagree”, read it as a comment on the work, not on you. In PH we soften with “maybe we could maybe consider”, here people skip the wrapper. The bluntness is the norm, not a sign you are in trouble.
2. In code review, stop adding “sorry” and “po”-style softeners to every comment. A plain “I think this loop can be simpler, what do you think?” is normal and respected here. Over-apologizing reads as unsure.
3. Separate the two questions PH culture blends together: “Are they criticizing my work?” (often yes, normal) versus “Do they respect me?” (usually still yes). Disagreement and respect coexist here in a way they often do not back home.
4. Practice saying “I disagree, here is why” out loud before your next standup. The hardest part for most Filipino devs is not the accent, it is overriding the hiya reflex to stay quiet and agree.
5. When you get direct feedback, ask one clarifying question instead of just nodding: “Do you mean the naming or the structure?” This signals you are engaging, not wounded, and it buys you time to not take it personally.
6. Give feedback up the chain too. Telling your manager or a senior “I do not think that deadline is realistic” is expected here, not insubordination. Staying silent and then missing it quietly is the bigger sin.
7. Watch how Dutch colleagues disagree with each other in meetings, then copy the phrasing. “Ik ben het er niet mee eens” (I do not agree) said calmly is your template. Note that nobody gets offended.
8. Decouple direct work feedback from the relationship. The same colleague who tore apart your PR at 11am will genuinely invite you for a beer at 5pm. That is not fake, the two things are just not connected the way they are in PH.
9. Notice the agenda culture: feedback often comes in scheduled 1-on-1s, not surprise hallway chats. If something is wrong, you can ask “can we put 15 minutes on the agenda?” instead of bottling it up.
10. Give yourself a recovery line for when something stings: “Okay, that is fair, let me look at it again.” It ends the moment with composure instead of a defensive reaction you will replay all night.

Common mistakes

• Reading every blunt comment as disrespect and going quiet for the rest of the day.
• Agreeing to everything to keep the peace, then being seen as someone with no real opinion.
• Over-apologizing in Slack and reviews until people start wondering if you trust your own work.
• Saving up complaints for months instead of raising them early, then exploding or burning out.
• Assuming a colleague dislikes you because they criticized your code, when they have already mentally moved on.

What to verify

Every team has its own culture on top of the national one. Watch your specific team for a few weeks and check what is normal there, and if feedback ever crosses into genuinely disrespectful or discriminatory territory, that is an HR matter, not a culture quirk. Talk to your manager or HR.

Jake note

The first few months, I took every “no, that is wrong” personally and went silent. What actually fixed it was realizing the same person would joke with me ten minutes later like nothing happened. They were not mad, I was just running on PH social rules in a Dutch room.