How do you land a WordPress job? In 2021, Cory Millercolleague and I answered that across five episodes of the Get Hired podcast from Post Status. Each episode took one step: find the jobs, pick a direction, learn the basics, build a portfolio, meet the community.
🎙️ About the Get Hired podcast
- Show: the career series from Post Status, episodes 1 to 5
- Hosts: Cory Miller, then CEO of Post Status, and me, Courtney Robertson, then a web designer and developer advocate at GoDaddy
- Published: August 25 to September 27, 2021
- Episode notes: How to Get a Job in WordPress; Figuring Out What You Want to Do in the World of WordPress; Essential Skills in the Remote WordPress Workplace; Start a Project; and Get Involved, all on Post Status
🧭 What the Get Hired podcast covered, episode by episode
Episode 1: what jobs exist in WordPress?
We launched the show for anyone starting or growing a career in WordPress. The first conversation covered the kinds of WordPress jobs available and where employers post them.
The publisher’s notes also laid out the season plan. Decide what you want to do, learn the minimum skills and tools, start a project, then join in. Each later episode took one of those steps.
Episode 2: how do you decide what you want to do?
Episode 2 focused on that first step. We talked about figuring out what you want from a WordPress career. Then we covered how to identify the minimum skills and tools you need to get there.
WordPress work spans support, development, design, writing, marketing and more. So the direction you pick decides what you learn next.
Episode 3: what skills does every remote WordPress job expect?
Episode 3 covered the basic competencies for remote WordPress work, whatever your role. The show notes start with a WordPress.org account and a complete profile. Next, learn the vocabulary of the support forums and the developer site.
After that, get familiar with the plugin and theme directories and the admin screens. Security basics come early: strong passwords, a password manager and two factor authentication. Then come domains, web hosting, software versioning, and remote team tools such as Slack, Zoom and Google Workspace.
Episode 4: how do you build a portfolio from scratch?
Many roles expect a portfolio alongside a résumé, even when the posting doesn’t say so. Our answer for people with nothing to show yet: start a project.
The show notes suggest starting a WordPress blog and sharing what you learn as you learn it. Embed code you’ve written, too. You can also start or contribute to a code project, then link your GitHub portfolio from your WordPress.org profile.
Episode 5: where do you meet the WordPress community?
The fifth episode covered the many ways to take part. We talked about meetups, WordCamps and other web tech meetups. We also named communities such as Post Status and Big Orange Heart, which supports remote workers’ wellbeing.
The notes point to Slack groups as well. Those include regional WordPress groups and product communities like Beaver Builder and WooCommerce. Others serve business owners, women and BIPOC in WordPress. Then the simplest advice: engage, and share what you know.
🧪 What can you take from the Get Hired podcast?
- Job seekers: list the WordPress roles that interest you before you polish a résumé.
- Career changers: pick a direction first, because it narrows which skills to learn.
- New job seekers: set up your WordPress.org profile this week, since employers can find it.
- Everyone: turn on two factor authentication before your first day.
- Beginners: a site where you write about what you’re learning is a portfolio piece.
- Newcomers: attend one local meetup and introduce yourself to the organizer.
- Remote workers: join one community Slack and answer a question you know.
For more conversations like these, browse my speaking and podcast archive.
🗓️ Archival note
This post carries the date Post Status published the first episode’s notes. On November 9, 2026, I added the five episodes as separate posts, then combined them here the same day. Castos hosted the audio, and that address no longer loads. So this summary sticks to what the published notes say. The old episode addresses now redirect to this post.