
I’d say the best way to write a writing sample for a job is to match the sample to the actual role you’re applying for—not just pick your best college essay. Recruiters want proof you can do the work, not just proof you can write. So start by reading the job description closely. If they ask for “clear, concise reports,” send a one-page executive summary. If they want “creative storytelling,” send a blog post or a case study. Always keep it under 500 words unless they specify otherwise. Hiring managers skim; they’ll judge your ability to organize thoughts within the first 30 seconds.
Here’s a simple framework I’ve seen work in practice:
| Step | What to do | Why it matters |
|---|---|---|
| 1 | Pick a real sample from a past project, internship, or even a volunteer role. | Authenticity beats fabrication. If you have no relevant experience, create a mock assignment based on the company’s industry. |
| 2 | Chop it down to one core idea. | A focused piece shows you can prioritize—a key skill in any role. |
| 3 | Add a short context note at the top (1–2 sentences explaining the original purpose and your role). | This helps the recruiter understand the scenario without guessing. |
| 4 | Check for formatting consistency—same font, same heading style, no typos. | Sloppy formatting signals lack of attention to detail. |
If you’re in a specialized field like technical writing or marketing copy, use industry-specific terminology correctly (e.g., “call-to-action” instead of “button”). For general roles, focus on clarity and structure. And please, never send a sample that’s older than two years unless it’s a standout piece—outdated references can hurt your credibility.

Honestly, I just write a short version of something I already did, then tweak it to fit the company’s voice. If the job is in social media, I’ll take a post I wrote that got good engagement and format it like a case study. I keep it to three paragraphs max. Recruiters don’t have time for novels. One thing I always do: run it through a grammar checker—even if you think it’s perfect, a second pass catches weird phrasing.

From my experience, the smartest move is to write a sample that solves a problem the company has. Look at their recent blog posts or press releases, spot a gap, and write a short piece addressing it. For example, if they’re hiring a content writer and they keep talking about remote work, draft a 300-word guide on remote team communication. It shows you’ve done your homework and you’re already thinking like an employee.

I think the key is structure over style. A lot of people try to be clever, but recruiters just want to see you can organize information. I always use a simple intro-body-conclusion format. If the job requires data analysis, I’ll include a small table (like the one above) to show I can present numbers clearly. Also, label the sample—put “Writing Sample: [Role]” in the file name so they don’t lose it.

What worked for me was keeping it personal but professional. I used a story from my own career—a time I had to explain a complex idea to a non-technical audience—and turned it into a 400-word narrative. Then I added a one-line “why this matters” at the end. Recruiters remember stories more than lists. Just make sure your story has a clear lesson tied to the job description. Oh, and always ask a friend to read it before you hit send. Fresh eyes catch tone issues.


