The Empty Seat at the Lab Bench

The first time I noticed the empty seat, it wasn’t dramatic. It was just a stool pushed slightly under a lab bench, untouched during a late-afternoon robotics session when the room smelled like solder and burnt plastic. Our team was loud—motors whining, laptops humming, ideas bouncing off the walls—but that seat stayed quiet, like it didn’t belong to anyone. I remember thinking, It’s just one seat. Then I looked around and realized it wasn’t just one.

In a room built for building things, there were invisible boundaries—who spoke first, who got handed the tools, whose mistakes were treated as “learning” instead of “proof.” I didn’t have language for it yet, but I could feel it in the air, as tangible as the heat rising from our 3D printer.

Where I Learned to Love Engineering

I grew up the kind of kid who collected broken objects like treasures. A dead radio wasn’t trash—it was a puzzle. My dad taught me how to hold a screwdriver properly, and my mom taught me something equally important: how to notice people. By the time I got to high school, engineering felt like the natural place for me—logic, precision, a world where the right answer existed if you worked long enough.

When I joined the STEM club, I expected a meritocracy. I expected equations to be the only gatekeepers. Instead, I found a culture with its own shortcuts: confidence mistaken for competence, familiarity mistaken for belonging.

The Moment That Changed My Definition of “Qualified”

The complication arrived quietly, almost politely.

A new member—Aisha—joined our club mid-semester. She was brilliant in a way that didn’t announce itself. She would listen, take notes, run tests twice, and then ask the question that made everyone stop talking. But during group work, she was often assigned “documentation” or “presentation slides,” as if the hands-on parts were reserved for someone else.

One afternoon, our prototype failed for the third time. The room tightened with frustration. Someone joked that we should “let the experienced guys handle it.” I laughed along—half reflex, half fear of becoming a target. Aisha didn’t laugh. She stared at the wiring diagram and said, calmly, “The power draw exceeds what the battery can supply. We’re starving the motor.”

She was right. Silence fell, followed by a scramble to revise the design. And still, when the tools came out, nobody handed them to her.

That was the moment I realized talent wasn’t the scarce resource. Access was.

Choosing Discomfort on Purpose

I wish I could say I transformed overnight into a fearless advocate. I didn’t. At first, I corrected small things—“Aisha should be on testing,” “Let’s rotate tasks”—and my voice shook when I said it. There were eye rolls, the subtle punishment of being ignored, the feeling of stepping outside an unspoken script.

But those moments added up. I started watching patterns: who gets interrupted, who gets credited, who gets mentored. I started practicing a different kind of engineering—designing a team culture the way we designed circuits, looking for points of failure and reinforcing them before they broke.

I proposed a rotating build schedule so every member touched the hardware and software. I asked our advisor to implement peer feedback that included collaboration, not just output. When someone repeated Aisha’s idea and got applause, I learned to say, “That’s what Aisha suggested earlier—can you expand on it?” The first time I did, my heart pounded like a faulty motor. The second time, it felt like tightening a bolt: small, necessary, secure.

What Inclusivity Actually Builds

On International Day of Women and Girls in Science, I read a statement from Engineers Australia calling for inclusivity across STEM—language that made my small club feel suddenly connected to something much larger (Engineers Australia, 2026). Their message didn’t frame inclusion as charity. It framed it as essential infrastructure: the way we ensure STEM reflects the world it serves.

That idea rearranged something in me. Inclusivity isn’t a poster on the wall; it’s a daily practice. It’s noticing the empty seat and asking why it stays empty. It’s building systems where belonging doesn’t depend on being the loudest voice in the room.

The Seat Isn’t Empty Anymore

By the end of the year, our team meetings sounded different. Not perfect—but different. We argued more openly and listened more carefully. New members spoke sooner. Tasks rotated without anyone acting like it was a favor. Aisha led our final testing sprint, hands steady, eyes sharp, as the robot finally ran its course without stalling.

The empty seat at the bench got claimed, not with a grand announcement, but with presence—tools laid out, notebook open, space taken.

And I realized the biggest lesson I’ve learned from engineering isn’t just how to solve problems. It’s how to recognize which problems count. When I step onto a campus that values both innovation and equity, I won’t just bring my love of building things. I’ll bring the habit of looking around the room—and making sure no one’s brilliance is left waiting at the edge of the table.

Source Link

Engineers Australia. (2026). Engineers Australia calls for inclusivity across STEM on International Day of Women and Girls in Science. https://www.engineersaustralia.org.au/news-and-media/2026/02/engineers-australia-calls-inclusivity-across-stem-international-day-women