What Makes a Software Engineer: The Essence of the Job

Every so often someone asks me what software engineering actually is. A kid thinking about majors, someone considering a career switch, a relative who's genuinely curious and not just being polite. It's a harder question than it should be, because every other profession gets a clean sentence. A doctor treats patients. A lawyer interprets law. A botanist studies plants. Four or five words and you basically get it. We don't have that sentence. "Writes code" is wrong the same way "a surgeon holds a knife" is wrong — technically true, completely missing. "Solves problems" is worse, because it describes literally everyone. Here's where I've landed, both on what the job is and on the part nobody mentions: who it's good for, and who it quietly makes miserable. The word we skip The answer's been sitting in the job title. It's engineering. A civil engineer looks at a river and a town on the other side and builds a bridge. Nobody calls that person "someone who works with steel.