Most of a writer's day isn't writing. It's reading briefs, chasing sources, arguing gently with an editor and fixing the same paragraph again. This page follows an in-house writer on a content team, the most common version of the job you'll see posted.
Writer is a wide title. The same word sits on postings for a blog writer at a software company, a staff writer at a trade magazine, a proposal writer at a consulting firm and a writer on a brand team who owns product pages and emails. The tools change a little from place to place. The shape of the day changes less than you'd expect. You get a brief, you find out what's true, you draft, someone pushes back, you revise, and the piece goes live with your name on it or without it. The day below follows a writer on an in-house content team, because that's where a lot of the openings are. If you land at an agency, swap the single editor for a handful of client contacts and add more meetings.
You open Slack and the content calendar in Asana before anything else. Today's main job is a long explainer for the product blog, due to your editor by end of day. The brief from the marketing lead names the reader, the search term the team wants to rank for and the one point the piece has to land. You read it twice and write down what's missing, which is usually the actual angle.
You get on a video call with a product manager who knows the topic far better than you do. Your job is to ask the plain questions a reader would ask and to get the real example, not the pitch-deck version. You record it, pull a transcript into Google Docs and highlight the few lines worth quoting. Everything else is background.
This is the block you protect. Notifications off, outline on one side, transcript on the other. You write fast and badly on purpose, then go back and cut. By mid-afternoon you have a full draft that's too long, with a weak opening and a strong middle. That's normal, and you know which parts to fix.
Here's where the plan breaks. A comment lands from the legal reviewer on a different piece you filed last week: a couple of claims need softening and a customer quote needs sign-off before it can run. That post is scheduled for tomorrow morning. You drop the explainer, email the customer's contact, rewrite the claims so they're still useful, and tell your editor the explainer will slip a day. Nobody's happy. It's still the right call.
You close out the day in the CMS, usually WordPress or Webflow. You add internal links, write the meta description, check headings against the brief and paste your notes for the editor at the top of the doc. Then you update Asana so tomorrow's version of you knows where things stand.
Feedback is the hard part, and not because editors are cruel. It's that feedback comes from people who don't write for a living. A product manager wants every feature mentioned. A sales lead wants the piece to sound like a pitch. You'll learn to take each note seriously, work out what's really bothering the person and fix that, which is often not what they asked for. The other grind is volume. A content team runs on a calendar, and the calendar doesn't care that a piece needed another week. Writers who last get good at shipping solid work on time and saving their perfectionism for the few pieces that deserve it. If you need every piece to be your best, this will hurt.
Reporters and staff writers move to in-house teams all the time. You already know how to interview, hit a deadline and take an edit. The adjustment is learning that the reader is often a buyer and that search traffic matters. Hiring managers treat newsroom experience as a strong signal.
Plenty of writers start in support, sales, teaching or a technical role and become the person everyone asks to write things. Knowing an industry from the inside is worth a lot. If you can write clearly about accounting software or medical billing, you'll beat a stronger stylist who can't.
Freelancing builds the portfolio fast, and a portfolio matters more than a degree for this job. Pick a subject and write real pieces for real clients, even small ones. A few published samples on one topic will do more for you than a pile of scattered ones.
10% of openings are fully remote.
$68,340 – $102,000
Typical range in the 17 of the newest 60 postings that list pay.
No. Many postings list one, but hiring managers mostly read your samples. A degree in the subject you'd write about, like finance or nursing, can help you more than an English degree. What you can't skip is a portfolio of published work that matches the kind of writing the job asks for.
Pick your strongest pieces and put the most relevant one first. Link to the live versions where you can, and add a line on what you did: the brief, your research, the result if you know it. Keep it to a handful. A reviewer will read the top couple, so make those count.
A copywriter writes to get someone to act: ads, landing pages, email subject lines, short and sharp. A writer on a content team usually writes longer pieces that teach or explain, like articles, guides and case studies. Plenty of people do both, and small teams often hire one person for everything. Read the posting's samples list, not just the title, to see which job it really is.
HeroApply applies to them for you, so you can keep doing the job you have.