Developer Audience Sponsorships, Bought and Measured

Hacker News does not sell advertising. Anyone offering you a Hacker News placement is selling something adjacent to it, usually a newsletter that aggregates the front page, and the honest version of this engagement starts by saying so. What is buyable around this audience is a short list of sponsorships: developer newsletters, a handful of podcasts, community properties, and on Stack Overflow the Collectives programme, where a company sponsors tags it can credibly answer questions in. We build that list from your own referral logs rather than from a rate card, and no placement gets a third insertion until two have been measured. Why we do this work at all: We sell to ecommerce operators, and the vendors selling into the same operators are increasingly engineering-audience companies: headless storefronts, subscription billing, payments, fulfilment APIs. They kept asking who buys their media. So this is the one part of the practice aimed at a technical reader, run by the same people, under the same rule that copy has to survive a comment section. Selection: We start with what already sends you traffic and signups, pulled from analytics referrer data and your self-reported attribution field. That list is usually more interesting than the media kits. Each candidate is then priced against a target cost per qualified signup that you set, not against an impression estimate, and we walk away from any property that will not sell a single test insertion. Copy: A sponsorship read for this audience is a technical note. A number, a constraint you actually hit, a link to something inspectable: documentation, a benchmark, a repository. No superlatives, no founder story, none of the words this reader has already seen in every other slot that week. If your product cannot be described honestly in four sentences to somebody who will check, the problem sits upstream of the media buy and we will say so before invoicing. Measurement, since none of this carries a pixel: Every placement gets its own landing path and short link, a self-reported attribution field on signup, and where relevant a code. We track weekly signup cohorts against insertion dates rather than pretending to click-level attribution. The renewal decision is made on two insertions of data against a cost per qualified signup agreed in advance, and we bring you the placements that failed as plainly as the ones that worked. Stack Overflow specifically: Collectives sponsorship is a staffing commitment, not a media line. It means your engineers answering questions under their own names, on a schedule, indefinitely. If nobody on your side has that time budgeted, we say no to the buy rather than sell you a logo on a tag page that decays into evidence you abandoned it. What we refuse: Seeded Show HN posts, coordinated voting, comments placed by anyone who is not who they say they are, and any arrangement where a paid placement is presented as editorial. With this audience the discovery of that is not a risk to be managed; it is the most expensive thing that can happen to a technical brand, and it is permanent. Not included: Writing your documentation, producing your benchmark, engineering time, conference sponsorship, and public relations. We buy and measure media and we write the copy that runs in it. Who this is not for: Companies without a working self-serve signup or trial, since the measurement approach depends on an action we can count. And anyone who needs reach numbers for a board deck. This channel produces a small number of well-qualified people and a large number of readers who now know you exist, and only the first half is countable.