Hiring a WordPress Developer: Tests, Terms and Red Flags
Which kind of WordPress developer to hire, what to ask, how to run a paid trial and which access and ownership terms to agree before work starts.

The short answer
- “WordPress developer” covers four different jobs: site builder, theme developer, plugin and integration developer, and WooCommerce developer. Decide which one you need before you look at anyone.
- A portfolio only proves what someone shipped. A small paid trial task on a staging copy of your site shows how they work, communicate and hand over.
- Give the developer their own WordPress account with the lowest role that does the job. Never share your own login, and keep hosting, the domain and premium plugin licenses in your name.
- Agree ownership of code and content, the change process and handover notes in writing before work starts.
- With Attors, WordPress work on an existing site is $25 an hour with a time estimate first; custom features start from $249 and custom themes from $990.
Hiring a WordPress developer well comes down to three moves: match the job to the right kind of developer, test your shortlist with a small paid task on a staging copy of your site, and put access and ownership terms in writing before anyone logs in. Interviews and portfolios help, but those three steps are what separate a good hire from an expensive one.
This guide is for business owners and marketing managers who need someone to build, fix or extend a WordPress site and have never hired for it before. It gives you the questions to ask, the answers to listen for, a trial task you can copy, and a scoring sheet for comparing candidates. If you would rather skip the search, our WordPress developers for hire work on a fixed written quote or by the hour.
Which kind of WordPress developer do you need?

Most WordPress hiring problems start with the wrong kind of developer. A business website built from a theme and a page builder needs a site builder; a new booking feature needs a plugin developer who writes PHP; an online store needs WooCommerce experience. Name the job first, then look for people who have done that exact job before.
| Role | Typical jobs | What to test | Attors price for this work |
|---|---|---|---|
| Site builder (implementer) | New business site from a theme or page builder, new pages, layout changes | Editable pages, mobile layouts, page speed, sensible plugin choices | Websites from $349 (up to 6 main pages and 8 service pages) |
| Theme developer | Turning a design into a custom theme, custom blocks, template fixes | Clean block markup, editor experience, accessibility, no hard-coded text | Custom themes from $990 |
| Plugin and integration developer | Custom features, CRM or payment integrations, fixing broken plugins | PHP quality, security habits, documentation, update safety | Custom features or plugins from $249; complex integrations from $1,290 |
| WooCommerce developer | Store builds, checkout changes, product data, subscriptions | Checkout testing, order handling, payment gateway experience | Stores from $549 |
Plenty of developers cover two or three of these roles. Very few are equally strong in all four, so ask which kind of work makes up most of their week. Someone who mostly assembles sites with Elementor can be excellent at that and still be the wrong person to write a custom plugin that touches your orders.
Where to find WordPress developers worth interviewing
Each source suits a different size of job. The goal at this stage is a shortlist of three people or teams who have done work close to yours, not a long list of cheap bids.
- The official WordPress jobs board. jobs.wordpress.net is run by the WordPress project and lets you post a job for free. It reaches people who follow WordPress closely, though you do all the screening yourself.
- Referrals from businesses like yours. Look at sites you admire in your industry and ask who built them. A referral tells you how the developer behaves after launch, which a portfolio never does.
- Freelance marketplaces. Good for small, well-defined tasks where you can judge the result yourself. Read reviews for repeat clients, since those show who stays reliable over time.
- WordPress agencies. Better when the site matters to revenue, when work never really ends, or when you need several skills at once (design, development and SEO). You pay for a team that does not vanish when one person is busy.
- White-label partners, for agencies. If you are an agency hiring capacity for client work, a white-label WordPress partner delivers under your brand and is a different decision from hiring for your own site.
How to check a WordPress portfolio in ten minutes
A portfolio shows finished screenshots; you need to know what the developer actually did. Pick two live sites from the list and spend five minutes on each.
- Open the live site on your phone. Menus, forms and buttons should work with a thumb. Many portfolios look fine on desktop and fall apart on mobile.
- Run it through PageSpeed Insights. A slow score is not always the developer’s fault, but ask about it. A good developer explains what slows the site and what the client chose not to fix.
- Ask what they built and what came with the theme. If the site is a commercial theme with the demo content swapped, that is fine for a simple brochure site, but it says nothing about custom development skills.
- Ask to see the editor. A short screen recording of the page editor shows whether the client can change text and images themselves or needs the developer for every edit.
- Ask for one client you can speak to. Ten minutes on the phone with a past client tells you about deadlines, communication and what happened when something broke.
Our own project pages describe what we delivered in the same plain way. For a Los Angeles plumbing company, for example, we rebuilt the website in WordPress and Elementor Pro with service pages, a gallery of their work and a request-a-quote page, and handed it over so their team can edit every page without a developer.
Questions to ask a WordPress developer, and the answers to listen for
The best interview questions for a WordPress developer are about how they protect a live site: where they test, how they handle updates, where custom code lives and who owns what at the end. Good developers answer these without hesitating, because they deal with them every week. Vague answers here predict trouble later.
| Question | A good answer | A warning sign |
|---|---|---|
| Where will you test changes before they reach the live site? | On a staging copy, with a link you can check before anything goes live | “I’ll be careful on the live site” |
| Where does your custom code go? | In a child theme, a custom block theme or a small site-specific plugin, never in the parent theme or WordPress core | Editing the theme’s own files, so the next theme update wipes the work |
| How do you handle plugin and core updates? | Backup first, update on staging, check key pages and forms, then update live | “Just click update” or “never update, it breaks things” |
| When do you add a plugin and when do you write code? | A well-maintained plugin for common jobs, custom code when a plugin is heavy or a poor fit | A new plugin for every small request |
| Which coding standards do you follow? | The WordPress Coding Standards, with input checked and output escaped | No answer, or “it works, so it’s fine” |
| Which PHP version should my site run? | A supported version; WordPress.org currently recommends PHP 8.3 or greater | Leaving an old PHP version in place because changing it is “risky” |
| What access do you need from me? | Their own WordPress account at the lowest role that works, plus hosting or SFTP only if the job needs it | Asking for your personal admin password |
| What do I get at the end? | Working site, list of changes, notes on custom code, every account in your name | Nothing written down |
You do not need to understand every technical detail of the answers. Listen for specifics. A developer who says “I clone the site to a staging subdomain, update there, and check the checkout and contact forms before I touch live” is describing a habit. One who says “don’t worry, I’ve done this many times” is describing confidence. Our guide to WordPress staging sites explains what a proper staging setup looks like if you want to check.
Run a small paid trial before a big project

