PHP FullStack Developer
Role details
Job location
Tech stack
Job description
We're looking for a mid-level PHP Developer to join our team and contribute to day-to-day execution of development tasks within a structured, experienced team.
Our development team works on the group's international platform, handling everything from maintenance and feature development to third-party integrations and new jurisdiction rollouts.
What you'll work on
- Evolution and maintenance of the group's websites across multiple jurisdictions
- Development of interfaces for gaming providers
- Integration of third-party APIs
- Backend processes and frontend functionality
- Support for new country/jurisdiction rollouts
About the team and role
You'll work within a structured team. The stack is mature - PHP with MVC patterns, jQuery, SQL. A migration to Laravel is being evaluated for the future, but the current stack will remain the primary environment for the foreseeable future.
You won't be thrown in alone. The environment is collaborative, remote-first, and the domain (heavily regulated iGaming) is technically interesting - external audits, certification processes, and compliance constraints are part of the day-to-day context.
We are a product company - we build and maintain our own platform, not client projects. That means full ownership of what we ship, consistent domain knowledge, and no context-switching between unrelated codebases.
Requirements
Essential
- 3+ years of professional PHP experience with MVC frameworks
- JavaScript / jQuery
- HTML5 / CSS3, responsive/mobile design
- SQL (MySQL or similar)
- Git
- Basic Linux knowledge
- Fluent English and native-level Spanish
- Based in Barcelona or available to travel there when needed
Desirable
- Laravel
- Experience with in-memory stores (Redis, Memcached)
- Familiarity with regulated environments or compliance-driven development
What we're looking for
Someone reliable, technically solid, and comfortable working in a structured team. You solve problems, communicate blockers early, and don't need constant oversight. Experience in legacy codebases doesn't put you off - you understand that real systems have history.