MC-Guide
Content Writing
Website 08: arstechnica.com
How Can You Earn Money Writing For “arstechnica.com” Website
This guide shows you, step by step, how a beginner can learn to pitch and sell stories to arstechnica.com.
You will learn what arstechnica.com wants, how to test your idea, how to write a pitch, and how payment roughly works. You can use this like a small SOP.
Guide: How to Get Paid to Write for Ars Technica (Step by Step)
This guide shows you, in simple steps, how you can plan, research, and pitch articles to Ars Technica — even if you are a beginner writer but already love technology, science, games, and policy.
You will learn what Ars Technica publishes, how to choose the right story idea, how to prepare a strong outline or sample, how payment roughly works, and how to use an Ars byline to grow your writing career. Sentences are simple. You can treat this like a small pitch SOP.
Section 1 · Understand the publication
What Ars Technica actually wants from writers
Ars Technica is a long-running technology and science site that publishes news, reviews, guides, and deep analysis on topics such as computer hardware and software, science, tech policy, security, and video games.
They are known for long, detailed stories written for smart, tech-literate readers, not quick clickbait. Many articles live in sections like Information Technology, Science, Gaming, Gadgets, Tech Policy, and Reviews.
Most Ars pieces look like one (or a mix) of these:
- News + analysis on big tech, science, or gaming stories (mergers, AI breakthroughs, big data leaks, space missions).
- Deep explainers that unpack a complex topic like encryption, net neutrality, quantum physics, or chip design.
- Reviews of hardware, gadgets, and software with careful benchmarks and pros/cons.
- Science long-reads that show how research affects everyday life, policy, or industry.
- Policy & law coverage (antitrust, privacy, copyright, security, regulation).
Ask: “Does my idea give tech-savvy readers new information, context, or insight they cannot get from quick news sites?”
The typical Ars reader is:
- A developer, sysadmin, scientist, engineer, researcher, policy watcher, or very serious hobbyist.
- Comfortable with jargon when necessary, but still wants clear, honest explanations.
- Busy, and looking for signal, not noise — strong reporting instead of hype.
Your piece should feel like a well-researched magazine article, not a shallow guest post.
| Article type | Ars section | Depth | Best use |
|---|---|---|---|
| News + analysis | IT, Policy, Security, Business | Timely story + context + quotes | Breaking news with clear impact on tech, users, or companies |
| Deep science feature | Science | 2,000–3,000+ words, multiple sources | Showing how research works and why it matters |
| Gadget / hardware review | Gadgets, Reviews | Benchmarks, tests, long-term use notes | Helping readers decide what to buy or avoid |
| Gaming & culture story | Gaming | Interviews, history, business or community angle | Explaining trends, culture shifts, or game-industry news |
Section 2 · Fit your idea
Is your idea an Ars-shaped idea?
Do not start with “I want to write about AI” or “I want to review a phone.” Start with a real story, conflict, or decision that affects readers: a new law, a broken product, a risky corporate decision, a research mystery, a game-industry problem.
Is there a clear news hook or strong question?
Ask: “Why should an Ars reader care today?” Good hooks include: a new study, a product launch, a major bug, a court case, a leaked document, or a clear gap in coverage. If there is no timing or question, it may be too soft.
Can you bring something new?
Search Ars for your topic first. Your idea needs a fresh angle:
- A voice from a community that has not been heard.
- Data or documents that have not been analysed this way.
- A deeper technical explanation than general-news outlets offer.
If your pitch could run on any random tech blog, sharpen it until it feels “very Ars.”
Do you have or can you get real reporting?
Stronger Ars-style ideas usually include:
- Interviews with experts, developers, researchers, or affected users.
- Public documents, filings, or datasets you can read and explain.
- Hands-on testing, benchmarks, or real-world experiments.
If you only have your opinion, build reporting first (emails, calls, tests). Take notes. That becomes your article’s backbone.
Section 3 · Prepare yourself
Build a small base before pitching Ars Technica
Ars Technica pays well and expects professional work. As a beginner you can still get there — but it helps a lot if you build a small ladder of practice first.
- Write tech or science posts on your own blog or on platforms like Medium and Dev.to.
- For science/long-form, look at outlets like Longreads or niche blogs and see their structure.
- Make every sample article clear, sourced, and accurate with links to studies, docs, and official pages.
These samples prove you can finish serious pieces and respect facts — exactly what Ars editors want to see.
- Pick one beat: for example science, gadgets, tech policy, or gaming.
- Read 5–10 stories only from that section. Note word count, number of sources, how they use charts or photos.
- Check bylines and Google those writers; see how they describe themselves on personal sites or Twitter/X.
Your future pitch will feel more “right” if it matches the tone and depth of that section.
| Step | Where | Main goal |
|---|---|---|
| Start | Your blog / Medium / Dev.to | Practice clear explanations and basic reporting |
| Middle | Smaller paying tech & science sites | Learn to work with editors and meet deadlines |
| Higher | Ars Technica & big magazines | Publish flagship pieces that boost your career and rates |
Section 4 · Practical workflow
Step-by-step Ars Technica pitch plan (for beginners)
Now we connect everything into one simple workflow. You can reuse this same workflow for other tech and science magazines too. Think of it as a compact Ars Technica pitch SOP.
Map your story to one Ars section
Decide first: is your idea mainly news, analysis, review, or feature? Then match it to a section such as:
- Information Technology – enterprise, cloud, operating systems, development.
- Science – research, climate, health, astronomy, physics.
- Gadgets / Reviews – phones, laptops, devices.
- Gaming – business, culture, history, streaming.
- Tech Policy – law, regulation, antitrust, privacy.
A clear fit makes it easier for the right editor to imagine your piece on the site.
Shape a one-paragraph pitch + bullet outline
In a doc, write:
- Working headline: short, clear, and specific.
- 1–3 sentence summary: what happened / what you will show, and why it matters to Ars readers.
- Evidence: who you will interview, which docs / studies you will use, what tests you will run.
- Outline: 4–6 main sections in bullet points.
Keep this tight. Editors like pitches that respect their time but still prove you did homework.
Collect links that prove you can do the work
Before writing your email or form:
- Pick 2–3 of your best tech/science/gaming articles (even from your own blog).
- Grab links to your GitHub, portfolio, or research page if relevant.
- Note any past reporting experience, even student journalism or volunteer work.
You will paste these in your pitch so the editor can see your voice and skills quickly.
Send your pitch through the right channel
Ars does not have a big “write for us” banner, but you can still reach them. Practical options include:
- Their general contact page (choose the category closest to “story tip” or “editorial”).
- The confidential news tips page for sensitive leads (follow instructions there).
- Finding section editors’ names on recent articles and respectfully pitching via professional channels (LinkedIn, verified email if available, or their stated contact preference).
Keep your message short and professional: 1–2 paragraphs plus links and outline.
Use a simple email pitch template
Adapt this to your topic:
- Subject: Pitch – [beat] / [short headline]
- Line 1: Who you are (1–2 lines, including tech background).
- Line 2–4: What the story is, why it matters now, and which Ars section it fits.
- Next: 4–6 bullet outline points + what sources you will speak to or docs you will use.
- End: Links to 2–3 relevant clips + thanks.
Do not attach a full draft unless an editor asks. Lead with the idea and plan.
Follow up politely, then reuse the idea if needed
If you do not hear back after 10–14 days, send a short follow-up: one line to check in, and a deadline after which you will offer the idea elsewhere. If they pass or do not reply, you can adapt the story for another outlet.
Section 5 · Money side
How you actually earn money with Ars Technica
Exact pay is decided with editors, and can change. Public reports and round-ups say Ars Technica pays up to around $0.21 per word for freelance work, especially for strong features and in-depth pieces. Some stories may pay less, some more, depending on length and complexity.
- A one-time payment agreed per assignment (often per-word or flat fee).
- Professional editing and fact-checking that makes your work stronger.
- Placement on a high-authority site read by companies, recruiters, and fans.
- A byline you can show to future clients, editors, and employers.
So one good story is both immediate money and a long-term career signal.
- Track hours: research, interviews, transcription, writing, revisions.
- Divide the fee by total hours. That is your effective hourly rate.
- Use 1–3 strong Ars pieces as your “hero clips” when pitching other outlets that pay more.
- Leverage your byline to sell consulting, courses, or newsletter subscriptions later.
Over months, these clips help you move from beginner rates to higher-paying work.
| Type of piece | Rough pay picture* | Strategy for you |
|---|---|---|
| Short news + analysis (1,000–1,400 words) | Lower–mid range on per-word rate | Good way to start if you can move fast and verify facts |
| Deep feature (2,000–3,000+ words) | Upper range; more work but higher total | Make it a flagship piece with original reporting and strong narrative |
| Series or follow-ups | Negotiated per story | Turn one area of expertise (e.g. security, AI, space) into repeat work |
Section 6 · Ethics & AI
Very important: honesty, AI use, and trustworthy reporting
Ars Technica has built trust over many years. Readers expect real sources, accurate numbers, and working explanations. AI tools are normal now, but your name and Ars’ reputation are still on the story.
- Do not send AI-generated drafts without heavy editing and fact-checking.
- Do not copy-paste from other outlets without permission and clear attribution.
- Do not invent interviews, quotes, measurements, or lab results.
- Do not hide conflicts of interest (e.g. if you work for a company you write about).
Editors quickly notice generic or suspicious work. It harms your chance of future assignments.
- Use AI to brainstorm angles or questions to ask sources, then refine yourself.
- Use it for grammar and clarity checks, especially if English is not your first language.
- Use it to summarise long documents for your notes, then read key parts yourself.
- Generate sample code or diagrams only as a starting point, and test everything personally.
Final rule: you are responsible for correctness and honesty. Treat AI as a helper, not a ghost-writer.
Section 7 · Micro-SOP
Final checklist before you pitch Ars Technica
Use this checklist each time you pitch Ars Technica (or a similar publication). It keeps you organised and more confident.
Section 8 · Quick answers
FAQ: Beginner questions about writing for Ars Technica
- Ars Technica – official site (browse sections and recent stories)
- Have a confidential news tip? – Ars tips page
- Ars Technica is accepting submissions – CreativeWritingNews overview
- 10 Magazines & Websites Paying for Writing on Technology – Freedom With Writing
- 27 Magazines That Accept Submissions from Freelancers – Knowadays (tech section includes Ars)
- Ars Technica – background & history (Wikipedia)