Pronouns in email signatures and bios in tech in 2026 — norms across companies

Pronouns in email signatures and bios in tech in 2026 are common enough that they are no longer surprising, but they are not universal enough to be risk-free in every context. The norm across many software, SaaS, AI, fintech, and remote-first companies is optional inclusion: employees may add pronouns to email signatures, Slack profiles, Zoom names, LinkedIn, GitHub bios, and internal directories, but should not be forced to disclose them. The best companies make pronoun sharing easy, ordinary, and voluntary. The worst companies turn it into a culture-war signal or a performative checkbox.

For an individual employee, the decision is practical: will adding pronouns reduce friction, signal allyship, support trans and nonbinary coworkers, or create avoidable exposure? For a manager or People team, the decision is operational: can systems support names and pronouns cleanly without outing anyone or making people explain themselves repeatedly?

Pronouns in email signatures and bios: the 2026 tech norm

Across tech companies, the broad pattern is:

• Email signatures: optional pronoun line, usually after name or title.
• Slack and Teams: optional profile field or display-name convention.
• Zoom and Google Meet: optional name display, often “Name (she/her).”
• LinkedIn: increasingly common for candidates, recruiters, ERG leaders, and people managers.
• GitHub and portfolio bios: mixed; more common in people-facing engineering communities than in anonymous open-source contexts.
• HR systems: improving, but still inconsistent across legal name, chosen name, display name, payroll, and benefits.

You will see stronger adoption at remote-first companies, companies with active LGBTQ+ ERGs, larger public tech firms, developer tools companies with global teams, and organizations where managers model the practice. You will see weaker adoption in very small startups, security-sensitive communities, companies with older leadership norms, and offices in regions where LGBTQ+ visibility can create safety concerns.

Should you include pronouns? A decision framework

Add pronouns if:

• You want to be referred to correctly and the workplace context feels safe enough.
• You are a manager, recruiter, interviewer, HR partner, ERG leader, or public-facing teammate and want to normalize optional sharing.
• Your name is unfamiliar to some coworkers and pronouns reduce guessing.
• You work on a global team where gender assumptions vary by language or culture.
• You want to signal that corrections and inclusion are normal, not awkward.

Consider leaving them out or using limited disclosure if:

• You are not ready to be out about gender identity or expression.
• Your legal, immigration, family, or safety situation makes disclosure risky.
• You work with clients, vendors, or regions where pronoun visibility could create real exposure.
• You feel pressured by a manager and want to preserve privacy.
• The company has poor confidentiality norms or a history of outing people.

The key word is optional. Voluntary pronoun sharing supports inclusion. Mandatory pronoun disclosure can harm the exact people it is meant to support.

Email signature formats that work

Keep it simple. Do not over-design the signature or turn pronouns into a lecture.

Standard:

Name Lastname Role, Company pronouns: she/her email | phone | calendar

Compact:

Name Lastname (they/them) Senior Product Designer, Company

Formal:

Name Lastname Director of Engineering, Company Pronouns: he/him

If your company uses brand-controlled signatures, ask whether a pronoun field can be optional in the generator. Avoid requiring employees to manually hack HTML signatures if the company can support a clean field.

For external email, remember the audience. A recruiter emailing candidates may benefit from pronouns in the signature because it sets a tone. A security engineer communicating with a vendor in a sensitive region may make a different choice. Both decisions can be reasonable.

Slack, Teams, and internal bio norms

Internal profiles are where pronoun sharing is most useful because coworkers use them daily. A good profile setup includes separate optional fields for display name, pronunciation, pronouns, location, timezone, manager, and working hours. The pronoun field should not be tied to legal sex, HR gender marker, payroll, benefits, or identity verification. It should be a display preference.

Good profile examples:

• Alex Rivera — they/them — Staff Backend Engineer — NYC — UTC-5
• Priya Shah — she/her — Product Lead — London — works 8:30-4:30 local
• Jordan Lee — no pronouns listed — Security — Seattle

The third example is important. No pronouns listed should be normal. Do not ask people why the field is blank. Do not infer identity from omission. Do not use profile completeness nudges that pressure disclosure.

LinkedIn and public bios

LinkedIn pronouns are visible to recruiters, hiring managers, coworkers, customers, and sometimes family. Adding them can be useful if you want consistency across your public professional identity. It can also invite unwanted attention in some fields or geographies. Treat LinkedIn as public, not internal.

For candidates, pronouns in a LinkedIn profile are usually fine in progressive tech recruiting circles. They are common among recruiters, people managers, DEI workers, designers, product managers, and many engineers. If you are applying to companies where inclusion is a stated value, pronoun inclusion is unlikely to be unusual. But if you are applying globally, working in a conservative market, or not out in all parts of your life, you may prefer to keep pronouns off public profiles and use them only after trust exists.

GitHub and personal sites are similar. Use pronouns if they help collaborators refer to you correctly. Skip them if anonymity, safety, or focus matters more.

How companies should set policy

A strong 2026 tech-company policy says:

1. Employees may share pronouns in approved profile fields, email signatures, and meeting tools.
2. Sharing is optional for everyone.
3. Managers should not require employees to explain why pronouns are absent.
4. Systems should support chosen names and pronouns separately from legal records.
5. Intentional or repeated misgendering can violate anti-harassment policy.
6. Corrections should be brief and normalized.
7. Pronoun data should not be used for analytics without explicit privacy review.

