Position: Senior Backend Engineer (Java)
Company: Datagazer
Category: Java
Experience required: 5y
English level: fluent

Project Description

We are building a new hospital documentation processing platform, including:

Patient registration module.
Processing of his documentation: doctor notes, procedures, X-rays, medications, etc.
Creation of everything the insurance will need to pay for the visit.
Fancy dashboards for KPI, tools for audits and a lot more.
AI for summarization and feature extraction.

The system has been in active development for 2 years, successfully launched to production with US hospital chains as clients. We are writing new modules and onboarding new clients.

The team is fully remote spread across US, Canada, Ukraine, Brazil, Montenegro, and India. Engineering team is 4 Backend engineers, 3 Frontend, 3 QA, 1 DevOps.

The platform runs on AWS and follows microservice approach: 
About 20 ECS services (mostly dockerized Spring Boot) 
About 20 lambdas (Quarkus + Serverless)
Mongo Atlas + Redis for data
Spring Cloud Config
S3, SQS, API gateway

There are parallel projects that use python, pytorch, doctr OCR, Huggingface, chatGPT and Microsoft stack.

Responsibilities

An ideal candidate would combine these qualifications:

Have 5+ years of experience building complex distributed data processing systems using Java ecosystem. Our system is fairly complex with a lot of moving parts. It should scale proportionally to the amount of data. The team is very experienced and is moving fast. We would prefer a person that has built complex systems before, hands-on with most of the tech we use and can get productive quickly.
Be comfortable owning some of the components: work with the product team on how it should work, come up with appropriate technical design, implement and work with QA on nailing down the defects, support post-launch, be the first responder if prod explodes. 
Be a good communicator. The team is fully remote. We would like you to be able to comfortably jump on a call with a guy in the US that will be using your API, explain how it works, answer his questions, debate potential changes etc. Good spoken and written English is essential.
Be proactive. Ask for help if stuck. Let the team know if there is a problem no one else noticed. Grab the elusive product manager and ask him all the questions to make sure you are solving the right problem.