Careers WordPress QA Engineer
Full-time role based in our Lucknow office. You test our WordPress themes and plugins before customers do: functional and regression testing, release smoke tests, reproducible bug reports, and fix verification across the Reign theme, BuddyX, and the active plugin line.
We are looking for a QA engineer who can own the quality of what we ship: themes and plugins that run on 100,000+ active installs across 40+ countries. You test the work before customers do, and your sign-off is part of every release.
You will work alongside the engineering team. You test against the changelog and the spec, file reproducible reports in Basecamp, and verify the fix before the release tag. Manual testing is the core of the role; automation is where it is heading.
Responsibilities
Four areas of the work. The split shifts week to week depending on what is shipping, but all four are part of the role.
01
Functional and regression testing across the Reign theme line, BuddyX, and the active plugin lineup. Work through WordPress and PHP version matrices, multisite, and common host configurations so issues surface here, not on a customer site.
Functional + regression coverage.
02
Build a test plan from a changelog or feature spec, then file reproducible bug reports: exact steps, environment, version, expected versus actual, with screenshots or a short screen recording. Reports go to engineers and are tracked in Basecamp.
Test plans + reproducible reports.
03
Run the pre-release smoke on every theme and plugin before it tags. Verify the critical journeys (install, activate, settings, core flows) and either sign off or block the release. Your sign-off is part of the release gate.
Smoke + sign-off on every release.
04
Confirm each fix actually resolves the report, and that it did not break an adjacent feature. Cross-browser, responsive down to 390px, and accessibility spot-checks are part of the pass.
Fix verification + regression watch.
Requirements
Four hard requirements. Without these the role will not be a fit. With them, we want to talk.
01
You have tested WordPress themes or plugins before. You know wp-admin, how to install and configure plugins, set up test content, and reproduce an issue reliably across different setups.
WordPress testing experience required.
02
You write the steps so an engineer reproduces the issue in one read: environment, version, expected versus actual, evidence attached. No "it does not work" reports.
Reports an engineer can act on.
03
You catch the layout break at 390px, the broken hover state, the console error nobody noticed. You test on more than your own machine and you do not assume one browser is every browser.
Cross-browser, multi-device testing.
04
You turn a changelog or a feature spec into a test plan, work through it without hand-holding, and communicate findings in writing. Quality is something you drive, not something you wait to be assigned.
Self-directed, written communication.
Nice to have
Not required, but if you have any of these, mention them in the cover letter.
01
Playwright, PHPUnit, or comparable. We test the WordPress admin and front end with Playwright and run PHPUnit on plugins; automated coverage is growing and you could help grow it.
Playwright / PHPUnit automation.
02
Our products live in these ecosystems. Knowing how groups, activity streams, carts, orders, or license keys behave shortens the ramp considerably.
Ecosystem familiarity.
03
WPCS, PHPStan, and reading a PHP stack trace. You do not need to write the fix, but understanding the codebase helps you test the right things and write sharper reports.
WPCS / PHPStan / stack traces.
Apply
Two-line cover letter is fine. Attach your resume and link any test plans, bug reports, or automation samples in the message body. Applications go straight to hr@wbcomdesigns.com.
Not ready to apply yet?
See how we work on /process/ and what we engineer on /services/. The careers landing has the other open roles. We are happy to chat before you apply if you have questions.
After 16 years of buying WordPress themes and plugins, I know exactly what bad support looks like and Wbcom Designs is the polar opposite. My setup was a nightmare: multiple tools, deep integrations, custom configurations that required…