Amy Kamala’s path into tech didn’t follow a predictable route. She started as a trained artist, earning an MFA from UCLA and making video installations, sculptures, and interactive works that leaned on technology. Over time the balance shifted: tech began supporting her art, and later art informed her technology work. That blend of creative and logical thinking now defines her approach to web development and open source contribution.
Early technical roots and varied roles
Amy’s first exposure to code dates back to learning HTML around 2000. Her early jobs mixed graphic design, web production, video editing and systems work — managing video assets, learning Linux at an animation studio, using FTP, and working with high-end editing tools. Those technical skills kept growing alongside her art practice.
In 2015 she joined DreamHost in social support, quickly moving through technical support, live chat and into a specialised WordPress support team. At DreamHost she trained people, handled escalations, helped document processes and even worked directly on WordPress-related product strategy. That job opened the door to numerous career pivots: tech lead at an agency, web development manager at InMotion Hosting (where she oversaw numerous web properties, servers, DevOps pipelines and teams), a stint as a solutions architect at Pantheon that didn’t quite fit, a year-long contract as a local government web developer, and then freelancing. Along the way she worked with Canopy Studios and is currently sponsored by Elementor to contribute to WordPress.
Art and tech: a productive overlap
Amy sees art and technology as complementary rather than opposed. Art is about creating experiences — movies, books, installations — and software and websites do the same for users. Skills from fine art translate directly into UI/UX work: composition, color, user-centered thinking. In web development particularly, there’s often crossover: many front-end developers have backgrounds in design or visual arts and excel at CSS and visual polish even if they aren’t deep into backend languages.
That hybrid perspective made Amy a versatile leader: she’s taken on DevOps, system administration, design oversight, accessibility, and team management. She’s quick to admit she’s a generalist rather than a deep specialist, but that wide umbrella is what enabled her to lead teams effectively.
On learning, failure, and visibility
Amy emphasizes two personal traits that shaped her career: curiosity and a willingness to look foolish in public. She repeatedly asked questions, reached out to people in her network, and jumped into meetings. That outgoingness made her visible — both in workplaces and in open source channels — and often led to opportunities.
She also values public failure as a learning mechanism. Making mistakes in front of others can be embarrassing, but it makes lessons stick. Amy uses the theatre idea that the audience wants you to succeed; that mindset reduces fear and encourages experimentation. Practically, she recommends asking lots of questions and not expecting flawless onboarding when you start contributing — everyone stumbles, and that’s part of the route to growth.
Finding WordPress and why she contributes
Amy’s involvement with WordPress began with DreamHost encouraging employees to participate in the project’s Slack channels and meetings. The Hosting Team — originally a collaboration between DreamHost and wordpress.org — provided a gentle on-ramp: familiar faces, welcoming team reps, and a low-pressure environment to start contributing.
From joining the Hosting Team in 2018, Amy became a team rep in 2019 and has served several non-consecutive years in that role. Her Core contributions grew after meeting people through Ladies of WordPress and branching into release squads and the release model working group. Her first Core release experience was with 5.6, and later releases like 6.9 and 7.0 broadened her exposure and responsibilities.
Sponsorship and balancing paid work with volunteer contributions
Amy’s contributions have been supported in different ways over time. DreamHost allowed her to work on WordPress during company time, Canopy Studios set aside a few hours per week for contribution, and InMotion officially sponsored 10 hours per week. Today Elementor sponsors her 10 hours weekly, though she often contributes far more hours because the work feels meaningful and the social connections are rewarding.
Why give extra time? Amy frames it as both personal and professional: contributing builds friendships, creates a sense of belonging, and connects her to a larger purpose. Professionally, leading teams and working on public projects strengthens her resume, hones skills, and opens job opportunities. The meaningfulness of contributing to something larger than oneself is what keeps many contributors engaged beyond formal sponsorship.
Practical advice for would-be contributors and hosts
– Be welcoming. Amy stresses the importance of how existing contributors receive newcomers. Patient, helpful onboarding and encouragement make a huge difference in whether people stick around.
– Start small. Low-pressure tasks — taking meeting notes, updating documentation, fixing small bugs — are great first steps that build familiarity and relationships.
– Ask questions. Reach out to people, introduce yourself, and don’t be afraid to look inexperienced; most contributors are happy to help.
– Be visible and volunteer. In open source, being willing to step up to run a meeting, join a release squad, or maintain a repo gets you noticed and builds trust.
– Embrace cross-disciplinary skills. Design sensibilities, UX thinking, and front-end styling are valuable in web projects and can set you apart even if you’re not a backend specialist.
The value of community and events
For Amy, the WordPress community offers authenticity and human connection. Events amplify the warmth of online interactions, creating intense, in-person bonds and a strong sense of collective purpose. That feeling of contributing to something meaningful, being part of a community that wants you to succeed, and doing work that has lasting impact is what she and many others find most rewarding.
Final takeaways
Amy Kamala’s story is a reminder that careers don’t have to be linear. Artistic instincts can enrich technical work, curiosity and audacity open doors, and open source communities reward meaningful participation with skills, friendships, and sometimes paid opportunities. Whether you’re creative, technical, or somewhere in between, there’s room to contribute — and often, that contribution becomes a defining and deeply satisfying part of your career.
