Your Best Work Is Invisible. Write It Down Where People Can Find It
Your best work is invisible outside your company. Writing and posting in public is how a senior engineer turns private experience into reputation, opportunities and clearer thinking. What to share, where, how often, and what to avoid.
On this page
Think of the best engineer you have ever worked with. The one who quietly fixed the thing nobody else could, who saw the problem three weeks before it happened.
Now search for their name.
Probably nothing. A profile with a job title. Perhaps a photo from a conference in 2019. All of that skill, and the internet has no idea they exist.
Then think of someone you know who is, to be polite, average at the job and excellent at posting about it. They get the conference invitations, the job offers and the newsletter features.
It is unfair. It is also fixable, and the fix is not to become a full-time influencer.
Most good engineers are invisible. Their best work sits in private repositories and internal documents, known to a dozen colleagues. That is fine until they want a new role, a client, a co-founder or simply more options, and discover that nobody outside their company has any way of knowing they are good.
Writing in public fixes that. It is the one piece of career advice I would give every senior engineer.
What it actually gives you
Opportunities arrive instead of being chased. People look you up before they contact you. If what they find is a short profile and nothing else, they move on. If they find three articles that show how you reason about hard problems, the conversation starts from trust.
It compounds. A post written once keeps being found. Search engines index it, and increasingly AI assistants read it and repeat it when someone asks a relevant question. I cover that side in AEO and GEO.
It sharpens your thinking. You do not really know what you believe until you have to write it clearly enough for a stranger. Half the value is private, and it shows up in better design documents and clearer arguments at work.
It is a senior skill. At staff and principal level, influence comes from writing: proposals, strategy, post-mortems. Public writing is practice at exactly that, with a larger and less forgiving audience.
It is insurance. Companies change direction and teams get cut. A reputation that exists outside your employer is not affected by a reorganisation.
Why most engineers do not do it
- “I have nothing new to say.” You do not need to be first. You need to be clear, and to speak from experience. Most people looking for an answer have not found a good explanation yet.
- “Someone will tell me I am wrong.” Occasionally, and usually you learn something. Being corrected in public is uncomfortable for a day and useful for years.
- “It feels like self-promotion.” Sharing what you learned so others can avoid a mistake is teaching. The distinction is whether the reader gets something.
- “I do not have time.” One good post a month is twelve a year. That is a body of work.
What to post
The posts that build a reputation are about judgment, not about syntax.
- Decisions. “We had two options. Here is what we chose, what we gave up, and how it turned out.”
- Lessons from failure. What broke, why, and what you changed. These are the most read and most trusted.
- A defensible opinion. Something you believe that not everyone agrees with, argued properly.
- Clear explanations. A concept people in your field find confusing, made simple.
- Patterns you notice. After years in an area, you see things newcomers do not.
- Honest case studies. A project from problem to result, including the constraints.
What to avoid:
- Tutorials that repeat the documentation. They are everywhere, and AI now produces them on demand.
- Announcements with no substance. “Excited to share” followed by nothing a reader can use.
- Engagement bait. Polls and hot takes built to provoke. They attract attention from the wrong people.
- Vague inspiration. General advice with no experience behind it.
A simple test: would a peer you respect learn something from this, or save time because of it?
Where to post
Pick one home and one or two distribution channels.
- Your own site is the home. You own it, it does not change its algorithm, and it is where search engines and AI crawlers find a stable record of your work.
- LinkedIn reaches hiring managers, founders and clients. It rewards plain, specific writing about work.
- X is where a lot of engineering and startup conversation still happens, especially in AI and Web3. It rewards short, sharp observations.
- Communities in your niche, such as a forum, a Discord or a newsletter, often matter more than broad platforms.
Write the full piece once on your site. Then post the main idea natively on each platform, in that platform’s style, with a link for people who want more. Do not paste a link and leave.
The contradiction I should own
I am recommending all of this without a large audience to show for it, and my own accounts do not follow the tidy advice above.
My split is simple: LinkedIn gets the judgment, X gets the jokes. Two of the jokes, for the record:
tried being myself. the algorithm said “who”
guess my replies were the only thing ive ever shipped that reached its target audience
I am fine with that. The case I am making here does not depend on reach. It depends on findability. When someone looks me up before a call, there is something to read that shows how I think, and the jokes tell them I am a person.
How to keep it going
- Keep a running note of things that surprised you at work. Almost every good post starts as “that was not what I expected”.
- Write from questions people ask you. If you have explained something three times, it is a post.
- Lower the bar for length, not for clarity. Three hundred clear words beat two thousand vague ones.
- Set a pace you can hold for a year.
- Do not measure the first six months. Early posts reach almost nobody. That is normal, and it is also useful, because it is when you are learning to write.
What not to share
Being public does not mean being careless.
- Never share confidential business information, customer data, unreleased plans or security details of systems you work on.
- Describe the shape of a problem without identifying a client or colleague, unless you have permission.
- Check your employment agreement and, if in doubt, ask. Most employers are happy when engineers write well about general lessons.
- Criticize ideas and decisions, not people.
The compounding effect
A year of steady writing produces a dozen or more pieces that describe how you think. A hiring manager reads two and already knows more about you than an interview loop would tell them. A founder searching for someone with your experience finds you directly. An AI assistant, asked who knows about your niche, has something of yours to cite.
None of this replaces doing good work. It makes good work visible, which is the part most engineers skip. If outreach is part of your plan, public writing is also what makes cold email credible when the recipient looks you up.
Questions people ask
Should software engineers post on social media?
If they want opportunities to find them, yes. Hiring managers, founders and clients look people up before reaching out. A small body of public writing that shows how you think is stronger evidence than a resume, and it works while you are busy doing other things.
What should an engineer post about?
Decisions and lessons, not announcements. How you chose between two approaches, what went wrong and what you changed, an opinion you can defend, a clear explanation of something people find confusing. Specific experience is more valuable than general advice.
How often should you post?
Consistency matters more than frequency. One thoughtful post a week, or one substantial article a month, kept up for a year, does far more than a burst of daily posts that stops after three weeks.