Two jobs live in your head when it comes to thinking about yourself, I personally train only one of them.
- There's the Assessor: the voice that finds the truth about your skill.
- And the Advocate: the voice that states the case for you.
Assessors should doubt themselves. Advocates should doubt the doubt.
Problem is, humble people run Assessor all day, in every context, including in interviews. So "I'm not the strongest backend engineer" quietly becomes "I'm not full-stack," and a comparative fact gets treated as a categorical verdict.
The fix isn't affirmations. It's one framework before you speak:
- Mode: Assessing vs. Advocating: Am I trying to find the truth, or state the case? These require opposite defaults: Assessor should be skeptical of itself; Advocate should be skeptical of doubt, not of self.
- Trigger: Invited vs. Unprompted: Did someone ask for the weakness, or am I volunteering it? Most of your flustering happens on unprompted disclosure — you're doing the interviewer's skepticism-work before they've asked for it.
- Context: Verdict vs. Trajectory: Is this framed as a fixed state ("I'm not strong at backend") or a moving one ("I'm deepening backend")? Same facts, opposite implications for how a listener weighs it.
These are independent: you can be Advocating, Unprompted, and still choose Trajectory language. Or Assessing, Invited, Verdict — that's you journaling honestly about a real gap. Both are legitimate
Choosing which combination shifts your language. "Claiming" becomes "stating." "I'm not strong at X" becomes "I'm still deepening X". It’s the same honesty, but at a different trajectory.
Being confident isn’t about a feeling, it’s about a mindset. It's where you get once you've correctly classified which voice should be talking.