The Pragmatic Engineer (YouTube channel)

What the channel covers

This is the YouTube side of The Pragmatic Engineer, run by Gergely Orosz, who also writes The Pragmatic Engineer newsletter and wrote The Software Engineer's Guidebook. The channel describes itself as interviews about software engineering, Big Tech and startups, aimed at developers and engineering leaders.

Most uploads are full podcast episodes with one guest. Recent conversations include context engineering, building coding agents, why performant code matters with Casey Muratori, formal methods with Hillel Wayne, distributed databases, CI/CD, and Kubernetes with Kelsey Hightower. Language designers appear too: one episode covers TypeScript, C# and Turbo Pascal with Anders Hejlsberg. The tone is curious and specific: guests explain how their teams work, what went wrong and what they would do differently.

Where to start

• The Pragmatic Engineer Podcast: the main playlist. Pick episodes on topics you already touch at work so you can connect what you hear to something real.
• Software Engineer Career Paths: shorter material on how engineering careers progress, useful if you are trying to see what senior, staff and management tracks actually involve.
• Performance Reviews for Software Engineers: worth watching before your first or next review cycle.
• Engineering Management: for anyone leading a team or deciding whether to.
• Gergely's Talks: his own conference talks, a quicker way into his thinking than a full episode.

Who it suits

It suits developers with some working experience, roughly from your first job onwards, and people moving into lead or manager roles. Students can get value from the career playlists, but many episodes assume you know what code review, on-call or a deployment pipeline feel like. If you are still learning to code, start with a beginner channel and come back later.

How to turn watching into action

Long interviews are easy to listen to and easy to forget. A few habits help:

1. Keep a one-line note per episode: the single idea you want to try. For example, "write a short design note before starting the next feature".
2. Try one thing within a week. If an episode is about testing or CI, change something small in your own pipeline.
3. Bring questions to your manager. Career episodes are most useful as a starting point for a real conversation about expectations at your company.
4. Do not binge. One episode a week, applied, beats ten in a weekend.

Pair it with on Sefism

• The Mid-level to senior roadmap and its cheat sheet turn the ideas from career episodes into a staged plan.
• The Staff and leadership roadmap and cheat sheet cover the next step if management or staff work is on your mind.
• Read The Staff Engineer's Path alongside the career playlists.
• Career questions that fit: How do I go from mid-level to senior software engineer? and How do I get promoted faster in a large company?.
• On the blog: Twelve Moves That Take You From Mid Level to Senior.

Best for: working engineers who want an honest, detailed view of how good teams operate and how careers really grow.