Back to Jobs

Senior Java Cloud Engineer – Azure

Not Disclosed

Job Description & Details

This is a heavy-duty backend role focused on building and scaling microservices on Microsoft Azure. If you are local to the Dallas-Fort Worth area and know your way around Java ecosystems and modern cloud setups, this gig lets you own critical architecture without drowning in endless meetings.

What You'll Actually Be Doing

You will spend your days designing, coding, and maintaining cloud-native applications that have to actually scale under real-world traffic. Expect to build microservices using Spring Boot, deploy them via Azure Container Apps, and hook up messaging pipelines with Azure Service Bus. You will also touch data pipelines using Python and Databricks, meaning you need to be comfortable context-switching between core application logic and data-heavy processing.

The Core Tech Stack

You need absolute fluency in Java, Spring, Spring Boot, and Spring Cloud to survive here. On the infrastructure side, Microsoft Azure is non-negotiable—specifically Azure Container Apps and Service Bus. They also care about modern tooling, so expect to use GitHub Actions for CI/CD and PostgreSQL for your relational data layer. Bonus points if you are already comfortable leveraging AI-assisted coding tools to speed up your workflow.

Interview Expectations

Expect the technical rounds to dig deep into how you handle distributed systems failures, particularly around message ordering and idempotency in Azure Service Bus. The interviewer will likely ask you to trace a request from an API Gateway through a Spring Cloud microservice down to a PostgreSQL query, probing for where latency usually creeps in and how you would optimize it.

Application Advice

Make sure your resume doesn't just list Java; highlight your actual production experience with Spring Cloud and Azure deployments. The ATS will definitely screen for exact matches like Azure Container Apps, Databricks, and GitHub Actions, so weave those terms naturally into your past project descriptions rather than hiding them in a skills section at the bottom.