Java Backend Engineer
software technologyWashington (DC)
Java Backend Engineer
Posted 9 days ago
software technologyWashington (DC)
SENIORITY
Lead
About the role
Backend Developer Project Scope: The roadmap is extraordinarily long – streamline teams that are product specific as well as higher level technical roadmaps. Build more functionality is the main scope. Working on Java and Springboot microservices to collect metrics and analysis on the services scalability using the Prometheus tech stack. Need to be able to monitor and measure what they’re seeing without guidance. Looking for backend capacity and design with the systems – not looking for architects necessarily, but looking for people to come in pick up keyboards / stories. One project: They need to get better observability of microservices over time i.e. hypothetical observability? Allow teams to work autonomously. Metric stack is Prometheus and Grafana. Another: Consumption of X12 837 claim files, breaking them into transactions and feeding into Kafka.
Tech Stack:
Microservices / Java / React Native – cross platform (Android, iOS and Web) / Angular for internal Admin Apps / Postgres DB / Kafka (message broker, MQ, orchestrator) / Databricks for processing on DS models / Ascend for pipelines (like airflow) / AWSDevelopment Methodology: Agile – 2 weeks Backend Developer Java (17) – Looking for 8 at a minimum, design skills Spring / Springboot / Microservices – RESTfulGood OOP skills Kafka – Pub Sub / Consumer / Producer DevOps release process understanding – release multiple times a day (the more they have with Jenkins / Terraform the better) Extending capabilities of Prometheus monitoring – not tool specific, but need to know the concept (what they need to measure and how to interpret it) Unit & Integration testing – ideally TDD so this would be nice Redis & Elastic is a plus2 Backend: Interview Give them coding examples, finish writing this code block and talk through it. Sr. Level Software Engineer 5-8 years’ experience (would consider someone 3-5 years) Technical leader for team and mentor to more Jr.
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.