If you run an HVAC, roofing or plumbing company, hiring someone to build your website is a gamble most owners have lost at least once: six weeks gone, a site that looks fine and brings in nothing, and a developer who stopped answering messages after the final payment.
It got harder this year, and not because good developers are scarce. AI has made everyone look competent on paper. Portfolios are polished, code samples run and test tasks come back fast. The old screening signals stopped working. Here is the checklist I would use myself: what to pay, what to ask and which red flags should end the conversation.
Key takeaways
- Decide which of three jobs you are hiring for before you write the ad. Most bad hires are scope mismatches, not skill failures.
- Published freelance rates run from $25 to $160+ per hour depending on level. Hiring on the lowest rate is the expensive mistake.
- AI-generated code made reviewing, not writing, the bottleneck. Screen for judgment, not speed.
- Ask for reasoning, not just deliverables. Anyone can produce a working snippet now.
Why Hiring Changed in 2026
Research analyzing 470 open-source pull requests found AI-generated code produces 1.7x more issues than human-written code, with logic and correctness errors up 75%. (Source: CodeRabbit) Telemetry from teams with heavy AI adoption shows pull requests 51.3% larger, 54% more bugs and review time up 199.6%. (Source: Faros AI, AI Engineering Report 2026)
Output went up, quality went down and review became the bottleneck. What you are really paying for is judgment: someone who checks the work before it goes on the site your customers use.
Step 1: Decide Which Job You Are Hiring For
- The Implementer. Builds pages from an approved design in Elementor, Divi or Bricks. Fast and cost-effective for template-shaped work, but stuck when the design needs something the builder lacks.
- The Custom Developer. Writes custom code: custom post types, hooks, API integrations, plugins. Costs more per hour but is often cheaper per project once you outgrow a builder. See page builder vs custom code for where that line is.
- The Maintainer. Handles updates, backups, security and speed. That is a retainer role, not a project role.
If you are not sure which you need, describe the outcome, not the tool. “Our quote form should create a lead in our CRM and text the customer in a minute” attracts better applicants than “WordPress developer needed.”
Step 2: Know What Rates Look Like
Published 2026 freelance WordPress benchmarks (Source: goLance 2026 rate guide):
| Level | Experience | Typical range (USD/hr) |
|---|---|---|
| Junior | 0 to 2 years | $25 to $50 |
| Mid-level | 2 to 5 years | $50 to $95 |
| Senior | 5 to 10 years | $95 to $160 |
| Expert | 10+ years | $160 to $275 |
Mid-level developers average around $73/hr and seniors around $128/hr. Developers in your own time zone often charge a 15 to 30% premium. These are marketplace figures, so the real spread is wider, and rate tracks capability more than years served. The expensive mistake is not overpaying. It is hiring at $20/hr for work that needed $70/hr judgment, then paying someone else to rebuild it.
Step 3: The Screening Checklist
Portfolio and proof
- Ask what they built, not what they showed. Screenshots prove a design shipped, not who wrote the code.
- Strong developers often cannot show client work. Serious contracts include NDAs. I cannot show client sites or metrics either. Ask instead: “Describe a complex build you cannot show me. What was the hardest problem and how did you solve it?”
- Ask for a code sample of their own, such as a small plugin or a GitHub repo they can explain.
Technical questions (listen for reasoning, not keywords)
- “I want a custom field on every service page. How would you build it?” Good: a custom post type first, then custom fields, and they ask what the field is for. Red flag: they name a random plugin and stop.
- “My theme needs a layout change. Do you edit the theme files?” Good: a child theme or hooks and filters. Red flag: editing the parent theme directly, which gets wiped on the next update.
- “How do you query the database safely?” Good: WP_Query where possible, and
$wpdb->prepare()and escaping otherwise. Skipping sanitizing is a security liability. WordPress launched a Core Security Initiative this year because AI helps attackers find vulnerabilities faster. (Source: Search Engine Journal) - “Elementor cannot do what the design needs. Now what?” Good: custom CSS, a widget or shortcode, a custom template. Red flag: “change the design.”
- “This site takes 6 seconds to load. What is your first hour?” Good: measure first, then check queries, images, plugins and server response. Red flag: “install a caching plugin.”
AI-era screening
- “How do you use AI in your workflow?” You want scaffolding and drafting, with every output reviewed. Be suspicious of both extremes.
- “Tell me about a time AI gave you code that looked right but was not.” The best question right now. Anyone who really works with AI has a story. Someone pasting blindly will not.
- Make the paid test explanation-based. Ask for the code plus a short note on why it is structured that way.
Communication and process
- Check availability honestly. Ask which specific hours they are reachable each week, and agree it in writing.
- Ask how they handle handoffs: documentation, staging URLs, secure credential sharing or a walkthrough video.
- Start with a small paid project, such as one landing page, not your whole site.
Red Flags That Should End the Conversation
- A fixed price before a single question about scope.
- They cannot explain their own code sample.
- They would edit parent theme or core files.
- They proudly show named client results that should be under NDA.
- No staging environment in their workflow.
- They refuse a small paid test.
- They cannot name one thing they double-check in AI-generated code.
Where to Find Developers
Upwork and Fiverr give volume and escrow, but screening is on you. OnlineJobs.ph suits hiring Philippines-based talent on a monthly basis. WordPress communities skew technical. Referrals from other business owners still tend to have the highest hit rate. Wherever you source them, the checklist matters more than the platform.
Frequently Asked Questions
How much does it cost to hire a WordPress developer?
Published benchmarks run about $25 to $50/hr for juniors, $50 to $95 mid-level, $95 to $160 senior and $160+ for experts. Rates vary by region and by whether they write custom code.
Should I hire a developer or just use a page builder?
A builder fits standard templates and basic functionality. Hire a custom developer for integrations, custom post types or anything that would need five stacked add-ons.
How do I test a developer if I am not technical?
Test reasoning. Questions 4 to 8 work without deep technical knowledge. Then run a small paid test.
Is it safe to hire a developer who uses AI?
Yes, and you will struggle to find a good one who does not. Ask what they check before shipping AI-generated code.
What belongs in the contract?
Scope with exclusions, revision limits, payment milestones, code ownership, handoff deliverables, a post-launch bug-fix window and agreed availability hours.
The Short Version
The best signal is simple: a good developer asks questions before quoting. What is the page for? What happens to the form data? What will you need to edit yourself? That curiosity about your business is what AI cannot fake.
Looking for a developer who builds for home service companies? Book a call with me.
About the author: Rolijon Clemenia is a web designer and WordPress developer based in Iligan City, Philippines. He builds fast, custom-coded websites and local SEO for home service trades like HVAC, roofing and plumbing. Read more about Rolijon.