A paid trial task is the most reliable way to hire a WordPress developer for anything bigger than a one-off fix. Give your top two candidates the same small, real task, worth two to five hours of work, on a staging copy of your site. Pay for it. You learn more from how they handle it than from any interview.
Pick a task that matters but cannot hurt the business if it goes wrong. Good examples:
- Fix a layout problem on mobile on two or three pages.
- Add a new section to the home page that your team can edit afterwards.
- Find out why a form stopped sending emails and fix it.
- Review the site’s plugins and write a short list of what to remove, replace or keep.
Send the same short brief to each candidate: what the problem is, where the staging copy lives, what “done” looks like, and that you want a written note of what they changed. Then judge five things: whether they asked sensible questions before starting, whether they hit the estimate, whether the work holds up on a phone, whether the note is clear, and whether they touched anything they were not asked to touch.
From our projects: on-demand WordPress work with us starts with a time estimate before any work begins, every change is tested on a staging copy first, and each invoice comes with a time report. A first small task is the way most clients try us before a larger build.
Score your shortlist side by side
After the interviews and the trial task, score each candidate out of five on the criteria below and multiply by the weight. Price is on the list, but it is not at the top: a cheap developer who breaks the live site costs more than the difference in rates.
| Criterion | Weight | What a 5 looks like |
|---|---|---|
| Trial task quality | x3 | Works on desktop and phone, nothing else changed, clear note of what was done |
| Safe working habits | x3 | Staging, backups and updates explained in specific steps |
| Relevant past work | x2 | Live sites of the same type as yours, with a reference you could call |
| Communication | x2 | Asked good questions, replied within a business day, wrote in plain English |
| Ownership and handover terms | x2 | Agrees in writing that code, content and accounts are yours |
| Price and payment terms | x1 | Clear estimate or fixed price, payments tied to delivered work |
The maximum is 65. In practice the decision is usually obvious by the time you add up the trial task and working-habits rows, and the rest only breaks a tie. If two candidates are close, choose the one whose note from the trial task you understood best, because you will be reading their notes for years.
Access, ownership and contract terms to settle first

