The Product Engineer Subscribe

Field Notes · Act 2 — Prove · 04 of 9

Why Product Engineering, Why Now?

Adilson Chicoria

Published: Field NotesResearchAI

Observe

Market signals, hiring threads & job data
Evidence note

This note separates three kinds of material. The first is public sources: a financial chronology, one company’s announcement, two community threads and published essays. The second is the project’s own counts: Hacker News “Who is hiring?” posts from 2012 to 2026, 77 job postings from September–October 2026, and Stack Overflow’s yearly survey data on AI use and trust. The third is my own experience and interpretation. The counts show when things moved, not why, and none of them is a census of the market.

Two notes back, I argued that the title matters less than whether you take part in all of The Product Engineer Path: from a user’s problem, through a decision and a build, to what you learn after shipping. The last note found that about half of the 77 postings collected under the title ask for exactly that. One question is left: why are companies asking for it now, and not ten years ago?

The career promise became harder to rely on

As I lived it, a software career felt dependable: build depth, keep learning, and there would be a place for your skills. Never a guarantee, but a reasonable bet. My reading is that this bet grew up in a long stretch of cheap money.

Gergely Orosz counts 10 of the 14 years before 2024 with US interest rates at or below 0.5%, and sums up the period plainly: “growing tech companies was easy.” My reading of those years: with budget for the person next to you, a role could stay narrow. A product manager decided, a designer researched, an engineer built, and each handoff had someone on both sides.

Cheap money, narrow roles

Left: years with US interest rates at or below 0.5%, out of the 14 before 2024 (Gergely Orosz, The Pragmatic Engineer). Right: my reading of how teams split the work, with a handoff at every break.

10 of 14 years US rates at or below 0.5% “growing tech companies was easy.” Gergely Orosz, The Pragmatic Engineer Product managerdecides Designerresearches Engineerbuilds
The squares are a count, not a timeline. The split line is my interpretation, not something the numbers prove.

From cheap money to expensive money, 2008 to 2026

  1. The Federal Reserve cuts rates to 0–0.25%.

  2. Rates go back to 0–0.25%.

  3. Venture funding reaches $621 billion, more than double 2020.

  4. The Federal Reserve starts raising rates.

  5. Meta’s “Year of Efficiency”: fewer management layers, less hiring.

  6. Rates reach 5.25–5.50%. Cheap money is over.

  7. Layoffs.fyi counted about 263,000 tech layoffs, 59% more than in 2022 (TechCrunch).

  8. Stack Overflow survey respondents using AI tools go from under half to more than four in five.

When money got expensive, Orosz describes startups with few options left but profitability, “even if it means deep cuts”. My reading: growth had to pay for itself, and the question a team asked changed, less “who else do we hire for this?”, more “how much of this can one person carry?” The narrow role was easier to fund when money was cheap.

One company’s announcement doesn’t prove every team followed. But if one engineer can attempt more of the building with AI, a smaller team may expect that engineer to take on decisions that used to sit in product, design or customer-facing roles. Related pressures, not a causal chain.

The title grew as the hiring thread shrank

Every month, Hacker News hosts a “Who is hiring?” thread. I counted the 166 threads I could retrieve since 2012: how many posting accounts mention “product engineer” in their post.

A niche label for a decade, then a climb

Share of accounts posting in “Who is hiring?” that mention “product engineer”, each account counted once a year

0%2%4%6%8%after 20222013: 0.3% (7 of 2,051 accounts)2014: 0.3% (8 of 2,406 accounts)2015: 0.2% (8 of 3,267 accounts)2016: 0.8% (31 of 3,925 accounts)2017: 0.9% (42 of 4,572 accounts)2018: 1.2% (57 of 4,749 accounts)2019: 0.9% (37 of 4,155 accounts)2020: 1.5% (54 of 3,599 accounts)2021: 1.6% (82 of 5,070 accounts)2022: 1.8% (66 of 3,705 accounts)2023: 2.5% (54 of 2,129 accounts)2024: 4.1% (85 of 2,090 accounts)2025: 6.0% (128 of 2,133 accounts)2026: 7.9% (144 of 1,815 accounts)1.8%7.9%’13’14’15’16’17’18’19’20’21’22’23’24’25’26
2026 covers January to November. A mention isn’t always the job title.

The climb didn’t come from a busier thread. The thread itself shrank.

More accounts mentioned the title while fewer accounts posted

2022 = 100

