The Work No One Could See by sara

The Work No One Could See by sara - August 2026 Scholarship Essay

“You haven’t had the best communication.”

Out of everything I expected to hear during my software engineering internship, that sentence was not on the list. I had spent the summer building a cybersecurity web application almost entirely from scratch. It worked, people were interested in using it, and I was proud of how much I had figured out on my own. In my head, I was doing well. Then my manager gave me feedback that made me question whether I had been measuring “doing well” the wrong way.

My first reaction was honestly embarrassment. I wanted to explain that I had been working hard, even when I was quiet. Whenever I ran into a technical problem, I researched it, tested different solutions, and kept going until something worked. I thought that was what being independent looked like. I did not want to bother people with constant updates or ask questions I believed I could answer myself.

The problem was that my team could not see everything happening inside my head. They did not automatically know what I had finished, what I was struggling with, or why I made certain decisions. I had treated communication like an extra step that came after the “real” work. That conversation made me realize communication was part of the real work.

Afterward, I became more intentional about sharing my progress before everything was perfectly finished. I started explaining what I had completed, what I planned to do next, and where I needed clarification. I also learned to ask questions earlier instead of quietly spending hours trying to solve every problem alone.

This became especially important when I presented my project. The application collected information about a company’s public-facing technology and organized potential security risks. I understood how it worked because I had spent weeks building it, but not everyone needed the same explanation. A security analyst might care about the data and technical details, while a director might care more about how the application could save the team time. I learned that explaining my work well did not mean proving how technical I was. It meant helping the person in front of me understand why the work mattered.

That feedback followed me outside my internship too. I have always been the type of student who will stare at a programming problem for hours because I am convinced I should be able to figure it out alone. Persistence has helped me accomplish a lot, but I now understand that silence and independence are not the same thing. Asking a clear question does not cancel out the work I have already done. Sometimes it is the step that finally moves the work forward.

I still like being resourceful, and I still try solving problems before immediately asking for an answer. The difference is that I no longer wait until I am completely stuck to communicate. Whether I am working on a class assignment, building an application, or collaborating with a team, I try to share what is happening while there is still time for feedback to make a difference.

Hearing that my communication needed improvement did not feel encouraging in the moment. It felt like my hard work had been reduced to something I had done wrong. Looking back, however, I am grateful my manager said it directly. My internship taught me new technical skills, but that uncomfortable sentence taught me how to make those skills useful to other people. I entered the summer wanting to prove that I could build something on my own. I left understanding that the strongest work is rarely completed alone.