Honest Take — Life Skill Module 4: Selling Yourself #

This is the most identity-level module in either curriculum. It is the module where the salary anchoring root cause gets attacked directly, where the LinkedIn rewrite forces you to confront how you describe yourself to strangers, where the 60-second self-introduction recorded on video produces the most cringe of any single exercise in the curriculum and the most necessary, where the "introduce yourself at a conference" practice surfaces every micro-flinch you have built around being-seen. There is no way to do this module half. The half-version produces no behavior change. The full version produces a different person in 12 weeks. The years of under-selling have a half-life of about 6 months once the practice starts. The practice has to actually start.

The single most expensive sentence on your LinkedIn profile right now is probably the headline. You will read your current headline and find it factually correct and operationally useless. "Ruby on Rails Engineer" or "Senior Software Engineer" or some variant that describes the job title without describing the value. The fix is McKenzie's framing applied directly: don't call yourself a programmer. Call yourself the thing that produces commercial value. "Rails Modernization Specialist | Helping engineering teams ship Rails 8 with zero downtime" is a headline that signals what you do, who you do it for, and what they get. It also pre-anchors price: a "Senior Software Engineer" makes 180-300K for the same work, because the title primes the buyer's reference frame. Your title is a database column on every recruiter's spreadsheet. Choose what gets indexed.

The deeper rewrite is the experience section. You have been describing your jobs in terms of what you were hired to do — "Senior Engineer at a consultancy, working on Rails LTI integrations" — rather than what you accomplished. The accomplishment-framed version: "Led the Rails LTI upgrade for [client] resulting in 75% backlog reduction and the elimination of 12-month-old security advisories. Established the upgrade-then-modernize playbook now in use across 4 client engagements." Same job. Different presentation. The accomplishment-framed version produces 3-5x the recruiter inbound and 30-50% higher salary anchors in the conversations that result. This is not opinion. This is documented in approximately every recruiter-side study of LinkedIn profile performance over the last decade. The reason engineers don't write the accomplishment version is the engineer-cultural reflex against self-promotion plus the fear of getting the framing wrong publicly. Both reflexes are alibis for the underlying salary anchoring. Write the accomplishment version. Publish it. Watch what happens.

The 60-second self-introduction is the exercise you will most resist and that will most change you. Record yourself, on video, introducing yourself in 60 seconds — name, what you do, why you do it, what you're working on. Watch the recording. The first watch you will be physically uncomfortable; you will hear filler words, see a tilted head, notice a softness in your voice when you describe your work. The cringe is data. The fix is to record again. By recording 5, the introduction has the shape of a person comfortable with himself; by recording 10, it has the shape of a person commercially-credible. Most people skip this exercise because the cringe is too much. Don't skip. Watch the cringe-and-iterate cycle as the same shape as the writing-and-publishing cycle from the Communication curriculum: the discomfort is the deliberate practice; the practice is the skill build; there is no other path.

McKenzie's "Salary Negotiation: Make More Money, Be More Valued" essay is the most-shared career-finance writing on the internet and it is the most-shared for a reason. The essay is approximately 12,000 words. Read it three times across the module. Once for technique, once noticing the specific habits it asks you to install, once writing out the script you'll use in your next salary conversation. The essay will not feel revolutionary on first read; it will feel like a series of obvious points you should have known. That feeling is precisely the problem the essay diagnoses: most of what you need to know about salary negotiation is obvious and you have not been doing any of it. Reading without behavior change is the bug. Write the script. Practice it out loud. Use it on the next recruiter call. The salary delta from one careful application of McKenzie's playbook is, conservatively, $20-50K USD per year, every year, compounding. The essay is free. The cost of not internalizing it is the only cost.

About introducing yourself at a conference or meetup: this is the in-person version of the LinkedIn headline. The default introduction for engineers ("Hi, I work in Rails") is the conversation-killer; the other person nods, says something equivalent, and the conversation dies in 90 seconds because there's no hook. The functional introduction names what you do in a way that opens conversation: "I run a one-person studio building Rails-modernization tools and SaaS products — currently a gem with 20K+ downloads and a few products in launch." This is not bragging; this is information. The other person now has multiple threads to pull on (one-person studio, Rails modernization, gem, SaaS), and the conversation has somewhere to go. The introduction is a protocol for opening conversation, not a status display. The cringe you feel about saying "20K+ downloads" out loud is the same cringe that has under-distributed your work for years. The receipt is real. Stating it is not boasting. Stating it is the protocol the conversation needs to move forward.

