You need to sign in or sign up before continuing.
Reflection — An Honest Take 8 min

Honest Take — Before You Begin

Honest Take — Module 9: The Engineer-Shaped Patterns & the Solo Founder Variant #

Many working engineers are simultaneously some combination of open-source maintainer, senior individual contributor, founder, and consultant. If you hold more than one of these roles, they compound in specific ways and each carries its own characteristic imposter trigger, and I want to address each with as little softening as I can manage, because the soft framing is what lets engineers carry these feelings unchallenged across all their roles for longer than the data justifies. Start with the open-source maintainer pattern because it is the easiest to argue from numbers. Picture the maintainer whose package has 25,000 downloads. Sixty releases. Dozens of GitHub stars. Thousands of passing specs. Organic growth without marketing, and production deployments at companies whose names they do not even know. By any working definition of "open-source maintainer" — someone who ships releases of a thing that strangers depend on — that person is one. And that person, reliably, still hesitates to say "I maintain a widely-used library" and reaches for "I have a small gem" instead. If your numbers are anywhere in that neighborhood, the internal feeling that you are not really a maintainer is not a calibration issue. It is a refusal to update the self-model in response to the data. The cure is not more confidence; the cure is to look at the numbers and let them mean what they mean. Say "I am an open-source maintainer" in the next conversation where it is relevant. Stop qualifying it. Tens of thousands of downloads is not small in this category.

The senior IC pattern is more textured because the title-and-tenure data is genuine but the role identity is unstable. Years of production work; real titles at real companies; perhaps a tech-lead stint, perhaps a stretch at a startup or a unicorn whose name carries weight. The titles are real; the tenure is real. And yet many senior engineers are not settled in the senior identity, because senior in some companies means manager-track which they have intentionally not taken, and because some kinds of work — internal tools, platform plumbing, large inherited codebases — do not make contributions visible the way a senior IC role elsewhere would. The imposter feeling here is partly a category-mismatch feeling, and the cure is to name what kind of senior IC you are rather than to argue with the term: a senior IC who chose the IC track over management deliberately, who has shipped production work that companies depended on, and who may have built independent work that demonstrates senior capability outside any employer context. That is the identity you can actually defend — including in a staff-level interview loop, where "what kind of senior engineer are you" is not a philosophical question but literally the hiring manager round. The founder pattern is where the unspecified-milestone trap operates, and it is the pothole I am most worried about. The solo founder who incorporated a one-person company, ships products, and has something live is, by any working definition of "founder," one. But the imposter feeling moves the goalpost: not really a founder until revenue, until funding, until employees, until [the next milestone after wherever you currently are]. The trap is structural and has no exit because the milestones can move forever. The cure is a definition problem, not a confidence problem: pick a criterion — strict or loose, but written — and then you either meet it or you don't by the rule you set, not by whatever the feeling is currently insisting on. If you have moved this goalpost more than once in the past year, write the rule down and stop renegotiating it under the influence.

Here is what the solo-founder configuration adds, and it is a structural point the general imposter literature does not address. The canonical sources — Clance, Young, Burns, Neff — all wrote within institutional contexts where the imposter feeling is at least socially scaffolded by peer review, performance reviews, hierarchical feedback. As a solo founder you have none of that. You are evaluated by clients, whose feedback is noisy, indirect, and transactional, and by yourself, whose feedback runs through the unreliable evaluator we have spent eight modules examining. This is a much harder calibration environment, and it is also the arrangement that most strongly rewards acting under doubt and most strongly punishes waiting for confidence. Every quote you don't send, every rate you under-charge, every public claim you don't make — these are not neutral acts of caution. They are quiet payments to the imposter feeling, made out of the bank account of your business. The bank account is finite. The feeling does not become full. After a few years you can run the account low while the feeling is still asking for more. That is the trap specific to the solo configuration, and if you run a one-person company, it has probably been making some of those payments since incorporation.

