A few days ago I wrote a LinkedIn post about how the job market has changed for senior engineers. The short version: the application funnel is broken, the work has shifted upstream, you compete by being legible to the right people before you need them. The post traveled further than I expected. What I keep returning to is not the data. It is what the post made visible, in me and in the engineers who answered.

The volume nobody names

There is a clean version of the visibility argument that goes something like this. Write publicly. Build in the open. Show how you think. Opportunities follow. The version is true. It is also incomplete in a way that matters.

What gets left out of that version is the volume. The actual texture of doing this work is not one polished article a month while you sip coffee and contemplate your career. It is articles, and LinkedIn posts, and engagement on other people's threads, and showcase projects on GitHub, and open source contributions, and the open-to-work tag, all happening in parallel with the actual job search. Applications. Screening calls. Recruiter conversations that go nowhere. Technical assessments. Take-home tasks that eat a weekend. Panel interviews with people who have not read your CV. System design rounds. Behavioral rounds. Follow-up emails. Rejection emails. The occasional silence that is somehow worse than rejection.

I joke constantly that I cannot wait to get a job so I can rest a little. That joke is the most honest thing I have said about this period of my life. The strategy works. The strategy also runs in parallel with everything that the strategy was supposed to make easier, because you cannot stop applying while you wait for the inbound to start, and the inbound takes months to start, and the rent does not pause while the compounding compounds.

Anyone telling you that public output is the smarter, calmer alternative to the grind is selling you something. It is not the alternative. It is the additional load you carry while you do the grind, until the grind shifts shape. That shift is real, and it is worth the cost. But the cost is not abstract. The cost is hours of your life, every day, on top of an already exhausted nervous system.

The part everyone skips

There is a lot of writing about why senior engineers should be more visible. Most of it focuses on the upside. Better opportunities. Higher signal inbound. More control over your career. All of that is true. I have lived it. The conversations that come back when people already know how you think are a different caliber from anything that came out of cold applications. The compounding is real.

What almost nobody writes about is what this work does to the part of you that has to keep showing up. Not in time, though it is slow. Not in effort, though it takes more than people admit. In the part of you that has to keep producing despite every signal in your nervous system telling you not to.

I have ADHD. I have social anxiety. I am not naturally an extrovert who occasionally needs alone time. I am closer to the opposite. An extrovert who has to be introvert in chunks to function. Publishing publicly is not something I do easily. It is something I do with my hands shaking on the keyboard.

I reread every post more times than I would like to admit. Every comment, every reply, every article. I run scenarios in my head before publishing. I run them again after. The criticism that never came, I have rehearsed defenses for. The misreading that did not happen, I have prepared corrections for. The dismissal that nobody actually wrote, I have already felt.

This is the part most productivity advice does not mention. Not because the writers are dishonest, but because acknowledging it does not sell the strategy as cleanly. "Just write publicly" is easier to say than "write publicly while your nervous system convinces you that you are about to be humiliated, and do it again next week, and keep doing it while you also send out applications and prepare for interviews and explain yourself to recruiters who have not read past the headline."

What the responses showed me

The post traveled. What surprised me was not the reach. It was what the reach surfaced.

Strangers wrote back with their own versions of the same exhaustion. Some pushed back on the strategy. Some validated it. Some told stories from inside the same fight. Some named fears they had not said out loud before. Some signaled solidarity from somewhere quiet. A few wanted to give up. A few wanted permission to keep going. A few wanted a shortcut, and a few wanted a witness.

The shape underneath all of it was the same. People are tired. The market has made everyone smaller. The strategies that used to work do not work anymore, and the new strategies have a cost the old discourse refuses to name. Engineers who have spent fifteen, twenty years building real things are sitting at their kitchen tables refreshing inboxes that do not refill. Some are losing their belief in what they built. Some are considering walking away from the field entirely. Some are quietly afraid that the version of themselves that knew how to do this job is no longer welcome in the room.

Reading the responses, I understood that the cost I had been carrying privately was not mine alone. It was widely distributed and largely unspoken. The thread, for a few days, was a place where it could be spoken. That mattered more than the impression count.

