
Women Who Build: How Tech Changed Their Career Path
Five women share the experiences that shaped where they are today and what they learned along the way.
Your career path rarely follows a straight line, and that’s perfectly fine.
What you think you want to do in college might look very different after your first internship, project, or job. Along the way, you start figuring out what you enjoy, what you're good at, and what kind of work energizes you.
That curiosity is exactly what led me to ask five women in AWS one question:
How did tech change your career path?
I got five very different answers. Some started in tech, while others came into it from completely different fields.
If you're still figuring out what you want to do, I hope there's something in their experiences that helps.
Jessica Gilmore: The Mission Stayed the Same

Jessica Gilmore didn’t start her career in tech. She started in education.
She worked as a faculty member, dean, associate provost, and associate commissioner, with much of her work focused on student success and helping more people access opportunities.
She didn’t originally plan to move into tech. But she kept seeing the same challenge: students wanted to learn and build skills for the future, but the right resources didn’t always reach the people who needed them.
“After years of working in higher education, I made the leap to tech because I saw an opportunity to scale the impact I care most about: empowering people to grow.”
At AWS, that mission has continued. As Jess put it, “I get to combine my passion for community building and development with the reach of technology, helping students and user groups connect with the tools and skills that shape their futures.”
The role changed, but the focus stayed the same: helping people grow and making opportunities easier to access.
Suely Barreto: Changing Direction Didn’t Mean Starting Over

Suely Barreto spent more than 15 years working as a doctor in Brazil before moving into tech.
Suely’s interest in tech started early. “I’d solve math problems to relax, the way other people listen to music.” When she discovered computer science in high school, it immediately felt like something she wanted to pursue. But at the time, she felt pressure to follow a more traditional path and became a doctor instead.
Years later, after moving to the United States, she decided to come back to the interest she had never really forgotten. She went back to school, learned about Ada Developers Academy through a conversation at a conference, and eventually joined AWS as an intern. Today, she’s a Software Development Manager.
Changing careers didn’t mean starting from zero.
A lot of what she learned in medicine still shows up in how she works today. She compares diagnosis to debugging and triage to prioritization. Medicine also taught her how to stay calm, explain difficult things clearly, and build trust with people.
“My unusual path was never baggage. It turned out to be my edge.”
The career changed, but the skills came with her.
Lahari Chowtoori: One Conversation Changed My Direction

Lahari Chowtoori went to grad school planning to become a data scientist.
While she was looking for a job, one of her professors was invited to present at UN Open Source Week and offered a few students the chance to attend. Lahari was one of them.
She had used open source software throughout school, but the conference gave her a different view of it. For the first time, she saw how open source projects are built, how people contribute, and the communities behind the tools she had been using.
After a panel, she introduced herself to the president of the Apache Software Foundation. That conversation led to introductions with other people at the conference, and within a month, Lahari had joined the team.
“That conversation at UN Open Source Week showed me a career path I didn’t know existed.”
Today, Lahari works on open source full time at AWS, including projects and foundations that much of today’s AI is built on.
Her own career started with one conversation at a conference, which is why she now sees networking as more than just meeting people. Conferences and meetups can be a chance to connect with the people building the tools and projects you’re interested in.
She also wishes she had known earlier that students don’t have to wait until graduation to get involved.
“I wish someone had told me back then that I could contribute to open source projects like Jupyter or Apache projects, which I used constantly in data science.”
And contributing doesn’t mean writing code. Community building, governance, policy, organizing events, and helping shape a project roadmap can all count as real experience, and students can start long before graduation.
Jenny Feldman: Changing Industries Didn’t Mean Starting Over

Jenny Feldman started her career in New York magazine publishing, working at ELLE and later Condé Nast.
As publishing became more digital, she started noticing how quickly audience expectations were changing. Readers wanted content that felt more personal and was available right away. She loved marketing, but she also became increasingly interested in the technology and systems behind it.
In 2011, she joined Amazon to help launch MyHabit, a fashion flash-sale site. The role gave her a chance to combine what she already knew about fashion and audiences with Amazon’s technology, data, and scale.
From there, her career kept evolving. She went on to lead retention for Amazon Prime, run Amazon Teens, and eventually moved to AWS after becoming curious about a completely different side of the business.
Today, her team builds tools and AI systems that AWS marketers use to run everything from re:Invent to account-based marketing meetings. She also leads work focused on AI productivity, workflow automation, and helping teams use AI tools more effectively.
As Jenny put it, “Changing industries and domains a few times in my career didn’t mean starting from zero.”
She still uses lessons from publishing today, especially around storytelling, moving quickly, focusing on outcomes, and staying close to the customer.
“Publishing taught me to move fast on deadline, cut what doesn’t matter, and never lose sight of the customer.”
Kat Esser: Impact at Speed + Scale