0501001502002502022202666 → 144 accounts mention the title (index 218)66 → 144 (×2.2)accounts mention the title3,705 → 1,815 accounts post in the thread (index 49)3,705 → 1,815 (×0.5)accounts post in the thread
Data and methodology
Accounts posting in Hacker News “Who is hiring?” threads, by year
YearAccounts postingMention “product engineer”Share
20132,05170.3%
20142,40680.3%
20153,26780.2%
20163,925310.8%
20174,572420.9%
20184,749571.2%
20194,155370.9%
20203,599541.5%
20215,070821.6%
20223,705661.8%
20232,129542.5%
20242,090854.1%
20252,1331286.0%
2026 (Jan–Nov)1,8151447.9%

Source: the 166 monthly Ask HN: Who is hiring? threads posted by the whoishiring account, December 2012 to November 2026, read through the public Hacker News API on 2026-11-10. Two months of 2015 are missing from the API list, and the November 2026 thread was read while still open. A post counts when its text mentions “product engineer” or “product engineers”. Each posting account is counted once a year, because companies repeat the same post every month. An account is not always one company. Replies and deleted or flagged posts are excluded. The 2012 thread (December only) is left out of the charts.

Both lines start at 100 in 2022, so they show change, not size.
  • Who posts. Hacker News posters likely lean toward US startups and companies whose engineers read it.
  • What a mention is. In the posts I read, often the job title (“Senior Product Engineer”); sometimes a team, and at least once a product manager role. No precision rate was measured.
  • What it shows. When mentions rose, not why.

Two threads, two points on the curve

Two Reddit threads, two years apart, show how the question sounded as the line climbed.

Two community threads placed on the title’s rise

May 2024 · an interview question

r/ExperiencedDevs on a “product engineer” interview, with no PM on the team

It’s just engineering, but explicitly in a customer-facing product.

Mar 2026 · a question about identity

r/ClaudeCode: are we all just becoming product engineers?

Good developers always were.

Two examples, not a measure of how many engineers ask.

What the postings ask for now

Across last note’s 77 postings, about half (41) ask for all of The Product Engineer Path, and about two in three expect AI in that work. That shows what the title asks for today; postings collected in one window can’t show how the same job looked before.

Each dot is one posting

41 of 77 postings ask for all of The Product Engineer Path

41 of 77 ask for all four steps of The Product Engineer Path: Problem, Decide, Build and Learn. Counting only strong evidence, 29; including open weak marks, 44.

50 of 77 postings ask for or prefer work with AI

50 of 77 ask for, or prefer, working with AI tools or building with AI.

Data and methodology
Explicit AI requirement by location group
Location groupCountShare
Portugal12/2254.5%
Other collected locations38/5569.1%
All50/7764.9%

The count of postings that ask for all of The Product Engineer Path comes from the Product Engineer Opportunity Map, edition Sep–Oct 2026. The AI count: the full public text of each posting, re-read on 2026-10-07 against a written codebook with a quoted line per judgment; cultural mentions and what an employer says about AI in its own hiring don’t count. The two groups were collected differently, and with samples this size there is no statistically detectable difference between them (exact test, p = 0.29). Of 78 saved records, 77 descriptions are included; one recruiter message with keywords only is excluded.

Download the aggregate AI data (JSON)

The two grids are separate counts and don’t mark the same postings. Collected September–October 2026; not a market census.

Reflect

Mechanism, counterpoints & experience

What's actually getting compressed

Addy Osmani: The output of all this exploration isn’t features. It’s judgment. Boris Cherny, on a team at Anthropic: roles there are not really tied to job function […].

The simplest story would be that engineers came to trust AI. The survey data doesn’t support that.

Use went up. Reported trust stayed at a similar level. The title climbed.

2023–2026, each on its own scale. Compare the direction of each line, not the heights.

Use AI tools

% of respondents to the question

0%25%50%75%100%20232024202520262023: 43.8%43.8%2024: 61.8%2025: 78.5%2026: 82.8%82.8%

Trust AI output’s accuracy

% of AI users who answered the trust question

0%25%50%75%100%20232024202520262023: 42.2%42.2%2024: 43.0%2025: 41.8%41.8%new scale,not comparable

Mention “product engineer”

% of accounts on HN “Who is hiring?”

0%2%4%6%8%10%20232024202520262023: 2.5%2.5%2024: 4.1%2025: 6.0%2026: 7.9%7.9%
Data and methodology
Values behind the three panels
Measure2023202420252026
Use AI tools (% of respondents to the question)43.8%61.8%78.5%82.8%
Trust the accuracy of AI output (% of AI users who answered the trust question)42.2%43.0%41.8%new scale
Mention “product engineer” (% of accounts on HN “Who is hiring?”)2.5%4.1%6.0%7.9%

