How to Hire a WordPress Developer: 7 Steps, Costs and Questions to Ask

To hire a WordPress developer, write a one-page brief, decide what kind of developer the job needs, shortlist two or three from a source that fits your budget, check sites they actually built, pay for a small test task, and agree scope, price and code ownership in writing before you give them access. The seven steps:

1. Write down what you need built and what “done” means.
2. Pick the kind of developer: site builder, theme, plugin, WooCommerce or maintenance.
3. Shortlist from a marketplace, a vetted network, an agency or the official WordPress jobs board.
4. Check live sites, references and how they work.
5. Pay for a small test task before the big job.
6. Agree scope, price, timeline and ownership in writing.
7. Give access through their own account, on a staging copy, and plan the handover.

Developers can only quote accurately against a clear brief, and a written one makes quotes comparable. Cover:

• What the site or feature must do, for whom, and the pages or screens involved.
• What you already have: hosting, theme, page builder (Gutenberg, Elementor, Divi or another) and the plugins in use.
• Integrations: payments, forms, CRM, email, shipping or anything else with an API.
• Who will edit content after launch, and how comfortable they are with WordPress.
• Deadline, budget range and what “done” means: the checks the work must pass.

Attach examples of sites you like and say what you like about each. “Make it modern” gets you ten different quotes; “a services page like this one, in our existing Elementor theme” gets you comparable ones.

“WordPress developer” covers very different skills, and the best value is the one that matches the job.

Then decide how to hire. A freelancer is usually the most cost-effective for a defined project. An agency costs more but puts design, development and maintenance under one contract, and the work doesn’t stall if one person is away. In-house only pays off when there is a steady stream of WordPress work.

Codeable’s prices and Toptal’s terms were checked on their own sites on 3 November 2026. A developer’s experience and location move the price more than the platform does, so compare quotes for your brief rather than hourly rates.

A portfolio shows what a developer can make look good; a live site shows whether it still works. For two or three sites they built:

• Open the site on your phone and check that it loads quickly and nothing breaks.
• Ask what exactly they did on it: design, build, custom code or maintenance.
• Ask the owner, or a reference they give you, how the project went and whether they would hire them again.
• For custom code, ask for a sample or a GitHub profile; a WordPress.org profile with plugins or themes is a good sign.

Then ask these on a call:

1. Which of your projects is closest to mine, and what would you do differently now?
2. Will you build with our theme and builder, so we can still edit the site ourselves?
3. Which plugins would you use, and why those?
4. How do you handle backups, a staging copy and updates while you work?
5. How do you estimate, and what happens when the scope changes?
6. Who owns the code and the design files at the end, and how do we receive them?
7. What does support cost after launch?

Good developers ask you questions back. A fast quote with no questions usually means the price will move later.

A paid trial of a few hours tells you more than any interview. Pick a real piece of the job: fix one bug, build one section, or speed up one page, and pay for it at their normal rate. Judge the result, but also how they communicated, whether the estimate held, and whether they explained what they changed. Some platforms build this in: Toptal offers a trial of up to two weeks.

• Scope: the brief, the deliverables and the checks that mean “done”.
• Price: a fixed price for a well-defined job, hourly with a cap for open-ended work, and milestone payments for anything longer than a few weeks.
• Timeline: the dates, and what happens if either side is late.
• Ownership: the custom code and design files are yours and are delivered in full, for example in a Git repository, and premium themes and plugins are licensed in your name.
• Support: a warranty period for bugs after launch (Codeable’s is 28 days) and the rate for help after that.
• Access: you keep the admin and hosting accounts; the developer gets their own.

Never share your own login. Create a separate user for the developer under Users > Add New User and give them the lowest role that does the job: Administrator only if they need to install plugins or change settings. WordPress’s guide to roles and capabilities explains what each role can do. If a tool needs to connect to the site, give it an application password that you can revoke at any time.

• Take a full backup before work starts, and have changes built on a staging copy first.
• Give hosting, SFTP or Git access through the developer’s own credentials, not yours.
• At handover, get a list of every plugin and licence, the custom code, and notes on how things work.
• When the project ends, remove their account or lower its role, and change any shared passwords.

• They ask for your admin password instead of their own account.
• No live sites to show, or they can’t say what they did on the ones they show.
• A quote far below everyone else’s, with no questions about your brief.
• They want premium plugins or themes licensed in their name, or a builder only they can edit.
• No written agreement, or no plan for backups and a staging copy.

A lot of what people hire developers for isn’t development. New pages in an existing theme, text and image changes, a homepage section, SEO titles, product updates in WooCommerce: these are the same clicks every time, and an AI agent can now do them from a request.

WPOS puts an agent inside wp-admin on the site you already have, on any host. It builds natively in Gutenberg, Elementor and Divi, checks its own render in a browser before it reports a job done, and leaves normal pages you can still edit by hand. A request looks like this:

“Add a careers page in the same style as the About page, with three open roles and a short application form.”

Keep a developer for what an agent shouldn’t own: custom plugins and integrations, a new design system, complex performance or security work, and decisions about how the site is built. WPOS is our product, so weigh this section accordingly; you can try it free for 30 days with 5,000 credits, a live site plus a staging sandbox, and no card.