Hiring: mid-level PHP developer with Hyperf or Swoole, remote EU hours
We are a small product team hiring a mid-level PHP developer to work on a coroutine-based backend, Hyperf on Swoole, plus a Vue frontend. Remote, overlapping EU working hours required, contract or employment both possible. The work is real high-concurrency backend, not CRUD, so some comfort with coroutines and pools matters, but we are happy to grow the right person into the Swoole specifics.
Posting partly to hire and partly to ask: for those who hire in this niche, how do you screen for coroutine-safety understanding without making it a trivia quiz, and what mid-level rate is realistic for this skill set in 2026?
For screening, skip trivia and give a small realistic bug: a service with a static property that leaks between requests under Swoole, and ask them to find and explain it. Someone who actually understands the coroutine model spots the shared-state problem and talks about per-request context, someone who memorized definitions does not. It separates real understanding from buzzword familiarity far better than asking them to define a coroutine.
On rate, the Swoole and Hyperf niche carries a premium over generic PHP because the pool of people who have run it in production is small. For a genuine mid-level who can work safely in coroutine context, EU remote, expect to pay clearly above a plain Laravel mid rate. If you lowball it you will only get people who have read about Swoole, not shipped it. The specificity of the skill is the whole reason it costs more.
Be honest in the posting that you will grow them into the Swoole specifics, because very few true mid-levels already have deep Hyperf experience. The realistic hire is a strong general PHP developer who understands concurrency conceptually and can learn your stack. If you insist on existing Hyperf production experience at a mid-level rate you will be searching for a long time, that combination usually already commands senior money.
The leak-finding exercise is a great idea and exactly the kind of real signal I wanted, I will build the screen around that instead of a quiz. And the point about growing a strong generalist rather than demanding existing Hyperf experience at mid rate is well taken, that is a more honest and more fillable posting. Adjusting both the rate expectation and the requirements accordingly.
One practical filter for remote EU overlap: state the required overlap hours explicitly in the posting, not just remote. The single biggest source of bad-fit applications in this niche is timezone, people apply from a zone with two hours of overlap and it never works for pairing on tricky concurrency bugs. Being blunt about the hours up front saves everyone the dance. Good luck with the search.
```php blocks are runnable.