On the Jukebox Podcast from WP Tavern, Nathan Wrigley speaks with Amy Kamala about the unlikely but powerful intersection of art, technology, and open source contribution. Amy’s path didn’t follow a traditional tech trajectory: she trained as a fine artist (MFA, UCLA) and gradually saw technology move from a supporting role in her artwork to the central focus of her career. Since 2018 she’s been an active WordPress contributor, serving multiple terms as a Hosting Team rep and more recently as a Core team rep.
A non-linear career
Amy’s professional story moves through customer-facing and technical roles at DreamHost, InMotion Hosting, Pantheon, Canopy Studios, local government, and freelance work. She started in social support at DreamHost in 2015, worked up through technical support and live chat, helped form specialized WordPress support, and collaborated on product initiatives with senior leadership. Later roles included tech lead at an agency, web development manager at InMotion (overseeing sites, servers, and DevOps pipelines), a brief stint at Pantheon, and a year-long contract building web tools for local government. More recently she’s freelanced and is sponsored by Elementor to contribute to WordPress.
Art and engineering: the same conversation
Amy explains that art and tech aren’t opposites. Her art practice—video, installation, interactive pieces—required technical skills (HTML, PHP, Linux, editing tools) long before she took a job in the tech industry. That blend gave her strengths in UX and visual thinking that translated well into web projects. She sees websites and software as experiential art: both aim to shape how people feel and interact. The same composition and color principles that guide fine art inform interface and user experience decisions.
A generalist who leads
Rather than specialize in a single technology, Amy developed a broad skill set: design, DevOps, accessibility, user experience, and team leadership. That versatility suited management roles where understanding multiple disciplines matters more than being the deepest specialist. She credits being outgoing and willing to ask questions—often publicly—for many opportunities and for the leadership roles she later held.
On learning by failing
Amy values being willing to look foolish in front of others as a learning strategy. She argues that making mistakes publicly creates memorable lessons and invites help. Her background in theater also taught her that audiences are usually rooting for you; that mindset helps reduce stage fright and encourages experimentation.
Finding WordPress and contributing
DreamHost’s push to become a WordPress host led Amy to the hosting team in the WordPress Slack, a gentle entry point because many of the initial contributors were people she already knew. That warm welcome was key—Amy stresses how important openness and patience are for onboarding new contributors. Small, low-barrier tasks like meeting notes or documentation are great ways for new contributors to start and build trust.
From there, her social nature helped her expand into other teams. Befriending contributors in communities like Ladies of WordPress led to invitations to participate in Core meetings and working groups. She volunteered for release squads (her first core release was 5.6) and later helped run release-process discussions. Visibility and willingness to help were recurring themes in how she grew her role.
Sponsorship and the cost of contributing
Amy’s contribution story includes both on-the-clock work and volunteer time. Early on she contributed while working long hours at DreamHost. Later, employers like Canopy Studios encouraged contribution (they set aside time for it), and InMotion formally sponsored her for ten hours a week. Sponsorship can make open source participation sustainable, but Amy notes she routinely invests more time than officially allocated because the work is meaningful.
Her current sponsorship came from an unexpected human connection. While attending WordCamp Europe and meeting people through shared cultural ties she built a relationship with Miriam Schwab from Elementor. That friendship led to a sponsorship offer; Amy now receives part-time support from Elementor to contribute to WordPress.
Why she gives time beyond the clock
Amy points to a mix of personal and professional motivations. Contributing creates friendships, deepens skills, leads to job opportunities, and provides meaningful involvement in a project larger than herself. That sense of meaning often precedes and enables professional benefit. She also believes organizations should hire people who can learn on the job and is an advocate of employers supporting contribution time.
What the WordPress community offers
Both Amy and Nathan reflect on the intangible pull of WordPress: a genuine, volunteer-driven ethos that creates strong human connections. Events amplify those bonds, making collaboration feel visceral and communal. Amy describes the community as authentic—people are there because they care, not just for profit—which in turn makes the project and events especially rewarding.
Advice for contributors and teams
– Be welcoming: a warm reception matters. New contributors need patience, guidance, and low-pressure ways to get started.
– Volunteer visibly: if you’re outgoing, use it. Visibility helps you build relationships and opens doors.
– Embrace failure: asking “stupid” questions and showing vulnerability speeds learning and attracts help.
– Start small: take notes, update docs, or do beginner-friendly tasks to get comfortable and build trust.
– Seek sponsorship where possible: employer support can make sustained contribution feasible.
Final thoughts
Amy’s story illustrates how creative and technical paths can merge into a career that’s driven by curiosity, community, and a willingness to learn publicly. For her, WordPress isn’t merely a platform to work on; it’s a place to build relationships, develop leadership, and contribute to something meaningful. The episode is a reminder that open source thrives when people bring not just skills, but heart.