Who Reads AIpresso? Roles in a Selected Cohort
Who reads AIpresso? In a selected group of 457 AIpresso recent-clicker records matched to a Dupple quiz answer, 62 selected marketing and 59 selected engineering. The 5 November 2026 snapshot describes newer subscribers in a particular engagement segment, not AIpresso's entire readership or all AI professionals.
Published and updated 5 November 2026. Extracted 5 November 2026.
Dupple publishes AIpresso and offers sponsorships. Our data is drawn from Dupple's segment cache and quiz records, not an independently audited audience survey. Role choices are self-reported and may no longer reflect someone's work.
Roles in the matched records
The AIpresso role CSV starts with records last seen in a configured AIpresso engagement segment from 29 October through 4 November 2026 UTC. Of 512 distinct resolved email addresses, 457 matched a quiz response; 55 did not. Unresolved segment records are not included in the 512. Percentages in this table use the 457 matches, not all AIpresso subscribers.
| Self-reported quiz role | Matched respondents | Share of 457 matches |
|---|---|---|
| Other, selected in the quiz | 78 | 17.1% |
| Marketing | 62 | 13.6% |
| Engineering | 59 | 12.9% |
| Leadership | 51 | 11.2% |
| Sales | 35 | 7.7% |
| Operations | 31 | 6.8% |
| All remaining roles and missing role | 141 | 30.9% |
The last row combines role groups with fewer than 30 matches, including missing values. It is separate from the quiz's own other option. Because each displayed group depends on at least 30 matched records, the table avoids presenting small groups as precise standalone audience segments. Rounding to one decimal place can affect the displayed total. The raw labels describe a quiz choice, not a verified job title or a record of tool purchases.
What this cohort actually contains
The source segment is configured for active AIpresso subscribers who signed up in the last 30 days and had at least one verified click in that period. A separate system stores when it last saw each segment membership and attempts to resolve the subscription identifier to an email address. This extraction keeps resolved addresses last seen during the seven-day window and deduplicates them by normalized address within AIpresso.
The segment cache is not a live subscription ledger. Someone seen during the window might no longer qualify when the file is read. A partial or failed synchronization may also change which entries appear. Unresolved members are excluded from the starting count rather than assigned a role. The selected cohort is skewed toward recent subscribers who clicked and cannot represent long-standing subscribers, non-clickers or the full mailing list.
To find roles, the exporter matches a resolved address to the most recently created Dupple quiz record available at extraction; it uses a stable record identifier to break ties. Quiz answers can predate the engagement window and can come from another Dupple flow. The match does not establish that a particular quiz was filled out through AIpresso. The downloadable method file shows the selection and grouping without including individual records.
What the numbers can and cannot say
The matched sample contains 62 people who selected marketing, or 13.6% of the 457. It does not say that 13.6% of every AIpresso subscriber works in marketing. The 55 unmatched addresses may have different roles, and we do not know the role distribution of people whose segment emails were unresolved or whose membership fell outside the extract. Applying a selected-cohort percentage to the newsletter's total subscriber count would create unsupported precision.
The engineering group has 59 matches, close to the 62 marketing matches. This small difference does not establish a stable ranking across time or show that these people use a particular AI model. Nor does the leadership label prove a purchasing role. A respondent can do several jobs but choose one category; the answer may have become outdated since it was recorded.
The aggregate also cannot tell us which subscribers saw an ad, clicked a sponsor's link or bought a product. The segment requires a verified click under its configuration, but this export does not independently recheck each event or attribute it to an advertiser. A verified click in a segment is not evidence of a campaign conversion.
Using the snapshot in a proposal
For an AI product, the spread of answers suggests asking how a proposal will reach its intended user and what a reader should do after the click. A technical product might need a destination with integration details; a workflow product might need a concrete example of the task it helps with. The table is a prompt for those questions, not a guarantee that either group will engage with a particular offer.
The AIpresso advertising page explains the publication and current formats. For a message embedded in an issue, read the Primary Ad page. A Dedicated Send is a separate email and should be assessed on its own available audience and schedule. Ask the seller which issue, creative, link and reporting are included before approving a proposal.
The newsletter buying guide lists practical questions for a placement. The sponsorship ROI guide explains why campaign clicks and downstream outcomes need separate definitions. If a buyer wants post-signup targeting, the lead generation product is a different surface; this AIpresso cohort is not a count of its eligible impressions.
Comparing this with the AI tools data
Dupple's AI tools snapshot begins with people who selected Technology in a network-wide quiz and answered an AI tools question. The AIpresso role file starts with a selected publication engagement cache and then finds quiz roles. These are different entry rules, windows and denominators. Neither file shows the intersection, so the AI tool percentages cannot be applied to the 457 people in this table.
The data and methods hub includes other network-level aggregates. The Techpresso selected cohort uses the same general matching method for another publication, but the number of matches, missing addresses and selection may differ. An address can be present in more than one publication. The tables do not measure distinct people across both newsletters or establish which one caused a click.
External publishers describe their own audiences using different methods. daily.dev's audience page, checked 5 November 2026, covers its own developer community. It is not a source for this AIpresso role table. When comparing audience claims, request the population, question wording, sample date and whether the figures come from declared answers, analytics or estimates.
A repeatable but limited export
The CSV groups by the selected role after joining the two systems. Each matched address contributes once, and a latest quiz record supplies the role. The extraction runs against a read-only database snapshot and returns aggregate counts, not emails or individual subscription histories. Rows under the disclosure threshold are combined. The file names the publication, extraction date, number of resolved addresses, matched count and unmatched count.
If the snapshot is refreshed, keep the selection window and the matching rule alongside the new values. An increase in the number of matches might come from more segment members, more resolved addresses or more quiz coverage. Changes in a role's percentage can also come from the denominator. Without comparable definitions and a repeated series, a single week cannot establish an audience trend.
The country snapshot describes operational country values from quiz records using a different population. It does not establish the geography of this AIpresso cohort. No age, seniority, employer, AI tool usage or country cross-tab is present in this file. Ask for substantiated evidence before using any of those characteristics to describe the group.
A role label also does not establish a person's reason for subscribing. A marketer may follow AI news for research, an engineer may be exploring a personal project and a leader may have no near-term purchasing plan. The export does not ask those questions. Any campaign hypothesis about motivation should be tested with the actual audience and a clearly defined outcome, rather than presented as a finding from this file.
FAQ
How many selected AIpresso addresses matched a quiz?
The snapshot matched 457 of 512 resolved addresses last seen in the specified segment window. Another 55 did not match; unresolved segment records are outside that starting count.
Are these percentages for every AIpresso subscriber?
No. They describe a selected recent-clicker segment with a resolved address and matching quiz record. They are not a representative survey of the full list.
How many selected marketing or engineering?
Among the 457 matches, 62 selected marketing and 59 selected engineering. Those are self-reported quiz roles, not independently verified titles.
Does this show which AI tools the cohort uses?
No. The published role table does not join this specific cohort to the AI tools answers. Network-wide AI tool figures describe a different population.
Can it predict sponsorship performance?
No. The file contains role counts rather than advertiser-level views, clicks, leads or sales. Use reporting for the proposed campaign to evaluate its outcome.