Email Signature for Software Engineers
Engineers famously hate email signatures, which is exactly why a clean one stands out. The goal is a signature that reads like good code: minimal surface area, no dead links, nothing you'd have to maintain.
What a software engineer's signature should include
- Name, role, company. Possibly nothing else.
- GitHub if your profile is active, it's the portfolio link that matters.
- Your team in the title if you're client-facing ("Platform · API team") so external threads route correctly.
- Pronouns if you share them, signatures are where they're most-read.
What to leave out
- The stack list. "React | Node | K8s | Rust" is a CV line, not a signature.
- Availability status, it goes stale by Thursday.
- ASCII art. We know. Resist.
Work at a practice or firm on Google Workspace? Sincerely can manage every colleague's signature from one template, see how teams use it.