By Divya Nekkanti
During high school, I looked unquestionably at technology leaders like Bill Gates and his wife Melinda, whose philanthropic foundation aimed to solve every apparent misfortune in the Global South. Even more, I found solace in the “giving back” days that Silicon Valley tech companies employed as a fulfillment of their corporate social responsibility.
But increasingly, no matter where I look–in the world, in my community, within myself–tech and development are misaligned. There seem to be two mutually exclusive avenues of engaging with the world–innovating or giving–the only overlap for which involves donating money to admirable causes or engaging in occasional volunteer service. This dichotomy between the fast-paced, disruptive tech world that doesn’t afford engineers the time to fully understand the complexities of social challenges and the slower-moving development sphere, where the redundancy of approaches and lack of human, financial, and tech capital hinder growth, have become more and more apparent to me in my experiences at Cal.
Perhaps this dichotomy was once not so strong, but as an Electrical Engineering and Computer Science (EECS) major today there’s a very distinct path you follow. You take onerous math and programming classes, cease at nothing to get accepted into the engineering or business consulting organizations that flood Sproul Plaza in the semester’s first few weeks, and then embark on a toxic pursuit of software engineering internships at Facebook, Google, Microsoft, Salesforce, Amazon, etc. You attend every info session, stand in hour-long lines to talk to a single recruiter, and apply to hundreds of companies without distinction as to why–all because the sole purpose of your “technical” education is to work at the biggest, most profitable software company in the Valley.
Application of knowledge becomes fixated on the destination rather than the journey, and despite going to a school as economically and experientially diverse as Berkeley, you get so lost in the allure of free T-shirts and food, the glitz and glamour, that social problems–even at the campus level–go unnoticed. Despite having few requirements outside the EECS major, the exhaustion from technical courses prompts you to deliberately pursue humanities courses that offer the highest average grade and lowest workload, rather than taking classes that actually pique your interest.
Disillusioned by this herd mentality and eager to explore a multidisciplinary Berkeley education, I decided to pursue a minor in Global Poverty & Practice. Taking on this minor was the best decision I made at Cal, as it is affording me an evaluative lens not only to examine determinants of poverty, but for the first time to critically analyze the bubble I have been living in for my entire life in Silicon Valley. A productive hiatus from my homogenous computer science courses, GPP is allowing me to daily interact with students from a broad array of majors and backgrounds, whose perspectives challenge my own and elevate every classroom discussion.
Yet despite the minor’s longstanding diversity, I see few engineers, even fewer computer scientists, in my GPP classes. At the same time, across campus I see few engineering and computer science students willing to confront the economic misfortune and inequality of access that exist beyond Soda Hall. With my eyes more open than ever been, I can now critically assess a variety of complexities: the tax evasion benefits and occasional alternate agendas behind philanthropic donations; the dependencies that result from inconsistent foreign aid; and the millions of laptops donated by the tech community’s One Laptop Per Child program, which never reached children in need.
Unlike the abundance of engineering courses that posit innovation must be accelerated to be disruptive (thus often fabricating problems to “solve” and oversimplifying ones that already exist), GPP courses are making me careful about my language, as I “practice” how to effectively address people in poverty (rather than naively think I can “serve” them).
Never anticipating the ability to reconcile my passions for tech and development, last summer I intentionally took on two very different internships: one with an NGO that focuses on education, economic empowerment, and equality for women and girls in developing regions; and the other an analytics consulting company.
At the NGO, I actively tried to refrain from imposing my software skills, as I was wary of oversimplifying the problems the nonprofit inwardly faced and outwardly worked on with redundant tech solutions. Yet day after day, the need for tech internally to scale the organization and externally to enrich the organization’s education programs, felt glaringly critical.
My most surprising discovery was the NGO’s high turnover, which appeared to engender bottlenecks like lack of data standardization. As employees came and went on their own volition, they stored years of donor and program information on different online services, in independent accounts, and with inconsistent formats. The irregularities on this scale of data made communication with donors and tracking of scholarship students nearly impossible, with half the incoming mail consisting of emails undeliverable as addressed. Seeing as the NGO was primarily funded by donors, the gravity of mismanaged data heightened by the day.
Even more of a hurdle was the lack of technology for educational programming and outreach. While the organization received Chromebook donations from Google, low electricity in the areas where the NGO work prevented deployment of the laptops. And while the girls finishing high school requested technical curriculum in robotics and web development, there was no one with the bandwidth to structure the programs. Meanwhile, in my second internship at the analytics consulting company, the resources seemed endless. If I didn’t like the size of my Mac, with a few clicks I could instantly order a new one. Unlike at the NGO, where I knew the faces and names of the women my work was directly affecting, working on software projects at a large tech company felt like coding in a black box. I was assured there were huge companies on the other end, transforming their businesses with the firm’s services, but my role in delivering this value was largely ambiguous and concerns were cursorily dismissed.
It was only during my practice at the nonprofit that I began to view challenges of sustaining an NGO and achieving development goals as technical opportunities. Sourcing data from all accounts, I wrote scripts to parse CSVs and standardize entry formats, transitioning the entire organization onto Salesforce’s nonprofit success pack for centralized donor and program management. I researched solar chargers and the historical reception of robotics and web development curricula in the NGO’s target regions, wrote cost/benefit analyses, and developed technologies for later deployment in schools.
With every task I completed and every proposal I pursued, I realized how invaluable technology in the social sector has the potential to be, especially in streamlining internal processes and scaling external facing projects. Connecting the two disparate dots in my life, I have felt fulfilled and inspired. I have realized innovation isn’t solely synonymous with the next iOS update, computer science has the power to impact the lives of the 99 percent, and the “technical vs. nontechnical” mentality we unconsciously employ fails to represent the very multifaceted and interdisciplinary approaches requisite in development.
As an engineer, I have gleaned that it is possible to transcend the stereotypical boundaries of a traditional tech job, that it doesn’t take the philanthropic capital of a billionaire to change the world, and most importantly that I don’t need to compromise my technical background to alter paradigms in the development sector. Instead, I can actionably address the assemblage of social issues that keep me up at night with the skills I learn during the day.
Divya Nekkanti ’20 is a UC Berkeley Electrical Engineering & Computer Science major and a Global Poverty and Practice minor from San Jose, California.
There is a saying in Swahili: “Maji Yaje Kwanza” which means “water is the first of many things”. The people of Mihingoni—most of whom are subsistence farmers—depend largely on rainwater for survival, but climate variability and long dry seasons continue to stunt crop yields. Low agricultural productivity decreases household income, and increases hunger. Lack of proper water, sanitation and hygiene leads to disease, and Kenya continues to have one of the worst under five mortality rates, globally. Families are forced to choose between sending their girls for water or sending them to school, and they choose water first. This limits the prospects for their future, and the cycle of poverty in Mihingoni continues. Until now.
“I didn’t want to make any assumptions about what the community needed, or what the solution should be,” Miller said. “The meeting was entirely spoken in KiGiriama, which allowed those most affected by the project to fully express themselves and their needs. We wanted to put the people’s needs at the center of all of our work.”
Global Poverty and Practice student, Marissa Kaye Scott, travels to Malawi to support the program making big impacts in the “warm heart of Africa”. Click 
