Open role · WordPress

WordPress without the apology tour.

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

Engineering delivery session
CWV
Performance as a requirement
ACF
Blocks, fields, sane content model
IST+
Remote India, agreed overlap
WordPress Engineer: accountable delivery environment at Some Tech Work
Role

WordPress Engineer. Contract · Project-based

India · Remote

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.

← Careers overview

What you own

Three slices of one accountable lead.

Content model first, plugins second.

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.

  • 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 have actually debugged under traffic.
  • Hosting and caching literacy (object cache, CDN, query bottlenecks). You can read Query Monitor output and act on it.
  • Written English for async scope, estimates, and risk flags. Overlap for reviews and launches, agreed in writing.
Location

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.

Short paid assessment if we move past the first call. Contracts first. Full process on the careers page.

Apply for this role ↗
Hier starten

Bereit fürs Gespräch.Buchen Sie eine kurze Diagnose.

Sagen Sie uns, was nicht läuft

Ein Prozess, ein Tool, eine hängende Entscheidung. Ein Satz reicht.

Mit dem Absenden stimmen Sie unserer Datenschutzerklärung.

Wir lesen jedes Briefing und antworten innerhalb eines Werktags.

Lieber erst sprechen?oder Tech-Stack-Audit anfragen →oder direkt per E-Mail →

Unklar, wo Sie anfangen sollen? Schicken Sie die hängende Entscheidung, den Workflow oder die Seite. Wir sagen, ob ein Diagnosegespräch, ein Tech-Stack-Audit oder ein anderer erster Schritt passt.