Amy Kamala’s path into technology didn’t follow the usual script. With a Master of Fine Arts from UCLA and a long history in video, sculpture, and digital art, she gradually shifted from art supported by tech to tech supported by art. Since 2018 she’s been an active WordPress contributor, serving as a team rep on the Hosting Team for several years and more recently as a Core team rep. Her career has passed through DreamHost, InMotion Hosting, Pantheon, Canopy Studios, local government, and now freelance work while being sponsored by Elementor for open source contributions.
From art to code: complementary mindsets
Amy’s creative training plays directly into her approach to web development and user experience. She points out that art is fundamentally experiential: it creates relationships between a viewer and an object or moment. Good software and websites do the same. Composition, color, and UX thinking carry over from fine art into interface design. While she admits she isn’t a specialist in any single programming language, her background gives her the instincts to lead teams where both design and functionality matter.
Her technical journey began early — she learned HTML at 18 and later used PHP, Perl, Linux, and command-line tools to build interactive art and manage video workflows. Those experiences made it natural to move into support, DevOps, and ultimately web development management. Rather than seeing art and tech as opposites, Amy treats them as overlapping toolsets that make her a better collaborator.
A broad skill set, and the pros and cons
Amy describes herself as a generalist who’s comfortable across DevOps, design, accessibility, and management. That range has helped her in leadership roles: she can communicate across disciplines and understand trade-offs. The tradeoff is that she hasn’t specialized deeply in one technical niche, which she sometimes regrets, but her people skills and organizational strengths have steered her into roles where breadth matters.
Embracing failure in public
One recurring theme is Amy’s willingness to ask “stupid” questions and fail publicly. She’s found that being outgoing, asking for help, and accepting embarrassment are powerful learning tools. Her theater experience reinforced the idea that audiences want you to succeed; that mentality helps reduce the fear of screwing up in front of peers. In her view, people in open source are often supportive and eager to help, and making mistakes is a way to learn more quickly and remember lessons.
How she found WordPress contribution
Amy’s involvement began at DreamHost, where the company encouraged employees to participate in WordPress.org. The Hosting Team grew out of those efforts, and because many contributors she already knew were in the room, her first meetings felt like a warm, easy landing. She volunteered, asked lots of questions, and became visible — which led to leadership responsibilities. Her outgoing nature and willingness to take on tasks like meeting notes or documentation helped her gain traction.
Over time she branched into Core, ran release model working group meetings, and joined release squads for major releases. The path was often accidental: friendships formed in Slack or at WordCamps led to new opportunities. That serendipity eventually resulted in sponsorship; after meeting people at events and building genuine connections, Elementor offered part-time sponsorship for her contribution work.
Sponsorship and time: why she contributes beyond the hours
Amy is sponsored for roughly ten hours a week but frequently contributes far more. She explains that the work is personally meaningful: it connects her to people, to projects larger than herself, and to a community that she values. Contribution has led to friendships, jobs, and professional opportunities. She also gains concrete skills — repo maintainership, release coordination, and team leadership — which bolster her resume.
Beyond personal benefit, Amy highlights an important cultural point: many people come to WordPress because of shared values, not pure profit. For her, that meaningfulness is primary. The skills and career benefits follow. She argues that companies should be willing to hire people who don’t know everything and train them, because learning on the job is powerful and inclusive.
Advice for contributors and teams
– Be welcoming. People who receive new contributors warmly make a huge difference. Extra patience and guidance pay off in strong relationships and long-term value.
– Start small. Low-pressure tasks like updating documentation or taking meeting notes are great entry points for new contributors and help build visibility and trust.
– Ask questions. Don’t be afraid to look foolish; public mistakes teach fast and stick.
– Volunteer visibility matters. In remote communities, being outgoing and consistent helps you get noticed and invites responsibility.
– Organizations that sponsor contributors should expect contributors to give more than the allotted hours; many contributors do this because it’s meaningful work.
The WordPress community’s deeper value
Amy and Nathan both return to the same observation: the WordPress community is driven by authentic, often non-commercial motivations. Volunteers come together to build software, run events, and support each other. That shared sense of purpose creates an experience people want to be part of — at meetups it intensifies into a feeling of belonging, mutual support, and doing something meaningful together.
Final thoughts
Amy Kamala’s story shows how non-linear careers can flourish at the intersection of art and technology. Her blend of curiosity, social courage, and cross-disciplinary experience has made her a visible and effective contributor. For anyone considering contributing to open source: bring curiosity, be willing to fail, start with small tasks, and cultivate genuine connections. The community will likely surprise you with how welcoming and rewarding it can be.