Skip to content
Stack&Scale

Loading search…

Menu
Subscribe

Write for us

Write for Stack & Scale

You've solved hard problems in production. Explain them well, and we'll help you reach the developers who need them.

Pitch an articleHow it works

What you get

  • Real editing

    An editor works with you from outline to final draft, with a technical review of every code sample.

  • Your name on it

    A byline, an author page with your links, and every article you publish in one place.

  • Readers

    Each article goes out to newsletter subscribers and RSS readers, and is built to be found in search.

  • Your rights

    You keep the rights. Cross-post on your own blog with a canonical link back here.

What we publish

Tutorials, guides, deep dives, case studies, and comparisons across these topics.

  • Backend
  • Frontend
  • React
  • JavaScript
  • Java
  • AI & ML
  • DevOps

Open calls

Topics we're actively looking for writers on.

How it works

  1. Step 1

    Pitch

    Send a working title and a few sentences on what readers will learn.

  2. Step 2

    Outline

    We agree on the angle, the structure, and the code examples together.

  3. Step 3

    Draft

    You write in Markdown (MDX). Most drafts take two to four weeks.

  4. Step 4

    Review

    Editorial and technical review, usually one or two rounds.

  5. Step 5

    Publish

    The article ships with cover art and goes out to the newsletter.

Editorial standards

  • Original work grounded in real experience
  • Complete, runnable code with versions stated
  • Honest about trade-offs and failure modes
  • No AI-generated filler or marketing copy
  • No undisclosed affiliate links
  • Typically 1,500–3,000 words; depth matters more than length

Pitch an article

A good pitch is short: a working title, who it's for, and what readers will be able to do after reading it. An outline helps but isn't required.

We reply to every pitch within a week.

Fields marked with an asterisk are required.

For example: How we cut p99 latency by 60% with connection pooling
GitHub, portfolio, or previous writing
The problem, your approach, and 3–5 key takeaways. A rough outline is fine. At least 80 more characters.
Where you've used it in production, talks you've given, and so on.

We reply to every pitch within a week.