Skip to content
Information about development job opportunities and career in Mews Systems.
Branch: master
Clone or download
Latest commit 41f0bd6 May 17, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
Android Update Jan 14, 2019
Backend Update Jan 14, 2019
Frontend Removed a typo XD Apr 5, 2019
.gitignore frontend test task added Aug 12, 2016 Update May 17, 2019

Mews developers

Information about development job opportunities and career at Mews Systems. If you're looking for specification of interview tasks for our open positions, check Open positions. 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 with latest information.

You can always reach us at

💼 Open positions

Currently, we are seeking backend developers, frontend developers and Android developers of all seniority levels. As part of the interview process, we'd like to see some code. If you have something existing that you can share with us, then great! Send us a link to your public repository or send the code attached to the email. Otherwise, if you don't have anything shareable at the moment, feel free to complete one of the following tasks depending on the position you are applying for:

For all current openings, even outside development, check our Breezy where you can also apply.

📚 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 40 countries in 700+ 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.

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.
  • 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 plan to migrate to .NET Core. In general, there is data layer to access Azure DB and Azure Storage, business layer consisting of various components and a transactional layer (web, API, background jobs).
  • How is frontend strutured? We are currently finishing migration of everything from various frameworks and libraries to a React-based stack with supporting libraries like Redux and styled-components. Frontend code development is governed by principles of functional programming and validated by automated strict linting rules and Jest-based tests. Also on frontend, we use code quality tools, mainly custom Eslint rules (99% of Airbnb rules). The long-term plan is to split all the frontend code to a separate application and have the backend just as an API service for the frontend app(s). Currently some parts of the system, especially data heavy screens like reports are rendered on server using Razor.
  • How does technology stack for mobile apps look like? iOS and Android versions of Commander are native apps written in Swift and Java correspondingly (with latest one being migrated to Kotlin). Operator kiosk application is written from scratch in Kotlin. For Android development we use a standard set of libraries: Dagger, Retrofit, RxKotlin (and Detekt 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. We're also experimenting with Flutter in order to understand whether it fits well into our tasks.
  • 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.
  • 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? We're on a path to continuous delivery, most of the deployment work is already automated, so now we deploy multiple times a week. As we improve our test base, we can be more confident to deploy much more often. Also since the frontend applications are hosted by backend, their deployment is tied together. So one of the steps forward is to make their deployment independent on backend. Some of our mobile apps, which are not offered via Appstores, are already delivered continuously.

⛹️ 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).
  • What benefits do you offer? We have Rohlí coming every day to deliver a variety of fruit, crisps, cookies, coke and other yummy things - we prefer to keep our fridge rather full. However, these snacks are not a substitute for regular meals. In addition to snacks, we have batch brew beans from ČerstváKá delivered every month, which means there is a huge supply of fresh, quality coffee in the office at all times. We have just recently abandoned the stage of being a startup. The environment in our office is much more similar to a startup than to that of a corporate one, but although it is changing, we do not offer most of the corporate benefits (company car, mobile plans, meal tickets, etc.). We provide these things to make the office environment more pleasant.
  • 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.
  • 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, but 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.
    • When you start working with us, you should probably spend the first several weeks in the office, as otherwise, you would surely be in conflict with rule no. 2.
  • 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.

✈️ Relocation

You can’t perform that action at this time.