Tripla helps travelers book directly with hotels. While OTAs provide value through comparison and reviews, their business model creates a significant burden for the hospitality industry. They typically charge hotels 10% to 30% of revenue and force price reductions for better ranking. To survive this margin compression, hotels often cut costs, which degrades the quality of the guest experience. Tipla gives hotels the tools they need to own their booking platform and regain control so that hotels can offer better rates to customers while keeping their own businesses healthy.
For an engineer, Tripla hits the sweet spot between a startup and a large enterprise. We are financially stable and profitable, so you do not have to worry about our runway. Because our products are revenue generators rather than cost centers for our customers, we see consistent growth and low churn, when hotels sign up with us they stay. Our products serve hotels across Asia, not just in Japan. Yet, despite this reach, we keep the agility of a startup. Our structure is flat, with only one management layer between engineers and leadership. The team is international, English is our primary language, and you will work closely with the founders. You get to move fast, wear multiple hats, and do impactful work without the instability usually attached to a company of our size.
We currently operate on a single Ruby on Rails monolith. It is reliable and has served us well, but we know the current setup will not sustain us for the next ten years. As we launch new products, integrate with large hotel chains, and expand overseas, we are moving toward a service-oriented architecture. We are actively exploring a new technology stack for these future services, one that prioritizes type safety, concurrency, and developer experience, but we have not made a final decision. We need someone to come in, challenge our assumptions, and help make that choice.
Designing a system from scratch is easy. Designing a system iteratively under high traffic, where paymen