Software Engineer, Backend Developer, Cloud Engineer - Software

Introduction

At Cloudbeds, we're not just building software, we’re transforming hospitality. Our intelligently designed platform powers properties across 150 countries, processing billions in bookings annually. From independent properties to hotel groups, we help hoteliers transform operations and uplevel their commercial strategy through a unified platform that integrates with hundreds of partners. And we do it with a completely remote team. Imagine working alongside global innovators to build AI‑powered solutions that solve hoteliers' biggest challenges.

Since our founding in 2012, we've become the World's Best Hotel PMS Solutions Provider and landed on Deloitte's Technology Fast 500 again in 2024 – but we're just getting started.

As a Software Engineer on the Payments team, you'll contribute to the infrastructure that powers billions in annual transaction volume across nearly 10,000 properties worldwide. You'll investigate and resolve issues across payment processing and reconciliation systems, improve test coverage and automation, and tackle the steady stream of fixes and improvements that keep a high‑reliability platform running. You'll work in a domain where correctness matters and small details compound – and you'll grow your craft inside a team that holds a high engineering bar.

Engineers who demonstrate strong judgment, reliability, and ownership earn increasing scope – including contributing to higher‑impact projects across the payments platform.

At Cloudbeds, our Payments tribe builds the systems that keep money moving securely, efficiently, and globally for thousands of our customers. We love solving complex, interconnected problems, integrating with global partner APIs, designing for compliance and security, and constantly iterating on better, more scalable payment solutions.

Working on Cloudbeds Payments means joining a supportive, collaborative group of engineers who are building the financial backbone of the industry, together.

Ownership mindset:
You take responsibility for the quality and reliability of your work. You don’t wait to be told what needs fixing – you flag it, follow through, and close the loop with your team.

Technical fundamentals:
You understand the importance of writing clean, maintainable, and well‑tested code. You care about getting the details right – naming, test coverage, edge cases – because you understand that’s where reliability lives. You follow standards and code patterns.

Integration aptitude:
You’re comfortable working with external APIs and can navigate documentation, debug integration issues, and build toward resilient interfaces – even when the partner side is unclear.

Security and compliance awareness:
You may not be a PCI expert, but you understand why it matters. You default to secure patterns and ask the right questions when you’re unsure.

Collaboration under pressure:
You communicate clearly when things break, contribute to investigations without needing full context upfront, and stay composed in high‑urgency moments.

Continuous learning:
You’re ready to learn. You’re curious about how systems connect beyond your immediate scope. You learn from senior engineers, absorb domain context quickly, and aren’t shy about asking why.

• 2+ years of PHP/Java web application software engineering experience.
• Solid working knowledge of MySQL or Postgre
  
  SQL – you can write efficient queries and understand indexing basics.
• Exposure to event‑driven architectures and/or microservices concepts; hands‑on experience is a plus but not required.
• Familiarity with modern infrastructure tooling (e.g., Data Dog, Git Hub Actions, Kubernetes, Docker, AWS).
• Understands the value of logging, metrics, and monitoring, and actively contributes to observability in the systems they work on.

• Familiarity with PCI‑DSS, GDPR, or other compliance frameworks – even if just operating within a compliant environment.
• Experience working in payments, fintech, or any domain where transaction accuracy and data integrity are non‑negotiable.
• Exposure to Domain‑Driven Design concepts or…