Tell us about yourself!
I'm Saranya Vedagiri, a Member of Technical Staff at eBay, where I work on building scalable, high-performance systems that support the backbone of global e-commerce. I’ve always been drawn to solving complex engineering problems—whether it’s optimizing legacy systems, addressing technical debt, or architecting new services that impact millions of users. Over the years, I’ve had the opportunity to work across multiple layers of the tech stack, which has helped me develop a holistic understanding of how robust systems are designed and maintained.
What truly drives me, though, is the intersection of people and technology. I care deeply about mentoring early-career engineers, sharing knowledge, and creating spaces where innovation can thrive. I'm a strong advocate for diversity and inclusion in tech, and I believe that empowering more women to pursue technical leadership roles is critical to the future of the industry.
Outside of code, I enjoy diving into conversations around engineering culture, process improvement, and the role of continuous learning in shaping impactful careers. Whether I’m debugging a gnarly issue or speaking at a community event, I try to bring curiosity, empathy, and a builder’s mindset to everything I do.
Why did you choose this field in the first place?
I’ve always been fascinated by how things work—from taking apart gadgets as a kid to writing my first lines of code in school. But it wasn’t just the logic or structure that drew me in; it was the creativity behind problem-solving in tech that really hooked me. Software engineering offered this perfect blend of structure and imagination—it wasn’t just about writing code, but about building things that could actually make someone’s day a little easier or better.
What sealed it for me was realizing how much impact technology has on everyday lives. I wanted to be part of that change—to build systems that scale, to solve real-world problems, and to constantly evolve along with a fast-moving industry. Being in this field has given me the chance to learn endlessly, collaborate with incredibly smart people, and contribute to products that reach millions. That sense of purpose and constant growth is what keeps me inspired.
What tech are you most excited/passionate about right now and why?
Right now, I’m most excited about technologies that improve developer experience and system scalability—things like platform engineering, observability tools, and advancements in cloud-native architecture. As systems grow more complex, the ability to build resilient, self-healing, and performant platforms becomes critical. I’m particularly interested in how internal developer platforms are evolving to abstract away complexity and enable teams to move faster without sacrificing quality or stability.
I’m also passionate about the conversations happening around technical debt—how we measure it, manage it, and most importantly, build cultures that prioritize long-term maintainability over short-term fixes. These aren’t always the flashiest topics, but they’re foundational. Getting them right is what allows innovation to happen at scale and sustainably. To me, that’s where some of the most meaningful tech work is happening right now.
What tech are you most worried about right now and why?
One area I’ve been increasingly concerned about is the unchecked complexity that can come with rapid adoption of emerging technologies, especially in large-scale systems. While tools like Kubernetes, microservices, and event-driven architectures offer incredible flexibility and power, they also introduce a level of operational overhead that can be difficult to manage if not approached with clear intent and discipline. It’s easy to end up with a tangled web of services, unclear ownership, and systems that are hard to debug or scale.
Another thing that worries me is when innovation gets prioritized at the cost of maintainability. The pressure to move fast sometimes leads teams to take shortcuts, defer critical tech debt conversations, or adopt trends without fully understanding the long-term implications. Over time, that can lead to brittle architectures and developer burnout. I think the tech community is becoming more aware of these risks, but there’s still a long way to go in normalizing conversations around sustainable engineering practices.
What are your hobbies and interests outside of tech?
Outside of tech, I love to unwind through painting and sketching. Whether it’s mural art, acrylics, or oil painting, I enjoy working with different styles and mediums—it’s a calming and creative outlet that helps me reset after a busy day. There’s something really satisfying about starting with a blank canvas and slowly seeing a piece come to life, one brushstroke at a time.
I don’t always get long stretches of time for it, but even spending an hour here and there sketching or adding layers to a painting helps me recharge. It’s a nice contrast to the structured logic of software engineering and gives me space to explore a different side of creativity.
Let's talk about breaking the glass ceiling. What were the biggest challenges you faced as a woman in tech, and how did you deal with them?
One of the biggest challenges I’ve faced as a woman in tech is navigating environments where you often feel like you have to prove yourself a little more, whether it's being the only woman in the room or having your contributions overlooked until someone else echoes them. Early in my career, I struggled with impostor syndrome, especially in fast-paced teams where confidence often spoke louder than competence. Over time, I realized that staying quiet wasn't helping anyone—not me, not the team, and definitely not other women watching from the sidelines.
What’s helped me most is building a strong support system - mentors, peers, and women in tech communities that remind you that your voice matters and your perspective brings value. I’ve also learned to advocate for myself more directly, to ask for opportunities, and to speak up even when it feels uncomfortable. I’ve seen firsthand how representation matters, and now I try to pay it forward by mentoring others and creating space for more inclusive conversations around growth and leadership.
Any questionable misogynistic story/situation you faced/handled, and you want to share with the HackerNoon Fam?
There have definitely been moments where subtle biases showed up, often not in loud or obvious ways, but in the smaller interactions that add up over time. Early in my career, I was once in a technical discussion where I shared an idea that was dismissed pretty quickly, only to hear the same idea repeated by a male colleague a few minutes later, and suddenly it was well received. It wasn’t malicious, but it was a clear example of how unconscious bias can play out in real time.
At the time, I didn’t know how to respond, so I let it go. But that experience stayed with me. Since then, I’ve learned to gently call it out, either in the moment or in a 1:1, by saying something like, “That’s actually what I was suggesting earlier, and I’d love to build on it further”. It’s a subtle nudge, but it reclaims the space and also signals that these moments matter.
I’ve also seen a big shift in awareness over the years, and I think continuing to have open conversations about these experiences—especially in public forums like this, helps move the needle for the next generation of women in tech.
What was the biggest setback/failure that you faced, and how did you manage it?
One of the biggest setbacks I faced was a few years back, during the earlier part of my career, when I took end-to-end ownership of a feature implementation. While the development process went fairly smoothly, it was during thorough end-to-end testing that we discovered few critical use cases had been missed. The core functionality worked, but we hadn’t accounted for a range of real-world scenarios that the feature would eventually need to support.
Looking back, it was a turning point for me. It highlighted just how essential cross-functional collaboration is—not just during execution, but right from the planning stage. I worked closely with test engineers, product managers, info sec teams, DBAs, and domain-specific teams to revisit the design and ensure we were building something truly robust. Each team brought insights that helped us uncover edge cases and hidden dependencies we had initially overlooked.
It was a challenging experience, but one that shaped my approach moving forward. It taught me the importance of asking the right questions early, involving the right stakeholders, and never underestimating the complexity of real-world usage. More than anything, it reminded me that growth often comes from the moments that stretch us the most.
What's your biggest achievement that you're really proud of?
Honestly, my biggest achievement isn’t tied to just one project or milestone—it’s the fact that I’ve been able to sustain and grow in this fast-paced industry for over 18 years while continuing to do meaningful, impactful work every single day. Tech evolves rapidly, and staying relevant means constantly learning, adapting, and pushing yourself beyond your comfort zone—and that’s something I’ve embraced throughout my journey.
From building scalable systems and improving platform performance to mentoring engineers and navigating complex cross-functional initiatives, I take pride in consistently showing up, delivering value, and growing along the way. There have been challenges, of course, but what makes me proud is the ability to keep evolving, to stay curious, and to contribute in a way that’s both technically sound and deeply collaborative.
It’s easy to celebrate the high-visibility wins, but I find the greatest fulfillment in the consistency—the quiet, steady progress, the technical choices that make systems better behind the scenes, and the positive ripple effect of investing in people and teams. That, to me, is a lasting achievement.
In your opinion, why do we see this huge gender gap in the tech industry, and how can we reduce it?
The gender gap in tech is largely rooted in systemic and cultural barriers, starting from limited early exposure to STEM, to a lack of visible role models and subtle biases in the workplace. Over time, these factors can discourage women from entering or staying in the field.
To close the gap, we need to start early by making tech more accessible and inclusive for girls, and continue that support through mentorship, fair hiring practices, and inclusive work cultures. Representation at all levels is crucial—but so is creating environments where diverse voices are genuinely valued and heard. Those of us in the industry can play a big role by mentoring, advocating, and leading by example.
Who is your tech idol? Why?
I don’t have just one tech idol—I find inspiration in people from different backgrounds, both within and beyond the tech world. I truly believe that leadership, resilience, and innovation aren’t limited to any one field, and there’s so much to learn from a range of voices.
Indra Nooyi is someone I deeply admire for her practical leadership style and her strong emphasis on building support systems for women to grow. Her clarity of thought, strategic mindset, and her advocacy for long-term, systemic change really resonate with me.
I also find a lot of inspiration in Oprah Winfrey—not for her connection to tech, but for the way she communicates with intention, leads with empathy, and has carved out her own path through sheer determination and authenticity. The way she connects with people and turns personal stories into powerful movements is something I truly admire.
For me, learning never stops. I find value in hearing different perspectives—whether it’s from industry leaders, teammates, or even people just starting out. Everyone has a story, and those stories often spark new ways of thinking.
Do you have any advice for aspiring girls who want to join the field?
My biggest advice is this: focus on building a strong foundation and a mindset of continuous learning. In today’s world, there are countless tools, frameworks, and technologies—and while they’re helpful, they can also be overwhelming. Don’t get caught up in trying to learn everything all at once. What really matters is understanding the core concepts, developing problem-solving skills, and staying curious.
Tech is always evolving, and tools will come and go. What stays with you is how you think, how you approach challenges, and how willing you are to learn and adapt. It’s okay not to know everything—no one does. What’s important is to keep asking questions, seek mentors, and give yourself permission to grow at your own pace.
Also, don’t underestimate your voice. You belong here, and your perspective matters. The industry needs more diverse thinkers, and by showing up, you’re already paving the way for others.
HackerNoon editorial team has launched this interview series with women in tech to celebrate their achievements and share their struggles. We need more women in technology, and by sharing stories, we can encourage many girls to follow their dreams. Share your story today!