Dear Candidate,
Before submitting your resume, please pay attention to the location – we will not be able to review your resume and provide feedback if you are not (in fact) located in the location of the vacancy.
Thanks for understanding
About the project:

Client is Cloud Based Saa S application that manages orders for Radiologists and can resolve clients’ issues. Clients are hospitals and groups of hospitals that are situated in different countries worldwide.
This product team develops a Node.js / Angular web application, the product is in the healthcare field. All deployments are containerized in a large distributed architecture. We have co-developed a Healthcare API with Google that is central to our solution.
The product has been developed from scratch and we are already in production. We will increase in multiple times amount of clients soon, now we support around 100 facilities, soon this amount will be over 500.
Besides maintaining the product we are working on new custom and technical features, improving the performance of the platform, and a few new major milestones in progress. Also, we have a few subprojects based on client architecture.
Client offers an end to end Radiology Solution that brings the power of modern computing technology to the field of Radiology in a meaningful way, while remembering that our goal is to always assist the radiologist, never to replace them.
Google Cloud Next ’19 | April 9-11 | San Francisco (presentation) — www.youtube.com/watch?v=Y-yvlt5m VXk
Team
48 people:
7 QA
3 AQA
24 Developers
9 Dev Ops
2 PM
3 BA
1 Designer
1 HR
Team processes:
— As basic we are using standard git-flow but we added some minor changes to It. This change depends on our environments and our release process. The lifecycle of the developer’s tasks based on scrum (3 weeks sprints), ops team is working by kanban style.
— We have a code review process by 6 BE and 2 FE experienced developers and a knowledge-sharing process for all team members weekly.
— We have a bunch of various processes, some of them are main and some of them are added to make the life of the team and project better. Here is the list of basic ones:
Sprint Planning process;
1 Daily stand up meeting per team (1 for Ukraine team [19 members], 1 for AQA [2 members], 1 for OPS [4 members], 1 for Eng teams from different countries [5 members]);
Sync meetings for QA team once per sprint;
Sync meetings for FE and BE teams once per sprint;
Tech retrospective process;
Retrospective process;
Demo process;
BA process for BA team;
Hotfixes process for maintaining production.
Technical details:
— For version control are used gitlab and CI/CD builds. Almost all deploys are automated.
— Different kinds of testing: manual testing by the best QA team, UI testing by AQA (cypress), unit tests, API integration tests, functional tests, load tests using k6, microservice unit and integration tests.
Now are improving coverage for all types of testing.
— Google cloud and many google services (storage, pub/sub, healthcare, Postgre SQL, Kubernetes, firestore, logging, etc ) for infrastructure.
— Above 40 microservices.
— Additional technologies details are:
Loose coupling through Pub Sub Messaging;
Auto-scaling microservices through Kubernetes;
REST API and GRPC integrations;
Big Query for DW and analytics;
Looker for reporting;
Speech recognition development including model development;
Distributed Cloud SQL Database
Alloy DB
Technology stack
Google cloud platform, Node JS, Koa JS, Angular 7, Postgre SQL, Big Query,