The "Soft Skills" That Actually Determine Your Engineering Career (With Specific Examples)

I hate the term "soft skills." It implies they're fluffy, optional, nice-to-have. They're not. They're the skills that determine whether you get promoted, whether your ideas get adopted, and whether people want to work with you. Here are the 5 that actually matter, with specific, practical examples — not vague advice like "communicate better." 1. Writing Clearly Not "writing documentation." Writing ANYTHING clearly. This includes: Slack messages, PR descriptions, incident reports, design proposals, email updates, ticket descriptions, commit messages. Bad Slack message: hey, so i was looking at the thing and it seems like there might be an issue with how we handle the stuff in production, not sure tho, what do you think? Good Slack message: Found a potential issue: our payment webhook handler doesn't verify Stripe signatures in production (it only checks in staging). This means anyone could send fake payment events to our endpoint. Verified by: checked the middleware config in deploy/pr