WordPress Engineer

Some Tech; Wiesbaden; Hybrid; EUR 52,000 - 78,000; Full time

Job summary

Some Tech is seeking a WordPress Engineer for contract, project-based work. You will ship production WordPress builds with custom themes or blocks, ensuring performance budgets are met and a clear line between what ships and what waits.

Strong in ACF, Gutenberg blocks, and WooCommerce when needed, you read Query Monitor outputs to fix bottlenecks. You will operate remotely with agreed overlap from India, handling staging, releases, and client communication in writing.

Qualifications

• Shipped multiple production WordPress builds with custom themes or block work.
• Deep comfort with ACF (or equivalent) and Gutenberg block development where the editor experience matters.
• WooCommerce when the project needs it: checkout flows, subscriptions or complex products you've debugged under traffic.
• Hosting and caching literacy (object cache, CDN, query bottlenecks).
• Written English for async scope, estimates, and risk flags. Overlap for reviews and launches, agreed in writing.

Responsibilities

• Define and maintain performance budgets and ship-now criteria.
• Implement caching, image delivery, and query discipline strategies.
• Coordinate with clients to agree overlap windows in contracts.
• Produce release notes and staging environments with rollback paths.

Skills

WordPress development

ACF

Gutenberg blocks

WooCommerce

Performance optimization

Tools

Query Monitor

Hosting & CDN

WordPress CLI

Caching strategies

WooCommerce debugging

Job description

You build WordPress like a product: performance budgets, staging discipline, and a clear line between "nice" and "ships now."

WordPress Engineer. Contract · Project-based

Performance-first builds, ACF, Gutenberg blocks, WooCommerce. You understand why WordPress has a reputation and how to make it undeserved. Strong opinion on what ships versus what waits.

ACF, native blocks, and Woo only where commerce is real. You can defend every dependency: what it costs in load time, update risk, and who fixes it when it breaks.

The reputation is optional.

Caching strategy, query discipline, image delivery, and admin UX that does not punish editors. You treat Core Web Vitals as a delivery requirement with measurable targets.

Staging, rollback, release notes.

No "Update All" on Friday. Changes land with a path back. Clients see what changed and why, in language they can forward to their board.

Requirements

Signals we actually check.

• 01 Shipped multiple production WordPress builds with custom themes or block work.
• 02 Deep comfort with ACF (or equivalent) and Gutenberg block development where the editor experience matters.
• 03 WooCommerce when the project needs it: checkout flows, subscriptions or complex products you have actually debugged under traffic.
• 04 Hosting and caching literacy (object cache, CDN, query bottlenecks). You can read Query Monitor output and act on it.
• 05 Written English for async scope, estimates, and risk flags. Overlap for reviews and launches, agreed in writing.

India, remote, with agreed overlap

Remote from India. No desk policy, no commute fiction.

Client workshops, UAT, and launch windows still need predictable overlap. We set the window in the contract so launches do not depend on heroics.

Wrong fit

Probably not us if this is you.

• You add every requested extension without ownership or a performance budget.
• You disappear after handover; ongoing stability is "hosting support."
• You cannot be available during the overlap window this role needs.

What's slowing your team down? (required)

We read every brief and reply within one business day.