Who Reads Devshot? A Selected Subscriber Sample

Who reads Devshot? In a selected recent-clicker cohort, 256 resolved Devshot addresses matched a Dupple quiz response; 43 of those respondents selected engineering. This sample, extracted on 5 November 2026, is not a representative survey of the full Devshot list and does not establish anyone's current job title.

Published and updated 5 November 2026. Data extracted 5 November 2026.

Dupple publishes Devshot and sells newsletter sponsorships. Our data combines its own engagement cache with self-reported quiz answers. The records have not been independently audited, and a selected role is not proof of a person's employer, programming skills or buying authority.

What the selected answers show

The Devshot role CSV contains aggregate answers for the subset that could be matched. The starting group consists of resolved addresses last seen in the configured Devshot recent-clicker segment between 29 October and 4 November 2026 UTC. It includes 296 addresses, 256 of which match a quiz response. The other 40 do not match and have no role assigned here.

Individual groups with fewer than 30 matched respondents are combined in the last row. That row includes missing values and is not the same as the quiz's own other choice. Percentages are rounded to one decimal place. The table does not disclose individual addresses or show an advertiser's results. The combined group is large, so the table cannot determine the prevalence of its individual roles.

Which subscribers enter the sample?

The segment feeding the cache is configured for active Devshot subscribers who joined within the last 30 days and recorded at least one verified click within 30 days. The email-sequence system periodically stores the subscription identifiers it sees and resolves some to email addresses. This export retains resolved addresses whose membership was last seen in the stated seven-day window, then counts each normalized address once for Devshot.

A membership cache is not a point-in-time audit of the newsletter. An entry seen during the window could have left the segment by extraction time; a partial synchronization could omit some members. Records with unresolved addresses are excluded before the 296 are counted. We cannot infer their roles or assume that unresolved people resemble those with a match.

The exporter matches each retained address to the latest available quiz record in Dupple's database, choosing a stable record identifier if creation times tie. It does not require that the quiz was completed during the segment window or through Devshot. Someone could have completed it through another Dupple flow, used a different address, or changed jobs afterward. The read-only aggregation method documents the query and suppresses individual identifiers from its output.

Reading the engineering figure

The 43 engineering selections are 16.8% of the 256 matched quiz records. The denominator is not the number of Devshot subscribers. It leaves out 40 resolved addresses without a quiz match, all unresolved segment memberships, subscribers outside this recent-clicker segment and anyone who receives Devshot through a different address. Multiplying 16.8% by the whole list size would imply a precision this selection cannot support.

Engineering is one quiz role choice, not a measure of a person's seniority, programming language, team, employer or use of a specific developer product. A reader can work across product and engineering but choose only one category. Conversely, a person who selected marketing or other could also use technical tools. This file does not ask enough to allocate readers to individual developer specialties.

A verified click is part of the configured segment definition, but the export does not independently inspect each click or say it was on an advertisement. These counts are not impressions, sponsor clicks, qualified leads or purchases. A person who appears here might not have received a specific issue. To evaluate a campaign, use its own reporting window and definitions.

Questions for a developer-tool campaign

Start with the task the product solves and the action a reader can take. An advertiser promoting an API may want a destination that makes setup and documentation easy to find. A security tool may need a clear explanation of the problem it addresses. Those are campaign-design ideas; this dataset does not establish which message works best or whether the selected engineering respondents are the intended users.

The Devshot advertising page describes the newsletter and placement options. A Primary Ad appears within an issue, while a Dedicated Send is a separate sponsored email. Ask which product is being proposed, which date and creative are included, how sponsorship is disclosed and what the report measures. Availability and eligibility need to be confirmed for the actual proposal.

The Primary Ad guide explains the in-issue format. The newsletter buying guide offers questions to compare options, and the ROI guide discusses tracking beyond a click. Dupple's lead generation page covers a different post-signup surface; the Devshot role sample is not a count of leads that product can deliver.

Why other data pages have different totals

The data hub publishes network-wide quiz and offer aggregates using their own windows and populations. Its quiz respondents are not restricted to recently clicking Devshot subscribers. The Techpresso selected cohort also uses an engagement cache, but its resolved and matched counts differ. A person may subscribe to both publications, so the samples cannot be added to count distinct people.

Similarly, the AIpresso cohort reflects another newsletter's selected segment. None of these tables measures how many Devshot readers use a particular AI model. The AI tools snapshot begins with a different network-wide quiz population and has no published intersection with these 256 matches.

The country mix is another quiz snapshot and is not Devshot-specific. It cannot be combined with the role shares to estimate how many Devshot engineers live in a country. Its stored country values are not verified residence. Ask for campaign-specific data if geography is necessary to a buying decision.

daily.dev's audience page, checked 5 November 2026, describes a separate developer audience. The provider's page does not establish the Devshot figures here. Audience comparisons need comparable populations, dates and methods; a self-reported role among recent clickers and an estimate for an entire network answer different questions.

Keeping the sample in context

There are relatively few matched records in this extract, and more than half fall in the grouped remainder. The seven-day window is a period in which memberships were seen, not a controlled experiment. Segment synchronization, address resolution and quiz participation introduce selection effects. Changes in any of them can change both the count and the mix even if the broader newsletter audience is stable.

A repeat extraction should retain the observation window, the number of resolved addresses, the number without quiz matches and the grouping threshold. A percentage can fall because another group grew, even when its own count stayed the same. The snapshot does not provide uncertainty intervals and should not be used to claim a trend without comparable observations over time.

The file cannot establish whether the latest quiz record belongs to a current employee at an employer, whether a reader opened or read a particular issue, or whether a sponsor influenced a buying decision. Quiz choices can be inaccurate or stale. Ask for evidence tied to the publication and outcome of interest rather than treating these role categories as individual profiles.

When comparing periods, retain the count as well as the share. A small sample can move noticeably when a few records are added or removed, and the grouped remainder masks differences among its component roles. This table is most useful as a documented view of one selection process at one extraction date, alongside the publication's current media kit and the terms of a real campaign.

FAQ

How many Devshot records were matched?

Of 296 resolved addresses last seen in the selected segment window, 256 matched a Dupple quiz response and 40 did not. Unresolved segment memberships are outside the starting count.

How many matched respondents chose engineering?

Forty-three of 256 matched records selected engineering, or 16.8%. This is a selected sample, not a percentage of the full Devshot subscriber list.

Why are most other roles grouped together?

Role groups with fewer than 30 matches, including missing answers, are combined. The quiz's own other response remains a separate category.

Does this identify programming languages or employer sizes?

No. The published aggregate contains role choices only. It does not supply language, employer, company size or specialty cross-tabs.

Does a verified click mean a sponsor conversion?

No. The segment is configured around verified clicks, but this export does not attribute a click to a sponsor or measure leads and sales.