Quill
Quill
Subscribe
§ 01 · A reading list for engineering leadership

The essays your team should actually read.

A weekly long-form essay from one of forty-seven principal engineers, VPs of Engineering, and CTOs we've quietly built relationships with over the past four years. Commissioned, edited, and fact-checked. One concrete idea per piece, ready to be forwarded to your staff list on a Tuesday morning.

Subscribed teams
1,408
42 of the YC top 100
Avg. seats / team
24
Forwarded internally x3.4
Featured authors
47
Industry voices, on retainer
Essays / year
78
Avg. 3,200 words · 11 min
Forwarded around the staff channels at
Linnea FORECAST Glide VANTAGE Mercury brightwave Halcyon Northwind Quartermast atrium Linnea FORECAST Glide VANTAGE Mercury brightwave Halcyon Northwind Quartermast atrium
§ 02 · From the editors
“If a single essay changes how your team works for a quarter, that's better than any conference.
— Annika Voss, editor
Founding letter · Volume I · September 2022
§ 03 · What lands in your team's inbox

One essay. One question. Tuesday morning.

Each essay opens with a question we've heard from at least three engineering leaders that month — "Should staff engineers be on-call?", "How do you measure platform team success?", "When do you fire a tech lead?" — and answers it with the practiced honesty of someone who's done the work. Three thousand words. Eleven minutes. Pre-circulated to your channels with a one-line summary so people actually open it.

Pieces are paid $0.78 per word on acceptance. We've sent twelve $400 kill-fees in three years — the standard is honest, the bar is high.

Commission essays for your team's actual problems.

On the Org plan, you submit two questions a quarter and we match each one with an author who's solved that problem in production. The author writes the essay, our editors shape it, and the piece is delivered with your name redacted. Twenty-eight of our 1,408 teams use this; the renewal rate sits at 96%.

Pieces remain Quill's IP and run in the public archive six months later — your team gets it first, the industry gets it eventually.

§ 04 · The roster

Forty-seven authors. A few of them.

Full masthead →

Priya Anand

№ 01
Staff Engineer · Linnea

Writes on incident review, observability culture, and what it actually takes to keep a senior IC at a Series A.

Marcus Tobin

№ 02
VP Engineering · Forecast

Twelve years scaling teams from 6 to 188. Writes on staff promotion, hiring loops, and the cost of org charts.

Hana Suzuki

№ 03
ML Lead · Glide

Built and shipped a 28-person ML org without a manager-track. Writes on flat structure, evaluation, and trust.

Yusuf Abara

№ 04
CTO · Mercury

Co-founder of a payments company at 188 engineers. Writes on what to delegate, when, and to whom.

Ines Calderón

№ 05
Head of Eng · Brightwave

Eight years on platform & infra. Writes on developer experience, internal tools, and platform-as-product.

Tomás Reyes

№ 06
Principal Engineer · Halcyon

Sixteen years as IC, by choice. Writes on the principal-engineer ladder, technical leadership, and saying "no."

§ 05 · Editorial methodology

How an essay reaches your team's inbox.

Week 01 · Mon

Commission & outline

An editor and an author sit on a 45-minute call. Out of it comes a 400-word outline, a thesis sentence, and the four objections an intelligent reader will raise.

Week 02 · Fri

First draft & structural edit

Author submits a draft. Editor returns it with structural marginalia within 48 hours. We average 4.2 rounds before line-editing.

Week 03 · Wed

Line edit & fact-check

Every claim about a company, a salary, a system, or a person is verified against at least one primary source. Numbers ending in ",000" are rejected on principle.

Week 04 · Tue · 06:00

Delivered to your team

Email to every seat at 06:00 local. One-line summary on the corresponding Slack/Linear channel via integration. Archived to your private Quill workspace forever.

§ 06 · Two team plans

Team. Or Org.

Per-seat pricing that drops as your team grows. Both plans include the full archive, Slack & Linear integrations, and the public-facing essay digest.

Team

§ A · 5+ seats
$14 / seat / month

For a single engineering team. One essay a week, the full archive, integrations included.

  • §One essay every Tuesday, 06:00 local
  • §Full archive (188 essays since Vol. I)
  • §Slack & Linear integrations
  • §Internal forwarding tracker
Subscribe your team
Custom essays

Org

§ B · 50+ seats
$9 / seat / month

When the essay program runs across multiple teams. Adds two custom-commissioned essays per quarter.

  • §Everything in Team
  • §Two custom essays / quarter, matched author
  • §Private workspace, internal index
  • §Quarterly 60-min editor consultation
Speak with an editor
§ 07 · From engineering leaders
“We changed our staff-engineer rubric after one essay. It paid for the whole year in twelve days.”
— Yusuf Abara · CTO · Mercury
“I forward 6 of every 12 to my entire org. The hit-rate is unreasonably high.
— Ines Calderón · Head of Eng · Brightwave
“The custom essay program is our best-kept secret. We've shipped two re-orgs off the back of them.”
— Marcus Tobin · VP Eng · Forecast
“The only newsletter my staff engineers actually read without me asking.”
— Priya Anand · Staff Engineer · Linnea
§ 08 · Sensible questions

Before you bring it to your director.

§ FAQ.01

How do you vet authors? What's stopping a vendor-funded essay from sneaking in?

+

Authors sign a conflict-of-interest disclosure at commission and a fact-checker re-verifies it at line-edit. No essay is funded, sponsored, or paid-for by any external party — full stop. We've turned away four vendor sponsorship offers in the past 14 months; none of our authors are paid more than $0.78 / word, and we publish their full disclosure with each piece.

§ FAQ.02

Will essays show up on the public internet, or are they kept behind a team paywall?

+

Your team reads every essay six months before the public sees it. After 180 days, the piece moves to the public archive with the author's permission. Custom essays commissioned via the Org plan stay private for 12 months.

§ FAQ.03

Do you integrate with our SSO, and what's the SCIM provisioning story?

+

SAML/SSO on Team and Org. SCIM 2.0 is included on Org without additional fees — we don't believe in the "SSO tax." We support Okta, Google Workspace, Azure AD, and JumpCloud. Setup averages 38 minutes.

§ FAQ.04

Can we export the archive — a piece, or all of it — to ingest into our internal wiki?

+

Yes. Markdown, HTML, or EPUB. We expose a small REST surface to feed Notion, Confluence, or Linear documents — about 28 teams pipe new essays into a "reading" project automatically. Custom essays from the Org plan are licensed for indefinite internal use.

§ FAQ.05

What's the renewal track record, and what happens if half my team doesn't open the essays?

+

Renewal sits at 92% across all 1,408 teams. If open rate on your seat falls below 40% in any given quarter, we'll pro-rate a refund — no calls, no clawback negotiation. We measured this in 2024 and the cost to us was $1,840 across 1,108 then-active teams.

§ 09 · The standing invitation

Bring one essay to your next staff meeting. See what happens.

28-day trial for five seats, no card. Cancel before day 28 and we'll send your team a print copy of Volume I, on us — 312 copies remain.