What it actually feels like

Here is what writing publicly is like for me, on a regular Tuesday, while also looking for a job.

I have an idea. Usually from a real problem I am solving or have solved. I draft it in fragments over a few days, between recruiter calls and technical assessments. I am pulled in twenty directions because my brain works that way, and because the job search itself is twenty directions.

Then I have a draft. The draft is bad in places. I rewrite. The rewrite is worse in different places. I rewrite again. At some point I have something that says what I meant to say, in the voice that sounds like me. This is the part I love.

Then I have to publish. This is the part I do not love.

Before I hit publish, I read it again. I check for one more typo. I check the phrasing of one more sentence. I am not actually looking for problems. I am looking for permission to publish, and my brain is not granting it. I hit publish anyway.

The first hour is the worst. I check the post too many times. I read it as if a stranger were reading it. I imagine the worst possible reader and what they would say. I imagine my friends reading it and thinking less of me. None of this is rational. All of it happens.

If a comment comes in, I read it ten times before I reply. If the comment is critical, I draft three responses before I send one. If the comment is positive, I am suspicious that the person did not read carefully enough to see the parts that are wrong.

And then, slowly, the post settles. A day passes. Another post is in the draft. The cycle starts again. Meanwhile, the job search continues, and the interviews continue, and the rejections continue, and the writing continues, and somewhere underneath it all you keep hoping that this is the week the math turns.

Why I do it anyway

Two reasons. The first is the one the original post made the case for. The work pays off. Not in volume, in quality. People who reach out have already met you on the page. Conversations start at a different level. Opportunities show up that would not have otherwise. This is true and I would not unrecommend it.

The second reason is the one I did not understand when I started. The work does something to you, not just for you.

The fear does not vanish. It does get quieter. Not because you have become a different person, but because your nervous system slowly learns that the catastrophic version of the post did not happen. That the dismissive comment you rehearsed defenses for never came. That the people who do not engage are not silently judging, they are just busy. That most readers are generous, and the ones who are not are usually not paying close attention anyway.

Each post you survive teaches your brain that you can survive the next one. Not survive in a metaphorical sense. Survive in the actual sense of: I felt the fear, I did the thing, I am still here, the worst case did not happen, I can do it again.

The first post is the hardest. The second is a little easier. By the fifth, the panic is shorter and the recovery is faster. Not because the wiring changed. Because you have proof now, accumulated, that the catastrophic prediction was wrong.

What I want to say to the engineer reading this

If you are reading this and recognizing yourself in any of it, here is what I want you to know.

The work is real. The cost is real. You are not weak for finding this hard. You are not failing if you have to stop and start. You are not less capable than the people who seem to publish effortlessly. They are also doing this. Most of them just do not write about that part.

The advice to be visible is correct. The strategy works. But the version of the advice that does not acknowledge the cost is incomplete. Showing up is not a small thing. It is a small act of public courage, repeated. The compounding only happens because you keep doing it.

If the only way you can start is small, start small. Two short posts a week. One article a month. One open source contribution. The size of the move is not what matters. The repetition is what matters.

And if your first post terrifies you, that is not a sign you are doing it wrong. That is the sign that you are doing it for real. Hit publish anyway. The hands shaking are part of the work.

The honest accounting

The post that led to this article ended with: start writing, start shipping, start showing up, the market has changed and the strategy has to change with it. That is still true.

What I want to add, now that I have had a few days to watch the responses come in and feel the weight of doing this work for months, is this. The strategy has a cost most writers do not name. The cost is paid in a specific kind of quiet courage that does not look heroic from the outside. It looks like a person reading their own draft for the seventh time before hitting publish. It looks like checking notifications too often. It looks like rereading a comment ten times to figure out if it was actually critical or you just imagined the edge. It looks like opening yet another technical assessment after a long day of writing.

It looks, in other words, like ordinary work, done by someone who is afraid, who is tired, who does it anyway, who keeps doing it.

That is the part worth writing about. That is the part I wish someone had written for me when I started.

The compounding is real. The cost is real. Both are worth saying.