Taylor Waldon is the Director of Technical Product Ownership for Platform Extensions at Fueled, where she works with teams building apps, integrations, and platform-connected products across the web. She has spent years in the WordPress ecosystem across product and marketing roles with companies including LearnDash and GiveWP. A repeat WordCamp speaker, Taylor is known for making complex technical and product conversations approachable, practical, and grounded in real-world experience. She lives in the California high desert with her dogs, where she spends her free time building trails, wandering the desert, and trying to stay at least a little offline.
Q&A with Taylor
Who or what helped you find your footing in WordPress, and how do you try to pay that forward today?
The old, tiny GiveWP team from 2018. I started just after Michelle Frechette and Amanda Gorman. At that time, I was fresh to the software product world, though I had been using WordPress for years before that at an agency, and before that as a hobby. Amanda and Michelle both taught me a lot about customer expectations in WordPress and how to handle them. Matt Cromwell and Devin Walker both taught me a lot about the WordPress community overall. Matt and I both really honed in together on how best to boost GiveWP marketing. Around then, it really thrived for a solid several years as a product and pillar in the WordPress community. I’m really proud of that, because it was a team effort and literally every person on the team was invested and involved in its success. Back then, Ravinder Kumar answered tons of my technical questions, even when they probably sounded a little dumb to an engineer, which ultimately helped me go from nontechnical to technical over time. Kevin Hoffman also taught me tons about product management and was probably the first spark that inspired me to move into Product from Marketing later on in 2024. When he came on board, Jason Adams taught me tons about systems thinking, backend engineering, and honestly how to speak to a developer and translate between types of stakeholders on a project- which is really important in my day-to-day work now. Ben Meredith taught me what to expect from a support team as a customer, marketer, and product manger. Now every bug ticket triage review has Ben’s voice in my head. That whole original team really triggered my career in WordPress and helped get me to where I am now. Now that I’ve landed at Fueled, I try to bring everything I learned to my current role and teach others what I’ve learned where it applies. In the WordPress community, I participate when and where I can to help bring what I’ve learned to others.
If you could engineer one connection at WCEH 2026 — a conversation, an intro, a collaboration — what would it be?
This is a really good question, and I’m not sure. Every career-changing conversation I’ve had at a WordCamp has been completely accidental. If I’d tried to scheduled it ahead of time, it probably never would have happened. The best part about these events is wandering into a hallway conversation, sitting down to eat with someone you’ve never met, or sticking around to talk about a session afterwards. I’d rather leave room for that kind of organic inspiration than manufacture it.
WordPress powers 43% of the web, but it’s the people who keep it alive. What’s a moment in this community that reminded you why you stay?
Probably getting laid off, which sounds backwards. But the reason that I landed on my feat at that time was this community and my time networking at WordCamps. Through an interesting series of events, I not only found a new position quickly, but Fueled found me just at the moment where I realized that first new position wouldn’t work out long term. Now I’m part of helping shape the future of a team I’m really excited about and even more deeply embedded in the community that helped me when I needed it most.
What does the WordPress community get right that other tech communities don’t. What could we still do better?
I struggle with this question a little. I think it’s because I don’t think about it as a “tech” community as much as where I found my place. WordPress attracts people from all kinds of backgrounds. Plenty of us, me included, didn’t start out as engineers and still found a place where our skills mattered. That’s probably what WordPress does best. What it could do better is perhaps welcoming in these folks and making it easier to navigate the waters. Coming in fresh is not easy for a newcomer, especially one who came from a nontechnical background.
What’s a form of contribution you think is undervalued, and why does it matter?
Communication. Documentation, UX writing, support, translating between engineers and users… all of that gets taken for granted because it’s invisible when it’s done well. I’ve spent most of my career somewhere in the middle, taking technical information and turning it into something people can use or turning user needs into feasibly technical solutions. AI can draft documentation and requirements all day long, but it cannot understand people the way humans do. Somebody still needs to bridge that gap, and that is a hard skill to come by in tech.
A lot of people want to contribute but feel they’re not technical enough. What would you say to them?
I used to be one of those people. I wasn’t writing code (still don’t), but I started out by learning just enough to keep up with engineers until that bloomed into a highly technical background. My focus has always been on what customers actually need combined with what will grow the business in the market. Those are valuable skills to have. WordPress needs writers, designers, support specialists, testers, organizers, product people, marketers… a full team of real humans with a wide set of skills, to make it work