Technical Writing Salary Reality

Walk me through what you make.

I started at $62,000. That's what the offer letter said and I said yes because I'd applied to about 40 jobs and this was the first one that wanted me. I didn't negotiate. I was 24 and I was grateful and I had no sense of what the market rate was. The company is a payment processing startup. They make software that handles merchant onboarding and transaction processing for e-commerce businesses. About 200 employees. Venture-backed. My job is API documentation and the merchant onboarding guides.

I found out I was underpaid about eight months in. There was a TW who joined after me, a guy named Brennan, who mentioned in a casual conversation that his starting salary was $73,000. Same title. Same team. He'd negotiated. I hadn't. The difference was $11,000. I sat with that for a while, which is to say I went home and updated the spreadsheet and stared at it for about 20 minutes. Then I started looking at what the market actually paid for my role. Levels.fyi doesn't have great TW data, but I found some survey results through the Write the Docs community. Junior TW in New York, two years of experience, software documentation: roughly $68,000 to $78,000. I was at $65,000 by then, two years in, after a 3-point-something cost-of-living raise.

Did you do anything about it?

Yes, eventually. I waited until my two-year anniversary review, which felt like the right moment because I had a track record to point to. I'd owned the entire API reference rewrite. 400 endpoints, documented from scratch after we migrated to a new platform. My manager Theo sat in on that review and I asked for $76,000. I had research. I had the Levels.fyi data, the Write the Docs survey, the Glassdoor ranges. I framed it as a market alignment issue, not a fairness complaint about Brennan. Theo went to HR. They came back at $72,000. I said yes. I should have held for $74,000 but I was nervous and $72,000 felt good after starting at $62,000.

I'm at $72,000 now. With a 5% annual bonus target, last year's came in at $3,400. Total comp is about $75,000 to $76,000. For New York with my rent situation, that's manageable but not comfortable. I have a roommate. I don't have a car. My student loans are $380 a month. I'm not in debt. I'm not investing very much either. The trajectory is good, I think, but I think about the two years I spent at $62,000 and $65,000 and I'm aware that Brennan had an extra $22,000 in that period that I didn't, just because he asked and I didn't.

What do you make of the gap between TW pay and engineering pay at your company?

I document our API. Every developer who builds against that API is using documentation I wrote. When the docs are good, integration goes faster. When the docs are wrong, developers spend hours debugging integration issues that are actually documentation errors. I've seen support tickets that traced back to things I didn't explain clearly enough. That's real. That costs the company money.

Brennan told me that Marcus, one of our backend engineers who joined around the same time as me, started at $130,000. Same experience level. Marcus is great at his job. I'm not saying that's unfair. I'm saying that I document the work Marcus produces, and the people who depend on that documentation to use the product we both helped create, and my starting salary was less than half of his. Those two things can both be true. The market set those prices. I'm just aware of what they are.

Where do you think this goes?

I need to specialize. Junior generalist TW at a fintech startup is not a title I can ride for another five years at competitive pay. The writers making real money are the ones who specialize in developer documentation at companies that treat TW as a technical function, not a writing function. The difference matters. Places that treat it as a writing function put you in the marketing org and pay you content writer rates. Places that treat it as a technical function put you in the engineering org or alongside it, pay you on an engineering-adjacent scale, and give you access to the product you need to do the job well.

I'm looking at a senior TW role at a cloud infrastructure company. The job description lists Kubernetes and API experience, which I have. Base is $95,000 to $115,000. That's a significant step. My dad thinks I should just go back to grad school. He's an accountant, he's not wrong that an MBA would open certain doors, but the MBA path is not the path to senior developer TW. The path is building a portfolio of API reference work and developer tutorials at a company that takes the function seriously. I think I'm close to being ready to make that jump. I want one more year of API work at Theo's company first.

What's yours?

How much the salary affects what you think your work is worth. I've been at $72,000 for nine months now, which is better than $62,000, obviously. But I notice that when I'm in a meeting with Marcus and he says something about the API design, people treat it as more important than when I say something about the API documentation. Same meeting, same conference table, different weight. I don't know if that's the salary difference talking through the room or something else. Maybe it's just that engineers in tech are culturally more visible than writers. Probably both. I've started speaking up more, which helps. But there's a thing that happens when you've been underpaid for a while where you internalize it a little. You start to wonder if maybe the price the market set for what you do is the price because that's what it's worth. And then you have to actively push back against that thought. Because the documentation is how anyone uses the product. It's not a decorative element. But the salary sometimes makes it feel like one.

