The Skill I Most Want to Develop: Communication by Naman

Naman's entry into Varsity Tutor's November 2026 scholarship contest

  • Rank: 204
  • 0 Votes
Naman
Vote for my essay with a tweet!
Embed

The Skill I Most Want to Develop: Communication by Naman - November 2026 Scholarship Essay

The Skill I Most Want to Develop: Communication

The academic skill I most want to develop further is communication, not because I am bad at it, but because everything I want to do next depends on doing it well, and I have learned how much of the work sits in the translation.

I am a computer science senior at Penn State, and most of my training has been in the opposite direction: precision, correctness, systems that either work or do not. I parallelized C++ simulations of Rydberg atom arrays on a supercomputer at Ursinus College. I am building an LLM inference engine from scratch in C++ and CUDA, every kernel written by hand. At IBM in Austin, I built AI tooling for tech sales, including a quoting agent that maps plain language to part numbers through watsonx. That work rewards exactness. A kernel that produces wrong numbers is wrong, and no amount of framing fixes it.

But the IBM summer also taught me the limit of exactness. The quoting agent only mattered if the salespeople using it trusted it, and trust did not come from the model being right. It came from whether I could explain, in their language, what the tool did, what it could not do, and why a particular answer was the one to use. I sat in rooms where a technically correct explanation landed flat because it answered a question nobody in the room had asked, and I watched a simpler explanation, one that started from the salesperson's actual problem, change the whole conversation. The engineering was the smaller half of the job. The communication was the part that decided whether the engineering got used.

My campus roles keep teaching me the same lesson from different angles. As a Resident Assistant for 73 students in Hibbs Hall, I have learned that the same message lands differently depending on who is hearing it, and that listening first usually tells me which version to use. As Communications Organizer for HackPSU, I do outreach to other universities, which means writing to strangers who owe me nothing and asking them to care about an event at a school that is not theirs. Both roles reward the same thing: saying the right thing, in the right shape, to the right audience, the first time.

That is the skill I want to keep developing, because my next step demands it. In July 2027 I start in Client Engineering at IBM through the Pinnacle Program, a role that sits directly between technical systems and the clients who have to live with them. I will be explaining AI tooling to people whose expertise is their business, not my code, and my success will depend on whether I can make a complex system legible without stripping out the parts that matter. A model I cannot explain is a model a client cannot trust, and a client who cannot trust the tool will not use it, no matter how good the engineering is.

So I want to get better at the parts of communication that are hardest to practice in a computer science curriculum: structuring an explanation around the listener's problem rather than the system's architecture, choosing the one example that makes an abstraction concrete, and knowing when to stop talking and let a question reshape the answer. I practice these in small ways already, in RA conversations and HackPSU outreach and the way I write documentation for the tools I build, but I want to treat them as a discipline, not a side effect. The goal is not to become a better presenter in the abstract. It is to become the kind of engineer whose work actually gets used, because he can carry it across the gap between the people who build systems and the people who depend on them.

Votes