This policy is better than a mandate. The point is to create a workplace where correct reference is easy and privacy is respected.

Manager scripts

Opening a team norm:

“You’re welcome to add pronouns to your Slack, Zoom, or email signature if you want. It’s optional. If someone shares pronouns, please use them; if they do not, do not make assumptions or ask them to explain.”

Correcting a mistake in a meeting:

“Quick correction: Jordan uses they/them. Go ahead.”

Private coaching after repeated mistakes:

“I’ve noticed you’ve misgendered Jordan several times after being corrected. I need you to use their pronouns consistently. If you make a mistake, correct it briefly and move on.”

Responding to pushback:

“This is about referring to coworkers accurately and maintaining a respectful workplace. Pronoun sharing is optional; using shared pronouns is not optional.”

Common mistakes

The biggest mistake is making pronouns mandatory. This can force trans, nonbinary, questioning, closeted, or safety-conscious employees into a disclosure choice they did not want. It can also force people to choose between lying and outing themselves.

The second mistake is performative formatting without operational support. If Slack supports pronouns but payroll deadnames someone, the company has not solved the real issue. If an email signature has pronouns but managers ignore repeated misgendering, the signature is branding.

The third mistake is inconsistent correction. If only LGBTQ+ employees correct pronouns, they carry the social cost. Managers and peers should handle routine corrections too.

The fourth mistake is treating pronouns as a political debate in work channels. Employees do not need to litigate whether they should be referred to correctly.

Candidate and new-hire playbook

If you are interviewing and want to test norms without over-disclosing, ask:

• “How does the company handle chosen names and pronouns across internal systems?”
• “Are pronouns in Slack or email signatures optional?”
• “Is there an LGBTQ+ ERG or benefits contact I can review after offer?”

If you are onboarding:

1. Decide where you want pronouns visible: HR system, Slack, Zoom, email, LinkedIn, none, or some.
2. Check whether legal name appears in unexpected places.
3. Ask your manager to model your correct name and pronouns if helpful.
4. Use short corrections early so the wrong habit does not spread.
5. Keep a record if mistakes become repeated or targeted.

If you are an ally:

• Add pronouns if you genuinely want to and can do so safely.
• Do not pressure others to match you.
• Correct mistakes briefly.
• Support system fixes, not just signature lines.
• Remember that allyship is measured when someone is not in the room.

International and customer-facing considerations

Global tech companies need nuance. Pronoun norms differ by language, law, and safety context. Some languages do not map cleanly to English pronouns. Some employees work in regions where LGBTQ+ visibility creates legal or personal risk. Some customers may react poorly, and employees should not be forced to absorb that risk alone.

A good company provides options: internal-only display, external signature choice, localized guidance, travel safety support, and manager backing if customers behave disrespectfully. Inclusion should not mean “individual employees take the risk while the company takes the credit.”

How to handle mistakes without making the moment bigger

People will make mistakes. The useful norm is fast correction, not public shame or elaborate apologies. If you use the wrong pronoun, say “sorry, they,” correct the sentence, and continue. Do not spend five minutes explaining how supportive you are. The attention should return to the person’s work, not your feelings about the mistake.

If someone corrects you, accept it the first time. If you are unsure how to refer to someone, use their name until you know. Do not ask invasive questions about identity, transition, medical history, or why pronouns changed. If a coworker updates pronouns, treat it like any other profile update: use the new information going forward and avoid turning it into gossip.

Repeated mistakes need management, not endless patience from the affected employee. Managers should distinguish between a one-time slip and a pattern. A pattern after correction becomes a workplace issue because it affects belonging, credibility, and participation in meetings.

The practical bottom line

Pronouns in email signatures and bios in tech in 2026 are a normal optional practice, not a universal requirement. Include them if they help you be addressed correctly, support the norm you want, or fit your role. Leave them out if privacy or safety matters more. If you manage people, make the systems work, keep sharing voluntary, and enforce respectful usage when pronouns are shared. The mature norm is not everyone displaying pronouns. The mature norm is everyone having control over how they are referred to.

Related guides

• Health insurance comparison across tech companies in 2026 — premiums, deductibles, and HSA eligibility — A practical framework for comparing tech-company health plans in 2026, including premiums, deductibles, out-of-pocket exposure, networks, and whether the plan actually qualifies for an HSA.
• 401(k) match norms in tech in 2026 — by company size and stage — A guide to 401(k) match norms across tech companies in 2026, including startup vs public-company patterns, vesting schedules, true match value, mega backdoor Roth availability, and offer-stage questions.
• Parental Leave at Tech Companies in 2026 — Benchmarks, Policies, and How to Negotiate — Parental leave policies in tech vary widely by company stage, country, caregiver type, and manager culture. This guide gives 2026 benchmarks, policy questions, and negotiation scripts for expecting parents and candidates.
• Severance Package Norms in Tech in 2026 — What's Standard and What's Negotiable at Exit — Tech severance packages usually combine cash, healthcare, equity treatment, release terms, and transition support. This guide explains 2026 norms, red flags, and the negotiation levers employees should check before signing.
• Accessibility Accommodations in Tech in 2026 — The Request Process and What's Reasonable — Accessibility accommodations in tech in 2026 cover far more than ramps and screen readers: remote work, flexible schedules, assistive software, meeting norms, interview adjustments, and sensory-friendly office expectations. Here's how to request accommodations clearly, what is reasonable, and what to document.