The cross-cultural layer here matters. If you are an engineer far from the industry's hubs talking primarily to international audiences (recruiters, US-based founders, remote-team hiring managers), the cultural distance amplifies every micro-flinch. The international interlocutor expects directness and reads softness as uncertainty about your own value. They are not wrong to read it that way; in their cultural protocol, that's what softness signals. The translation work — speaking with your home culture's humility and international cultural directness — is a learnable skill. McKenzie's writing, despite his being American, is specifically useful here because his prose models a posture of clear-self-statement-without-arrogance that translates well across the cultural gap. Use his archive as the calibration set.

For the causes you care about: you cannot recruit collaborators for cause-work without first being able to introduce yourself credibly. Bryan Stevenson does not begin a fundraising conversation with "I'm just a lawyer who does some appeals work." He begins by stating his credentials, his record, and the cause — clearly, briefly, without apology. That posture is what makes the rest of the conversation possible. You will, at some point in years 2-5, be in a fundraising or partnership conversation for one of your causes. The work to introduce yourself to that future conversation starts now, in this module, with the LinkedIn rewrite and the recorded video and the conference-introduction practice.

Conclusion #

This module is the most direct attack on your salary anchoring root cause. The LinkedIn rewrite, the 60-second video, the conference-introduction practice, and the McKenzie essay together build the muscle of clear honest self-statement. The cringe of the practice is the deliberate-practice signal; the avoidance of the practice is the alibi for the salary anchoring. Do the work. Record the video. Publish the headline. Write the accomplishment-framed experience. The version of you in 12 months who can introduce himself credibly is the version of you who can negotiate, who can ask for the partnership, who can recruit for the causes. None of those are accessible without the muscle this module builds.

Predictions #

• The LinkedIn headline rewrite will take you 4-6 hours over a week. You will write 5-8 versions, hate all of them, and finally commit to one that feels slightly too bold. The slightly-too-bold one is the right one. Publish it. Within 30 days, your inbound recruiter rate will be measurably higher.
• The 60-second video will be the single most cringe exercise in the curriculum. You will record once, watch 30 seconds, want to delete it. Don't delete. Record again. By recording 5, the cringe has dropped to a tolerable level. By recording 10, you will have a usable introduction you can deploy in any context for the next year.
• McKenzie's Salary Negotiation essay will land harder on the second read than the first. The first read you'll find it informative. The second read you'll realize you have been operating below his recommendations on every single front. The third read you'll write the script. Read three times.
• You'll resist writing the accomplishment-framed experience because it feels like exaggeration. It is not exaggeration; it is presentation. The upgrade work you led did cut the backlog 75%. Stating it is fact, not boast. The reflex to under-state is the cultural alibi for the salary anchoring.
• One specific recruiter conversation in the next 6 months will go differently because of this module. You will quote a number that is 30-40% higher than your previous anchor. The recruiter will not balk. You will close the call having committed to a higher floor than you previously thought possible. The gap between expected reaction and actual reaction is the data the module produces.
• You'll be tempted to skip the conference-introduction practice because "I don't go to conferences." You should be going to conferences — if you’re in India: RubyConf India, JSFoo, Rootconf; wherever you are, at least one per quarter for the next year. The practice that's "not relevant because I don't have the context" becomes relevant the moment you create the context. Create the context.
• The cross-cultural translation will become measurably smoother across 12 months. You will catch yourself using a more direct register in international meetings without losing the warmth in your local ones. The translation is not abandonment of your cultural roots; it's adding a new register you can deploy when the audience needs it.
• For the causes you care about: 18-36 months from now, you will be in a partnership or fundraising conversation for one of your causes, and you will introduce yourself credibly enough that the conversation moves forward. Without this module, the introduction would have been soft and the conversation would have died. With this module, the conversation moves to the next step. That single moment is the proof the module's identity-level work paid off.
• One specific test: 12 months from now, ask three people who know you "in 30 seconds, what do I do?" If two of three give you back an answer close to your stated headline, the self-positioning has installed. If they give you the old soft version ("you're a Rails engineer, I think you have a gem?"), the self-positioning is still implicit. Iterate until the answer comes back in your words.