Backend Engineer (Python)

Tooling: We use AI-assisted development using Claude Code. We encourage developers to use AI, but we're also critical of what it produces. 5+ years of backend engineering experience, with at least 2 years writing production Python. Solid experience building and consuming APIs, integrating third-party services, and working with relational databases. You write code that's tested, documented, and won't become a mystery in six months. You're comfortable with shared ownership: code reviews, collaborative decisions, handing things off cleanly. You can talk about trade-offs without needing to win every argument.

We're not running a checklist interview. If you're strong on the core stuff and interested in the domain, apply. What you'll get 27 vacation days. Hybrid: 2 days remote per week, flexible after onboarding. Relocation budget for candidates moving to the Netherlands. Visa sponsorship and 30% ruling support where applicable. A Windows or MacBook and a remote working budget. Coaching, training, and career development support. Mental health support via OpenUp for you and your family. Commuting reimbursement. About Paylogic Paylogic is part of EVENTIM, Europe's largest ticketing and live entertainment company, ranking as the world's number two provider. The client list runs from Tomorrowland and André Rieu to Comic Con and Zoute Grand Prix. The engineering challenges are as varied as the events. The engineering team is small enough that people notice your work, but big enough that you are not doing everything by yourself. Experience level: Mid

Paylogic is the ticketing and event operations platform behind some of Europe's biggest events. Tomorrowland runs on it. So does Paradiso. Millions of fans use our systems to buy tickets. Event organisers use them to run their operations end-to-end. We're looking for a Backend Engineer with solid Python experience to join the team in Amsterdam or Groningen. You'll work on systems that matter at scale, high-traffic ticketing shops, payment flows, automated payouts, and the internal tools that help events run smoothly, seen by millions of fans and thousands of event organisers. This is not a role where you'll be parked on one microservice. It's varied backend work across APIs, async processing, integrations, data modelling, and reliability. The kind of work where you actually have to think. What you'll be working on Paylogic's backend has two distinct layers worth understanding before you apply. Fan-facing systems. White-label ticket shops that go live the moment a high-demand event opens for sale. Throughput, reliability, and correctness under peak load are non-negotiable. This is where a poorly handled queue or a missing database index will cost someone their ticket and the start of their event experience. Organiser-facing tools. The platform event organisers use to manage their events, configure ticket products, track payments, and handle operational workflows. Less visible to fans, but genuinely complex to model and maintain well. The kind of code that needs to still make sense in two years. Day-to-day, you'll be: Building and improving Python services across the platform. Designing and shipping payment flows, payout logic, and API integrations. Working on performance and reliability, both at scale and in everyday production. Contributing to technical discussions, architecture decisions, and code reviews. Keeping existing systems understandable, not just adding new features. Tech stack: Python, FastAPI, Flask, Celery, Redis, Memcached, MySQL, SQLAlchemy.