Made for your work
Email signatures for software engineers
Technical partners benefit from knowing which engineering team owns the conversation. Include your role and collaboration timezone, and link to public code only when it is maintained and cleared for sharing.
Fictional examples. Replace sample credentials and licence numbers with your own verified details.
| ||
| Made with InboxSig | ||
| ||
| Made with InboxSig | ||
What to include
- Engineering role and team
- Company engineering team
- Public work profile only if it can be shared
- Time zone if you regularly collaborate across regions
- Maintained GitHub profile
- Professional name and a business email address
What to leave out
- Private repository links
- Images containing your only contact details
- More than one primary call to action
Questions for software engineers
What should software engineers put first?
Lead with your name, then your role. Include engineering role and team where it helps recipients identify you.
Which link belongs in a software engineer signature?
Use a link to your maintained github profile. Label the destination clearly and check it before pasting the signature into your mail client.