Walk me through the numbers.

Current base is $162,000. The RSU grant this year was $52,000 worth of stock, vesting quarterly. Last year's annual bonus came in at 8.4% of base, which was $13,600. Total compensation for last year was about $214,000. I live in San Jose. That number is not what it would be in Columbus, Ohio. But it's real.

The path to these numbers took time and it wasn't a straight line. When I transitioned from software development to technical writing eight years ago, I took a pay cut. Not massive, but real. I was at $155,000 as a mid-level software engineer. My first TW role at this company was $118,000 base, Senior TW. They valued my engineering background enough to come in at Senior rather than Mid. I lost about $37,000 in base and the RSU grant was smaller because I was a lower level. Over three years I moved to Staff, which brought the base back to engineering-adjacent territory. The RSUs now are meaningful. I have 10 more quarters on this current grant.

Is $214K a normal number for a staff TW at a big tech company?

At the companies that pay engineers well and treat TW as a technical function, yes. At other companies, no. The tech companies where TW sits in engineering or DevEx and is evaluated on a roughly parallel ladder to SWE will pay roughly like this at the Staff level. Companies where TW sits in marketing or communications pay significantly less. Same skills. Same work. Completely different compensation structure depending on where the org chart puts you.

The difference matters more than people outside this field realize. When I was a developer, I was in engineering. When I became a TW, this company put me in the Developer Experience org, which is adjacent to engineering. My performance is reviewed by people who understand technical work. My compensation is benchmarked against technical roles. If I'd joined a company that put their TWs in the communications team, I'd be benchmarked against communications roles, which pay $70K to $90K for equivalent experience. Same resume. Same portfolio. Completely different number depending on where the hiring manager sits.

What does the golden handcuffs situation actually feel like?

I have a whiteboard. It's a running RSU vesting tracker. Every quarter that vests, I mark it. The visual is not accidental. This company has been good to me. The work is genuinely interesting. I write developer documentation for cloud infrastructure products. My colleague Priya and I cover the container and orchestration documentation suite. Between the two of us, we own about 1,800 pages of documentation that gets millions of views per year. That's not nothing.

But there's a moment that happens every time a recruiter reaches out. I do the math. What's my unvested equity right now? Currently about $190,000 across the remaining 10 quarters. If I leave tomorrow for a company offering $180,000 base but starting equity from scratch, I'm leaving $190,000 on the table in addition to absorbing a year or two of ramp time before I'm fully effective at a new company. That math doesn't close most of the time. So I stay. And I'm mostly happy to stay. But "mostly happy" and "making an unconstrained choice" are different things, and I think about that sometimes when I'm marking off another quarter.

What's the ceiling look like from where you are?

Above Staff is Principal, then Distinguished. There are maybe eight or ten Distinguished TWs at this company. I know two of them. The compensation at Distinguished is meaningfully higher: base in the $180K to $200K range, large RSU grants, significant influence over documentation strategy across product areas. It's a small number of slots and the path there is not a climb so much as a recognition: you've shaped how documentation works at scale, not just done the work yourself. I think I'm capable of getting there. Whether I'm on a realistic timeline, I'm less sure. The people above me in this path have been here fifteen to twenty years and they're exceptionally good at both the technical and the organizational parts of the work.

My wife Gabrielle is a software engineering manager at a different tech company. She makes more than I do. That's just true. We've talked about it. She doesn't rub it in and I'm not resentful. It's market data. I made a choice to move into a role I find more intrinsically satisfying. The writing is more interesting to me than coding was. The ability to shape how a complex system is understood by thousands of developers, that's genuinely compelling. The market has priced that at less than the equivalent position in engineering. I'm making peace with that. Most days the math works. Some days I look at the whiteboard and I do the calculation again.

What's yours?

How much the TW salary discussion still makes people uncomfortable inside tech companies. Engineers at my level know what I make. Not the exact number, but roughly. Sometimes I see a look. Not hostile. More like... calibration. They're updating their model of how the company values different kinds of work. My former engineering manager Kofi, who I'm still friendly with, once told me that he thought the TW and SWE pay gap at this company was a structural artifact from an era when documentation was an afterthought and that it was slowly narrowing as documentation quality became a competitive differentiator. He might be right. The trajectory at Staff TW has improved noticeably over the eight years I've been here. But we started from behind. The gap closed from the company's side, which took eight years, and from my side, which took moving from engineering and leveraging the fact that I could read the codebase. Most writers don't have that option. That's not a ladder. That's a particular set of circumstances I can't fully claim credit for.

