When a professional receives an invitation to speak at a major technology conference alongside a trusted colleague, the initial reaction is typically one of validation and excitement. However, for many underrepresented professionals in the tech industry, the experience is frequently complicated by the uncomfortable realization that diversity mandates may be at play. Recently, one technologist shared an introspective account of how a conference speaking opportunity—offered initially to satisfy diversity, equity, and inclusion (DEI) requirements—transformed from a bruised ego into a catalyst for deep open source involvement, long-term community contribution, and personal growth.
The journey began when a friend and colleague approached the author about co-presenting a project at an upcoming conference. Initially, the invitation came as a pleasant surprise. The author had not contributed significantly to the specific project being showcased, but the prospect of speaking on a prominent stage was undeniably appealing. A meeting was arranged to hash out the presentation details, but during this discussion, the underlying motivation for the invitation surfaced. The conference organizers enforced specific DEI initiatives that required panels and presentation lineups to feature at least one speaker who did not identify as a man.
For the author, this revelation struck a sensitive nerve. The immediate reaction was a sharp sense of offense and tokenism. It felt deeply discouraging to be approached solely on the basis of gender rather than on individual merit, technical achievement, or direct involvement with the work.
However, the co-presenter quickly stepped in to provide broader context and reassurance, explaining that gender diversity was not the sole factor driving the invitation. The project itself was expansive, demanding a heavy workload, and the team genuinely required additional contributors to bridge a widening gap. They were hoping the author could step in, help carry the operational weight, and share the responsibilities of the project moving forward.
Left to process these conflicting realities, the author took time to reflect. It required stepping back to evaluate the dual nature of DEI initiatives within the broader technology landscape. On one hand, these policies can sometimes make individuals feel reduced to demographic checkboxes. On the other hand, the author recognized the systemic hurdles on the flip side of the coin: teams eager to showcase their technical innovations were frequently blocked from presenting entirely unless they could secure representation from minority groups.
Beyond the politics of conference compliance, a deeper and more pressing ethical dilemma emerged. Once the sting of wounded pride subsided, a profound sense of discomfort took hold regarding the integrity of the presentation itself. The author questioned the ethics of stepping onto a major stage to act as the public face and advocate for a project to which they had not yet made any direct, meaningful contribution. How could one authentically present code and architecture built entirely by others?
Resolving to help more
Rather than walking away from the opportunity or accepting a superficial role, the author decided to bridge the gap between presence and participation. Independent research into the project began immediately. While the specific codebase was not entirely familiar, the foundational technologies and the core problems the project aimed to solve aligned closely with the author’s broader technical background. More importantly, the overarching goals of the initiative sparked genuine professional excitement. The software, if executed successfully, promised to deliver immense utility to end users across the ecosystem.
This realization shaped a firm personal resolution: the speaking engagement would only proceed under the strict condition that it served as a launching pad for a much deeper commitment. The author resolved to give back to the project and the broader community tenfold, transforming from a reluctant co-presenter into a core, active contributor. The co-presenters welcomed this condition enthusiastically, offering full support and reassurance that passion, interest, and a willingness to learn were far more important than prior tenure on the codebase.
With this renewed sense of purpose and alignment, the team finalized and submitted their talk proposal. Throughout the preparation phase, the co-presenters fostered an inclusive and encouraging environment, ensuring that the author felt entirely welcome within the team dynamics.
Participating in the conference ultimately proved to be a transformative milestone. Immersed in the vibrant atmosphere of a major technology event, the author connected with seasoned professionals and leaders from across the global open source community. The panels, technical sessions, and hallway discussions provided a wellspring of inspiration and exposed the author to a wealth of new perspectives and technical insights. The presentation itself unfolded smoothly, delivering the project updates to a receptive audience. Standing on a large stage and successfully delivering a talk at a major industry conference was celebrated as a significant career achievement.
However, once the conference lights dimmed and the euphoria of the event subsided, an unexpected psychological weight began to set in. A quiet wave of guilt started kicking in.
Guilt as a motivator
Reflecting on the experience, the author realized that the initial tokenistic circumstances had given way to a moral obligation. A promise had been made to the community, the project team, and to oneself—a commitment to earn the platform that had been provided.
Channeling that sense of obligation into daily work proved challenging, particularly when weighed against higher-priority professional responsibilities and competing deadlines. Yet, that lingering guilt acted as a persistent internal compass, keeping the author anchored to the original pledge. It served as a constant reminder that the opportunity to stand on that stage had been a privilege, and that the debt owed to the welcoming community had to be repaid through genuine labor.
After several months of balancing competing priorities, navigating technical hurdles, and sustaining a steady workflow, the effort bore fruit. The author proudly transitioned into an active, dedicated contributor to the project. The engagement moved far beyond a one-off conference appearance into the realm of sustained open source stewardship. Navigating the complex technical challenges, solving core architectural issues, and successfully driving the implementation of the upstream project into downstream ecosystems became deeply rewarding professional pursuits.
As a testament to this genuine integration into the project team, the author was subsequently invited back to present updates to the community once again. This time, the invitation carried no connection to DEI ratios or compliance checklists; the gender balance of the presentation team was already established organically. The invitation was extended purely on the basis of merit, leadership, and ongoing contributions.
Reflecting on the arc of the experience, the author concluded that the initial discomfort and subsequent guilt were ultimately powerful forces for good. What began as an awkward encounter with institutional diversity mandates evolved into a mutually beneficial win-win scenario for everyone involved. Without that initial push—uncomfortable though it may have been—the author likely would never have discovered or engaged with the project, representing a tremendous missed opportunity for both the technologist and the open source community.
Acknowledging that this dynamic is likely experienced by many women and underrepresented technologists across the industry, the author offered an encouraging perspective to others who might find themselves in similar situations. When presented with opportunities that feel complicated by demographic mandates, there is no need to internalize guilt, feel weighed down by a sense of artificial indebtedness, or succumb to undue pressure. Instead, professionals facing these scenarios are encouraged to harness those complex emotions as fuel, turning initial discomfort into constructive action.
By accepting opportunities that offer professional growth and making the most of them, technologists can build a foundation from which they can later lift up and mentor others. Ultimately, that cycle of empowerment and shared effort forms the very heart of the open source movement—a culture defined as much by the human connections it fosters as by the technology it builds.
