WordPress Plugin Engineer
Build and maintain WordPress plugins running on thousands of live sites, where backwards compatibility and performance are the whole job — not an afterthought.
Posted 28 July 2026 · 1 opening · Applications reviewed within 3–5 working days
About the role
GuestDock secures guest posting on WordPress sites we do not control, running against themes we have never seen, on PHP versions we did not choose. Three more plugins are in development behind it. Writing the feature is the easy part; keeping it working everywhere is the job.
This role sits onsite at the Dhaka studio because it works hand in hand with support and QA — reproducing a customer's conflict on a staging copy of their site is a same-hour activity, not a same-week one.
What you'll do
- Build new plugin features against the WordPress plugin API, hooks, and REST API.
- Maintain backwards compatibility across supported PHP and WordPress versions, and own the deprecation path when something has to change.
- Reproduce and fix conflicts with third-party themes and plugins on staging copies of real customer sites.
- Write and maintain PHPUnit coverage, and keep the plugin passing WordPress Coding Standards in CI.
- Harden every input and output — nonces, capability checks, sanitisation, escaping, prepared statements — as a matter of routine.
- Profile query counts and page weight, and keep the plugin's footprint small on shared hosting.
- Prepare wordpress.org releases: readme, changelog, assets, and the version bump.
What we're looking for
Everything in this list is a genuine requirement — if one of them is missing, the role will not work out, and we would rather say so here than at the fourth stage. We do not ask for a degree, and we do not count years of a framework that has not existed that long.
- 3+ years of professional PHP, with at least two spent on WordPress plugin or theme development.
- Fluent in the WordPress plugin API: actions, filters, custom post types, the settings API, and the REST API.
- Genuine command of WordPress security practice — you can explain why a nonce is not an authorisation check.
- Experience supporting a plugin in the wild, with the compatibility judgement that comes from it.
- Comfortable with Git, Composer, and a CI pipeline.
- Able to work onsite in Dhaka, Sunday to Thursday.
- Conversational English for written tickets and code review.
Nice to have
Genuinely optional. Missing all of these has never stopped us making an offer.
- A published plugin on wordpress.org, or contributions to WordPress core.
- Gutenberg block development in React.
- WooCommerce or multisite experience.
- Working knowledge of the wordpress.org plugin review process.
What you'll work with
- PHP
- WordPress
- PHPUnit
- MySQL
- JavaScript
- Composer
- WP-CLI
Working arrangement
Onsite — Dhaka, Bangladesh
Onsite at the Dhaka studio, five days a week. The role pairs closely with support and QA on live client sites, which is why it is not remote.
40 hours a week, Sunday – Thursday, with core overlap 11:00 – 17:00 (UTC+6). Probation is 3 months on full salary and full benefits, with a written check-in at the halfway point.
Compensation
৳45,000 – ৳90,000 / month
The band is real and the offer lands inside it — where, depends on the practical exercise and the experience you bring, and we tell you which end we are aiming for at the intro call rather than at the offer. Reviewed annually, in writing, against criteria you are told in advance.
Two festival bonuses a year, paid leave, parental leave, hardware, an internet stipend for remote and hybrid roles, and a learning budget come with every role — see the full list.
How hiring works for this role
Two to three weeks, start to offer. The practical exercise is paid, and you get an answer at every stage — including if the answer is no.
Application review3–5 working days
A human reads every application — no keyword filter sits in front of us. You get an answer either way, including if the answer is no.
Intro call30 minutes
A conversation with the hiring manager about your work, what you want next, and the specifics of the role — including compensation, so nobody's time is wasted later.
Practical exercise4–6 hours, paid
A scoped, realistic task close to the actual work — or, for design and motion roles, a walkthrough of work you already own. We pay for take-home time. We do not ask for free work on a live problem.
Team conversation45–60 minutes
You meet the people you would work with, and the founder. We go through your exercise together, and you get as much time to ask questions as we do.
Decision and offerWithin 3 working days
A written offer with salary, level, start date, and the probation terms spelled out. If it is a no, you get specific feedback rather than a template.
How to apply
Send us a short introduction, links to work we can open, and your earliest realistic start date. Mention WordPress Plugin Engineer by name — the form below pre-fills it for you. No cover letter template required; we would rather read three honest paragraphs.
Equal opportunity
Degird hires on the strength of your work. We do not screen on gender, religion, age, ethnicity, disability, marital status, or where you went to school — and we will make reasonable adjustments to any stage of our process if you tell us what would help. If something in this posting is a barrier rather than a requirement, say so in your application and we will look at it.
Other open roles
Senior Full-Stack Engineer
EngineeringRemoteOwn SaaS features end to end in TypeScript, React, Next.js, Node.js, and PostgreSQL — from schema design to a release users touch the same week.
AI Integration Engineer
EngineeringRemotePut LLMs into products people pay for — prompt architecture, evaluation pipelines, cost and latency budgets, and the guardrails that keep it all honest.
Desktop Application Engineer
EngineeringRemoteBuild local-first desktop software with Electron and Tauri, where the user's data stays on the user's machine — and ship signed builds to macOS, Windows, and Linux.