software engineer · denver, co

WordPress engineering held to the same standards as the rest of your stack.

I’m Alex Bertens. I build custom WordPress applications, plugins and block themes with typed, linted, tested code, peer-reviewed pull requests and automated deploys you can roll back in one command.

profile.json v2026.11
focus
WordPress plugins, block themes, Gutenberg
languages
PHP 8.3, TypeScript, SQL
standards
WPCS, PSR-12, PHPStan L8
delivery
GitHub Actions → staging → prod
experience
12 yrs · 140+ production sites

Available for contract and full-time roles

01 / how i work

Engineering requirements, not afterthoughts.

Every project ships with the same baseline. These aren’t line items I add on request; they’re how the repository is set up on day one.

01

Coding standards

Lint and static analysis run locally and in CI. Code review is required on every merge, including mine.

WPCS · PSR-12 · PHPStan · ESLint · Stylelint

02

Security by default

Validate input, sanitize on save, escape on output. Nonces and capability checks on every privileged action.

least privilege · nonces · composer audit · npm audit

03

Version control

Short-lived feature branches, small PRs, conventional commits and tagged releases with generated changelogs.

trunk-based · PR templates · semver

04

CI/CD

Every push builds and tests. Deploys are atomic, gated on staging approval, and reversible in seconds.

GitHub Actions · Deployer · wp-env

05

Automated testing

Unit tests for logic, integration tests against a real WordPress, end-to-end tests for critical flows.

PHPUnit · Pest · Playwright

06

Performance and accessibility

Budgets enforced in CI, not checked once at launch. WCAG 2.2 AA is a requirement in the definition of done.

Lighthouse CI · axe-core · Query Monitor

02 / delivery pipeline

From commit to production, with a way back.

Nothing reaches production without passing review and the same checks in CI. Releases are atomic, and the previous build stays on disk for an instant rollback.

  1. commit

    conventional commit, pre-commit lint

  2. pull request

    review + CODEOWNERS approval

  3. test

    phpcs · phpstan · phpunit · e2e

  4. build

    composer –no-dev, asset bundle

  5. staging

    auto-deploy, smoke tests

  6. production

    manual approval, atomic release

rollback: dep rollback production re-points the release symlink to the previous build in under 2s

.github/workflows/deploy.yml yaml
# Runs on every PR; deploys main after review + green checks
on:
  pull_request:
  push: { branches: [main] }
jobs:
  verify:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: composer install --no-progress && npm ci
      - run: composer lint      # phpcs --standard=WordPress
      - run: composer analyse   # phpstan level 8
      - run: composer test      # phpunit + wp-env
      - run: npm run build && npm run test:e2e
  deploy:
    needs: verify
    if: github.ref == 'refs/heads/main'
    environment: production   # requires approval after staging

03 / selected work

Case studies, written as engineering notes.

Problem, approach, the decisions that mattered, and what changed. Client names withheld where under NDA.

04 / services

What I take on.

Custom development

Plugins, block themes, custom Gutenberg blocks, REST and headless integrations. Built to WPCS, typed, and covered by tests.

Maintenance and care

Dependency audits, core and plugin updates through staging, uptime and error monitoring, tested backups and a written monthly changelog.

05 / writing

Recent technical articles.

06 / about

Twelve years of PHP. Most of them spent cleaning up after “it works on my machine.”

I’ve worked on WordPress since the 3.x days, from agency builds to multisite networks serving millions of requests a month. I also run Bertex Design, a small studio for SMB clients; this site is about the engineering side.

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

07 / contact

Hiring for a WordPress-heavy team, or inheriting a codebase?

Send the role or the repo. I reply within two working days with questions, not a sales deck.