Black men in tech face a particular set of pressures: being the only one in the room, the visibility problem, the promotion gap that nobody on the leadership team will name. This circle is for the practical work — interview prep, salary research, mentorship pairing, the question of when to stay and when to leave.
Brothers in Tech is the room for the particular career arc that runs through software, data, infrastructure, security, machine learning, and the adjacent disciplines. The tech industry has, over the last fifteen years, become a major destination for African and African-diaspora men with technical interests, and it has also become a major source of frustration. The salary outcomes are real. The career ladder is, in theory, legible. The lived experience — being one of two or three Black men in an engineering organization of several hundred — is often quietly exhausting. This circle is where that exhaustion is named, examined, and worked on.
The brothers in this room are at all career stages. There are juniors in their first eighteen months who are trying to understand whether what they are experiencing is normal or whether they are at a particularly difficult company. There are seniors who are deciding whether to go for the staff promotion that has been dangled for two years. There are staff and principal engineers thinking about engineering management. There are managers and directors thinking about the VP jump, or about leaving for a startup, or about going independent. The stage spread is the point. The brother ahead of you in the path has already negotiated some of what you are negotiating now.
The threads here are practical. Interview preparation for the technical screen, the system-design loop, and the behavioral round, with specific examples of what worked and what did not. Negotiation scripts for the offer stage, including the rarely-discussed art of negotiating with competing offers without burning the relationship at either company. The promotion-packet thread, where brothers share the structure of strong self-assessment documents and anonymized excerpts from documents that landed the promotion. The 'when to leave' thread, which is the most-read thread on the circle and is updated every quarter.
We talk about the visibility problem in tech specifically. Open-source contribution as a career lever — what it is actually worth and where the diminishing returns kick in. Conference speaking as a way to build a public reputation, and the trade-offs of doing it when you are also raising young children. Internal visibility through technical writing — design documents, postmortems, internal blog posts — which is undervalued by most engineers and which brothers in this room have leveraged into outsized career mobility.
We also talk about the questions that do not have clean answers. Whether to stay at a company that is doing work you are proud of while paying you less than market. Whether to join a Big Tech company you have moral concerns about for the salary that will let you support a parent, pay off school debt, and build a runway for a future of your own choosing. Whether to go to a startup with a strong technical founder and a weak business model. The circle does not pretend to know the right answer for your life. It does help you think clearly about your own.
A consistent theme is the math of staying versus leaving. Brothers who have been at one company for six or eight years often hit a comp ceiling that does not match what the external market would pay them. The strategic choice — leave for the larger offer, stay and grind for the promotion, stay and accept the gap — is not one-size-fits-all. The circle has produced careful threads on the trade-offs, including the often-overlooked cost of starting over in a new codebase and new political dynamic at thirty-eight when you are also raising young children.
We hold the room to a high bar on respectful disagreement. Engineering culture can be combative and dismissive. This circle is not that. Brothers ask hard questions, but they ask them with respect, and they assume the person on the other side has thought about their situation more than any single thread can capture. The result is a room where the advice is sharper than what most brothers find at their actual companies.
The pinned threads include the interview-prep meta-thread, the offer-negotiation script, the promotion-packet templates, a thread for first-time engineering managers, and a thread for brothers transitioning from IC to product, design, research, or business roles. New brothers should read those first. After that, post your own question — be specific about the company stage, your role, and the decision you are trying to make. The room answers well-scoped questions thoroughly.
