Job Description & Details
This is a heavy-hitting backend role building out what is essentially the largest deposit platform in the country for the CCB Deposits Team. You'll be knee-deep in high-throughput distributed systems, so be prepared for a fast-paced environment where on-call rotations and production deployments are part of the reality.
What You'll Actually Be Doing
You'll spend your days architecting and scaling microservices that handle massive volumes of financial transactions for a brand-new deposits platform. Expect to design robust APIs, handle distributed data streams, and troubleshoot complex production issues during your on-call rotation every eight weeks. It is high-stakes engineering where performance and fault tolerance aren't just nice-to-haves—they are absolute requirements.
The Core Tech Stack
You need to eat, sleep, and breathe Java and Spring Boot. If you aren't completely comfortable building and securing production-grade microservices, you are going to struggle here. Kafka is non-negotiable for their distributed processing needs, so you better know consumer groups, offsets, and partition strategies inside and out. Pair that with solid AWS experience—though GCP or general cloud-agnostic chops work—and you have the exact toolkit needed to survive this codebase.
Interview Expectations
Expect the hiring team to grill you on how you handle message delivery guarantees and failure handling in Kafka, particularly what happens when a downstream consumer crashes mid-stream and how you prevent duplicate processing. They are secretly testing whether you understand distributed systems failure modes or if you just know how to spin up happy-path producers and consumers. You'll also have to do a live coding exercise while sharing your screen, so brush up on your core Java data structures, concurrency utilities, and algorithm fundamentals without relying on IDE autocompletions.
Application Advice
Skip the generic tech fluff on your resume and put your microservices architecture metrics front and center—highlight exact throughput numbers you've handled with Kafka and high-scale Spring Boot applications. Make sure keywords like Java, Spring Boot, Microservices, Kafka, and AWS are explicitly woven into your experience bullets so you easily clear their automated filters before a human ever looks at your profile.