Back to blog
November 19, 2026•6 views

How to Vet a WordPress Developer in 2026: Portfolio, Code Review, and Security Questions

hire wordpress developerwordpress developer vettingwordpress securitycode reviewhiring developers
How to Vet a WordPress Developer in 2026: Portfolio, Code Review, and Security Questions

Most "questions to ask a WordPress developer" articles are written for the developer, not for you. They are trivia quizzes: how many tables does WordPress create by default, what year was it launched, name three default post types. A candidate can memorize all of that in an afternoon and still write a theme that leaks data and breaks on the next PHP release.

I have hired and worked alongside WordPress developers for years, and I have also cleaned up the aftermath when a founder hired the wrong one. The expensive failures almost never come from a lack of trivia knowledge. They come from someone who cannot read a stack trace, ships a plugin with an unescaped database query, or has never touched version control because they edit files over FTP.

So this is the hiring-side guide. It walks through how to vet a WordPress developer in three passes: the portfolio review, a real code review, and a security conversation. Along the way I will give you the specific questions that actually reveal judgment, plus a scoring rubric you can reuse.

Why most WordPress vetting goes wrong

WordPress is deceptively easy to look competent in. A developer can install a theme, drag around a page builder, and produce something that looks fine in a screenshot. The problems show up six months later: a 4-second load time, a hacked site, an update that white-screens the homepage, or a custom feature that nobody can maintain because it lives in a snippet pasted into functions.php.

The fix is to stop evaluating output that is easy to fake (screenshots, a polished landing page) and start evaluating the things that are hard to fake: how they structure code, how they handle a database query, what they do before pushing to production, and how they think about security.

Treat vetting as a funnel:

  1. Screening (10 to 15 minutes): fit, communication, rate, availability, and a quick read of their portfolio.
  2. Portfolio review (your homework): verify claims, look at real sites, inspect what is publicly visible.
  3. Technical conversation (30 to 45 minutes): a few senior-level questions that reveal depth.
  4. Practical task (paid, 2 to 4 hours): a small, realistic piece of work.
  5. References and trial: short paid engagement before a long contract.

Each stage filters out a different failure mode. Skip one and you are gambling.

What "2026-ready" actually means

The fundamentals of good WordPress work have not changed, but the baseline has moved. A developer who is current in 2026 should be comfortable with a few concrete things, and you can ask about them directly:

  • Modern PHP. WordPress has been actively pushing its minimum PHP version upward, and current releases officially support PHP 8.1 through 8.3 (with 8.4 support arriving in recent versions). A developer still writing code that only runs cleanly on PHP 7.4 is a maintenance risk. Ask: "What PHP version do you target, and how do you test for deprecation warnings?"
  • Block editor fluency. The block editor (Gutenberg) is the default editing experience, and modern themes lean on theme.json and block patterns rather than the old Customizer-only approach. Ask whether they build custom blocks and how they structure a theme.json.
  • Block themes versus classic themes. Both are legitimate. What matters is that the developer can explain the trade-offs and knows when a block theme is the right call.
  • A real local and staging workflow. Local development with a tool like wp-env, Local, or Docker, plus a staging environment and version control, is the modern baseline. "I edit on the live server" is not.

You do not need to know the answers yourself. You need to hear specific ones.

Pass 1: The portfolio and claims review

Before you talk to anyone, do the homework. Ask for a list of 5 to 10 live sites they built or maintain, and their specific role on each.

What to actually check on each live site

Open the sites in a browser and run through this. You do not need to be a developer to spot most of it.

  • View source and search for "wp-content". If you see it, it is WordPress. Now check whether the theme looks custom or is a heavily modified commercial theme. Neither is disqualifying, but it tells you what kind of work they do.
  • Run the site through PageSpeed Insights. A developer who consistently ships sites scoring in the red on Core Web Vitals is telling you something.
  • Check the footer and read the fine print. "Built by" credits, theme names, and plugin credits are honest fingerprints.
  • Look for broken things. Console errors, mixed content warnings, forms that do not submit. Sloppy live sites are a preview of your live site.
  • Click into a blog post and a product page. Does the layout hold up on inner pages, or only on the homepage hero?

Questions that verify the portfolio

Ask these and watch how they answer:

  • "On this site, what did you build versus what was already there?"
  • "Which plugins were essential, and which would you remove if you rebuilt it today?"
  • "What was the hardest part of this project, and how did you solve it?"
  • "Can I speak to this client?"

Vague answers ("I did everything") on a site that clearly uses a commercial theme and six page-builder add-ons are a red flag. Honest answers ("I customized this theme, built two custom plugins, and handled the migration") build trust.

Pass 2: The code review (yes, you can do this)

You do not need to read PHP fluently to review code. You need to know what good looks like and ask them to walk you through it. Ask for a small sample: a custom plugin, a child theme's functions file, or a snippet they are proud of. If they cannot share client code (fair), ask for a public GitHub repo or a small demo.

