about

I’m Alex. I make WordPress codebases boring to deploy.

Software engineer in Denver, Colorado. Twelve years of PHP, most of it on WordPress: plugins, block themes, multisite networks and the pipelines that ship them.

How I ended up caring about process.

I started building WordPress sites for local businesses in 2014. The sites worked, but every change was a risk: no version control, no staging, updates applied live on a Friday afternoon.

The turning point was inheriting a membership site that lost a week of renewals to a silent plugin conflict. Fixing it took a day. Proving it wouldn’t happen again took tests, CI and a deploy process. That’s the part I’ve specialised in since.

Today I work as a contract and in-house engineer on WordPress-heavy teams, and I run Bertex Design, a small studio for SMB clients. This site is about the engineering.

experience

Where I’ve worked

2022 — now

Senior WordPress Engineer (contract)

Product and platform teams

Plugin architecture, CI/CD rollouts and legacy refactors for teams running WordPress at scale.

2019 — now

Founder, engineering lead

Bertex Design

Run a small studio building and maintaining sites for SMB clients. Own the engineering standards and deploy tooling.

2017 — 2022

Lead Developer

Digital agency, Denver

Led a team of four. Introduced code review, Composer-based builds and automated deploys across 60+ client sites.

2014 — 2017

Web Developer

Freelance

Custom themes and plugins for local businesses. Learned the hard way why staging exists.

stack

Tools I use daily

Chosen for boring reliability. I’ll work in yours if it’s different.

languages
PHP 8.x, TypeScript, JavaScript, SQL, Bash
WordPress
Block themes, custom blocks, REST API, WP-CLI, multisite
quality
PHPCS/WPCS, PHPStan, PHPUnit, Pest, Playwright, axe-core
delivery
Git, GitHub Actions, Deployer, Composer, npm, Docker
infrastructure
Nginx, PHP-FPM, Redis, MySQL/MariaDB, Cloudflare
elsewhere
Astro, Eleventy, Laravel, Node

A good fit

  • Teams with WordPress in production and no one owning its quality
  • Codebases that need tests and CI before new features
  • Migrations where URLs and search traffic matter
  • Roles that value code review and written decisions

Not a fit

  • Theme-and-plugin installs with no custom code
  • Work that skips staging or review to hit a date
  • Projects priced purely on the lowest bid

Hiring, or need a second pair of eyes on a codebase?