Women in STEM: Industry and Lab Bench

For Black and African-diaspora women across software engineering, hardware engineering, applied mathematics, life sciences, physical sciences, and interdisciplinary scientific work. The conversation here is technical first. We do not need to start every thread by explaining what an electrolyte is or what a stack trace is or what peer review actually entails. That is not a rule against accessible language; it is a baseline assumption about who is in the room. The technical fluency lets us get to the harder conversations faster.

Membership includes software engineers from intern through staff and principal levels. Machine learning researchers at industry labs and at research universities. Hardware engineers in semiconductors, robotics, and telecommunications. Biotech scientists at bench-level and at PI roles in academic and industry positions. Climate scientists. Civil and mechanical engineers. Mathematicians and statisticians. Computational biologists. The discipline list is long because Black women are doing the technical work across all of it, often as the only one in the room.

What we talk about. Technical decisions. The architecture choice you are carrying alone on a team where you are the senior IC. The grant proposal you are writing and the budget you cannot quite get to balance. The peer-review comment that landed wrong. The conference paper that needs sharpening. The patent application and whether to file. The decision about whether to publish early or wait for the bigger result. The IRB conversation. The animal-care protocol. The data-management plan that has to satisfy multiple funders.

Review cycles. The technical review where your reasoning was strong and the feedback was about something else. The promotion packet that did not move. The performance review that named a thing nobody had named to you in the moment. The two-year gap between your output and your title. The negotiation for the title you actually deserve. The decision about whether to fight for it where you are or carry the work with you to a place that will recognize it.

Hiring. The interview loops you have run and what you noticed. The candidates you championed. The candidates who got blocked at the close. The hiring manager who is trying and the hiring manager who is not. The conversation about pay banding for new hires that quietly hurt you when you negotiated your own offer. The work of refusing to let the next generation walk into the same dynamic.

The PhD conversation. The qualifying-exam strategy. The committee politics. The advisor who is generous and the advisor who is extractive. The decision to leave a program. The decision to stay. The thesis-writing work. The defense. The first postdoc and the second postdoc and the slow tenure-track search. The decision about whether to leave the academy for industry. The decision about whether to return.

The pipeline question. The undergraduate research experience you are now running and the women you are bringing through. The high-school programs you are mentoring at. The chapter of the National Society of Black Engineers or of the Black In X collectives you are running. The slow accumulation of a body of work that holds up and that brings other Black women along with it.

The technical-writing work. The blog post that became the talk that became the book. The Substack you are or are not writing. The conference circuit and what it has cost. The decision about whether to engage with technical Twitter and its successor platforms. The slow building of a public technical reputation alongside the internal work.

The lab politics. The collaboration that turned into authorship dispute. The co-author who left and took the project with them. The lab manager who was a lifesaver. The technician who has been there longer than anyone and knows where everything is. The funding bridge after the grant ended. The startup spinout decision.

Cadence: a daily channel for technical questions that need fast eyes. A weekly long-form thread on a single topic, rotated by discipline. A monthly virtual roundtable with rotating facilitators across disciplines. A quarterly technical talk delivered by a member on her own current work, with peer questions. An annual closed-door retreat for senior members on the discipline-specific structural problems that come with being further along the path.

Membership rules. Confidentiality on hiring details, compensation specifics, and internal company information. No recruiting blasts. We allow targeted individual outreach for roles, but cold mass posts go away. We allow paper and patent sharing with proper attribution. We allow code samples and project demos. We do not allow IP that you do not own to be shared from your employer to the network.

What we are not: a substitute for your professional society. A replacement for the formal mentorship structures inside your company or institution. A venue for technical disputes that should go through formal channels.

What we are: the room where you do not have to explain why a particular interaction was racialized before you can describe its technical content. The room where the question 'is this design good' gets a clean answer from a senior engineer who is not also evaluating your salary band. The room that knows what it costs to do this work and that holds you while you keep doing it. We are technical first and we are also each other's people. Both are the point.