<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/podcast/is-everyone-a-product-engineer-now/" -->

---
title: Is everyone a product engineer now? | Off the Leash, a daily.dev podcast
description: Satya Nadella says LinkedIn took four roles, combined them and said they're all "full stack builders." Claude Code's creator, Boris Cherny, thinks we'll start
canonical: https://daily.dev/podcast/is-everyone-a-product-engineer-now/
og:type: video.episode
og:url: https://daily.dev/podcast/is-everyone-a-product-engineer-now/
og:title: Is everyone a product engineer now? | Off the Leash, a daily.dev podcast
og:description: Satya Nadella says LinkedIn took four roles, combined them and said they're all "full stack builders." Claude Code's creator, Boris Cherny, thinks we'll start
og:image: https://daily.dev/podcast/is-everyone-a-product-engineer-now.jpg
og:site_name: daily.dev
og:locale: en_US
twitter:card: summary_large_image
twitter:site: @dailydotdev
twitter:creator: @dailydotdev
twitter:title: Is everyone a product engineer now? | Off the Leash, a daily.dev podcast
twitter:description: Satya Nadella says LinkedIn took four roles, combined them and said they're all "full stack builders." Claude Code's creator, Boris Cherny, thinks we'll start
twitter:image: https://daily.dev/podcast/is-everyone-a-product-engineer-now.jpg
---