Tell me about the income variance. $156K and then $89K.

2024 was good. I had three anchor clients. FinStack, a B2B payments platform that had me on a retainer for $8,500 a month. A cloud storage company that hired me for a six-month API documentation project at $145 per hour. And a smaller fintech startup that called me for quarterly doc sprints. When all three were running at once, I was billing 40 hours a week at an effective blended rate of around $125 per hour. That's where $156K comes from.

Then FinStack was acquired in early 2025. Acquisitions are the enemy of TW retainers. The acquiring company had their own internal TW team. My retainer ended. The cloud storage project wrapped up in March as planned. The startup reduced their sprint frequency because they did a down round and cut contractor spend. My Q1 2025 billing was $12,400. My Q1 2024 billing was $42,000. That drop happened in three months and I had almost no advance warning.

I had savings. I had the bad quarter fund. I had a husband, Declan, who makes consistent money in commercial insurance and whose response to my income swings is approximately "OK, what do we do?" without drama. I spent Q1 and most of Q2 2025 doing intensive business development, which is a clinical name for cold outreach, referrals, and working my network. By Q3 I had two new anchor clients. But the 2025 total ended up at $89,000. That's not a bad year in absolute terms. It's a bad year compared to the year before.

What does business development look like for a technical writer?

Mostly relationships. The cold outreach converts poorly. I've sent maybe 200 cold emails over my freelance career and gotten six clients from them. The work that actually fills my calendar comes from referrals and the Write the Docs community. I've been active in the Slack and the annual conference for seven years. When someone in there asks "does anyone know a freelance TW who does API docs for fintech?" my name comes up, because I'm there and I've helped people and people remember that.

The second thing is staying in contact with past clients. My client Yusuf at the cloud storage company, when he landed at a new company 18 months after our project ended, he emailed me directly. Not through a job board. He emailed my personal address because he had a good experience and he knew what I could do. That kind of thing is the economic foundation of freelancing. You're not getting hired for your resume. You're getting hired because someone knows you did good work for someone else they trust. Building that record is slow and it doesn't show up in any metric except the one that matters, which is how fast your next project starts after your last one ends.

What's the real take-home after everything?

In the $156K year: I paid roughly $38,000 in self-employment and income tax. Health insurance was $14,400 for the year for Declan and me, because he's self-employed in insurance so we're both buying individual coverage. Retirement: I maxed out a Solo 401k at $23,000. After all of that, I had about $80,000 in actual usable income. Which is good. But $156K gross becoming $80K net is a different picture than the headline number. That's true for any self-employed person and I knew going in. But people hear "freelance TW making $156K" and they imagine that's spendable money. Not exactly.

The $89K year: taxes were lower, obviously. Same insurance cost. Retirement contribution dropped to $12,000 because I was more conservative. Usable income was about $42,000. That was tight. We didn't go on vacation that year. I was stressed in a way I'm not usually stressed. Declan was fine, but I didn't want to lean on his income the way you might in an emergency. This is supposed to be my career. Those nine months were a reminder that "freelance" and "stable" are not synonyms. I know this. I've always known this. Knowing it doesn't make Q1 2025 less of a gut punch.

What's yours?

How much you invent your own value in this market. I charge $145 per hour. Not everyone who does what I do charges $145. Some charge $80. Some charge $200. The difference is usually not primarily skill, at a certain level of competence. It's positioning, confidence, and who your referral network is. I know writers who are technically better than I am and charge less because they undersell themselves, or they don't have the client relationships, or they've been in markets where $80 felt like a lot and they never recalibrated. I know writers who charge $180 and produce work that's not better than mine by any honest measure, but they came up through a higher-prestige network and built confidence around a higher price point early.

That's uncomfortable to sit with. I want the market to be rational. I want the price to reflect the quality. It does, partly. But it also reflects who you know, what you've been told you're worth, and how much discomfort you have asking for more. My sister Constance negotiated her salary twice in the same calendar year at her marketing job. She has no particular anxiety about it. I remember the first time I raised my rate from $110 to $125, I agonized over it for two weeks. The client accepted it immediately. Two weeks of anxiety for a yes that took four seconds. I've gotten better. The jar helps. Having a bad quarter fund means I'm not negotiating from fear of losing a client. You can't put a number on what it means to negotiate without fear. Actually, you can. The number is probably $35 per hour.