A culture of rushed shortcuts with an ironic level of staff turnover - Avis employé Employé (anonyme) Rippl

A lot has changed and continues to change at Rippl since previous Glassdoor reviews. Quality is improving and technical debt is reducing. There's much more focus on the roadmap (including a good percentage of time addressing technical debt) and fewer changes of direction. The CTO has good ideas for scaling the platform and there's also scope for developers to play a part in this too. A new CEO is also helping to set focus and direction. The team is welcoming and friendly, willing to help out and to work to make the platform better. Working hours are good - 35 hour working week with no expectation of overtime, and some good benefits (including discounted vouchers).

There is still a lot of technical debt in the system, and some parts of the system are not well understood or documented. This is being actively worked on, but there's still plenty to do here. Being a fully remote team can mean fewer opportunities for socialisation as a team.

None. I don't think there was a single thing. Even for a company which was meant to be based on employee recognition and engagement

I wouldn't recommend this company to any software engineer who values good leadership, modern tech practices, or even basic development hygiene. The CEO had zero understanding of what it takes to scale software properly—his definition of scaling was just “get more customers,” regardless of whether the platform could handle it. The product was a complete mess: no multi-tenancy, no separation of concerns, and a single codebase with hardcoded, customer-specific logic scattered throughout. Each deployment felt like a hackathon of manual interventions, fragile configurations, and duct-taped patches just to keep things from crashing. The worst part? The CEO clearly viewed the dev team as expendable. Most of the team turned over every year, with only one poor soul left holding any meaningful knowledge of the system. It was a revolving door of developers, because nobody could (or should) put up with such an environment. Rather than fix the root causes, the CEO tried to slap AI on top of the chaos, as if that would magically solve the underlying technical debt. Outdated tech, no documentation, poor architecture, zero support from leadership, and unrealistic expectations. If you're a developer looking to grow or even just maintain your sanity, stay far, far away.