For capable-but-quiet engineers, 1–3 years in

Stop shrinking in rooms
you already belong in

Outgrow 'junior' before your title does.

I help engineers in their first 3 years stop shrinking in rooms they belong in, so they outgrow 'junior' before their title does.

I have been the quiet, introverted one in the back of the room, unsure what to say in standups and code reviews. Now I help similar capable-but-quiet engineers close the gap between what they can do and how they're perceived. Better Every Build is where I share what I wish I had in my first years.

Get the weekly email Ask me a question
Headshot of Better Every Build founder Thimo Koolen
2000+
Engineers looking to level up

Close the gap between what you can do and how you're perceived.

Code review goes smoothly. You ship clean work. And still you're watching a mid-level disagree with a senior engineer in standup and think "I could never do that." You hold opinions that never come out of your mouth. You apologized four times in your last PR comment.

Your manager said you need "more visibility" in your review and gave you no how. Less-capable peers are getting promoted ahead of you. Trust me: you're not crazy. There's a pattern. And it's learnable.

The underlying cause is imposter syndrome. But naming it doesn't fix it, and neither does waiting for it to go away. You learn to act anyway.

The Promise

Close the gap between what you can do and how you're perceived, so promotions, projects and trust come to you.

The Symptom

Shrinking, and its six patterns. The visible behavior driving most of the gap, and where every fix actually starts.

For You If

You're 1–3 years in, technically respected, and quietly suspecting "keep your head down and do good work" is a lie with no replacement strategy.

The 6 Shrinking Patterns

Recognize these? These are the behaviors that quietly cost capable engineers their credibility and their next opportunity.

Apologizing

"Sorry if this is wrong, but..." four times in one PR comment, before an opinion you're right about. The credibility tax you pay before you even speak.

Hedging

"This might be dumb a dumb question, but..." You preface good ideas with disclaimers that tell the room to take you less seriously than your input deserves.

Going Quiet

A senior pushes back, your stomach drops. You had an answer, but swallowed it. You don't want to be "that person," so you say nothing. You leave the room thinking "I should have said something."

Waiting Passively

Hoping to be invited into the project you could be leading. Treating "more responsibility" as something granted instead of something claimed. You're ready, but you keep waiting for someone to notice.

Not Asking

Not asking questions you should ask. You stay stuck for hours because asking feels like admitting you don't belong. You don't ask for help, feedback, or the next opportunity, and you don't get them.

Skipping Feedback

Not giving feedback you should give. Not asking for feedback you should ask for. You feel like you don't have the right to give feedback, and that asking for it would be a sign of weakness.

What Engineers Are Saying

I am currently collecting stories and feedback from developers who follow Better Every Build. Once I have a few real results to share, you will find them here.

Join the Newsletter

Every Sunday: one story, one framework, one thing you can use this week to stop shrinking and start taking up the space you've earned. Written for capable-but-quiet engineers who want to close the gap between what they can do and how they're perceived.

    No spam. Unsubscribe anytime (no hard feelings).

    Your email is safe with us.

    Built with Kit

    Let's Connect

    Have a question? Want to collaborate? Or just want to say hi? I'd love to hear from you.

    LinkedIn
    Connect with me