Job Description & Details
This is a heavy-hitting technical lead role for a high-volume financial processing environment dealing with payment systems, debit cards, and Zelle integrations. You'll be expected to hit the ground running with enterprise architecture, requiring an in-person presence in Alpharetta 3-4 days a week, so keep the commute in mind before diving in.
What You'll Actually Be Doing
You'll be spending your days architecting and building out distributed microservices that handle critical financial transactions with near-zero tolerance for latency or downtime. Expect to juggle complex database designs across MS SQL Server and NoSQL, coordinate event-driven messaging pipelines, and guide junior devs on best practices while keeping code delivery aligned with enterprise security and AI-driven SDLC initiatives.
The Core Tech Stack
You need absolute mastery over .NET Core (specifically .NET 6+), C#, and robust RESTful API design. Beyond the backend basics, you must have hands-on production experience with Azure cloud services like App Services and Service Bus, alongside message brokers such as Kafka or RabbitMQ, and container orchestration using Docker and Kubernetes to keep these distributed payment engines humming.
Interview Expectations
Because this is an F2F interview requirement for a lead role, they are going to test your architectural chops hard. Expect a scenario where they ask you to design a fault-tolerant, high-throughput payment processing pipeline under extreme load, focusing heavily on how you handle eventual consistency and distributed transactions. They aren't just looking for a working algorithm; they want to see how you handle failure states, circuit breakers, and database deadlock scenarios in high-concurrency environments.
Application Advice
Your resume needs to scream enterprise-grade reliability and scale rather than just listing syntax. Make sure you explicitly highlight your hands-on metrics with .NET Core, Azure cloud infrastructure, and specific financial domain experience like payment processing or banking. Pull in heavy keywords like microservices architecture, Kafka, Kubernetes, and CI/CD pipelines so you easily clear the initial ATS filters before facing the rigorous in-person technical panel.