Skip to content
Go to file


Failed to load latest commit information.
Latest commit message
Commit time

Mews developers

Information about development job opportunities and career at Mews. If you would like to know more about Mews, what we use, how we work etc, have a look at About Mews section. We also have a Blog, Twitter and Facebook with latest news about events, tech stack and life of devs at Mews.

Would you like to meet us? Hear us talk or check if we're coming to your area? Check out the calendar of the events we organize or attend to never miss a Mews thing!

You can always reach us at

💼 Open positions

Currently, we are seeking highly experienced people for the following positions:

For all current openings, even outside development, check our open positions. If you don't match exactly any of the candidate profiles, but you feel you could contribute in some other way, let us know as well and we can figure it out.

📚 About Mews

We have revolutionised the way that hotels operate across all departments, through our mobile hotel management platform. We enable hoteliers to free themselves from boring administration (which we help automate) and rather focus on creating real customer experiences. Now live in 60+ countries in 1600+ hotels, we have truly started a revolution.

That's the marketing slogan. A more down-to-earth version of it would be, that we work on a system for hotel employees and their guests. The main goal is to improve the guest experience, by giving them possibility to have full control over their stay, possibility to check-in online, manage their profile, pay online etc. In consequence, that decreases workload on the hotel employees, because the guests actually do the work. The second big goal is opening up the system via APIs to 3rd party companies and developers, so that they can build interesting applications on top of our system. Or connect it with something else, which was traditionally very difficult in hospitality industry. If you'd like to know more, check this sample sales-pitch which explains what we offer to our clients and which problems we solve.

In the following sections, we'll try to answer frequently asked question that we believe a candidate might have when considering application to Mews:

🏨 Product

👨‍💻 Technology

  • Which technologies do you use? Generally, we try to use technology that is familiar to the development community. The benefit of using common technology is that everybody knows it well, and if not, they're able to Google the answers to their own questions. We also try to avoid building in-house solutions, but rather use third party sevices for responsibilities that are not directly related to our business (e.g. Logentries for logging, Sentry for error reporting, SendGrid for mailing). We want to focus on our product. Check our Stackshare to see a full list of what we use and check our Platform documentation for some other technical details.
  • What is architecture of the backend? The "executable" is a plain ASP.NET MVC application with no extra caveats. We use Entity Framework code-first approach, and we use Azure DB (a version of MSSQL) as our database. We run the application in Azure using App Services, so we don't need to manage the web servers or virtual machines. We use the original branches of .NET Framework and Entity Framework and are currently migrating to .NET Core. In general, there is data layer to access Azure DB, Azure Storage and Cosmos DB, business layer consisting of various components and a transactional layer (web, API, background jobs). BTW you can check our Awesome Mews reading list to see what is our philosophy, not only on backend.
  • How is frontend strutured? We keep all our apps in one monorepo to share as much code as possible. All the apps are written on the same stack based on Redux, React and styled-components. We are migrating everything to TypeScript - current adoption is around one third of the codebase. We are fans of functional programming and apply many of its principles to our code. There is some legacy in some parts of the system still though from early days that we're moving away from, especially data heavy screens like reports are rendered on server using Razor templates.
  • How does technology stack for mobile apps look like? Operator kiosk application is written from scratch in Kotlin. For Android development we use a standard set of libraries: Dagger, Retrofit, RxKotlin (and Detekt + ktlint for static code analysis). We have a fully set up CI/CD process for Operator app and are moving into this direction for other apps as well. iOS and Android versions of Mobile Commander were initially written in Swift and Java, but last year we've migrated them to Flutter.
  • Do you create microservices? At the moment, no. The idea of having small units that are responsible for a specific task is great, however this architecture style would not match the current needs of our system. But with increasing size of the system and teams, we might evolve there naturally. However at the moment, we see modular monolith as the way for us going forward.
  • What is your test coverage? We do not know. We do not measure code coverage, primarily because we do not see it as a crucial parameter. Of course, when the project started with just two people and not much time, they were not writing any tests. However, now that we have survived the startup stage, we have begun to rectify this situation and are now currently in the stage of covering of majority of the system with end-to-end integration API and UI tests. In our opinion, they bring the biggest value for cost.
  • How often do you deploy? That depends on the application. All of our web and mobile applications are delivered continuously which means that when a pull request gets merged, a new version of the application is released. We aim for the same even on the backend application, but there it is a bit more difficult. Currently it is being released daily with daily feature-freezes. So even though it is not deployment per pull request, it is still pretty frequent.

