We want to see how you think — not how quickly you can look something up. Please complete this assessment without using Google, AI tools, documentation, or any external references. If you're unsure of something, tell us what you would do to figure it out — that's a legitimate and valued answer.
There is no time limit. A thorough, well-reasoned answer that takes you an hour is worth far more to us than a rushed answer that takes ten minutes. Read each question carefully before you begin writing. We are genuinely interested in your depth of understanding, your reasoning process, and how you approach problems — not just whether you land on the right answer.
Paste is disabled on most fields to keep the playing field fair. Complete the assessment in one sitting if you can. When you're ready to begin, fill in your details below.
if ( ! defined( 'ABSPATH' ) ) { die; }<style>
#page .content p { color: blue; }
.content p { color: green !important; }
#page p { color: red; }
p { color: orange !important; }
</style>
<div id="page">
<div class="content">
<p>What colour am I?</p>
</div>
</div>💡 Consider: what does "priority" actually control about the order hooks run? And give a concrete example of a real situation where you'd need to change it.
💡 Think about the two different ways WordPress can render a block on the front end — they work quite differently. Explain both, and describe when you'd choose one approach over the other.
💡 Don't just list tools — explain your reasoning. Why those three checks first, and not something else?
💡 Assume the form submits to a custom handler and the data is being saved using $wpdb. Walk through every safety step you'd take, from the moment the form is submitted to the moment the data lands in the database.
💡 List as many methods as you can — code-based, server-level, and plugin-based. For each one, briefly explain what it does and why it helps.
💡 Think beyond just the theme editor. Cover wp-config.php settings, file permissions, user roles, and anything else you'd consider part of a hardened WordPress setup.
💡 Walk through the most likely root causes first, then explain how you'd confirm each one. What specifically would you look for in the markup and CSS?
💡 Mention any ARIA attributes, focus management, and keyboard event handling you'd expect to see — and what's missing when the menu is broken.
💡 Walk through your steps methodically — what do you check first and why? Include how you'd identify the offending plugin when the admin is inaccessible.
💡 Be specific: what do you check, in what order, and why? Think about the difference between a hook that's registered but not loading vs. one that's conditionally excluded.
💡 Be specific — reference how WordPress resolves template files and give a real example of when knowing the hierarchy saved you time or solved a problem.
💡 Tell us about a specific WordPress project you're proud of. What was the brief, what did you build or solve, and what would you do differently now? Then tell us why you'd be a good fit for Made Neat.
This usually takes 20–30 seconds. Please don't close this tab.
Thank you for completing the Made Neat WordPress Developer Assessment. Our team will review your results and be in touch shortly.