Senior Java Engineer, Commercial Banking Platform

Prolific Banking builds the commercial banking operating platform that financial institutions use to onboard, service, and process money movement for their commercial customers. Our product, Prolific Open Digital (POD), is in production at community banks through enterprise-tier institutions, processing live commercial account opening, ACH origination, wire initiation, positive pay, information reporting, ERP connectivity, and treasury management workflows every day.

We compete head-to-head with the major US core banking providers, the commercial onboarding platforms, and the treasury management vendors that most banks evaluate. We are not a payments aggregator, an open banking connector, or a treasury management point solution. We are the system of record for the bank's commercial relationship, wired natively into the major US core banking systems and the payment, fraud, KYC/KYB, ERP, and IAM ecosystems that surround them.

Our founder and President designed and built what is now an industry-standard cash management solution during his fifteen years as CTO at Online Banking Solutions, holds US Patent 10,657,289 for proximity-based authentication, and is building the next generation of commercial banking software on modern cloud-native technology. You would be joining a team that knows commercial banking deeply, continuously ships software, and is on a clear trajectory. Prolific Banking is a profitable, founder-owned company that is not chasing the next venture round.

What You'll Actually Work On

This is a senior engineering seat on the POD platform team. The work spans the productized modules that make up POD: Commercial Account Opening, Payments (wires, ACH, RTP, FedNow, international, ISO 20022), Information Reporting (BAI2, SWIFT MT940/MT942, ISO 20022 camt), Fraud and Positive Pay, ERP Connectors, Bank Operations, Self-Service, the Developer Portal, and Risk and Compliance workflows.

Concrete examples of recent and near-term work

• Designing and shipping payment workflows with dual-control approvals, sanctions screening, exception handling, and audit trails that hold up under FFIEC examination
• Building bidirectional API and webhook architectures for ERP integration, including BAI2, SWIFT MT940/MT942, and RTP/ISO 20022 information reporting endpoints
• Extending the Keycloak-based embedded IAM, including federated identity through major OIDC and SAML providers
• Hardening the Java/Spring backend for SOC 2 Type II, including ongoing remediation against CIS AWS Foundations Benchmark v1.4.0

What You'll Bring

Must Have

• Five to 7+ years of production Java experience, with at least 3 years on Spring Boot 3.x (Spring Security, Spring Data JPA, Spring Cloud)
• Deep experience designing and operating multi-tenant SaaS in AWS (Aurora, ECS, IAM, KMS, Secrets Manager, CloudWatch, VPC design)
• Strong React experience (functional components, hooks, Context, React Router, modern build tooling)
• Comfort with the realities of regulated software: change management, segregation of duties, audit trails, evidence collection, and writing code that has to survive an FFIEC or SOC 2 examination

Strong Nice-to-Haves

Any three of these moves you to the top of the pile

• Direct experience building or operating commercial cash management, treasury management, online banking, or core banking software
• Demonstrated ownership of a system in production that someone is paying real money for, where downtime or a data integrity bug is a board-level problem
• Hands-on work with payment rails: ACH origination and NACHA rules, wire initiation (Fedwire, CHIPS), RTP, FedNow, or ISO 20022 implementation
• Keycloak in production (custom SPIs, federation, fine-grained authorization, theme customization)
• ERP integration experience against major commercial accounting and property management platforms
• KYC/KYB platforms, fraud detection systems, or BSA/AML workflow tooling
• AI engineering: building with Anthropic's Claude API, AWS Bedrock, MCP, agentic workflows, or RAG pipelines
• Open source contributions, Java User Group involvement, or DevNexus or SpringOne speaking history

Stack

Java 17+, Spring Boot 3, Spring Security, Keycloak, Aurora PostgreSQL, AWS ECS on Fargate, AWS CodePipeline, Docker

Frontend

React, Mantine 7, TypeScript

AI

Anthropic Claude API and AWS Bedrock, MCP server in TypeScript over RDS Data API

Tooling

IntelliJ Ultimate, GitHub, Claude Code in active daily use across the engineering team, Snyk, SonarQube, Semgrep

Compliance Posture

SOC 2 Type II in progress, ISP v4.5, BC/DR documented and tested, AWS Config and Security Hub against CIS v1.4.0, CloudTrail with log file validation, VPC Flow Logs across all VPCs

Team

You would report to our VP of Engineering, who runs a small, deliberately senior engineering team alongside our VP of Product and our Risk and Compliance Manager. Code review is a real conversation here. Architectural decisions get debated and documented rather than handed down. Our VP of Engineering is hands‑on in the codebase, in design reviews, and in the room when hard tradeoffs get made.

Location and Working Model

We work together, in person, at least three days a week. We are not a remote‑first company, and we are not trying to be. The work we do (integrating commercial banking software with core systems, operating software that real banks depend on every business day, designing architecture meant to last a decade) gets meaningfully better when senior engineers are working through the hard parts in the same room. Teams that ship software and teams that talk about shipping it are usually different teams. We are the first kind. If you want to be part of building something that matters, in person, with people who are passionate about quality, this role is for you.

Our headquarters is in Midtown Atlanta. This role is hybrid. Candidates must be in the Atlanta metro area or open to relocating. Some onsite collaboration with our enterprise bank customers will be expected.

Prolific Banking is an equal opportunity employer. We hire on capability and fit, not on credentials. If you are excited about commercial banking, AI in regulated environments, and shipping software that real banks and real businesses depend on, we want to hear from you.