Build the Platform Behind Great Days Out
Every day, thousands of people across Germany and the USA wake up and decide to visit a zoo, theme park, or aquarium. Behind that simple ticket purchase is a surprisingly complex world: membership tiers with different benefits, seasonal pricing rules, capacity management, resource management, timed entry slots, and add-on purchases for parking or special exhibits.
Now multiply that by hundreds of venues. Add in point-of-sale systems and kiosks on site. Integrate access control hardware at entry gates. Sync everything in real-time. Make it work reliably when the internet connection is spotty. And somehow keep it simple enough that seasonal staff can learn it in an afternoon.
That's ToucanTix. We're building the all-in-one platform that handles ticketing, access control, retail, and visitor management for attractions across the DACH region.
We have a solid product that's already processing thousands of daily transactions for clients like Karls Erdbeerhof and Serengeti Park. While ToucanTix is a lean team of 5, we work hand-in-hand with our sister company Combase (50+ in Dresden, 30+ in Las Vegas), giving us the perfect balance: startup agility with enterprise-level backing.
We need a senior developer who can:
Core Stack:
What You'll Actually Build:
We're perfect for you if:
Bonus points for:
We're bootstrapped within a profitable ecosystem. This means:
Our combined teams span Berlin, Dresden, Las Vegas, and beyond. We've figured out async communication, respect work-life boundaries, and trust each other to deliver without micromanagement.
Here's the deal: We get tons of applications from recruiters and auto-applying bots. We want to hear from real developers who actually read this and are genuinely interested.
To apply: Send your CV to [email protected] with a brief note about:
Important: Include a 🎢 roller coaster emoji in your subject line so we know you actually read this far. Applications without it go straight to the "probably a bot" folder.
This isn't another CRUD app with a payments integration. You'll be solving genuinely interesting problems: How do you architect a system where each client needs different business logic but maintain a single codebase? How do you handle offline-first POS systems that need to sync perfectly when they reconnect? How do you model pricing rules that change based on weather, season, capacity, and customer type - all while keeping queries performant?
If you're tired of optimizing ad clicks or building features that get buried in some enterprise menu, come build something that directly impacts whether thousands of people have a great day out.
P.S. – If you're on the fence, apply anyway. The worst that happens is we have an interesting conversation about Rails and theme parks.