What is a WordPress developer? Someone who builds, extends and maintains WordPress sites and stores in code: PHP, JavaScript (React for Gutenberg), SQL and the core APIs. At WPPoland that is me, Mariusz Szatkowski. I have worked with WordPress since 2006, alone, from Gdynia in Poland. I write themes and plugins, work on Core Web Vitals, harden installs and connect WordPress to business systems. My patches go to Trac with tests. I do not configure Divi, Elementor or Avada sites. If the brief is already clear, service scope and pricing is below.
Key facts (short version)
A WordPress developer writes PHP 8.x and React (Gutenberg), builds block themes and plugins, wires CRM and ERP APIs, and builds WooCommerce stores to the WordPress Coding Standards. On this site that person is Mariusz Szatkowski, working alone.
A WordPress specialist handles the fire: failed updates, malware clean-up, Core Web Vitals (LCP within Google’s 2.5 s threshold), and database and cache scaling when traffic grows.
Who: Mariusz Szatkowski, WordPress developer since 2006, based in Gdynia, Poland. I work alone, with no team and no subcontractors, so the code you receive is code I wrote. I organise WordCamp Gdynia and have 30 free plugins on WordPress.org.
What: custom WordPress themes and WooCommerce stores, plugins, API integrations, headless builds, Core Web Vitals work measured on real-user data, multilingual sites and maintenance.
Pricing: scope and budget are set individually after a written brief. Rough timelines: simple site 1-2 weeks, business site 3-6 weeks, WooCommerce store 6-10 weeks, larger build with integrations 8-12 weeks or more.
Who you are hiring
- Shipping commercial WordPress since 2006, before Gutenberg and the REST API
- Senior-led: the engineer at discovery is the engineer at the keyboard at week six
- No offshore handoff, no PM layer billed back to you
- WordCamp Europe organiser, WordPress Foundation Credits mentor
- Shopify Academy: CRO learning path plus Partner Marketing (Credly, 2025)
WordPress developer skills 2026
A WordPress developer in 2026 needs to be at home in PHP 8.x, JavaScript with React, and the database, because they answer for whether the site is secure and holds up under load. The table sorts the stack by layer.
Work beyond WordPress (APIs, integrations, apps without a CMS) is covered on the software developer page.
| Layer | Day to day | Alongside |
|---|---|---|
| Backend | PHP 8.x (OOP, typed properties, enums), WordPress Core API, WooCommerce REST | Laravel, Symfony, Composer |
| Frontend | React, JavaScript ES6+, Gutenberg blocks, Full Site Editing, Tailwind | Next.js, Astro, Vue.js |
| Databases | MySQL / MariaDB, WP_Query optimisation, custom tables | Redis, PostgreSQL, ElasticSearch |
| DevOps | Git, Composer, NPM, CI/CD, Docker, staging and production | Cloudflare Workers, AWS, GCP |
| Security | WP hardening, OWASP Top 10, SQL injection and XSS protection | WAF, CSP, security headers |
A site looked after by a developer differs from a page-builder assembly in technical debt, attack surface, and the cost of every later change. It shows the first time the site needs something unusual.
What you can check in public
Everything in this list can be verified in open sources:
- WordPress core contributions: patches with unit tests submitted via Trac across query classes, the REST API and internationalisation (including #51811,
sas an alias forsearchinWP_Term_Query; #43502, reset postdata in the REST posts controller; #64986, gettext in preview). I am also a general translation editor for Polish (1,400+ strings), credited in the WordPress 7.0 release (profiles.wordpress.org/motylanogha). - Plugins on WordPress.org: 30 free plugins on my profile, including Polski for WooCommerce, which covers Polish store requirements and is maintained to the WordPress Coding Standards.
- Code on GitHub: for example
woocommerce-mcp, a read-only Model Context Protocol server that exposes WooCommerce data to AI agents. - Community: organiser of WordCamp Gdynia (since 2015), co-organiser of WordCamp Poland (since 2016) and WordCamp Europe (since 2024), conference speaker, and WordPress Foundation Credits Mentor (since 2025).
- This site: wppoland.com runs on Astro, and the rebuild write-up shows the process and architecture.
WordPress developer code examples
The difference shows up in the code that ships to production. Four patterns: a safe write, a listing without N+1, a REST endpoint, and caching.
1. Saving meta safely: per-post permission, nonce, sanitisation
A check of the edit_post capability for the specific post instead of a broad role, a nonce on save, and input sanitised before it reaches the database. Escaping happens separately, on output.
What this means for you: only the people who should be able to change a record can change it, and no outside page can trigger that write on their behalf. Without this chain, a single author login is enough to quietly rewrite data nobody keeps a separate backup of.
Show PHP code (44 lines)
declare( strict_types=1 );
add_action( 'init', 'wppl_register_projekt_meta' );
add_action( 'save_post_wppl_projekt', 'wppl_save_projekt_meta', 10, 2 );
// Meta with typing, sanitisation, and a capability-based auth_callback.
function wppl_register_projekt_meta(): void {
register_post_meta(
'wppl_projekt',
'wppl_budzet_pln',
array(
'type' => 'integer',
'single' => true,
'show_in_rest' => true,
'sanitize_callback' => 'absint', // Integer, no negatives.
'auth_callback' => static function ( bool $allowed, string $meta_key, int $post_id ): bool {
return current_user_can( 'edit_post', $post_id );
},
)
);
}
// Saving meta with the full security chain.
function wppl_save_projekt_meta( int $post_id, WP_Post $post ): void {
// 1. Nonce - CSRF protection.
if ( ! isset( $_POST['wppl_budzet_nonce'] )
|| ! wp_verify_nonce( sanitize_key( wp_unslash( $_POST['wppl_budzet_nonce'] ) ), 'wppl_save_budzet' )
) {
return;
}
// 2. Skip autosave and revisions.
if ( ( defined( 'DOING_AUTOSAVE' ) && DOING_AUTOSAVE ) || wp_is_post_revision( $post_id ) ) {
return;
}
// 3. Permission for the specific post, not the generic 'edit_posts'.
if ( ! current_user_can( 'edit_post', $post_id ) ) {
return;
}
// 4. Sanitise input before saving.
$budzet = isset( $_POST['wppl_budzet_pln'] )
? absint( wp_unslash( $_POST['wppl_budzet_pln'] ) )
: 0;
update_post_meta( $post_id, 'wppl_budzet_pln', $budzet );
}The clicker: stores the data in a page-builder field with no dedicated capabilities or nonce, so any author (and often CSRF) can overwrite the value, and the data is frequently saved raw and echoed back without esc_attr().
2. An efficient WP_Query with no N+1 problem
With 'fields' => 'ids', WordPress does not prime post meta, so every get_post_meta() call in the loop runs its own query. One update_meta_cache() call after fetching the IDs loads meta for all of them at once.
What this means for you: a listing of fifty items hits the database twice instead of fifty-one times. Under heavier traffic the server simply has less to do.
Show PHP code (30 lines)
function wppl_get_projekty( int $limit = 12 ): array {
$query = new WP_Query(
array(
'post_type' => 'wppl_projekt',
'post_status' => 'publish',
'posts_per_page' => $limit,
'no_found_rows' => true, // No SQL_CALC_FOUND_ROWS - I do not count pagination.
'fields' => 'ids', // Only IDs, not full objects.
'update_post_term_cache' => false, // Taxonomies not needed here.
)
);
$ids = $query->posts;
if ( empty( $ids ) ) {
return array();
}
// The key to avoiding N+1: prime meta for all IDs in a single query.
update_meta_cache( 'post', $ids );
$projekty = array();
foreach ( $ids as $post_id ) {
$projekty[] = array(
'id' => (int) $post_id,
'budzet' => (int) get_post_meta( $post_id, 'wppl_budzet_pln', true ), // Cache hit.
);
}
return $projekty;
}The clicker: a loop over bare IDs that calls get_post_meta() on every iteration, without priming the cache first, sends one SQL query per post. On top of that, the default SQL_CALC_FOUND_ROWS counts rows for pagination the listing does not have.
3. A REST API endpoint with a real permission_callback and schema
Authorisation for the specific object in permission_callback, plus type, validation and sanitisation of arguments declared in the route definition. That is the schema the API index also describes.
What this means for you: a CRM or ERP integration does not hand your data to anyone who finds the URL, and it does not break the first time the vendor changes something on their side.
Show PHP code (25 lines)
add_action( 'rest_api_init', 'wppl_register_rest_routes' );
function wppl_register_rest_routes(): void {
register_rest_route(
'wppoland/v1',
'/projekty/(?P<id>\d+)/budzet',
array(
'methods' => WP_REST_Server::EDITABLE, // POST, PUT, PATCH.
'callback' => 'wppl_rest_update_budzet',
// Real authorisation: permission for the SPECIFIC post.
'permission_callback' => static function ( WP_REST_Request $request ): bool {
return current_user_can( 'edit_post', (int) $request['id'] );
},
'args' => array(
'budzet' => array(
'type' => 'integer',
'required' => true,
'minimum' => 0,
'sanitize_callback' => 'absint',
'validate_callback' => 'rest_validate_request_arg',
),
),
)
);
}The clicker: plugin forms often expose data through admin-ajax or a route with permission_callback set to __return_true, with no type validation or schema, which opens the door to unauthorised writes and breaks the predictability of integrations.
4. Cache invalidation via last_changed
WordPress core’s last_changed pattern: a single write invalidates a whole family of cache keys. The detail that matters is the difference between the before_delete_post and deleted_post hooks.
What this means for you: after an edit the site shows the new version straight away, with nobody having to ask somebody else to clear a cache first.
Show PHP code (18 lines)
// Cache key based on the last_changed marker - one invalidation
// clears every variant (different $limit values) without deleting them one by one.
function wppl_projekty_cache_key( int $limit ): string {
$last_changed = wp_cache_get_last_changed( 'wppl_projekty' );
return sprintf( 'wppl_projekty_%d_%s', $limit, $last_changed );
}
add_action( 'save_post_wppl_projekt', 'wppl_flush_projekty_cache' );
add_action( 'before_delete_post', 'wppl_flush_projekty_cache' );
// I use before_delete_post because deleted_post fires AFTER the post is gone,
// when get_post_type() already returns false and the type cannot be checked.
function wppl_flush_projekty_cache( int $post_id ): void {
if ( 'wppl_projekt' !== get_post_type( $post_id ) ) {
return;
}
wp_cache_set_last_changed( 'wppl_projekty' ); // New marker = new keys.
}The clicker: page-builder cache plugins either hold stale data until a manual purge or try to delete individual keys and miss variants; wiring invalidation to deleted_post instead of before_delete_post silently stops working, because the post type can no longer be checked.
Four questions worth putting to anyone you shortlist
Ask how they check permissions before writing data, what a listing page costs in database queries, how they expose an integration without opening it to everyone, and what happens to their work when WordPress updates. Ask me too. Send the address of your current site and you will get those four answers about that specific site, not a capability deck. Scope and pricing come later and are individual.
Get the four answersHow a WordPress developer differs from an implementer
The implementer relies on ready-made themes and plugins; the developer writes what is missing and keeps the code small. Anyone who rents cheap hosting can click through a WordPress auto-installer, and for a brochure page that may be enough. It stops being enough once the site has to carry a real WooCommerce checkout or talk to another system.
The implementer (clicker)
Starts from a large marketplace theme and fills the gaps with more plugins and a builder such as Elementor or Divi. Every page loads the scripts and styles of all those layers, and every update touches a dozen independent sources of risk.
The WordPress developer
Treats WordPress as a framework with an API. Business logic goes into PHP, blocks into React, and plugins only where they earn their place. Each page loads what it needs, which makes Google’s Core Web Vitals thresholds easier to stay within.
What is a WordPress developer
I build custom themes and plugins, connect WordPress to CRM and ERP systems, run security audits and work on Core Web Vitals. The code follows the WordPress Coding Standards, and I add plugins only where they are needed.
Custom WordPress themes
Block themes (FSE) written from scratch from your wireframes and graphic design, responsive and built to WCAG 2.2 AA.
WooCommerce stores
Payments through Stripe, PayPal, Klarna or Mollie, shipping through Royal Mail, DPD or other carriers via their APIs, B2B pricing, multi-currency and multilingual stores.
Custom plugins and legacy code
When no existing plugin fits your process, I write one. I also take over code from a previous supplier and tidy it up.
Performance and Core Web Vitals
Object cache (Redis), CDN, WebP and AVIF images, a clean database and queries. Measured on CrUX data from real visitors, not a single Lighthouse run.
API integrations and headless
WordPress exchanging data with CRM, ERP and invoicing tools over the REST API or WPGraphQL. On a headless build the frontend is Next.js or Astro.
Security audits and hardening
Reviewing plugins and custom code for XSS and SQL injection, security headers, two-factor login for administrators, and a restore path that has actually been tested.
Headless makes sense when the frontend has to do something a WordPress theme handles awkwardly, such as merging data from several sources. WordPress stays the editorial back end and a Next.js or Astro frontend pulls content over the API. For an ordinary company site it is an extra layer you do not need, and I say so before quoting.

How much a WordPress developer earns
The most transparent public figure for the UK comes from ITJobsWatch, which tracks advertised vacancies: the median salary for permanent jobs citing WordPress was 37,500 GBP in the six months to 29 October 2026 (ITJobsWatch, WordPress). The page shows no contractor day rate for the skill, so I do not quote one. Advertised salaries are what employers offer, not what senior specialists end up earning.
What moves the number is visible in the same job ads:
- PHP and React deep enough to write blocks and plugins, not just theme settings.
- WooCommerce with integrations: payment providers, carriers, stock and accounting systems.
- Location and contract type: a permanent role in London or a contract outside IR35 are priced differently.
- Accessibility and privacy knowledge, now that clients ask about WCAG and cookie consent before they ask about design.
When AI shows up in hiring, real code still decides it: WordPress AI hiring and real code, October 2026.
Total cost of a WordPress site over three years
“How much does a WordPress developer cost” is usually a question about the whole life of the site, not the first invoice. The cheapest offer from a classifieds portal often leaves technical debt that comes due later: during a sales campaign, a hosting move, or the first integration.
| Area | Cheapest offer (clicker) | Individual quote (developer) |
|---|---|---|
| Starting point | ready theme with Elementor or Divi, many plugins | block theme (FSE) built to your design, few plugins |
| Core Web Vitals | builder scripts on every page | target is Google’s thresholds: LCP up to 2.5 s, INP up to 200 ms, CLS up to 0.1 |
| Security | updates postponed because something might break | updates tested on staging, custom code reviewed |
| Integrations | payments and shipping bolted on plugin by plugin | payments, shipping and invoicing configured together |
| Later years | bigger changes often mean a rebuild | extending what is already there |
Most sites that reach me worked fine until someone wanted to change something. The first unusual request, a new field on the order or a link to the accounting system, shows whether the code can grow.
Cookies, privacy and contracts for UK and Irish clients
For UK sites, cookies fall under regulation 6 of the Privacy and Electronic Communications Regulations 2003, as substituted on 5 February 2026 by the Data (Use and Access) Act 2025. The new Schedule A1 lists exceptions to consent, including storage strictly necessary for the service, statistical purposes and website appearance. A consent banner configured for an EU site is therefore not automatically right for a UK one, and I check against the current text before setting it up. In both cases I verify in the browser’s network tab that nothing non-essential loads before consent, not only in the banner settings.
Before I get access to a site holding personal data, I sign a data processing agreement under Article 28 GDPR (UK GDPR for UK clients). I use no sub-processors. The contract is governed by Polish law and invoiced from my EU VAT ID PL7393037445.
WordPress freelancer or agency
The choice depends on scale: with a freelancer you talk directly to the person writing the code, an agency has more people for large rollouts. Agencies that already sell WordPress and need development under their own brand use the agency development desk.
| Criterion | Freelancer | Agency |
|---|---|---|
| Typical fit | custom plugin, audit, refactor, migration | large rollout with design, copy, marketing |
| Communication | direct with the person writing the code | through a project manager |
| Bus factor | higher risk, one person | lower, cover available |
| Technical decisions | fast, no approval chain | slower, through several people |
I work as a freelancer: I write the code myself, and graphic design and wireframes come from you. I limit the bus factor by keeping the code in your repository with written change notes, so any developer after me can take over.
How to become a WordPress developer
The WordPress basics take a few months to learn; reaching the point where someone pays for your code usually takes at least two years of hands-on PHP, databases and modern frontend work. Installing a theme and configuring plugins is administration.
A realistic path: first HTML, CSS, JavaScript basics and the WordPress loop; then PHP 8.x, hooks and filters, the REST API and React for blocks; after that architecture, headless, design patterns, integrations, performance and security; finally audits, large builds and patches to core.
Real client work teaches fastest. The WordPress Developer Handbook is a better starting point than any bootcamp, but the real lift comes from reading core Trac tickets, watching how contributors argue patch trade-offs in Make WordPress Slack and the Advanced WordPress group, and shipping work that has to survive a traffic spike. I learned WP_Query not from the documentation, but from reading what Otto and Mark Jaquith answered on trac.wordpress.org back in 2009.
Hire a WordPress developer
Dutch searches for WordPress ontwikkelaar or gecertificeerde wordpress ontwikkelaar map to the same hire brief: PHP, WooCommerce, written scope before code.
Looking for a WordPress developer for hire? You work with me directly: written scope before the first line of code, staging for review, and the same person from start to finish. The quote follows the agreed scope. I also build and run stores as a WooCommerce developer.
A developer makes sense once the project moves beyond a simple brochure page, for example when:
- you need integrations with CRM, ERP, payments or internal tools,
- WooCommerce is slow, unstable or hard to scale,
- you want to rebuild a site trapped in Elementor, Divi or another heavy builder,
- legacy code needs repairing and bringing under control,
- you are planning a migration, a multilingual rollout, a member area or a headless setup.
Three situations have a fixed scope and their own page: a migration assessment when you want to know what a move to WordPress involves before you commit to it; a WooCommerce rescue sprint when cart, payment or orders have stopped working; a store reliability plan when checkout has to keep working while nobody watches the dashboard.
Cooperation process
Every step is written down, so you know what happens next:
- Brief and scope: requirements in writing, questions about integrations and hosting, then a specification and a quote with its assumptions.
- Layout: you mark which elements belong on each view in a spreadsheet template I send. Graphic design and mockups stay on your side; I code the responsive theme from that layout.
- Build: code in a Git repository, every change on staging with a note on what changed.
- Launch: before go-live I check Core Web Vitals, accessibility and SEO basics. After that the site can move into my maintenance.
I work by email, in documents and in the repository, so every decision stays on record. If you need a call, tell me.
Types of WordPress projects and timelines
| Project type | Price | Rough timeline | Best for | What it covers |
|---|---|---|---|---|
| Simple website | individual quote | 1-2 weeks | small businesses, portfolios | responsive theme, basic SEO, a few pages |
| Business website | individual quote | 3-6 weeks | growing companies | custom features, more content types |
| WooCommerce store | individual quote | 6-10 weeks | online retailers | payments, shipping, invoices, stock |
| Larger build | individual quote | 8-12 weeks or more | larger organisations | API integrations, multisite, custom architecture |
| Maintenance | individual quote | monthly | sites after launch | updates, monitoring, backups |
WordPress in numbers
According to W3Techs (October 2026), WordPress runs 39.5% of all websites and 58.3% of sites whose CMS can be identified. It has grown from a blogging platform into a framework that also serves headless architectures and AI implementation for companies.
Global market significance of WordPress (2025/2026)
Market data clearly shows why WordPress developer skills are so highly demanded globally.
Should you build a WordPress site with a page builder
A page builder can be fine at the start, but on a demanding project it soon gets in the way. The site gets heavy and depends on more and more add-ons. A custom theme contains only what the site needs, so it is easier to extend without slowing down. If the site has to run reliably today and grow next year, build it properly from the start.
Describe your WordPress project
Send a short brief of your requirements, the current state of the site and the problem to solve. From that I prepare a scope and a quote. Every quote is individual.
Send the briefRelated services
- WooCommerce development: stores and integrations
- WordPress maintenance: updates, monitoring, backups
- Performance optimization: Core Web Vitals
- WPPoland rebuild: public write-up of process and architecture
Regional pages
- WordPress Developer Warsaw
- WordPress Developer Krakow
- WordPress Developer Gdansk
- WordPress Developer Poznan
- WordPress Developer Wroclaw
- WordPress Developer Lodz
- WordPress Developer Berlin
- WordPress Developer London
- WordPress Developer Dublin
- WordPress Developer Amsterdam
- WordPress Developer Paris
- WordPress Developer Madrid
- WordPress Developer Barcelona
- WordPress Developer Lisbon
- WordPress Developer Milan
- WordPress Developer Rome
- WordPress Developer Prague
- WordPress Developer Munich
- WordPress Developer Hamburg
- WordPress Developer Copenhagen
- WordPress Developer Stockholm
- WordPress Developer Oslo
- WordPress Developer Helsinki
About the author. Mariusz Szatkowski, WordPress developer since 2006, working as WPPoland since 2007. Organiser of WordCamp Gdynia and author of 30 free plugins on WordPress.org. Works alone and remotely from Gdynia.
Sources. WordPress market share: W3Techs, as of 29 October 2026. UK salary: ITJobsWatch, six months to 29 October 2026. Core Web Vitals thresholds: web.dev. Cookie rules: legislation.gov.uk.




