WordPress FSE Expert Implementation Developer

ABOUT THE WORK
We turn strategy into shipped web properties across a growing portfolio of brands (advisory, education, media, wellness, and client work). This role is about building, not babysitting: standing up new WordPress sites from briefs, extending a shared theme system that powers the whole portfolio, and shipping clean, fast, and on-spec.

You'll work from clear scopes against real deadlines, in a codebase that has opinions. We value developers who take ownership, ask sharp questions early, and ship work that doesn't come back. If you do your best work in a quiet, focused, low-drama environment, you'll fit here.

THE STACK
We build modern block themes. Full Site Editing, theme.json-first styling, block patterns, and template parts. Our brands run on a shared base theme, so a change to the system can ripple across many sites. That means we care more about discipline than plugin count:
- Gutenberg / FSE native. We do NOT use Elementor, Divi, Bricks, or WPBakery, and we're not looking to. If your WordPress is "drag the page builder, install 30 plugins," this isn't for you. We use WordPress FSE best practices across the board. No exceptions.
- Clean cascade, no shortcuts. theme.json and colocated CSS over global stylesheets. No `!important` when a rule doesn't win, you fix the cause (specificity, source order, markup), not paper over it.
- Restraint over abstraction. A pattern, custom block, or template part earns its place by being reused across pages.
- Generic, semantic naming. Classes describe form, not location (card, not teaching-card).
- WP-CLI fluent. Safe search-replace, db, post, cron, cache. You reach for `wp` before raw SQL, and you back up before you mutate.

If that reads as constraints, this isn't your role. If it reads as relief, read on.

WHAT WE BUILD
New sites & funnel-based buildouts (primary)
- Stand up WordPress block-theme sites from briefs, wireframes, or designs - extending the shared base theme rather than reinventing per site
- Build pages with native blocks, patterns, and template parts; write theme.json and colocated CSS, not a pile of plugins
- Implement to spec: accurate, responsive, cross-browser, fast
- Build forms, opt-ins, membership/access-control, and lead flows that work the first time

Integrations & tracking (part of every build, not an afterthought)
- Wire up Fluent CRM, Amazon SES, affiliate/tracking (Everflow), and similar
- Implement and verify GTM, GA4, Meta Pixel, and conversion/event tracking - and confirm the data actually lands
- Connect third-party apps and APIs cleanly when appropriate

Performance & quality (baked in)
- Ship Core Web Vitals–friendly builds: optimized assets, lean plugin footprint, sane caching
- QA across devices and browsers before handoff - no broken links, no console errors, no surprises
- Only write custom PHP / JS / CSS where the build genuinely calls for it

System & maintenance (secondary, but it matters here)
- Extend and harden the shared theme system; keep file-based templates and DB overrides in sync
- Updates, fixes, and small enhancements on properties across the portfolio
- Document what you changed (we keep changelogs and context notes) so the next person picks up cleanly

WHAT WE'RE LOOKING FOR
- Strong, demonstrable WordPress FSE build experience - block themes / FSE specifically, not just maintenance or page-builder work. Live URLs you can point to.
- Real fluency in JavaScript, HTML, PHP, and CSS - you can read and write custom code, and you understand the cascade well enough to win specificity battles without `!important`
- Hands-on with `theme.json`, block patterns, template parts, and WP-CLI
- Comfortable with GTM, GA4, and pixel/conversion tracking
- Performance and SEO-readiness built into how you work, not bolted on at the end
- Self-directed: you run your own task management and communicate cleanly in Slack
- Reliable on deadlines and obsessive about the last 5% - the details that make a build feel finished

Bonus: experience with membership/access-control or building/maintaining a multi-site portfolio on a shared theme.

HOW WE WORK
- Remote and async-friendly; some overlap with US Central hours for syncs when needed
- Day-to-day comms in Slack
- Contract / project-based to start, with steady ongoing work for the right person
- Rate: competitive

HOW TO APPLY
Send:
1. Portfolio - 2–3 WordPress sites you built, with live URLs and one line each on what you actually did. Block-theme/FSE examples get read first.
2. One complex build or integration problem you solved and how you solved it
3. Your availability, timezone, and rate
4. Start your message with the word "Delivery" so we know you read this

Strong candidates will be asked to complete a short, paid test build before we move forward.