Growth Mindset¶
Not a rehearsed story. The thing you actually do when nobody's grading you for it.
Why This Exists¶
Behavioural teaches you to narrate judgement you already have — six well-told stories, STAR plus reflection, scoped to the level you're interviewing for. This section is upstream of that: it's about whether you actually have the judgement, not whether you can narrate it. A candidate can memorize a perfect "I pushed back on my manager" story and still, in the room three months later, fold the first time a VP raises their voice. The story and the character aren't the same thing, and only one of them is fakeable for forty-five minutes.
None of this is corporate-poster material. It's the specific, unglamorous mechanics of staying an engineer worth working with over a fifteen-year career, not just a good interview performance once.
Mental Model: Two Different Failure Modes¶
Almost every career-damaging mistake in this space falls into one of two buckets, and they require opposite corrections:
TOO SOFT TOO RIGID
───────── ─────────
Says yes to everything Digs in on everything, including
Absorbs blame that isn't theirs things that don't matter
Never names the real cost Confuses "I disagree" with
Burns out quietly, resents "this is a hill to die on"
loudly, six months later Every disagreement becomes
Mistakes agreeableness a character test
for professionalism Mistakes rigidity for integrity
↓ ↓
Both produce the same outcome:
people stop trusting your judgement,
for opposite reasons.
The skill this whole section is built around is calibration — knowing which situations are worth spending your credibility on, and which aren't, and being honest with yourself about which bucket you're defaulting to under pressure. Most people have a default direction (some fold, some dig in), and the correction is almost always toward the opposite of your default, not toward a fixed rule.
Pages in This Section¶
| Page | Covers |
|---|---|
| Respect — Yourself and Others | Why self-respect is a prerequisite for being useful to a team, not a personal indulgence — and where it curdles into arrogance |
| Standing Your Ground, Professionally | Disagreeing with someone who outranks you without becoming someone nobody wants in the room |
| Crucial Conversations | How to present difficult things — worked scripts for hard feedback, bad news, and unwelcome decisions, without softening them into uselessness or landing them as an attack |
| Protecting Your Sanity | Why burnout is a design flaw in how you work, not a badge of commitment — and the concrete signs you're past the line |
| Don't Say Yes When You Mean No | The compounding cost of a reflexive yes, and how to build the habit of a considered answer instead |
| The Strong Engineer | What separates a strong engineer from a merely skilled one — traits and conduct, and why they're not the same list |
| Seeing What Others Miss | The specific mental habits behind noticing the problem nobody else flagged, before it's an incident |
Read them in whatever order matches what's live for you right now — this section isn't sequential the way a technical curriculum is. If you're about to walk into a hard conversation, start with Standing Your Ground. If you're wondering whether the exhaustion you're feeling is normal, start with Protecting Your Sanity.
Key Takeaways¶
- Judgement and the ability to narrate judgement are different skills — this section builds the first one; Behavioural teaches the second.
- Most people default toward either too soft or too rigid under pressure — the fix is almost always toward your opposite, not toward a universal rule.
- None of this is about being liked. It's about staying someone whose judgement other engineers actually trust, which is a much narrower and more durable target.