# Freelance PHP Developer: How to Hire, Vet and Contract

> Find a freelance PHP developer through referrals, platforms such as Upwork, Malt or freelancermap, and contractor job boards. Check live projects or public code, start with a short paid trial, and put a written IP assignment in the contract. Treat them as a business, not an employee, or you risk IR35 problems in the UK and misclassification claims elsewhere.

- URL: https://php-entwickler-gesucht.de/en/hiring/freelance-php-developer/
- Language: en
- Updated: 2026-10-19
- Publisher: PHP-Entwickler gesucht (OnlineBuilders LLC, https://onlinebuilders.biz)

ITJobsWatch counted 76 UK contract jobs citing PHP in the six months to 18 October 2026, with a median day rate of £470. On freelancermap, the German-speaking market's big project board, close to 8,800 profiles mention PHP. Supply isn't the problem. The problem is that most profiles look the same, and the differences only show once the work starts.

Then there's employment law. Treat a contractor like an employee and you may end up owing employment taxes, in the UK, the US and most of the EU. That happens faster than many clients think.

## When a freelancer is the right call

Freelancers are expensive per hour and cheap per project, provided the project has an end. They fit well-scoped work: an upgrade from PHP 8.1 to 8.4, a payment integration, a performance audit. They also work as reinforcement when your team is too small for a few months.

They fit badly with ongoing operations and product ownership. If one contractor is the only person who understands your code for years, you have a concentration risk. When they take a better offer, the knowledge walks out with them.

My view: for a product you'll run for years, keep at least one employee at the core of the team. Freelancers add capacity; they don't replace a core team. If you need a permanent hire, see our guide on how to [hire a PHP developer](https://php-entwickler-gesucht.de/en/hiring/hire-php-developer/).

## Where to find freelance PHP developers

The options split into marketplaces that only connect you and services that also handle the contract.

| Channel | Model | Good for |
|---|---|---|
| Upwork | global marketplace with payment handling | English-language projects, wide price range |
| Malt | European platform with payment handling | small and mid-sized projects in Europe |
| freelancermap | project board, you contact people directly | Germany, Austria, Switzerland |
| Contractor job boards and LinkedIn | you post, contractors apply | UK and US day-rate contracts |
| Referrals | direct | often the best matches |
| Local PHP meetups | direct | specialists with a local link |

Agencies and brokers that handle contracting add a margin to the rate. For that, they do part of the vetting and sometimes share the status risk. Whether that's worth it depends on how many contractors you engage each year.

Search terms matter on every platform. "PHP" returns thousands of hits. "Laravel upgrade", "Symfony 7" or "PHPStan" return people who actually work on those things.

## Check a profile in 15 minutes

Freelancer CVs are often project lists full of keywords. You can't learn much from those. Look for things you can verify yourself.

**What to check before the first call**

- [ ] At least one project that's live or has public code
- [ ] A GitHub or GitLab profile with original work, not only forks
- [ ] PHP versions and frameworks listed with years
- [ ] Availability in days per week, not just immediately
- [ ] A stated hourly or day rate
- [ ] VAT status and how they invoice
- [ ] Professional indemnity insurance, if you require it

Then hold a short technical call. Three or four questions from our list of [PHP interview questions](https://php-entwickler-gesucht.de/en/assessing-candidates/php-interview-questions/) are enough. With contractors, also watch how they estimate. Give them a real task from your project and ask for a rough estimate with stated assumptions. People who state assumptions surprise you less later.

Paying for a trial of two to five days is fair to both sides. It replaces the take-home test you'd use for permanent hires and shows you how the person handles your actual code. Our guide to the [PHP coding test](https://php-entwickler-gesucht.de/en/assessing-candidates/php-coding-test/) has ideas for scoping such a task.

## Employment status: IR35 and its cousins

Every major market has a test for whether a contractor is really an employee. The details differ, but the questions are similar: who controls how the work is done, who carries the financial risk, and how integrated the person is.

For the UK, the off-payroll working rules (IR35) put the decision on the client for medium and large private-sector organisations since 6 April 2021. You issue a status determination statement for each engagement. Small clients leave the assessment to the contractor's own company. HMRC offers its [Check Employment Status for Tax tool](https://www.gov.uk/guidance/check-employment-status-for-tax) for a view on a specific case.

The IRS in the US looks at three groups of evidence under its [common-law rules](https://www.irs.gov/businesses/small-businesses-self-employed/independent-contractor-self-employed-or-employee): behavioural control, financial control and the type of relationship. Either side can request an official determination with Form SS-8, though the IRS says that can take at least six months. Some states apply stricter tests of their own.

**Signals of genuine self-employment versus disguised employment**

| | points to contractor | points to employee |
|---|---|---|
| Working hours | sets own schedule | fixed core hours imposed |
| How the work is done | outcome agreed | instructions on method |
| Equipment | own laptop and licences | company laptop and email |
| Clients | several | one, indefinitely |
| Financial risk | fixed prices, own marketing | none |
| Time off | no approval needed | must be approved |

No single line decides. The overall picture does. For long engagements with one client, get advice before the contract is signed rather than after a tax inquiry.

## Make sure you own the code

This trap usually surfaces during a dispute. Section 11 of the UK's Copyright, Designs and Patents Act 1988 gives the employer ownership of work an employee creates in the course of employment. Contractors aren't covered. Over in the US, software written by an independent contractor generally doesn't count as a work made for hire either.

Without a written clause, you may only get the rights needed for the original purpose. If you later want to extend the code yourself or hand it to another supplier, you need an explicit assignment of intellectual property, ideally including the right to modify.

Also settle what happens to libraries the freelancer brings along. Many reuse their own helper packages across clients. Usually a non-exclusive licence is enough there, as long as you can keep running and changing your application.

## The first week decides a lot

Many contract engagements waste their first days waiting. Access is missing, the local setup doesn't run, nobody has time for questions. At £470 a day that's expensive idling.

Prepare what the person needs on day one: access to the repository and the ticket system, a local setup that starts with one command, and a staging environment. Nobody needs production access in week one.

Name one contact on your team who answers domain questions and reviews the first pull requests. An hour a day in the first week usually does it.

Write down what "done" means. For some, done means it runs locally. For others: tested, reviewed, documented, deployed. Leave that unclear and you'll end up arguing about invoices instead of code.

## What a freelance engagement costs

Here's a worked example for a typical engagement, such as a framework upgrade with clean-up work, using the UK median day rate.

**Example: twelve weeks of support, three days a week (UK)**

- 12 weeks × 3 days: 36 days
- 36 days × £470: £16,920
- plus 20% VAT: £3,384
- **Gross (net £16,920 if you reclaim VAT): £20,304**

Worked example. Day rate is the ITJobsWatch UK median for PHP contracts, six months to 18 October 2026. VAT only applies if the contractor is VAT-registered.

How rates vary by region and seniority is covered in our article on [PHP developer hourly rates](https://php-entwickler-gesucht.de/en/salary-and-cost/php-developer-hourly-rate/). For upgrade projects specifically, our article on [PHP upgrade cost](https://php-entwickler-gesucht.de/en/salary-and-cost/php-upgrade-cost/) breaks down the effort.

If you'd rather hire a team that owns the outcome than buy individual hours, a studio like [OnlineBuilders](https://onlinebuilders.biz/how-we-work) is another option. You buy a result with operations, not a block of time.

Start with half a page covering the goal, the PHP and framework versions, days per week and the start date. With that you can search two platforms today and run the first five profiles through the checklist.

## FAQ

### How much does a freelance PHP developer charge?

In the UK, the median day rate for PHP contracts was £470 in the six months to 18 October 2026, according to ITJobsWatch. In Germany, Austria and Switzerland, freelancermap reported a median of 90 euros an hour for software developers in September 2026. Specialists for upgrades or performance often charge more.

### Who owns the code a freelancer writes?

By default, usually the freelancer. In the UK, the automatic employer ownership rule covers employees, not contractors, and in the US most software written by contractors isn't a work made for hire. Get a written assignment of rights in the contract.

### Can a freelancer join our daily stand-up?

Joining meetings on its own doesn't make someone an employee. Problems start when fixed hours, instructions on how to work and employee-style integration all come together. In the UK, HMRC's CEST tool gives a view on a specific engagement.

### Fixed price or hourly for a freelance PHP project?

Hourly suits unclear work such as debugging someone else's code. Fixed price only works when the scope is truly fixed, for example an upgrade to PHP 8.4 with all existing tests passing. A paid discovery phase followed by a fixed quote often works best.

Photo: helloquence, CC0 (https://commons.wikimedia.org/wiki/File:Helloquence-61189.jpg)