You are looking at a WordPress developer in Poland: me, Mariusz Szatkowski, working under the name WPPoland from Gdynia since 2006. I build, fix and maintain WordPress and WooCommerce sites for companies in the UK, Ireland, the US and elsewhere in Europe. I work alone, so the person who reads your brief is the person who writes the code. The project steps are further down.
Who I am
A senior WordPress developer based in Gdynia on the Polish Baltic coast. I have shipped commercial WordPress sites since 2006, published 30 free plugins on WordPress.org and organise WordCamp Gdynia. My background and recommendations are on LinkedIn.
What I do
Custom themes built from your design, WooCommerce stores and integrations, custom plugins, migrations, Core Web Vitals work and long-term maintenance.
What a remote WordPress developer from Poland takes on
Ongoing development for teams already on WordPress
New features, integrations with a CRM or ERP, changes to the marketing site and keeping PHP and plugin versions current. This suits companies where the site is part of daily operations and someone has to own its code.
Themes and plugins
Themes built from your design rather than assembled in a page builder. You bring the graphic design and wireframes, for example a Figma file or a spreadsheet template where you mark which element goes where on each view; I turn that into a responsive WordPress theme. I write a custom plugin when no existing one covers the workflow. A lot of my time goes into other people’s code: an inherited site with thirty active plugins usually needs three of them, and finding which three is the job.
Technical SEO and Core Web Vitals
Crawlability, structured data, hreflang on multilingual sites and Core Web Vitals measured on real visitors through CrUX data, before and after each change. The work is mostly removal: third-party scripts loaded later, images served as AVIF, plugins that run database queries on every request taken out.
Related pages: WordPress freelancer and development, customisation and themes adaptation.
Contract, timezone and language with a developer in Poland
- Timezone. Poland is one hour ahead of London and Dublin all year, because both switch to summer time on the same dates. New York is six hours behind, five for a few weeks in March and late October when the US and EU clocks change on different weekends. A UK or Irish team shares the full working day; a US East Coast team shares its morning.
- Contract and invoice. A B2B contract under Polish law, in English, with an NDA if you need one. Invoices carry my EU VAT ID PL7393037445; clients in other EU countries are invoiced under the reverse-charge mechanism.
- Data protection. Poland is in the EU, so the GDPR applies to my work. If I get access to a site holding personal data, I sign a data processing agreement under Art. 28 GDPR before I log in. I use no sub-processors of my own.
- Language. Briefs, proposals, commit messages and documentation are written in English.
- Holidays. Plan around Polish public holidays such as 3 May, Corpus Christi, 1 November and 11 November, which do not match the UK or US calendar.
What to check before hiring a nearshore developer
The distance that makes nearshore work affordable also makes a bad hire hard to unwind. These checks separate a developer from a reseller.
| What to verify | Why it matters | How to check |
|---|---|---|
| Public footprint | Seniority is easy to claim | WordPress.org profile, plugins, community roles |
| Who writes the code | Middlemen dilute accountability | Ask whether the person writing to you commits to the repository |
| Contract and jurisdiction | Enforceability if it goes wrong | Read the governing law clause before signing |
| Data processing agreement | Required once personal data is involved | Ask for the Art. 28 GDPR agreement before granting access |
| Handover | You must be able to leave | Ask what you receive if the work ends: repository, credentials, documentation |
Local agency, offshore team or one developer in Poland
| Local agency | Offshore team | One developer in Poland | |
|---|---|---|---|
| Timezone from London | Same | Often 5 to 8 hours | 1 hour |
| Who writes the code | Often a junior under a project manager | A team that may rotate | The developer you hired |
| Capacity | Several people in parallel | Large | One person, so scope and dates are set by one calendar |
| Availability | Depends on the contract | Depends on the contract | Working hours; no 24/7 on-call and no guaranteed response time |
One developer is the wrong choice when you need several people working in parallel or a guaranteed on-call rota. It is the right one when you want continuity: the person who built the site is the one maintaining it.
What full-scope WordPress development includes
Custom themes and plugins
Code written to your requirement and the WordPress Coding Standards, in a Git repository so every change can be reviewed and reverted.
PHP, React and headless WordPress
PHP 8, React for block editor blocks, MySQL and the WordPress core APIs. Headless setups where WordPress is the editorial backend and a separate frontend reads the REST or GraphQL API, when there is a reason for the second codebase.
Multisite and multilingual
Multisite networks, multilingual sites with correct hreflang, and WooCommerce integrations with payment providers, ERPs and CRMs.
Maintenance after launch
Maintenance covers uptime checks every 1 to 5 minutes, backups kept for at least 30 days in EU countries, and updates I test on staging before they reach production. I do not sell hosting: you choose the provider and I work with the stack you have. I offer no 24/7 on-call service and no guaranteed response or repair times.
How a WordPress project works
- Analysis. I read your brief and the existing site, its plugin stack and its performance data, and ask follow-up questions in writing.
- Proposal. Scope, assumptions and timeline are written down before code is written.
- Build. Code lives in a private Git repository. Every push goes to staging; production changes only after your approval.
- Review on staging. You check the work there and get a written description of each change.
- Launch. Deployment runs through a repeatable pipeline with a rollback path, after a test in current Firefox, Chrome, Safari and Edge and on iOS and Android.
On WooCommerce the checkout and payment path is tested end to end, including failed payments, before anything reaches production.
How to start
Send your scope, deadline and stack through the contact form. You get the next steps in writing and a proposal stating the assumptions it rests on. Related delivery work sits under WordPress developer.



