Senior Java Backend Engineer (Azure)

Senior Java Backend Engineer (Azure)
Location: any (except RU, BY, UA)
Core working hours: 9:00 AM – 5:00 PM EST
Fully Remote / B2B
Project: CTR Platform
Salary: 4500-6000 USD
Russian: native
English: C1+

We are hiring a Senior Java Backend Engineer to join a production-ready, Azure-based platform and be productive from day one.
CTR Platform is a mature, production-ready backend system running entirely on Microsoft Azure.
It supports real users and real workloads, which means reliability, observability, and operational readiness are critical.
Engineers working on CTR are expected to take ownership of backend services, contribute to system stability, and support production environments.
Core team members (Tech Lead, Senior Backend, Scrum Master) are based in Poland

About the role
Senior-level backend role in a live, production system
Strong focus on Java + reactive backend development
Fully remote team, async-friendly culture
High level of ownership and technical responsibility
Direct impact on system stability and scalability

☁️ Cloud & Tech Stack
We are 100% Azure-based. Experience with AWS is not sufficient unless you already have strong, real-world Azure expertise.

You will work with:
Java (senior level)
Reactive programming
Azure ecosystem (hands-on, production experience required):
Azure Service Bus / Event Hubs
Cosmos DB
Azure Key Vault
App Configuration
Application Insights
Production-grade backend systems

What we expect
You are a Senior Java Backend Engineer
You have strong, practical Azure experience (not theoretical)
You can be productive without a long onboarding or training period
You are comfortable supporting production systems
Your English is C1 or close to it — daily communication is 100% in English
You are self-driven, reliable, and comfortable working remotely

This is required to improve production coverage
You must be comfortable aligning with EST time zone
On-call & production support
Currently, there is no formal 24/7 on-call rotation
Engineers support production during their local working hours
You must be open to joining a 24/7 on-call rotation in the future
As the team grows, formal SLAs/SLOs and rotation will be introduced

Why we are?
No micromanagement
Mature engineering expectations
Clear technical ownership
Real product, real users, real impact

Hiring Process: 2 steps (tech+client’s interview)

tg Показать контакты