Here is a code review checklist you can run, even with limited PHP knowledge. The escaping, sanitizing, and database functions below are all documented in the WordPress developer reference.

What to look for Why it matters Red flag
Uses version control (Git) Recoverable history, collaboration, deploys "I edit on the server" or no repo at all
Escapes output (esc_html, esc_attr, esc_url) Prevents XSS attacks Raw echo $variable everywhere
Sanitizes input (sanitize_text_field, absint) Blocks injection and bad data Trusts $_POST directly
Uses $wpdb->prepare() for custom SQL Prevents SQL injection String-concatenated queries
Enqueues scripts/styles properly No conflicts, correct load order Hardcoded <script> tags in templates
Uses hooks (actions/filters) Extensible, upgrade-safe Edits core files or a parent theme directly
Nonces and capability checks on forms Prevents CSRF and privilege abuse Admin actions with no capability check
Child theme or clean custom theme Survives parent theme updates Modified parent theme, changes vanish on update
No bloated plugin stack Performance and security surface 40 plugins for basic features

A quick way to test whether they understand escaping: ask them to explain the difference between esc_html() and esc_attr(), and when each applies. A strong answer shows they think about context. A weak answer is "they both clean the output."

Senior-level technical questions

These separate people who use WordPress from people who understand it. You do not need to know the perfect answer. You need to hear a confident, specific one.

  • "Walk me through what happens when someone visits a WordPress URL." Strong answers mention the web server, index.php, wp-load.php, the query, the template hierarchy, and the render. Weak answers stop at "the theme loads."
  • "Actions versus filters. Give me a real example of each you have used." This reveals whether they actually extend WordPress or just configure it.
  • "How would you add a custom post type and its fields without a plugin?" Look for register_post_type, meta boxes or the block editor, and register_meta.
  • "How do you debug a white screen of death?" Strong answers: enable WP_DEBUG, check the error log, disable plugins, isolate the theme. Weak answers: "reinstall WordPress."
  • "How do you manage deployments and database changes across staging and production?" Look for version control, a migration process, and a staging environment. "I just upload files" is a no.

Pass 3: The security and performance conversation

This is where most vetting falls apart, because founders do not know what to ask. Security is not a checkbox; it is a set of habits. Here are the security questions worth asking, and what a good answer sounds like.

Security questions to ask a WordPress developer

  • "What is your process for keeping a site secure after launch?" Good: managed updates, staging tests before updating, least-privilege user roles, backups, and a WAF or security plugin configured properly. Bad: "I install a security plugin and forget it."
  • "How do you handle user input and database queries?" Good: sanitize on input, escape on output, $wpdb->prepare() for custom queries, nonces on forms. Bad: silence, or "WordPress handles that."
  • "What do you do when a client site gets hacked?" Good: isolate, identify the entry point, clean files and database, rotate credentials, restore from a known-good backup, then harden. Bad: "I reinstall."
  • "How do you manage credentials and API keys?" Good: environment variables or wp-config constants outside version control, secrets managers. Bad: keys hardcoded in a theme committed to a public repo.
  • "What is your backup and recovery plan?" Good: automated off-site backups with a tested restore. Bad: "the host does backups" with no idea how to restore.
  • "How do you handle plugin and core updates on a live site?" Good: staging first, changelog review, rollback plan. Bad: auto-update everything and hope.

Performance questions (Core Web Vitals)

Performance is a security-adjacent skill because a slow, plugin-bloated site is also a fragile one. Ask:

  • "How do you approach Core Web Vitals on a WordPress site?"
  • "What is your caching strategy (page cache, object cache, CDN)?"
  • "How do you decide whether to use a page builder or custom blocks?"

A developer who can talk about LCP, image optimization, critical CSS, and object caching without reaching for a single "speed" plugin is worth more than one who installs five.

The practical task: your best filter

Nothing beats a small, paid, realistic task. Keep it to 2 to 4 hours and pay for it. A good brief:

  • Build a small custom plugin that registers a shortcode rendering a list of recent posts, with proper escaping and a filter to change the number of posts.
  • Or: fix a deliberately broken snippet (an unescaped query and a missing nonce) and explain the fix in two paragraphs.

You are not testing speed. You are testing whether they escape output, use hooks, structure files sensibly, and can explain their choices. Ask them to submit the code plus a short written explanation. The explanation often tells you more than the code.

Screening for fit across regions

Your vetting bar does not change by country, but the logistics do. The same questions apply everywhere; what shifts is the paperwork and the time zone. A few things to confirm regardless of where a candidate is based:

  • Time-zone overlap. How many hours of real overlap will you have for standups and urgent fixes?
  • Invoicing and tax. Can they invoice cleanly, and who handles any applicable VAT or GST?
  • IP ownership. Confirm in writing that you own the code and assets on delivery.
  • References. Ask for at least one reference you can actually call, ideally in a similar time zone.

