In this video I break down what it really means to be a software engineer, and I answer the question I get all the time: do you need to know how to code? My honest take is yes—especially early on. Coding is a foundational skill for entry-level roles, and most companies still use coding interviews as the main filter. But I also call out the mismatch: grinding LeetCode and passing an interview doesn’t automatically mean you’re a strong engineer, because real SWE work is way more than solving isolated problems under a timer. I also talk about the other skills that actually make you effective on the job: communication, problem solving, creative/critical thinking, and embracing ambiguity. When you’re building features, you’re not just “writing code”—you’re working with PMs and stakeholders, weighing tradeoffs, and designing for real user flows. Then I compare Big Tech vs startups: in Big Tech, expectations are more structured and as you grow, you often code less and lead more. In startups, you usually have to do everything—move fast, influence decisions, and take on responsibility far beyond just coding. I wrap up by touching on non-coding roles and why knowing some coding still helps you speak the engineers’ language.