⛹️ Teamwork

🏢 Job

  • What does the office look like? The office is located at I.P. Pavlova square, 1789/5, which is great in terms of transport options (metro line C, A, many trams).
  • Do you pay out special bonuses? No, we do not. We prefer to pay good salaries transparently and on a regular basis so that you always know what you can count on.
  • Do you have stock option plan? Yes, every employee is awarded certain number of depository receipts.
  • How many years would it take to reach a senior position? We have a bit of a different understanding of what "senior developer" means. To us, a senior developer takes full responsibility for some part or component of the system and does not need anyone to help them with their tasks or to look over their shoulder. For this reason, we cannot guarantee that you will become a senior developer. It's up to you to determine how quickly you can become that skilled. Furthermore, if you consider yourself to be a senior developer already, it may happen that we will not agree. In our job posts for senior positions, you can find a list of topics. A senior developer should ideally have deeper knowledge with at least some of them.
  • Is it possible that a new junior developer would earn a higher salary than me as a senior developer? No. We try to avoid frustrations about money and keep an eye on the salary of each person individually; we believe it should correspond to their skill level. Therefore, if we would desperately need to hire a junior developer with a salary higher than yours, we would increase all the salaries in the company so that the levels are kept intact. We want to pay salaries that are competitive to CZ market as we don't want you to leave because of a better salary offer. We don't have open salaries, but try to structure them as if they were.
  • Can I have a home office? Yes, with the current world situation we became more open to possibilities to work from home. However, there are some rules to follow:
    • Home office is a thing of trust. We need to be able to trust that you are producing the same amount and quality of work as when working from the office. If you have a home office but do not respond for 2 hours on Slack, that's suspicious. Home office is not a day off.
    • When taking home office, we expect that you do not need anyone to help you accomplish your tasks that day and that you will not need to interrupt people via any communication channel.
  • What are the working hours? That really depends on you. Every person has a different rhythm to their life. As long as you accomplish what you have promised to accomplish, it's up to you. Most people are in the office between 11:00 and 17:00. Although there is a lot of flexibility, your working hours should intersect with this time period so that you have opportunities to meet with the team and consult them regarding your work.

🎓 Students

  • Is it possible to work for Mews while studying? Yes, we have many students in the team, especially from MFF CUNI and CTU. We treat students just like any other employees, which means they're working on real projects, in product teams with other developers and getting market salary.
  • Do you provide any support for students? Because Mews development team was founded by a group of students that met in school and were still studying, we know what it means to both work and study. Therefore we're OK with you having a month break during exam periods, so that you can prepare for the exams. Students also have lot of time flexibility because of their school schedules. And since we have graduates from both of the aforementioned schools in our team, we can also help with the studying.
  • Can I do a bechelor or master thesis for Mews? Definitely, we have many ideas that are appropriate either for bachelor or master theses. Just reach out to us and we can discuss the possibilities.

📰 Media

For 7 years we went rather unnoticed (mainly in our home base - Czech Republic) and didn't really mind as we never focused on clients in Czech Republic (only 5% of all). But things are changing...

  • English
    • TechCrunch - announcement of the Series B investment.
    • HospitalityTech - Mews' acquisition of Planet Winner PMS.
    • Travel Tech Conference Russia - Richard (founder) talking about why hotels should think like tech companies.
    • TechUncovered - First #TechUncovered event organized by us with cooperation with productboard, STRV, SCS Software and Pipedrive. CTO's, founders and tech leads discussing scaling tech teams.
  • Czech
    • CzechCrunch podcast - Intervirew with the founder of Mews Richard Valtr and CEO of Productboard Hubert Palan.
    • Forbes podcast - Another philosophical podcast featuring founder Richard.
    • - technical interview with the CTO Honza.
    • Forbes - announcement of the Series B investment.
    • CzechCrunch - interview with the founder Richard about his visions behind Mews.
    • E15 - changing the hospitality industry.
    • Radiozurnal - discussion about why it's important to support Universities.
    • Computerworld - Interview with CPO Jirka about how it is going in a growing start-up.


Information about career and technical job opportunities in Mews.



No releases published


No packages published


You can’t perform that action at this time.