#74: Developer Experience, FinTech, and Leading Remote Teams with Maryna Rybalko

·52 min·3 clips

Marina says AI makes prototyping and writing easier, but PMs still need market judgment and vision.

Imran starts with the career map. He puts Marina in London, traces the move from .NET developer to full-stack engineer to platform lead, then asks what that history does to product work. The opening feels quick and unvarnished: a little name-check banter, a nod to the late hour, then straight into engineering, startups, and product judgment. Marina's answer stays practical. In a smaller company, a technical PM may not have researchers or extra layers nearby, so the technical background becomes useful fast. She can look at the data herself. That means opening the database, doing her own analysis, and showing up to engineering conversations with something sturdier than vibes. She can also read code. She says she does not technically need to review implementation, but she can still tell when the work does not match the request. That part gets a little awkward, in the useful way. Her engineering history lets her give direct feedback and ask for changes without treating the codebase like a black box. Imran keeps testing the comparison. He is careful not to make her dunk on other PMs, but he wants the honest version: do engineers respond differently to someone who used to build software? Marina does not claim technical PMs are automatically better. She does make the startup case clearly, where roles stretch and context matters. The design-team tension fits right into that. Imran brings up the familiar product mess: unclear priorities, requests without context, and work whose impact is hard to explain. Marina's advice lands on value. If people cannot say why something matters, the work gets harder. The close stays warm. Imran notices it is 9 p.m. and still bright where she is, jokes about time disappearing into work, and says he hopes to have her back.

As heard by us

A grounded discussion of how technical PMs can verify work and catch mismatches before release.

The discussion stays practical. A product manager with an engineering background explains how technical fluency changes the job: she can check the database, run her own analysis, read code, and confirm whether the work matches the ask before it ships.

Read the full review in PlayNext →

Why you'd press play

You want a practical look at how technical fluency helps product leadership in a startup.

Read the full recommendation in PlayNext →

Listen to the show on

Apple Podcasts Spotify

Play clips from this episode More from Imran's Podcast