[Skip to main content ](#main-content) 

 Off the Leash · Episode 3 

#  Is everyone a product engineer now? 

Oct 20, 2026 14 min With Ido Shamun and Patchy 

[ ![](/podcast/is-everyone-a-product-engineer-now.jpg) Play episode 13:42 ](https://www.youtube.com/watch?v=WnG9k0R48pw) 

* [ ![Listen on Apple Podcasts](/assets/badges/apple-podcasts.svg?v=a462e008) ](https://podcasts.apple.com/us/podcast/is-everyone-a-product-engineer-now/id6819686986?i=1000797226088)
* [ Listen on Spotify ](https://open.spotify.com/episode/4T26EIvAruJXLcDHfMiJvX)
* [ Watch on YouTube ](https://www.youtube.com/watch?v=WnG9k0R48pw)

Satya Nadella says LinkedIn took four roles, combined them and said they're all "full stack builders." Claude Code's creator, Boris Cherny, thinks we'll start to see the title software engineer go away.

So is everyone a product engineer now? And if product engineers build the product, who builds what they stand on?

We check it against our own count of every Hacker News "Who is hiring?" post since 2019, plus Indeed, SignalFire and CompTIA. We go back to 1974, when the US Bureau of Labor Statistics saw programmers and systems analysts starting to merge into one job, and then explain it the way RPGs would, as two classes with many builds. It ends on who's still hiring juniors, and what to learn now.

## Transcript

The episode as it aired. Select a timestamp to play from that moment. 

### [ 0:00 ](https://www.youtube.com/watch?v=WnG9k0R48pw) Intro 

[ 0:00 ](https://www.youtube.com/watch?v=WnG9k0R48pw) **Ido Shamun:** Every role is collapsing into 

[ 0:01 ](https://www.youtube.com/watch?v=WnG9k0R48pw&t=1s) **Ido Shamun:** Product engineer or builder. 

[ 0:03 ](https://www.youtube.com/watch?v=WnG9k0R48pw&t=3s) Satya Nadella · All-In at Davos Jan 2026 

> “Took those first four roles and combined them,”

[ 0:05 ](https://www.youtube.com/watch?v=WnG9k0R48pw&t=5s) Satya Nadella · All-In at Davos Jan 2026 

> “They're all full stack builders”

[ 0:06 ](https://www.youtube.com/watch?v=WnG9k0R48pw&t=6s) **Ido Shamun:** Front-end, which used to be twenty-seven percent is now eleven percent, 

[ 0:10 ](https://www.youtube.com/watch?v=WnG9k0R48pw&t=10s) **Ido Shamun:** So we started 

[ 0:11 ](https://www.youtube.com/watch?v=WnG9k0R48pw&t=11s) **Ido Shamun:** With one percent roughly 

[ 0:12 ](https://www.youtube.com/watch?v=WnG9k0R48pw&t=12s) **Ido Shamun:** And already this month, we are at 

[ 0:14 ](https://www.youtube.com/watch?v=WnG9k0R48pw&t=14s) **Ido Shamun:** Nine point five percent 

[ 0:15 ](https://www.youtube.com/watch?v=WnG9k0R48pw&t=15s) **Ido Shamun:** We've been merging titles ever since nineteen seventy-four, 

[ 0:19 ](https://www.youtube.com/watch?v=WnG9k0R48pw&t=19s) **Ido Shamun:** You have the mage, 

[ 0:20 ](https://www.youtube.com/watch?v=WnG9k0R48pw&t=20s) **Ido Shamun:** You have the rogue, 

[ 0:21 ](https://www.youtube.com/watch?v=WnG9k0R48pw&t=21s) **Ido Shamun:** You have warrior, 

[ 0:22 ](https://www.youtube.com/watch?v=WnG9k0R48pw&t=22s) **Ido Shamun:** I actually think there is another role 

[ 0:23 ](https://www.youtube.com/watch?v=WnG9k0R48pw&t=23s) **Ido Shamun:** That is hiding there 

[ 0:27 ](https://www.youtube.com/watch?v=WnG9k0R48pw&t=27s) **Narrator:** What your job is turning into. And how to get ready for it. Today on Off the Leash, with Ido, co-founder and CTO at daily.dev. Made possible by Google Cloud. Let's fetch it. 

### [ 0:38 ](https://www.youtube.com/watch?v=WnG9k0R48pw&t=38s) Is every role becoming one? 

[ 0:38 ](https://www.youtube.com/watch?v=WnG9k0R48pw&t=38s) **Ido Shamun:** Hey, Patchy, have you heard the recent trend in software engineering? Every role is collapsing into product engineer or builder. I want to start by showing you a clip of Satya Nadella, Microsoft CEO, about a recent change that has happened in LinkedIn not so long ago. So let's hear from his words, and let's talk about it later. 

[ 0:57 ](https://www.youtube.com/watch?v=WnG9k0R48pw&t=57s) Satya Nadella · All-In at Davos Jan 2026 

> “At LinkedIn … we used to have product managers, we had … designers, we had front-end … engineers, back-end engineers, and … so on. So what we did is we sort of took those first four roles and combined them, in fact, increased scope and said they're all full stack builders”

[ 1:11 ](https://www.youtube.com/watch?v=WnG9k0R48pw&t=71s) **Ido Shamun:** So it's not just LinkedIn. Also, Boris Cherny of Claude Code and other well-known people in the industry are talking about how AI is changing the roles of software engineering and basically collapsing it into one. And I love looking at it just like RPG games. And I have great analogy that I'll share with you later. But before that, I want to share my experience. So ever since AI, I feel like we as a team can embark on a much more ambitious project and also single-handedly cover them or execute them. We used to have responsible developer for each repo, and this guy was the main guy that usually contributed or him and another one. But now I see that, you know, developers throughout the team contribute to many more repos than before. A web developer can contribute to the feed or to our content pipeline and back end engineer all of a sudden deploy fixes to the application where they see it. So the boundaries are so blurred right now and the definition of, you know, back end engineer or front end engineer or web engineer, whatever it is, is so blurred and people with agency just act on what they wanna fix, and it's all thanks to AI. And I also noticed that many of the recent features that we released, they are so big, but yet they are done with just a single person that I truly believe that the future is this sort of collapse into one role of product engineer. 

### [ 2:36 ](https://www.youtube.com/watch?v=WnG9k0R48pw&t=156s) What does the hiring data say? 

[ 2:36 ](https://www.youtube.com/watch?v=WnG9k0R48pw&t=156s) **Ido Shamun:** But let's leave what I feel or what people are saying, and let's look at the data. Let's see if the trend is already there. So, the first thing I noticed when diving into the data is the Hacker News job posting. Basically front-end, which used to be twenty-seven percent is now eleven percent, and QA used to be five percent, and now it's two percent. And you may think, okay, like, we may need less jobs but it's not true either. Basically, in the US, software job postings are up by twenty percent from last year, and seventy percent out of it is mostly senior job postings. So we see the trend that more jobs are being posted and not only that, we see that within the big tech companies, also the share of engineers went from forty-six percent to fifty-five percent. While the US tech job postings is at a three-year high, the specialty roles are falling back. 

### [ 3:31 ](https://www.youtube.com/watch?v=WnG9k0R48pw&t=211s) Is the product engineer new? 

[ 3:31 ](https://www.youtube.com/watch?v=WnG9k0R48pw&t=211s) **Ido Shamun:** So we started with one percent roughly of job postings in twenty nineteen talking about product engineers, and already this month, we are at nine point five percent of all job postings on Hacker News looking for product engineers. Linear CTO talks all about it. Let's have a quick look. 

[ 3:49 ](https://www.youtube.com/watch?v=WnG9k0R48pw&t=229s) Tuomas Artman (Linear's CTO) with Gergely Orosz · AI Engineer Europe Apr 2026 

> “So I think, you know, engineers will have to move to become product-oriented and product-focused. They will have to be sort of mini PMs who sort of talk with customers, are engaging in that layer, and then can, you know, implement functionality that your … customers want. Then the QA job, you got … the QA job, then you got DevOps. … Now we're saying we're even the, the product job and the customer support job as well”

[ 4:07 ](https://www.youtube.com/watch?v=WnG9k0R48pw&t=247s) **Ido Shamun:** But, you know, it's nothing new. We've been merging titles ever since nineteen seventy-four, and probably even before that. So we had keypunch operator, programmers, computer operator, system analyst, machine repair the analyst turned a business problem into a form a program can handle, And the programmer turned it into flowcharts and code. A survey that happened during the seventies found out that some companies, especially the small ones, took both the system analyst and the programmer and merged them into one. And this is not the only merge that we've seen happening throughout the years. May I remind you about full-stack engineers, which took front-end and back-end and put them together. Or DevOps, developers, you know, meets operation into one role. So, this is something the industry is constantly doing after identifying a need in companies. And the reason why it's happening is because we are changing. There are new tools coming in we need to adapt. Also because the more people you have, the more communication you need, the more time it takes to build something or deliver something, and the industry obviously always mo- want to move faster. So they are trying to find ways to create one-man team or very small teams that can be super efficient and can deliver value in in less time and less friction. 

### [ 5:20 ](https://www.youtube.com/watch?v=WnG9k0R48pw&t=320s) Who builds for the builders? 

[ 5:20 ](https://www.youtube.com/watch?v=WnG9k0R48pw&t=320s) **Ido Shamun:** And while many people believe in the industry that product engineer is the only role that will be there in few years' time I actually think there is another role that is hiding there and it's the systems engineer. It's the role that build the foundation for the product engineers. So in order for them to be efficient, in order for them to ship fast with high quality and to deliver all the business needs, they need a strong foundation. They need tools, they need platforms that will empower them to do so, and this is exactly where the system engineer come into play. They build agents, harnesses, infrastructures, platforms, all of this. If you look at companies like Stripe, GitLab, Cursor, LinkedIn, they all have their own infrastructure of agents that are running and executing, always trying to push fixes are being prompted by the product engineers. So this is exactly the layer where I envision system engineer working on. It is kind of the evolution of platform engineers if you wanna think about it like this. Basically developers who contribute for the internal staff of the organization and help with the developer experience or now the AI experience and improving all of that. You may also think of them as the people who are building Claude Code, for example, or Codex or this kind of layer that we all use, right? And remember I promised you the RPG analogy? So let's dive into it. This is the time. So if you ever played RPG games, you know there are many classes in RPG. You have the mage, you have the rogue, you have warrior, druid, whatever it is, and every such class has different builds or different forks to it that you can choose along the way, how you want to specialize and where you want to focus. So I think software engineering is the same. Not so long ago, we used to have so many classes in software engineering. We had web engineer with builds for React or PHP or Vue or whatever it is, right? And we have the backend class with Go and Rust and maybe some other thing. And we had the DevOps and platform engineering and all of them had different nuances and path. And now it's all converging into two classes. The product engineer, which I mentioned before, and the system engineer, right? And for each one, we have the specialty or the build. So I can be a product engineer with a strong passion about front-end or back-end or databases or whatever it is. And I can be a system engineer with a passion for building harnesses or building platforms or whatever it is. But still the kind of tasks and the kind of work that I will mostly do is set by the class I chose to be. In a few months we'll have two classes. And how do we get better with these new classes? So stay until the end, and I'll give you some tips you can apply right away to be a better product engineer and a better system engineer. 

### [ 8:10 ](https://www.youtube.com/watch?v=WnG9k0R48pw&t=490s) What happens to juniors? 

[ 8:10 ](https://www.youtube.com/watch?v=WnG9k0R48pw&t=490s) **Ido Shamun:** We've talked so much about the different professions and specialties and so on, but how this trend and how this change even impact juniors. Have you ever wondered that, Patchy? Have you thought about it? And this is actually the most polarized point in tech right now when you talk about hiring. So the data shows that companies hire less juniors than ever. And among recent graduates, computer engineering is the second highest unemployment rate. So juniors are less in demand right now. But when you talk with companies and when you look at companies' hiring policies, you see the split and the dissonance in great detail. So when you look at Shopify, Amazon, Cloudflare they all claim they are hiring juniors more than ever. They have more interns, and they have more open roles thanks to AI. Amazon CTO Werner Vogels talks all about it. Let's hear it. 

[ 9:01 ](https://www.youtube.com/watch?v=WnG9k0R48pw&t=541s) Werner Vogels Amazon's CTO · WeAreDevelopers World Congress 2026 

> “I think … the fact that, you know, we see decline in junior developers is a myth. At Amazon, we are hiring … more interns and more junior developers than ever. It's just they have to define the structure around it”

[ 9:13 ](https://www.youtube.com/watch?v=WnG9k0R48pw&t=553s) **Ido Shamun:** So this is the big tech, but when you look at smaller companies, they are not looking to hire juniors or interns or anything like that because it's just too much at the moment, and they'd rather have a senior with an AI shipping whatnot than focusing on, on juniors. And I believe this split will be even more opinionated as AI will improve over time. But on the other end, I feel like this is something we always had in the industry. Smaller companies kind of avoiding teaching and learning and all of that, and they want existing skills already that only senior dev, while big tech companies are willing to teach and learn for paying less and investing back in the industry. So I don't think it's something new, but I think AI just made a dissonance much, or the gaps much bigger. But obviously, we need to take care of our juniors and the interns to make sure they get proper skills, they advance. 

### [ 10:04 ](https://www.youtube.com/watch?v=WnG9k0R48pw&t=604s) How do you get ready? 

[ 10:04 ](https://www.youtube.com/watch?v=WnG9k0R48pw&t=604s) **Ido Shamun:** Now, if you want to prepare yourself for a world of builders and system engineers, here are a few points that may help you out, and you can apply them right away. If you used to get a task and just do it, now you want to understand why. You want to ask product questions. You want to reason about UI. You want to reason about the user experience. You want to ask these kind of questions. If you have people in your company that this is their role, like designers, product managers, and so on, you want to sit down with them, you want to talk to them. You want to understand why they made certain de-decisions and why not. You want to challenge them. You want to have these kind of discussions. But in the near future, you will be the ones making these calls, or at least some of them. So start talking to these people in your organization. Start learning from them. You also want to talk to your customers or at least get a stream of what the customers are saying about your product, to learn what are the customers paying what they like, what they don't like. Maybe also look at analytics data and to build your approach on how you analyze data, how you look at it, how you interpret it. You want to be a generalist. This is, you know, when we talk about builders, we talk about product engineers. These are generalists by design. There will be less demand for specialist people, as we saw before. And so if you decide to go deep, it's okay, but know that you'll have less opportunities and less job postings that are relevant for you. And as a generalist, my best recommendation is don't hold yourself from exploring new domains. So diving to domains you haven't dove before, try new things, use AI to bridge the gap of knowledge that you have. So by now, you probably have solid engineering skills and sometimes you lack of knowledge. So you may be a front-end engineer who has never done data engineering. So take a task from this domain and try to do it yourself with AI, try to challenge, try to learn in the process, use AI to learn and bridge the knowledge gap. So over time, you'll be able to tackle more domains, you'll be able to complete more tasks on your own because this is what companies are looking for this kind of engineer who can complete so many tasks by themselves and can just ship whatever they need to ship without needing another engineer to counterpart them. Dive into the platforms you use. So if you use Claude Code, if you use something else, try to reason about how they work, try to dive into them, try to understand the different components, right? So Claude Code, it has the memories, and it has the the harness, and it has so many things. Try to have a picture of how to build such a system in case you want to specialize more into the system engineering part of things. Experience building agents yourself if you haven't done it before. Go and explore other products, right? As someone who's gonna be making product decisions, you want to take inspiration from other products. So download apps or go check out B2B SaaS software, depending on, on, like, what you do, right? But look at the decision they made, try to reason about why they made this decision, try to take inspiration of their onboarding, different processes, and different things they have in the product just to enrich your mind with examples because you want to build taste, you want to build opinions, you want to build product instincts and you want to know what you like and what you don't like, and you want to be very clear about it. And I know this is not what you signed up for. Probably you loved coding you love writing it, and so on, but these days are no longer here, and we need to adjust ourselves. This is what the industry expects, and this is what your company will expect from you soon enough. And let me tell you this, once you get very good at this, and you build this skill, then you'll be unstoppable. You'll be able to build your own software, you'll be able to be top performer in the company you work for, and you'll just build amazing software. And on that note, thank you very much, and I'll see you again. 

## Sources

Everything the episode shows or quotes, in the order it comes up.

1. [ PostHog, "What is a product engineer?" (Product Engineer Handbook) ](https://posthog.com/product-engineer/what-is-a-product-engineer)
2. [ incident.io, Product Engineer job ad ](https://jobs.ashbyhq.com/incident/b4edacb2-1008-476f-9b96-d5c9f39b81a9)
3. [ Satya Nadella, Microsoft's CEO, on All-In at Davos (21 Jan 2026) ](https://www.youtube.com/watch?v=5nCbHsCG334)
4. [ Boris Cherny on YC's Lightcone (17 Feb 2026) ](https://www.youtube.com/watch?v=PQU9o%5F5rHC4)
5. [ Our count of every Hacker News "Who is hiring?" thread, Jan 2019 to Oct 2026 ](https://news.ycombinator.com/submitted?id=whoishiring)
6. [ Indeed Hiring Lab, US job postings tracker ](https://github.com/hiring-lab/job%5Fpostings%5Ftracker)
7. [ Indeed Hiring Lab, "AI and Job Postings: From Destruction to Creation?" (8 Jul 2026) ](https://www.hiringlab.org/2026/07/08/ai-and-job-postings-from-destruction-to-creation/)
8. [ SignalFire, "State of Tech Talent Report 2026" (22 Jun 2026) ](https://signalfire.com/blog/signalfire-state-of-talent-report-2026)
9. [ CompTIA Tech Jobs Report (2 Oct 2026) ](https://www.comptia.org/en-us/about-us/news/press-releases/employer-demand-for-tech-talent-reaches-three-year-high-comptia-analysis-finds/)
10. [ Tuomas Artman, Linear's CTO, with Gergely Orosz at AI Engineer Europe (Apr 2026) ](https://www.youtube.com/watch?v=wjk0ulMAkbc)
11. [ US Bureau of Labor Statistics, Computer Manpower Outlook (1974) ](https://fraser.stlouisfed.org/title/computer-manpower-outlook-4683)
12. [ Randy Schmidt, "Full Stack Web Developers" (Forge38, 3 Jun 2008), archived ](https://web.archive.org/web/20090815020323/http://forge38.com/blog/2008/06/full-stack-web-developers/)
13. [ DevOpsDays Ghent (2009) ](https://legacy.devopsdays.org/events/2009-ghent/)
14. [ Alan Page, "To Combine… or not?" (27 Oct 2014) ](https://angryweasel.com/blog/to-combine-or-not/)
15. [ Gartner, "Top 10 Strategic Technology Trends for 2023" (17 Oct 2022) ](https://www.gartner.com/en/newsroom/press-releases/2022-10-17-gartner-identifies-the-top-10-strategic-technology-trends-for-2023)
16. [ Tomer Cohen, LinkedIn's CPO, on Lenny's Podcast (4 Dec 2025) ](https://www.lennysnewsletter.com/p/why-linkedin-is-replacing-pms)
17. [ Earendil, "What Is a Harness?" (20 Aug 2026) ](https://earendil.com/posts/what-is-a-harness/)
18. [ HarnessTax, "How Much Does the Harness Matter for Coding Agents?" (16 Sep 2026) ](https://harnesstax.github.io/)
19. [ Stripe, "Minions: Stripe's one-shot, end-to-end coding agents" (9 Feb 2026) ](https://stripe.dev/blog/minions-stripes-one-shot-end-to-end-coding-agents)
20. [ Hugging Face, "Harness, Scaffold, and the AI Agent Terms Worth Getting Right" ](https://huggingface.co/blog/agent-glossary)
21. [ GitLab, Senior CX Platform Engineer job ad ](https://job-boards.greenhouse.io/gitlab/jobs/8871406002)
22. [ Wikipedia, "Character class" ](https://en.wikipedia.org/wiki/Character%5Fclass)
23. [ Wikipedia, "Glossary of video game terms" ](https://en.wikipedia.org/wiki/Glossary%5Fof%5Fvideo%5Fgame%5Fterms)
24. [ New York Fed, The Labor Market for Recent College Graduates ](https://www.newyorkfed.org/research/college-labor-market)
25. [ Farhan Thawar, Shopify, "Zero Experience, Infinite Leverage" (1 Jun 2026) ](https://internships.shopify.com/pages/zero-experience-infinite-leverage)
26. [ Matt Garman, AWS's CEO, interviewed by Platformer (23 Jun 2026) ](https://www.platformer.news/matt-garman-aws-ceo-interview-ai-jobs/)
27. [ Cloudflare, "One year later: the power of 1.1.1.1 interns" (5 Oct 2026) ](https://blog.cloudflare.com/one-year-later-1111-interns/)
28. [ Werner Vogels, Amazon's CTO, at WeAreDevelopers World Congress 2026 ](https://www.wearedevelopers.com/videos/100265-fireside-chat-in-conversation-with-werner-vogels-cto-of-amazon-com)
29. [ Eugenia Kuyda, interviewed by Platformer (16 Jun 2026) ](https://www.platformer.news/this-founder-isnt-hiring-junior-engineers-anymore/)

![](/podcast/off-the-leash.jpg) 

## About Off the Leash

Off the Leash is daily.dev's podcast for when the headline isn't enough. We take one thing happening in the developer world, usually a take everyone's passing around, sometimes breaking news, and go deep: what actually happened, what people are saying about it on daily.dev, X and Hacker News, what the sources say, and then our own take.

 The host is real and unscripted. This episode was made possible by Google Cloud. 

[All episodes → ](/podcast/)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/og-image.png?v=a830cdf1","width":1200,"height":630},"sameAs":["https://twitter.com/dailydotdev","https://www.linkedin.com/company/dailydotdev","https://github.com/dailydotdev","https://www.instagram.com/dailydotdev"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","description":"Free, personalized developer news aggregator. Stay on top of software development news, AI coding tools, and web dev - curated daily from trusted sources.","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}},{"@type":"WebPage","@id":"https://daily.dev/podcast/is-everyone-a-product-engineer-now/","url":"https://daily.dev/podcast/is-everyone-a-product-engineer-now/","name":"Is everyone a product engineer now? | Off the Leash, a daily.dev podcast","description":"Satya Nadella says LinkedIn took four roles, combined them and said they're all \"full stack builders.\" Claude Code's creator, Boris Cherny, thinks we'll start","inLanguage":"en-US","isPartOf":{"@id":"https://daily.dev/#website"}},{"@type":"PodcastEpisode","@id":"https://daily.dev/podcast/is-everyone-a-product-engineer-now/#episode","url":"https://daily.dev/podcast/is-everyone-a-product-engineer-now/","name":"Is everyone a product engineer now?","description":"Satya Nadella says LinkedIn took four roles, combined them and said they're all \"full stack builders.\" Claude Code's creator, Boris Cherny, thinks we'll start to see the title software engineer go away. So is everyone a product engineer now? And if product engineers build the product, who builds what they stand on? We check it against our own count of every Hacker News \"Who is hiring?\" post since 2019, plus Indeed, SignalFire and CompTIA. We go back to 1974, when the US Bureau of Labor Statistics saw programmers and systems analysts starting to merge into one job, and then explain it the way RPGs would, as two classes with many builds. It ends on who's still hiring juniors, and what to learn now.","episodeNumber":3,"datePublished":"2026-10-20T08:00:00Z","timeRequired":"PT13M42S","image":"https://daily.dev/podcast/is-everyone-a-product-engineer-now.jpg","inLanguage":"en-US","partOfSeries":{"@id":"https://daily.dev/podcast/#series"},"associatedMedia":{"@id":"https://daily.dev/podcast/is-everyone-a-product-engineer-now/#video"},"publisher":{"@id":"https://daily.dev/#organization"},"sameAs":["https://www.youtube.com/watch?v=WnG9k0R48pw","https://open.spotify.com/episode/4T26EIvAruJXLcDHfMiJvX","https://podcasts.apple.com/us/podcast/is-everyone-a-product-engineer-now/id6819686986?i=1000797226088"]},{"@type":"VideoObject","@id":"https://daily.dev/podcast/is-everyone-a-product-engineer-now/#video","name":"Is everyone a product engineer now?","description":"Satya Nadella says LinkedIn took four roles, combined them and said they're all \"full stack builders.\" Claude Code's creator, Boris Cherny, thinks we'll start to see the title software engineer go away. So is everyone a product engineer now? And if product engineers build the product, who builds what they stand on? We check it against our own count of every Hacker News \"Who is hiring?\" post since 2019, plus Indeed, SignalFire and CompTIA. We go back to 1974, when the US Bureau of Labor Statistics saw programmers and systems analysts starting to merge into one job, and then explain it the way RPGs would, as two classes with many builds. It ends on who's still hiring juniors, and what to learn now.","thumbnailUrl":["https://daily.dev/podcast/is-everyone-a-product-engineer-now.jpg"],"uploadDate":"2026-10-20T08:00:00Z","duration":"PT13M42S","embedUrl":"https://www.youtube.com/embed/WnG9k0R48pw","inLanguage":"en-US","publisher":{"@id":"https://daily.dev/#organization"},"transcript":"Ido Shamun: Every role is collapsing into\n\nIdo Shamun: Product engineer or builder.\n\nSatya Nadella · All-In at Davos: Took those first four roles and combined them,\n\nSatya Nadella · All-In at Davos: They're all full stack builders\n\nIdo Shamun: Front-end, which used to be twenty-seven percent is now eleven percent,\n\nIdo Shamun: So we started\n\nIdo Shamun: With one percent roughly\n\nIdo Shamun: And already this month, we are at\n\nIdo Shamun: Nine point five percent\n\nIdo Shamun: We've been merging titles ever since nineteen seventy-four,\n\nIdo Shamun: You have the mage,\n\nIdo Shamun: You have the rogue,\n\nIdo Shamun: You have warrior,\n\nIdo Shamun: I actually think there is another role\n\nIdo Shamun: That is hiding there\n\nNarrator: What your job is turning into. And how to get ready for it. Today on Off the Leash, with Ido, co-founder and CTO at daily.dev. Made possible by Google Cloud. Let's fetch it.\n\nIdo Shamun: Hey, Patchy, have you heard the recent trend in software engineering? Every role is collapsing into product engineer or builder. I want to start by showing you a clip of Satya Nadella, Microsoft CEO, about a recent change that has happened in LinkedIn not so long ago. So let's hear from his words, and let's talk about it later.\n\nSatya Nadella · All-In at Davos: At LinkedIn … we used to have product managers, we had … designers, we had front-end … engineers, back-end engineers, and … so on. So what we did is we sort of took those first four roles and combined them, in fact, increased scope and said they're all full stack builders\n\nIdo Shamun: So it's not just LinkedIn. Also, Boris Cherny of Claude Code and other well-known people in the industry are talking about how AI is changing the roles of software engineering and basically collapsing it into one. And I love looking at it just like RPG games. And I have great analogy that I'll share with you later. But before that, I want to share my experience. So ever since AI, I feel like we as a team can embark on a much more ambitious project and also single-handedly cover them or execute them. We used to have responsible developer for each repo, and this guy was the main guy that usually contributed or him and another one. But now I see that, you know, developers throughout the team contribute to many more repos than before. A web developer can contribute to the feed or to our content pipeline and back end engineer all of a sudden deploy fixes to the application where they see it. So the boundaries are so blurred right now and the definition of, you know, back end engineer or front end engineer or web engineer, whatever it is, is so blurred and people with agency just act on what they wanna fix, and it's all thanks to AI. And I also noticed that many of the recent features that we released, they are so big, but yet they are done with just a single person that I truly believe that the future is this sort of collapse into one role of product engineer.\n\nIdo Shamun: But let's leave what I feel or what people are saying, and let's look at the data. Let's see if the trend is already there. So, the first thing I noticed when diving into the data is the Hacker News job posting. Basically front-end, which used to be twenty-seven percent is now eleven percent, and QA used to be five percent, and now it's two percent. And you may think, okay, like, we may need less jobs but it's not true either. Basically, in the US, software job postings are up by twenty percent from last year, and seventy percent out of it is mostly senior job postings. So we see the trend that more jobs are being posted and not only that, we see that within the big tech companies, also the share of engineers went from forty-six percent to fifty-five percent. While the US tech job postings is at a three-year high, the specialty roles are falling back.\n\nIdo Shamun: So we started with one percent roughly of job postings in twenty nineteen talking about product engineers, and already this month, we are at nine point five percent of all job postings on Hacker News looking for product engineers. Linear CTO talks all about it. Let's have a quick look.\n\nTuomas Artman (Linear's CTO) with Gergely Orosz · AI Engineer Europe: So I think, you know, engineers will have to move to become product-oriented and product-focused. They will have to be sort of mini PMs who sort of talk with customers, are engaging in that layer, and then can, you know, implement functionality that your … customers want. Then the QA job, you got … the QA job, then you got DevOps. … Now we're saying we're even the, the product job and the customer support job as well\n\nIdo Shamun: But, you know, it's nothing new. We've been merging titles ever since nineteen seventy-four, and probably even before that. So we had keypunch operator, programmers, computer operator, system analyst, machine repair the analyst turned a business problem into a form a program can handle, And the programmer turned it into flowcharts and code. A survey that happened during the seventies found out that some companies, especially the small ones, took both the system analyst and the programmer and merged them into one. And this is not the only merge that we've seen happening throughout the years. May I remind you about full-stack engineers, which took front-end and back-end and put them together. Or DevOps, developers, you know, meets operation into one role. So, this is something the industry is constantly doing after identifying a need in companies. And the reason why it's happening is because we are changing. There are new tools coming in we need to adapt. Also because the more people you have, the more communication you need, the more time it takes to build something or deliver something, and the industry obviously always mo- want to move faster. So they are trying to find ways to create one-man team or very small teams that can be super efficient and can deliver value in in less time and less friction.\n\nIdo Shamun: And while many people believe in the industry that product engineer is the only role that will be there in few years' time I actually think there is another role that is hiding there and it's the systems engineer. It's the role that build the foundation for the product engineers. So in order for them to be efficient, in order for them to ship fast with high quality and to deliver all the business needs, they need a strong foundation. They need tools, they need platforms that will empower them to do so, and this is exactly where the system engineer come into play. They build agents, harnesses, infrastructures, platforms, all of this. If you look at companies like Stripe, GitLab, Cursor, LinkedIn, they all have their own infrastructure of agents that are running and executing, always trying to push fixes are being prompted by the product engineers. So this is exactly the layer where I envision system engineer working on. It is kind of the evolution of platform engineers if you wanna think about it like this. Basically developers who contribute for the internal staff of the organization and help with the developer experience or now the AI experience and improving all of that. You may also think of them as the people who are building Claude Code, for example, or Codex or this kind of layer that we all use, right? And remember I promised you the RPG analogy? So let's dive into it. This is the time. So if you ever played RPG games, you know there are many classes in RPG. You have the mage, you have the rogue, you have warrior, druid, whatever it is, and every such class has different builds or different forks to it that you can choose along the way, how you want to specialize and where you want to focus. So I think software engineering is the same. Not so long ago, we used to have so many classes in software engineering. We had web engineer with builds for React or PHP or Vue or whatever it is, right? And we have the backend class with Go and Rust and maybe some other thing. And we had the DevOps and platform engineering and all of them had different nuances and path. And now it's all converging into two classes. The product engineer, which I mentioned before, and the system engineer, right? And for each one, we have the specialty or the build. So I can be a product engineer with a strong passion about front-end or back-end or databases or whatever it is. And I can be a system engineer with a passion for building harnesses or building platforms or whatever it is. But still the kind of tasks and the kind of work that I will mostly do is set by the class I chose to be. In a few months we'll have two classes. And how do we get better with these new classes? So stay until the end, and I'll give you some tips you can apply right away to be a better product engineer and a better system engineer.\n\nIdo Shamun: We've talked so much about the different professions and specialties and so on, but how this trend and how this change even impact juniors. Have you ever wondered that, Patchy? Have you thought about it? And this is actually the most polarized point in tech right now when you talk about hiring. So the data shows that companies hire less juniors than ever. And among recent graduates, computer engineering is the second highest unemployment rate. So juniors are less in demand right now. But when you talk with companies and when you look at companies' hiring policies, you see the split and the dissonance in great detail. So when you look at Shopify, Amazon, Cloudflare they all claim they are hiring juniors more than ever. They have more interns, and they have more open roles thanks to AI. Amazon CTO Werner Vogels talks all about it. Let's hear it.\n\nWerner Vogels: I think … the fact that, you know, we see decline in junior developers is a myth. At Amazon, we are hiring … more interns and more junior developers than ever. It's just they have to define the structure around it\n\nIdo Shamun: So this is the big tech, but when you look at smaller companies, they are not looking to hire juniors or interns or anything like that because it's just too much at the moment, and they'd rather have a senior with an AI shipping whatnot than focusing on, on juniors. And I believe this split will be even more opinionated as AI will improve over time. But on the other end, I feel like this is something we always had in the industry. Smaller companies kind of avoiding teaching and learning and all of that, and they want existing skills already that only senior dev, while big tech companies are willing to teach and learn for paying less and investing back in the industry. So I don't think it's something new, but I think AI just made a dissonance much, or the gaps much bigger. But obviously, we need to take care of our juniors and the interns to make sure they get proper skills, they advance.\n\nIdo Shamun: Now, if you want to prepare yourself for a world of builders and system engineers, here are a few points that may help you out, and you can apply them right away. If you used to get a task and just do it, now you want to understand why. You want to ask product questions. You want to reason about UI. You want to reason about the user experience. You want to ask these kind of questions. If you have people in your company that this is their role, like designers, product managers, and so on, you want to sit down with them, you want to talk to them. You want to understand why they made certain de-decisions and why not. You want to challenge them. You want to have these kind of discussions. But in the near future, you will be the ones making these calls, or at least some of them. So start talking to these people in your organization. Start learning from them. You also want to talk to your customers or at least get a stream of what the customers are saying about your product, to learn what are the customers paying what they like, what they don't like. Maybe also look at analytics data and to build your approach on how you analyze data, how you look at it, how you interpret it. You want to be a generalist. This is, you know, when we talk about builders, we talk about product engineers. These are generalists by design. There will be less demand for specialist people, as we saw before. And so if you decide to go deep, it's okay, but know that you'll have less opportunities and less job postings that are relevant for you. And as a generalist, my best recommendation is don't hold yourself from exploring new domains. So diving to domains you haven't dove before, try new things, use AI to bridge the gap of knowledge that you have. So by now, you probably have solid engineering skills and sometimes you lack of knowledge. So you may be a front-end engineer who has never done data engineering. So take a task from this domain and try to do it yourself with AI, try to challenge, try to learn in the process, use AI to learn and bridge the knowledge gap. So over time, you'll be able to tackle more domains, you'll be able to complete more tasks on your own because this is what companies are looking for this kind of engineer who can complete so many tasks by themselves and can just ship whatever they need to ship without needing another engineer to counterpart them. Dive into the platforms you use. So if you use Claude Code, if you use something else, try to reason about how they work, try to dive into them, try to understand the different components, right? So Claude Code, it has the memories, and it has the the harness, and it has so many things. Try to have a picture of how to build such a system in case you want to specialize more into the system engineering part of things. Experience building agents yourself if you haven't done it before. Go and explore other products, right? As someone who's gonna be making product decisions, you want to take inspiration from other products. So download apps or go check out B2B SaaS software, depending on, on, like, what you do, right? But look at the decision they made, try to reason about why they made this decision, try to take inspiration of their onboarding, different processes, and different things they have in the product just to enrich your mind with examples because you want to build taste, you want to build opinions, you want to build product instincts and you want to know what you like and what you don't like, and you want to be very clear about it. And I know this is not what you signed up for. Probably you loved coding you love writing it, and so on, but these days are no longer here, and we need to adjust ourselves. This is what the industry expects, and this is what your company will expect from you soon enough. And let me tell you this, once you get very good at this, and you build this skill, then you'll be unstoppable. You'll be able to build your own software, you'll be able to be top performer in the company you work for, and you'll just build amazing software. And on that note, thank you very much, and I'll see you again.","hasPart":[{"@type":"Clip","name":"Intro","startOffset":0,"endOffset":38,"url":"https://www.youtube.com/watch?v=WnG9k0R48pw"},{"@type":"Clip","name":"Is every role becoming one?","startOffset":38,"endOffset":156,"url":"https://www.youtube.com/watch?v=WnG9k0R48pw&t=38s"},{"@type":"Clip","name":"What does the hiring data say?","startOffset":156,"endOffset":211,"url":"https://www.youtube.com/watch?v=WnG9k0R48pw&t=156s"},{"@type":"Clip","name":"Is the product engineer new?","startOffset":211,"endOffset":320,"url":"https://www.youtube.com/watch?v=WnG9k0R48pw&t=211s"},{"@type":"Clip","name":"Who builds for the builders?","startOffset":320,"endOffset":490,"url":"https://www.youtube.com/watch?v=WnG9k0R48pw&t=320s"},{"@type":"Clip","name":"What happens to juniors?","startOffset":490,"endOffset":604,"url":"https://www.youtube.com/watch?v=WnG9k0R48pw&t=490s"},{"@type":"Clip","name":"How do you get ready?","startOffset":604,"endOffset":822,"url":"https://www.youtube.com/watch?v=WnG9k0R48pw&t=604s"}]},{"@type":"PodcastSeries","@id":"https://daily.dev/podcast/#series","name":"Off the Leash","url":"https://daily.dev/podcast/","description":"Off the Leash is daily.dev's podcast for when the headline isn't enough. We take one thing happening in the developer world, usually a take everyone's passing around, sometimes breaking news, and go deep: what actually happened, what people are saying about it on daily.dev, X and Hacker News, what the sources say, and then our own take.","image":"https://daily.dev/podcast/off-the-leash.jpg","inLanguage":"en-US","publisher":{"@id":"https://daily.dev/#organization"},"sameAs":["https://www.youtube.com/@dailydotdev","https://open.spotify.com/show/1EDnZJP4wKO4QVB7HgrQej","https://podcasts.apple.com/us/podcast/off-the-leash-by-daily-dev/id6819686986"]},{"@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev/"},{"@type":"ListItem","position":2,"name":"Podcast","item":"https://daily.dev/podcast/"},{"@type":"ListItem","position":3,"name":"Is everyone a product engineer now?","item":"https://daily.dev/podcast/is-everyone-a-product-engineer-now/"}]}]}
```