If you are weighing a freelancer against an agency, ask both the same security and code questions. Agencies sometimes route your work to a junior, so ask who will actually write the code.

A simple scoring rubric

Score each candidate out of 5 on each row. Anything below 3 on security or code quality is a pass, regardless of portfolio.

Criterion What you are scoring Weight
Portfolio quality Real, live, working sites with clear role 15%
Code quality Escaping, hooks, Git, structure 25%
Security habits Updates, backups, input handling, credentials 25%
Performance Core Web Vitals, caching, plugin discipline 15%
Communication Clear answers, asks good questions 10%
Fit and logistics Time zone, availability, invoicing, references 10%

Red flags to walk away from

  • Cannot explain the difference between actions and filters.
  • No version control, or edits files directly on the server.
  • Modifies parent themes or core files.
  • Installs 30+ plugins to avoid writing code.
  • Hardcodes credentials or API keys in theme files.
  • Has no staging environment and no backup or restore plan.
  • Answers security questions with "WordPress handles that."
  • Cannot name a single client who will vouch for them.

Before you sign: lock down ownership and backups

Two things bite founders after the handshake, long after the interview is forgotten. The first is data ownership: if you cannot restore your own site without the developer, you do not really own it. Walk through a backup and data-ownership checklist with your candidate and ask them to demonstrate a restore on staging. The second is baseline security expectations. If you are a solo founder hiring help, the NIST Cybersecurity Framework gives you a plain-language list of what to demand from anyone you hire, useful ammunition when a developer waves off your questions.

About the author

I am a web developer and technical consultant who has built and audited WordPress and modern JavaScript sites for clients across several markets, and I run the same code and security review on every project I take on. This guide reflects the checklist I use when I am the one doing the hiring, and the mistakes I have seen cost founders the most.

FAQ

Q: How many questions should I ask a WordPress developer before hiring? A: Focus on quality over quantity. A 30-minute call with 6 to 8 well-chosen questions beats a 40-question trivia quiz. Prioritize the request lifecycle, actions versus filters, escaping and sanitizing, $wpdb->prepare(), staging and deployment, and security and backup habits. Then give them a small paid task. The task will tell you more than any list of questions.

Q: Do I need to know PHP to vet a WordPress developer? A: No, but you need to know what good looks like. Learn the red flags: raw echo $variable, string-concatenated SQL, edits to core or parent theme files, hardcoded credentials, no version control, and a bloated plugin stack. Ask the developer to walk you through a snippet and explain their choices. If they cannot explain their own code clearly, that is your answer.

Q: What PHP version should a WordPress developer be targeting in 2026? A: Current WordPress releases officially support PHP 8.1 through 8.3, with 8.4 support arriving in recent versions. A developer who only writes code that runs cleanly on PHP 7.4 is a maintenance risk. Ask what version they target and how they test for deprecation warnings.

Q: How do I check a WordPress developer's security practices? A: Ask directly about their process for updates, backups, input handling, credentials, and incident response. Then verify: ask to see a staging workflow, a backup restore process, and how they store API keys. A strong answer shows habits, not a single plugin. Run the same questions on an agency and ask who will actually write your code.

Frequently asked questions

How many questions should I ask a WordPress developer before hiring?

Focus on quality over quantity. A 30-minute call with 6 to 8 well-chosen questions beats a 40-question trivia quiz. Prioritize the request lifecycle, actions versus filters, escaping and sanitizing, $wpdb->prepare(), staging and deployment, and security and backup habits. Then give them a small paid task. The task will tell you more than any list of questions.

Do I need to know PHP to vet a WordPress developer?

No, but you need to know what good looks like. Learn the red flags: raw echo $variable, string-concatenated SQL, edits to core or parent theme files, hardcoded credentials, no version control, and a bloated plugin stack. Ask the developer to walk you through a snippet and explain their choices. If they cannot explain their own code clearly, that is your answer.

What PHP version should a WordPress developer be targeting in 2026?

Current WordPress releases officially support PHP 8.1 through 8.3, with 8.4 support arriving in recent versions. A developer who only writes code that runs cleanly on PHP 7.4 is a maintenance risk. Ask what version they target and how they test for deprecation warnings.

How do I check a WordPress developer's security practices?

Ask directly about their process for updates, backups, input handling, credentials, and incident response. Then verify: ask to see a staging workflow, a backup restore process, and how they store API keys. A strong answer shows habits, not a single plugin. Run the same questions on an agency and ask who will actually write your code.

Share this post

Native Web Share is available on mobile, so that share sheet includes Instagram and any other app you have installed.

Let's Connect

Get In Touch

Let's build something premium together.

Contact info

Follow me
Chat on WhatsApp