In the evolving landscape of technology conferences and open source communities, event organizers increasingly strive to ensure diverse representation on their stages. While these diversity, equity, and inclusion (DEI) initiatives are designed to amplify underrepresented voices, they can sometimes spark complex personal and professional dilemmas for the individuals they aim to spotlight. One technologist recently shared a candid reflection on her journey from initial frustration over being recruited for a speaking slot primarily due to her gender, to becoming an active, core contributor to an open source project she once had no direct hand in building.
The experience began when a friend and colleague approached her with a proposal to co-present at an upcoming technology conference. Initially, she was pleasantly surprised by the invitation, particularly because she had not contributed significantly to the project set to be showcased. However, during a subsequent planning meeting to discuss the presentation details, she learned the primary motivation behind the request: the conference’s DEI guidelines mandated that the speaker lineup include at least one individual who does not identify as a man.
Upon learning this, her initial reaction was one of offense. It felt as though she was being approached strictly because of her gender rather than on the merits of her technical background, expertise, or direct involvement in the work being presented.
Realizing her discomfort, her colleague quickly provided additional context, assuring her that fulfilling the diversity quota was not the sole reason for the invitation. The project team faced a substantial backlog of work and genuinely needed new contributors to help bridge the capability gap and carry the initiative forward. Recognizing this dual motivation, she paused to weigh the situation carefully. She considered the broader implications of conference DEI initiatives, reflecting on both sides of the dynamic—including instances where project creators eager to present their work might find themselves stalled unless they could secure a co-presenter from a minority group to satisfy event criteria.
Looking past the initial blow to her ego, she identified a deeper, more personal ethical concern: the discomfort of stepping onto a major stage to act as the public face of a technical initiative to which she had not yet directly contributed. Her professional ethics simply did not align with presenting work that was not her own.
Resolving to help more
Determined to bridge this gap, she dove into researching the project. While the specific codebase was not entirely familiar, she possessed a solid grasp of the foundational technology and the core objectives the project aimed to achieve. Moreover, the overarching goal of the initiative genuinely excited her. She recognized that if executed successfully, the technology would provide immense practical value to end users.
This realization led her to establish a firm personal condition for participating in the speaking opportunity: she would move forward with the presentation only if it served as a stepping stone to give back to the community tenfold and establish herself as a key, active contributor to the project. Her colleague and co-presenter welcomed this commitment and offered full support throughout her onboarding journey.
With her resolve solidified, the team submitted their talk proposal. Her co-presenters fostered a welcoming and supportive environment, reassuring her that as long as she brought genuine interest and passion for the project, her prior contribution level was secondary.

Participating in the high-profile conference proved to be a transformative milestone. She interacted with seasoned professionals across the broader open source ecosystem, drawing inspiration from the diverse array of panels, sessions, and technical discussions. The presentation itself went smoothly, and speaking at such a major industry event marked a significant career achievement. Yet, once the excitement of the conference faded, a new emotion emerged: guilt.
Motivation derived from guilt
The successful event left her with a profound sense of obligation toward the community and the colleagues who had extended the opportunity. She was determined to honor the promise she had made to herself, though balancing this new commitment alongside higher-priority professional responsibilities proved challenging. Whenever her schedule threatened to derail her plans, the lingering feeling of guilt served as an internal compass, steering her back toward her commitment to give back to the ecosystem that had elevated her.
After several months of navigating competing priorities and hard work, she maintained her momentum. Today, she is a recognized and active contributor to the open source project. She embraces the technical challenges it presents, helps resolve critical issues, and has even taken the lead in implementing the upstream project within her own organization’s downstream ecosystem.
As a testament to her ongoing dedication, she was invited back to present an update on the project to the community—this time entirely on the merits of her sustained technical contributions, as the speaker demographic ratio was already balanced. Reflecting on the journey, she noted that the initial pangs of guilt ultimately served as a powerful catalyst for professional growth.
Embracing opportunities and paying it forward
Looking back, she views taking the initial chance as a decisive turning point that created a win-win scenario for everyone involved. Had she allowed her initial frustration to deter her from accepting the invitation, she likely never would have crossed paths with the project, missing out on a deeply rewarding technical journey. She expressed deep gratitude to the colleagues who opened the door and supported her transition.
Recognizing that her experience likely mirrors that of other women in the technology sector, she offered encouragement to peers who might encounter similar circumstances. She noted that when presented with opportunities tied to diversity initiatives, there is no need to internalize guilt, feel burdened by unrealistic expectations, or experience undue pressure. Instead, she suggested channeling those complex emotions into positive action, maximizing the immediate benefits of the opportunity, and subsequently using one’s position to uplift and mentor others.
Ultimately, she emphasized, the strength of the open source community lies just as much in its people as it does in the technology being built, anchored by a shared responsibility to support one another’s growth.