Kat Esser didn’t start her career in tech, but she’s spent it democratizing technology as a force multiplier for really hard problems: the ones that determine whether individuals, and the community around them, gets access to essentials like health services, food, housing and education.
Kat’s purpose found her early. When she was young, her father spent significant time inside our health system with a terminal condition. Seeing this system up close, its gaps, its blind spots, and the long stretches where better information or better access could have changed everything left her with a conviction that drives her work with purpose: that the distance between a single person and the care they need is a solvable problem, not an inevitable one.
That conviction sent her to graduate school to study the intersection of design, business and technology, where she sharpened a question that still drives her work: what is possible when healthcare breaks free of the four walls of the hospital?
As Kat put it, “I haven’t always worked in technology, but technology has always been a part of my work.”
Before AWS, she spent more than 20 years building social innovation programs across the public and private sectors, much of it focused on a truth: that the communities with the greatest health needs are too often the last to benefit from innovation.
Every chapter of that journey, the lived experience, the academic questions, and two decades of social innovation, pointed to the same realization: the problems worth solving are too big for any one person to solve alone, but they become solvable when the people already closest to them are handed the right tools.
Today she is Principal Global Impact Accelerators for AWS Skilling and Social Impact, where she launched the Social Entrepreneur Accelerator (SEA), pairing business and technical support social enterprises building AI and cloud technology solutions for education, health and climate resilience.
Now she helps startups around the world use AI and cloud to solve hard problems and reach the people they serve at speed and scale.
“Working at AWS, I have come to realize that the means to agency is through equitable technology.”
Her path shows how personal experience shapes problems worth solving— while democratizing AI and cloud extends how far the solutions can reach to make positive human impact.
So, What Do These Stories Have in Common?
Their paths looked different, but I noticed a few things that came up more than once.
Most didn't have every step figured out from the beginning. They learned more about what interested them by getting experience, trying new things, and talking to people doing work they wanted to understand better.
I think that matters when you're early in your career and feel like every decision is permanent.
The major you choose matters, but it doesn't lock you into one career. The same goes for your first internship or your first job. As you get more experience, you're going to learn more about the kind of work you enjoy and where you want to grow next.
A Few Things You Can Try
Whether you're exploring tech through your school or community, or learning from somewhere else in the world, here are a few things you can try as you figure out what interests you.
- Ask Someone How They Got Here
When you meet someone, whose work sounds interesting, go a little further than asking what they do.
Try asking: "How did you end up doing what you do now?"
You’ll usually learn a lot more about how they got there.
- Explore Something Outside Your Plan
Try one thing you normally wouldn’t.
That could mean attending a session about a technology you haven't worked with, talking to someone in a role you've never considered, or learning more about another part of the industry.
If you're studying engineering, you might find yourself curious about product or design. If AI is your main interest, maybe spend some time learning how people work in cloud infrastructure, security, or data.
You don’t need to walk away wanting that job. The point is just to learn something you didn’t know before.
- Have a Few Good Conversations
It can be tempting to measure networking by how many people you meet, but you don't need to speak to everyone.
If someone's work interests you, ask them about it. Find out what skills they use, how they got started, and what they would recommend learning if you wanted to explore the same area.
If you have a conversation you want to continue, make a note of it and follow up afterward.
- Pick One Thing to Try Next
You'll probably come across more ideas than you have time to act on.
Pick one that you genuinely want to explore. It could be a technology you heard about, a small project you want to try, a role you want to research, or a person you want to stay in touch with.
You don't need to figure everything out at once. Just pick one thing you want to explore next.
Keep Exploring
If something you discover gets you curious, you don't have to stop there.
Builder Center gives you a place to keep exploring. Students can sign up for free to access student benefits, join free workshops, learn from other builders, discover what people are building, and share what they’re exploring too.
And I’d love to hear from you: Has tech already changed the direction of your career, or is there an area of tech you’re interested in exploring next?
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article