Podcast

Two devs getting coffee.

One conversation, one guest, nothing rehearsed. I sit down with another developer, CTO or whoever else is elbow-deep in technology that week, and we talk about the work the way engineers actually talk about it when no one is presenting.

Come on the show→Past appearances

Unscripted40 to 60 minutesGuests welcome

Two Devs Getting Coffee cover art: Oshri Cohen behind a studio microphone with two cups of coffee on the table

Hosted by Oshri Cohen

The show

Two Devs Getting CoffeeBooking guests now

Me, one other person in technology, and whatever we end up arguing about.

Some weeks that person is a developer two years in with strong feelings about their framework. Other weeks it's a CTO who just came out the far side of a migration that went badly. Seniority matters a lot less than having something you want to say out loud.

Nothing is scripted. I don't send questions ahead and there's no run of show. The good part of a technical conversation is almost always the tangent, so we start somewhere, follow it, and stop when we're done.

It stays technical. Architecture that aged badly, what AI has genuinely changed about the day job, the incident nobody wants to write the postmortem for, what breaks when a team doubles. The parts of the craft that never make it into a conference talk are the parts I want on tape.

ArchitectureAI in the day jobIncidents & postmortemsHiring engineersTech debtToolingScaling teamsWar stories

Pitch yourself as a guest→

The first episodes are being recorded now. As each one publishes it lands here and in In the Media with the rest of my appearances.

Format: One guest, one unscripted conversation
Length: Usually 40 to 60 minutes
Recorded: Remote, on video, Eastern Time
Preparation: None. Bring coffee.
Cost to guests: Nothing, and no pitch at the end

What we get into

The conversation you'd have anyway.

No theme weeks and no interview arc. These are the subjects the show keeps drifting back to.

◆

The decision you'd take back

Every engineer has one: the abstraction that looked right on the whiteboard and cost two quarters to unwind. Bring yours and we'll take it apart together.

✳

What AI actually changed

Not the keynote version. What a coding agent did to your review process, your estimates, your junior pipeline, and which parts of the job it left completely alone.

▲

The incident

The pager at 2am, the fix that made it worse, the thing you now check first. Postmortems get written for the org; this is the version you'd tell a friend.

●

Hiring, honestly

What your interview loop actually predicts, the hire everyone warned you about who turned out great, and how you decide when a team is big enough.

■

Tools and taste

Editors, languages, the framework you left and why, monorepo scars. Low stakes, strong opinions, occasional heresy.

✦

The career nobody plans

Going from writing code to running people and back again, staying technical past 40, the promotion that turned out to be a demotion in disguise.

Who I want on

If you build software, you qualify.

There's no audience-size requirement and no media training expected. I book people who are close to the work.

Developers

Anyone shipping code

Two years in or twenty. If you can walk me through something you built and where it hurt, that's an episode.

Leaders

CTOs, VPs and staff+

The people making the calls about architecture, hiring and what the team stops doing. Especially the calls that didn't work out.

Founders & adjacent

Everyone else in the stack

Technical founders working out how much of their first version survives, and the people in data, security, infrastructure and developer relations. Engineering is one seat at the table.

Come on the show

Pitch yourself. It's a short form.

Tell me who you are and what you'd want to talk about. I read every one of these myself.

Questions

Before you hit send.

The things people ask me before agreeing to sit down and record.

Do I need an audience to come on the podcast?

No. Two Devs Getting Coffee books people who are close to the work, not people with follower counts. Developers a couple of years into their first job are as welcome as CTOs running teams across several countries.

How long is an episode, and how much prep is there?

Episodes run 40 to 60 minutes and there is no preparation. Nothing is scripted, no questions go out in advance, and you will know the rough subject before we start recording. That is the whole brief.

How is the show recorded?

Remotely, on video, on Eastern Time from Fort Lauderdale or Montreal. Most guests are in the United States and Canada, and guests further afield are welcome too; the scheduling just takes an extra pass.

Is the conversation edited?

Lightly. The false start at the top and any dead air come out. Tangents stay in, because they are usually the reason the episode is worth listening to.

Where do episodes get published?

On this site, and every episode is added to the In the Media section alongside Oshri Cohen's other podcast and video appearances.

Is this a sales call in disguise?

No. Coming on the show costs nothing and ends with no pitch. If you do want to talk about hiring Oshri as a fractional or interim Chief AI Officer, that is a separate conversation and the contact details are on every page.

Bring your own coffee.

Pitch yourself as a guest, or send me the name of someone I should be chasing.

Come on the show→Email Oshri↗

hello@oshricohen.me (514) 777-3883Fort Lauderdale · Montreal