Before a WordPress developer starts, agree in writing who owns the code and content, which accounts they may use, how changes are requested and priced, and what you receive at the end. These terms cost nothing to settle on day one and are very hard to fix after a dispute or after a developer stops replying.
- Their own login, not yours. Create a separate WordPress user for the developer. WordPress has built-in roles and capabilities; give the lowest role that does the job, and Administrator only when the work needs it. Remove the account when the work ends.
- Hosting, domain and licenses in your name. If the developer buys a premium theme or plugin, the license should be registered to your business, so updates keep coming when you change developers.
- Code and content ownership. The contract should say the design, code and content transfer to you on final payment. Watch for builds on a developer’s own hosting platform that you cannot take with you.
- A written change process. Anything outside the agreed scope gets an estimate or a change note before work starts, so invoices never surprise you.
- Handover notes. A short document listing custom code, the plugins added and why, and anything that needs care at update time.
- Security basics. Strong passwords, two-factor login for admin accounts and access shared through a password manager, as described in WordPress’s own hardening guide. Never send passwords by plain email or a contact form.
Our contract terms work the same way: the price is agreed in writing before work starts, projects under $1,500 are paid 50% at the start and 50% when you approve the finished work, and the design, code and content are yours once the final invoice is paid. The guide to choosing a web development company covers general contract clauses for larger agency projects.
Freelancer, agency or dedicated developer: which to hire
Hire a freelancer for a small, clearly defined job you can check yourself. Hire an agency when the site earns money, the work is ongoing or you need design, development and SEO together. A dedicated developer only makes sense when you have a full-time workload, which is usually true for agencies rather than single businesses.
| If you… | Hire | Why |
|---|---|---|
| Need one fix or a small change on a simple site | A freelancer or hourly developer | Low cost, easy to check, little risk if it goes wrong |
| Need a new business website | An agency or experienced freelancer with a fixed quote | Design, content, SEO setup and launch in one written price |
| Run a store or a site that takes bookings or payments | An agency with WooCommerce experience | Someone is always available when checkout breaks |
| Have a steady list of changes every month | A care plan or monthly hours | Updates, backups and small changes handled on a schedule |
| Are an agency with client work every week | A dedicated developer or white-label partner | Capacity under your brand without hiring in-house |
For ongoing upkeep after launch, our WordPress care plans start at $49 a month per site. Agencies can reserve a dedicated developer through our white-label development team from $1,290 a month for mid-level or $1,890 for senior. If you are weighing in-house staff against outside help, our breakdown of outsourcing WordPress development versus hiring in-house runs the numbers.
Red flags when hiring a WordPress developer
- They want your personal admin login, or your hosting password for a job that only needs WordPress access.
- They quote a price before asking what the site does, who edits it or what plugins it runs.
- They plan to edit the live site directly and have never mentioned staging or backups.
- Their answer to every request is another plugin.
- They will not put ownership of code and accounts in writing.
- Every portfolio site uses the same commercial theme with different colors, but they describe themselves as a custom developer.
- They go quiet for days during the trial task. It rarely gets better once the real project starts.
Price questions deserve their own answer. Our breakdown of WordPress developer rates compares hourly, fixed-price and dedicated models across experience levels and locations, so you can tell whether a quote is realistic before you sign.
Hiring a WordPress developer questions
How much does it cost to hire a WordPress developer?
It depends on the job more than the person. At Attors, changes and fixes on an existing WordPress site are $25 an hour with an estimate first, a custom feature or plugin starts at $249, a custom theme at $990 and a complete business website at $349. Rates elsewhere vary widely with experience and location.
How long does it take to hire a WordPress developer?
About one to two weeks for most small businesses: a few days to build a shortlist, a day or two for calls, and a few days for a paid trial task. Rushing the trial is the usual mistake. For an urgent fix, hire an agency or developer you can start with quickly and run the full process for the larger project later.
What skills should a WordPress developer have?
For custom work: PHP, HTML, CSS and JavaScript, the block editor, and the WordPress Coding Standards. For any role: safe habits with staging, backups and updates, plus clear written communication. A site builder needs strong page-builder and mobile layout skills; a WooCommerce developer needs checkout and payment gateway experience.
Should I give a WordPress developer my admin password?
No. Create a separate user account for the developer with the lowest role that does the job, and delete it when the work ends. Your own account stays private, and the site’s activity shows who changed what. Share hosting access only if the task really needs it, through a password manager rather than email.
Can I hire a WordPress developer for just a few hours?
Yes. Hourly work is the normal way to handle fixes and small changes. Ask for a time estimate before work starts and a short report of what was done afterwards, so you only pay for the hours used and have a record of every change.
Is it safe to hire an offshore WordPress developer?
Yes, if you use the same checks as for a local hire: a paid trial, their own login, accounts in your name and written ownership terms. Time zones matter more than distance, so agree when you will get updates. Our team is based in Gujrat, Pakistan and works remotely with clients in the US, UK, Europe, Australia and the UAE.
Should I hire a developer or build the WordPress site myself?
Build it yourself if the site is simple, you have the time and a good theme covers what you need. Hire a developer when the site takes payments or bookings, needs custom features, must load fast for search, or when your hours are worth more spent on the business. Many owners start with a developer-built site and edit it themselves afterwards.
What should a WordPress developer contract include?
Scope and price, payment milestones, a change process for extra work, who owns the code and content and when, which accounts the developer may use, testing on staging, the handover you receive, and what support follows launch. Keep it short and specific; a one-page written agreement beats a long template nobody reads.
Start with one task and see how we work
Attors Technologies is a web development agency whose WordPress developers build, fix and maintain sites for businesses and agencies in the US, UK, Europe, Australia and the UAE. Tell us what your site needs, from a single fix to a custom plugin. You will get questions or a written estimate within one business day, with the work tested on staging before it reaches your live site.
Keep reading
More in Website StrategyWebsite Strategy
How Much Does a WordPress Website Cost in 2026?
What a WordPress website costs in 2026: $349 to $1,490 to build and $20 to $250 a month to run, with hosting renewal prices, three worked budgets over three years and the itemised list a fair quote should follow.
Website Strategy
Healthcare Website Cost in 2026: Prices and HIPAA Duties
What a clinic or medical group should budget for a website, which HIPAA and accessibility duties change the quote, and when the cheapest setup is the safest one.
Website Strategy
Dental Website Cost in 2026: Plans, Fees and HIPAA Setup
Plan on $349 to $1,490 or more for the dental website itself and about $10 to $25 a month to keep it online. Here is what each price buys, what you keep paying, and where patient privacy rules change the setup.



