06- Handling Disagreements During Code Reviews

07- Onboarding Language

Onboarding Language: Essential Terms to Guide Junior Developers Through Initial Team Syncs Your code is solid. But when your tech lead asks about your blockers, your bandwidth, and whether you're aligned with the sprint goals — do you know exactly what to say? For most junior developers, the first weeks on a new team aren't hard because of the code. They're hard because of the communication. The daily stand-ups. The async updates. The unwritten rules of how professionals talk about their work. In this episode of English for Devs, we close that gap. We break down the high-frequency vocabulary you'll hear from day one — stand-ups, sprints, velocity, backlog, PRs, technical debt, capacity — and go beyond the definitions to show you how these terms actually live in real team conversations. You'll learn not just what to say, but how to say it with technical precision and professional confidence. By the end of this episode, you'll be able to: * Structure a clear, confident daily stand-up update * Raise blockers professionally — without fear * Use terms like "bandwidth" and "sprint goals" the way senior engineers do * Write async stand-up updates that are clean, scannable, and respected Whether you're a bootcamp grad stepping into your first Agile team, a self-taught developer joining a structured engineering org, or a non-native English speaker navigating the cultural layer of tech communication — this episode was built for you. No more nodding along hoping no one asks you to elaborate. It's time to speak the language of your team. English for Devs is the podcast for developers who want to master the professional English behind the pull requests, the planning meetings, and everything in between.

06- Handling Disagreements During Code Reviews

Pull requests shouldn’t feel like battlefields. In this episode of English for Devs, we tackle one of the most uncomfortable — and most important — parts of working in tech: disagreeing during code reviews. You’ll learn practical English phrases that help you: • Suggest improvements without sounding rude • Push back professionally when you disagree • Ask questions that reduce tension • Protect team trust while still protecting code quality Because great developers don’t just write clean code — they communicate clearly. If you’ve ever stared at a PR comment wondering “does this sound aggressive?”… this episode is for you. Level up your communication skills, reduce friction in your team, and turn reviews into real collaboration.

05- 5 Steps for Acing Your Next Job Interview

Want to sound confident, professional, and prepared in your next tech job interview? In this episode of English for Devs, we break down the 5 essential steps every developer, PM, or tech professional needs to master to impress recruiters and hiring managers. Learn how to: - Research the company and role effectively - Deliver a clear 60-second personal intro - Answer behavioral questions with the STAR Method - Show your technical thinking (even if you don’t finish the problem) - Ask smart questions that make you look senior This episode is perfect for anyone preparing for software developer interviews, remote tech roles, and English-language interviews. Improve your communication, clarity, and confidence in English for real interview situations. Follow English for Devs for more episodes that help you grow your tech career through better communication.

04- Pitch a feature like a pro.

In this episode of English for Devs, learn how to present a software feature clearly and persuasively using the PSI framework — Problem, Solution, Impact. Ideal for developers, project managers, and tech professionals who want to improve their communication skills in English. Perfect for stand-ups, demo days, and job interviews in tech. Follow English for Devs to keep improving your soft skills, clarity, and confidence in English for real developer scenarios.

03- The remote team miscommunication.

In today’s episode, we tackle one of the most common challenges in global software teams: when communication collapses across time zones and roles. Follow a dynamic exchange between a Project Manager and three essential team members — a Backend Developer, a Frontend Developer, and a QA Engineer — as they try to untangle a misunderstood task.Whether you’re a junior dev or a seasoned engineer, this episode will help you boost your English and become a clearer, more confident communicator in any remote work setting.