The Quiet Algorithm of Belonging

The first time I felt “different” in a lab wasn’t because I didn’t understand the code. It was because I understood the silence.

Our community college research room was a converted storage space—two aging computers, a humming mini-freezer, and a whiteboard stained with old equations that never fully erased. I was the student assistant who stayed late, the immigrant kid who spoke carefully, as if each consonant had to pass through customs before it could leave my mouth. My supervisor, a kind but hurried graduate student, liked to say, “Science is objective.” I wanted to believe him. I also wanted to believe my work could speak for me.

Fluorescent Lights and Unspoken Rules

I found comfort in routines: pipette tips aligned like tiny soldiers, dataset columns cleaned until they looked almost elegant. I liked the moment when messy reality turned into something you could test—something that didn’t flinch when you asked it a question.

But later, in group meetings, I learned another kind of pattern recognition: who got interrupted, whose ideas were “building blocks” for someone else’s conclusion, and whose accent turned confidence into caution. When the conversation drifted to hiring or “fit,” I felt myself shrink, as if my body were trying to become small enough to avoid being evaluated.

I didn’t have the vocabulary for that feeling yet. I only knew it was exhausting to translate myself twice—first into English, then into acceptable English.

When Data Meets a Door That Won’t Open

The complication arrived on a Tuesday, disguised as opportunity.

Our lab posted a paid summer position in data analysis—exactly the kind of role that could bridge my interests in biology and software. I had already done the work informally: cleaning data, writing scripts, catching errors no one else noticed. I applied anyway, rehearsing my interview answers the way I used to rehearse introductions at family gatherings.

The interview wasn’t hostile. That was the problem. It was polite, smooth, and slightly out of reach—like watching people behind glass. I was asked where I was “really from,” whether I would “struggle” with communication, whether I could handle a “fast-paced culture.” None of those questions were about my code. All of them were about whether I would cause discomfort.

When the role went to someone else, I told myself it was merit. Then I saw my own script—my own function, my own comments—reappear in the project draft with another name attached to the work. No one called it theft. It was framed as collaboration. I stared at the screen, feeling heat rise to my face under the fluorescent lights, and wondered if I was being naive or simply convenient.

Small Acts of Courage, Iterated

I did what I always do when I’m confused: I documented.

I gathered version histories, saved timestamps, and wrote a calm email outlining my contributions. My finger hovered over “send” long enough for fear to become physical—tight throat, cold hands, the familiar immigrant instinct to avoid trouble. But something in me shifted. If science is built on reproducibility, so is fairness. If my work could be verified, then my voice could, too.

When the meeting happened, I expected dismissal. Instead, the graduate student looked genuinely startled. He apologized—awkwardly, imperfectly—and admitted he hadn’t noticed how credit was moving in the room. The lab revised the project record. I was added as a contributor. It wasn’t a parade. It was a correction.

Later, he asked if I’d help create a clearer authorship process for student assistants. I said yes, not because I trusted the system, but because I wanted to make it harder for silence to hide inside it.

What I Learned About Diversity That Isn’t Decorative

Around that time, I read that most Americans view racial diversity as a positive for the country. The number should have comforted me. Instead, it made me think about the difference between believing diversity is good and building spaces where diverse people are safe to be fully seen.

“Positive” is an opinion you can hold from a distance. Inclusion is a practice—messier, more specific, requiring people to notice who is missing from the center of the conversation and why.

I used to think my goal in STEM was to become undeniable: publish, code, design, outperform. Now I understand that excellence without equity can still reproduce harm—with cleaner graphs.

The Kind of Scientist I Want to Become

The resolution isn’t that everything changed. The lab didn’t suddenly become a perfect model of inclusion, and I didn’t stop feeling my throat tighten when I spoke up. But I learned that advocacy doesn’t always look like a speech. Sometimes it looks like keeping receipts. Sometimes it looks like sending the email anyway.

When I imagine my future—whether as a data scientist, a software developer in healthcare, or a biological technician working close to the raw human stakes of medicine—I picture building tools that respect people as more than variables. I want to design systems where credit is traceable, where decisions are explainable, where no one has to translate themselves into invisibility to be considered “professional.”

Under fluorescent lights, I learned how quickly silence can become policy. I also learned that one person, naming something true, can make the room recalibrate—like an algorithm correcting itself mid-run.

Reference Source Link

Pew Research Center (Mar 25, 2026): https://www.pewresearch.org/short-reads/2026/03/25/how-americans-value-racial-diversity-ahead-of-the-countrys-250th-anniversary/