WordPress without the apology tour.
You build WordPress like it is a product, not a plugin graveyard. Performance budgets, staging discipline, and a clear line between "nice" and "ships now."
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.
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 like a line item, not a blog post.
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.
Signals we actually check.
- Shipped multiple production WordPress builds with custom themes or block work, not only page-builder sites.
- 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 with Central European business hours for reviews and launches, agreed in writing.
India, remote, with EU overlap
Remote from India. No desk policy, no commute fiction.
Client workshops, UAT, and launch windows still track EU time for most files. We set the overlap in the contract so launches do not depend on heroics.
Save the intro if this is you.
- You default to twenty plugins because the client asked for "everything easy."
- You disappear after handover; ongoing stability is "hosting support."
- You cannot be available during the EU 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 ↗Bring the operational risk.You get a clear diagnosis and a concrete next step.
We are the right fit if you want a team that pushes back when it matters.
Company evidenceon the site.
Engagements with commercial outcomes on Work. Team bios and operating model on About. Nothing to download. Review it before you commit to a call. Open to review. Commit when ready.