Данная вакансия устарела и скорее всего уже не актуальна. Вы наверное попали к нам с поисковой системы, если Вас интересуют вакансии для веб-разработчиков, то Вы можете воспользоваться поиском по нашему сайту.
Описание вакансии7 июня 2016
We will be building a POS (Point of Sale) mobile app (tablet based) for Quick Service Restaurants (QSR) and retail domains. The app will run on PhoneGap/Cordova for iOS and Android, Electron for Windows. The reason to use the Cordova and Electron is that the POS module has to interact with IP devices such as credit card scanner and printers. The application should be designed to:a) work in offline mode. In case the LAN/WiFi connection goes down the app must still be able to accept new orders and provide persistence for future synchronisation with the Back of House (BoH) system.b) support plugin architecture. Each module should be developed and added to the core product separately, so we will be atomising the development of separate features. Code reuse between platforms is going to be critical point of success as well as performance and user experience.c) support 3rd party software integration. For this project, we will be partnering with several loyalty/payment and reporting systems.d) support 3rd party hardware integration. The application hosted on the tablet should be available to work with 3rd party hardware including, but not limited to: barcode scanners, pin pads, scales.The app is being developed from ground up by a company who has more than 20 years of experience in this industry. The end market would involve well over 100,000 installations onsite. The project is going to be based on using modern technology stack. You will have the option to gain experience and be a part of a great team developing the next big thing in QSR industry.High-level technology set is:1. Front end will be implemented for several platforms:a. iOS and Android using PhoneGap/Cordovab. Windows desktop app using Electron (JS + Node.js inside Electron)c. Web browser - single page app or a Chrome extensiond. It is likely that React.js is going to be used as a framework.e. Websockets are used as a data transport option.2. Backend implemented using Node.js. Cloud hosting (most likely AWS) with scalability in mind. HTTP/REST endpoints as well as websockets support.3. General design considerations:a. The apps are expected to work offline for some period of time (when connection to the cloud backend is not operating).b. Deployment is planned to use containers based approach, most likely using Docker.c. Live debug support - ability to turn on detailed logging in real time and a subsystem to collect and process logs (MongoDB + ElasticSearch).d. Events messaging approach is used to communicate between modules, most likely RabbitMQ is going to be used, pub/sub approach whenever possible.e. Code re-use is set as one of the top goals. Code reuse between platforms (mobile/web/desktop) as well as between frontend and backend (some libraries like business rules are going to be used on frontend and backend).f. Data coming from various devices need to be synchronized, that means that synch approach is going to be picked and implemented.
We are looking for:1. Senior level developers who can participate in technical design and influence the architecture2. Intermediate level developers are going to work on technical research tasks now and work on modules and sub-system under more senior persons' supervision later.
— React.js— Experience working with IP devices— Experience with websockets— Experience with REST API