On October 12, 2023, GitHub Senior Security Engineer Arthur Searle published a first-person account of his experience transitioning as a hubber on the official GitHub Blog, detailing how the company’s remote-first culture and fully covered gender-affirming benefits reduced common barriers for trans tech professionals.
Searle’s Role and GitHub’s Gender-Affirming Benefits
Searle holds the role of Senior Security Engineer on GitHub’s Enterprise Security team, operating under the GitHub handle @gleeblezoid. He initially joined the company’s IT Engineering team, and transferred to the Enterprise Security team 6 months later after contributing security-related pull requests to the department. In his current role, he has led work migrating GitHub’s main SaaS platform to infrastructure as code, and has served as a guest speaker at Oxford University on version control best practices.
GitHub’s standard benefits package for all full-time employees covers 100% of out-of-pocket costs for three transition-related services: voice training, hormone replacement therapy (HRT), and transition-related therapy. Searle notes this coverage removed the financial barrier to accessing these care services, which often cost thousands of dollars out-of-pocket for trans people without inclusive health insurance. For context, GitHub’s benefits overview outlines the company’s comprehensive health coverage.
How GitHub’s Remote-First Model Supported the Transition
GitHub’s handle-first, remote-first work model removed a range of administrative and social hurdles Searle anticipated facing during his transition. Unlike prior IT roles he held at companies that required legal name use for all internal identification, GitHub’s internal systems allowed him to use his chosen name and pronouns from his first day, before completing any legal name change paperwork.
Most of Searle’s team communication is captured in writing via Slack and GitHub’s internal tools, so the vocal changes he experienced from HRT did not disrupt his daily workflow or draw unrequested attention from colleagues. The company’s permissive avatar policy, which allows staff to use custom graphics for their profiles, also prevents coworkers from guessing an employee’s gender based on physical appearance, eliminating the need for repeated coming-out conversations related to visual presentation.
Administrative Hurdles and Team Response
The only administrative steps Searle completed during his transition were standard name-change processes for GitHub’s payroll and internal HR systems. After updating his name and pronouns in these systems, his entire Enterprise Security team began using his correct name and gendered pronouns immediately, with no repeated coming-out conversations required for new team members or cross-functional collaborators. This seamless process stood in stark contrast to his prior IT roles, where he was required to provide legal name documentation to multiple departments to update his identification across all internal systems.
Searle describes two specific emotional moments from his transition at work: the first time a teammate used his correct name and referred to him as “him” during a work Zoom call, which left him near tears, and the day a teammate mailed him a shaving kit to celebrate his transition, which made him cry. Every Hubber he has informed about his transition has responded with support, per his account; many sent congratulations via memes featuring GitHub’s Arthur the aardvark mascot and Monty Python and the Holy Grail references, aligned with the company’s geek-centric culture.
Caveats for Trans Tech Workers Outside GitHub
Searle emphasizes that his experience is not universal for trans professionals in the tech industry. He notes that while GitHub’s policies are replicable, many tech employers still lack basic gender-affirming benefits and inclusive remote work policies that reduce transition-related barriers. For a broader view of inclusion efforts in tech, see GitHub’s inclusion page.
Many trans tech workers remain closeted at work due to fear of discrimination, face repeated bureaucratic delays when updating legal names in company systems, or are forced to come out repeatedly to new teams and in new roles. These gaps leave trans employees at non-inclusive companies exposed to significant professional and personal risk during transition.
What This Means for Tech Workers Evaluating Employers
For trans tech professionals evaluating potential employers, GitHub’s example sets a concrete benchmark: fully covered gender-affirming care (voice training, HRT, therapy) and a handle-first remote work policy that eliminates repeated coming-out conversations. If a company’s benefits page does not explicitly mention gender-affirming coverage, ask during the interview process. If internal systems force legal-name identification before chosen-name support, that is a red flag for trans-inclusion. GitHub’s careers page provides a reference for how to present supportive policies publicly.
Bottom line: GitHub’s handle-first remote work policy and standard, fully covered gender-affirming benefits eliminated nearly all common transition-related barriers for Senior Security Engineer Arthur Searle, offering a replicable blueprint for other tech employers seeking to support trans staff without requiring ad-hoc, case-by-case accommodations.
