Title:- Lead Java Developer

Location:- New York, NY (On-site)

• Skills: All 100% purely Backend
• All Java, reactive miroservices, event based using Kafka for messaging between services.
• A lot of Java APIs, Springboot.
• These resources (especially on the messaging side) will probably do some work in Fargate AWS batch and serverless patterns.
• All APIs are Java based, there are no Python components.
• Project: Dual request / two different projects going on:

1. Legal Modernization: initiative called 25/25. Looking to modernize their legal domain in a couple of different ways. One of which involves allowing legal firms to open up digital experiences with the customers they re looking to engage with on Capital One s behalf, and then pulling that information about those digital experiences and exchanging that back and forth with those legal firms, then pull that into their analytic regions to do analysis and optimization, etc.
2. Cash Strategy / Contingency Strategy: Capital One agents are working with these [delinquent] customers looking to collect. Driving a modernization of their messaging strategies. What they want to do here is start to leverage the more current destination patterns for messaging (so want to start using Lighthouse and Maestro versus the older messaging patterns), as well as they want to explore dynamic messaging. They are partnering with their modeling team and want to do some reinforcement learning on the actual messaging content, the wording, all of that in their emails, SMS, digital experiences, etc. And then tie that in with the reinforcement models they will be