Use and trust: Stack Overflow Developer Survey 2023, 2024, 2025 and 2026, official aggregated data, licensed ODbL 1.0. Trust is the share of AI users who answered the trust question and “highly” or “somewhat” trust the accuracy of AI output. The 2025 question dropped the neutral option, and 2026 replaced the scale with situations, so 2026 has no comparable point. The use question was also reworded in 2025 and 2026. Respondents are Stack Overflow’s audience, not all developers.

Product engineer: the Hacker News count from chapter 2; 2026 is January to November.

Four yearly points show timing, not correlation or cause.

In 2026 the survey asked the trust question differently, and the answer says where trust lives now:

Developers trust AI when they can check it

  • “I trust it when I can easily verify the output”48%
  • “I trust it for many tasks, including important work decisions”6.6%
Stack Overflow Developer Survey 2026, respondents who answered the trust question (n = 14,304). Other answers not shown.

My reading is that what grew isn’t trust in the tool but use with verification: the harness an engineer builds around the AI. The survey asked about verification only in 2026, so this is an interpretation, not a measured trend. Gergely Orosz, January 2026: As AI generates more code, it becomes increasingly important to specify what to build.

What a harness can show, and what it can’t

The harness

  • Tests
  • Evaluations
  • Review
  • Watching the software in use

Gives evidence it was built right

Users

  • Their problem
  • What they do with it
  • What they stop doing

Gives evidence it was the right thing to build

Building a harness means deciding what “good” looks like and checking whether you got it. My reading: that’s closer to deciding and learning than to typing.

Where this argument is weaker than it sounds

Building isn’t maintaining.
One commenter in the 2026 thread pointed to contradictions, hotfixes, etc. in an existing codebase. A working prototype doesn’t show the same workflow handles legacy behavior or production failures.
The behavior is old.
Orosz described the product-minded software engineer in 2019. What changed is how often hiring posts mention it by name.
Range isn’t free.
One commenter argued that AI makes specialists stronger too: But as usual, everybody will have to choose if being mediocre at both roles, or specialize in either of the two. The claim is about the relative value of judgment, not the end of depth.
Timing isn’t cause.
The title, the end of cheap money and the spread of AI fall in the same years. With yearly points, that’s worth noticing, not proof.

What this looks like from the inside

I had been moving across software, design and business for years. Since 2023, AI-assisted development and agent workflows have become part of that practice. The projects below are current ones; not every tool in them existed in 2023. They show where AI saved effort and where it didn’t.

What AI compressed in my projects, and what it didn’t
ProjectAI compressedStill took judgment
Guarda-Costas ImobiliárioHome-buying due diligence, 22 Claude Code skillsReading condominium minutes and contract clauses; dating a property from photosWhich 11 stages the buyer’s journey needs; ranking contradictions so the serious ones come first
MKT BrainRetrieval pipeline for a multi-tenant marketing systemWriting meaningful parts of the implementationSeparating what the system observed from what it only declared: the harness in miniature
A production incidentSilent data-persistence errorsShipping the first version, including the part that was wrongReading what broke and redesigning the guarantee, still in progress: moving from an LLM-shaped architecture to a deterministic scoring rubric

Make

A working answer to “why now?”

So, why now?

My working answer: the promise of a career built on depth in one specialty got weaker at the same time that AI made building cheaper. In those same years, more accounts on Hacker News hiring threads began mentioning a title that, in 41 of the 77 postings we collected, asks for all of The Product Engineer Path.

  • TimingThe data shows it.
  • CauseThe data doesn’t show it.
  • The new default?Too early to tell.

That wider scope is a lot to ask. An engineer who built a career on technical depth may now hear that customers, product decisions and outcomes are part of the job too. It can feel like being asked to start over, and AI doesn’t fix that. In my experience, a tool that writes code faster doesn’t make a first conversation with a customer any less uncomfortable.

My reading: the step is smaller than it sounds. Parts of The Product Engineer Path may already show up in everyday engineering work, under other names:

Where The Product Engineer Path already shows up in engineering work
StepWhat you may already doOne step wider
ProblemReproducing a bug from a user’s report and asking what they were trying to doAsking that question before there’s a bug
DecideWeighing two designs in a code review; cutting scope so something shipsWeighing two features with the same judgment
BuildWriting, testing and shipping the codeAlready yours
LearnWatching dashboards after a deploy; writing a postmortem on what brokeAsking whether users got what they needed, not only whether the system held

None of this asks you to stop being an engineer. It asks the habits you already have to reach a little further, one step at a time, starting with the one closest to your work today. You don’t need to follow the route I took, or take all of it at once. It gives a concrete way to look at what is changing, and at which capabilities are worth building next.