The consultant pattern is where money is on the line in a way the other patterns are not, so I will be direct. The consultant quoting 30-40% under market as a pre-emptive apology — say 40-60K — is paying fifteen to twenty thousand dollars per engagement to a feeling, compounding annually. If that is you: some of the gap is M3-environmental, as that module argued; a meaningful portion is pure imposter-driven self-anchoring, and the M1 diagnostic will name it as such if you run it honestly on a specific upcoming pitch. Set the rate by the data — market rate, your track record, the value to the client — pre-decide the number before the call, anchor at the higher number, and run M8's protocol when the feeling fires before you say it out loud. Patrick McKenzie is the most intellectually honest writer in this space and his "Don't Call Yourself a Programmer" essay is the inverse-imposter move at the level of professional self-description: describe yourself in terms of the value you create, not the technical labels that hide it. When you tell a prospect you are "a Rails developer" — or whatever your stack's equivalent is — rather than "the engineer who keeps your billing system running so your customers pay you," you are letting the imposter mind shape your professional identity into a cheaper version. Graham's essays do adjacent work without ever using the vocabulary — "Schlep Blindness" especially: the imposter mind hides certain work from you because doing it would require claiming a competence you don't internally credit. Graham's correction is to name the schlep, do it anyway, and notice that the doing changes who you are.

Two operational notes to close. First, the stacking effect: the patterns do not average, they stack. When you walk into a staff-level interview loop, the senior-IC feeling fires in the foreground, the founder feeling fires underneath (should you be building your own thing instead of interviewing?), the consultant feeling is in the room because any offer will be priced against your current rate, and the maintainer feeling sits at the bottom because the next release is still pending. One narrative sentence may not cover the stack; build IMPOSTER_PROTOCOL.md with a subsection per pattern and run the relevant one in the relevant moment. Second, the peer-infrastructure advice — the quarterly call, the email exchange with one or two trusted operators — sounds like networking advice and is not. Networking is for opportunities; peer infrastructure is for calibration. Optimize for someone who can credibly tell you "you're underpricing that, raise the rate" and mean it; the opportunities sometimes follow as a side effect. If you operate in or from the Indian tech ecosystem, the context supplies its own discount flavors — the IIT-alumni dynamic, the FAANG-compensation comparison against consultancy income, the "but you don't have a US income" diminishment — and a peer who shares that context is worth two who don't.

Conclusion #

If the data says you are an open-source maintainer (tens of thousands of downloads is not small), say so. If you are a senior IC, name the specific, defensible IC-not-manager identity you actually hold. If you are a founder, write the definition down before the milestone trap moves it again. If you are a consultant, the rate gap is real money partly paid to a feeling. The solo configuration strips away the institutional scaffolding the literature assumes and punishes waiting for confidence with the business's own bank account. Run M1's diagnostic per pattern, build the protocol subsections, read McKenzie and Graham, and set up one calibration-grade peer relationship. The words you use about your roles determine which rooms and rates you can access; choose them by the data, not the feeling.

Predictions #

  • If the maintainer pattern is yours, you will resist claiming "open-source maintainer" out loud despite the data, and the resistance will outlast this module — it shifts only through repetition in actual conversations, including at least one interview.
  • If you consult, the rate will not move to market on the first engagement after this module; it takes one or two engagements before the new anchor internalizes. When revenue rises afterward, the discounting machine will credit "the market." Notice the credit.
  • The founder-definition exercise will surface two or more goalpost moves across the past year, and the recognition will be unflattering and useful.
  • The stacking effect will be most acute in whatever high-stakes window you are currently inside; build the protocol subsections before the first round, not after.
  • McKenzie's essay will land harder than anything else in the module and produce at least one immediate language change on your portfolio site or LinkedIn headline within two weeks.
  • The peer-infrastructure search will take 6-8 weeks, longer than feels reasonable, because finding someone who can do calibration rather than congratulation is genuinely hard.
  • You will under-credit your most legible artifact — the package, the product, the system you ran — in at least one job-search or client conversation this quarter, and the under-crediting will cost legible material: negotiation leverage, perceived seniority, or both.