Skip to content
Seed Lighthome
A WordPress plugin list showing versions and pending updates

Open role

Websites

Join Seed Light as a WordPress Developer

Also advertised as: WordPress engineer, WordPress theme developer, WordPress plugin developer, PHP/WordPress developer, WordPress specialist

In this remote Seed Light WordPress developer role, you build and maintain websites, including custom themes and small plugins that stay easy to update.

Full-time, contract or internshipRemote, wherever you are3+ years in WordPress
Apply for this roleAll open roles

Job description

WordPress developer

Employment
Full-time, contract or internship
Location
Remote, wherever you are
Experience
3+ years in WordPress
Hours
9am to 5pm Malaysia time

About the role

Most client websites use WordPress, so this role covers both new builds and ongoing maintenance. Some projects use custom themes, while others use a page builder where that better fits how the client needs to manage the site.

The work includes inherited sites. A good part of the job is opening a build somebody else made, working out what it does, and making it safe to change.

There is no application window on this role. It is open until it is filled.

People in this role work on Seed Light's Web Design & Development projects.

Responsibilities

  • Build custom themes and child themes from a design file
  • Write small plugins and mu-plugins instead of installing a heavy one
  • Take over inherited sites: audit them, fix them, document them
  • Handle updates, backups, staging and safe deploys
  • Fix speed, security and broken integrations on live sites

Requirements

  • You write PHP, and you know the WordPress hooks and template hierarchy
  • You have built a theme from scratch, not only edited one
  • You keep sites updatable, so nothing important lives in core files
  • You know MySQL well enough to find a slow query
  • You are careful on production, and you take a backup first

Nice to have

  • You have worked with ACF, custom post types and the REST API
  • You have used WP-CLI on a real server
  • You have run a headless WordPress back end

Tools

WordPress, PHP, MySQL, WP-CLI, ACF, Git, Elementor, SSH. The licences and subscriptions the job needs are paid for, and knowing every one of these already is not expected.

Your first three months

  • Month 1. Maintenance and fixes across the live client sites, so you learn the estate.
  • Month 2. You build a theme for a new client site, from the design file to launch.
  • Month 3. You own the WordPress standards here: how sites are set up, updated and handed over.

How to apply

Use the form on this page. Attach your CV and list three things you have worked on, with one line each on what you did. Every application is read by a person and gets an answer, usually within two weeks.

Apply for this role

Hiring

How we hire

Three steps, usually within two weeks, with a clear answer either way.

  1. Day 0

    Send your application

    Share your CV and three examples of work you contributed to, with one line explaining your role in each.

  2. If shortlisted

    A 30-minute call

    We talk through how you work, what you have built before, and what you would like to do next.

  3. By week 2

    A clear answer

    A clear yes or no on your application, with the reason behind it, so you know where you stand.

Straight answers

Questions about this role

Questions candidates usually ask before applying. If yours is not here, add it to the message box on the form.

Yes. Some sites use Elementor when it suits the client's editing needs, while others use custom themes. The role calls for judgement across both.

Yes, when a good one exists, and the licences are paid for. What gets avoided is installing five plugins to do a job that thirty lines of code does better.

There is no formal on-call rota. Sites on a care plan need somebody to look when something breaks, and that is shared rather than generally the same person.

The care plan sites are shared across the development team instead of being assigned to one person. A developer normally owns a new build from start to launch, while maintenance work is recorded so another developer can understand the site.

Both, depending on the project. What matters is that the result is updatable and that the next person can read it, which is the standard each build is checked against.

Legacy work is audited before you explain plainly what fixing it would cost compared with rebuilding it. The client then makes the decision with both options in front of them, based on the condition of the existing work and the two costs you have presented.

Apply for WordPress developer

The form takes a CV and a few links. Tell us what you built and what your part in it was. Every application gets an answer.

Applying for

WordPress developer

Fields marked * are required. A monthly figure or range in your own currency is fine. It is a starting point for the conversation, not a commitment. Your CV is used only for recruitment and kept within Seed Light's hiring records. Read our privacy policy.

Prefer email? Send your application to careers@seed-light.com with the role in the subject line.

Also open

Other roles we are hiring for

All 30 roles