Job Title: Technical Architect – Commercial Lending & Collateral Platform
Location: Charlotte, NC (On-site)
Employment Type: Contract (W2 through ZipStaff — No C2C or 1099)
About the Opportunity
ZipStaff is seeking a Technical Architect for a global technology services firm replacing vendor collateral products with a custom platform at a major US bank.
The target design is modular, API- and event-led, and becomes the master record for collateral, with approved changes sent to loan origination and loan servicing. You own the end-to-end technical design across a phased roadmap: P0 core controls and reconciled migration, P1 automation, P2 AI. This is a hands-on architecture seat — not a functional SME role and not a coding-only role.
What You’ll Do:
- Define target-state architecture: collateral engine, integration hub, data hub, and UI / workflow interaction layer.
- Design domain microservices for registry, valuation, perfection, insurance, release, and document management.
- Design configurable rules and workflow engines for triggers, maker-checker, and escalation.
- Produce ADRs, reference architectures, NFRs, and design standards, and take them through architecture review.
- Design API, event, and batch integration (pub/sub, converters, adapters, repair queues).
- Lead integration design with AFS Vision, Loan IQ, nCino, customer master, credit-risk systems, and document repositories.
- Reuse existing API and event hubs and retire point-to-point interfaces in steps.
- Design the collateral data model, authoritative record, data-quality controls, and regulatory reporting flows.
- Own migration and coexistence: incremental loads, parallel run, reconciliation, and decommission.
- Build in RBAC, segregation of duties, encryption, audit trail, and retention.
- Set performance, scalability, resilience, HA/DR, and observability targets aligned to bank security and OCC / FRB expectations.
- Stand up platform foundation, CI/CD, DevSecOps, test automation, and environment strategy.
- Guide onshore and offshore teams through design reviews and technical governance.
- Partner with the Commercial Lending Collateral SME and present the architecture in client workshops.
Required Qualifications:
- 15+ years in software engineering and architecture, including 6+ years as a solution or technical architect on banking or lending platforms.
- Proven architecture of large custom platforms in banking; commercial lending, collateral, or credit platforms strongly preferred.
- Microservices, domain-driven design, and API-first / event-driven architecture.
- Hands-on Java / Spring Boot or .NET, REST / GraphQL, and Kafka or equivalent messaging.
- Cloud-native architecture on AWS or Azure (containers, Kubernetes, managed services).
- Data architecture: Oracle, PostgreSQL, or SQL Server; data modeling; ETL/ELT; reconciliation design.
- Migration off legacy or COTS with coexistence and phased cutover
- Integration with lending systems such as AFS, ACBS, Loan IQ, nCino, or core banking.
- Enterprise security: IAM / SSO, OAuth2, encryption, secrets, audit logging.
- Able to present to CTO / CIO audiences and architecture review boards
- Ability to work on-site in Charlotte, NC.
- Must be legally authorized to work in the United States without sponsorship now or in the future.
Preferred Qualifications:
- Rules or workflow engines (Drools, Camunda, or Pega).
- STOC or Broadridge COLLATE.
- Angular or React, and document-management integration.
- AI/ML use cases such as document extraction or predictive monitoring.
- TOGAF, AWS or Azure Solutions Architect Professional, or Kubernetes certification.
Benefits:
- Health Insurance.
- Dental Insurance.
- Vision Insurance.
- 401(k).
- 401(k) matching.
- Paid time off.
- Referral Program.
About ZipStaff:
ZipStaff partners with leading organizations to connect skilled technology professionals with high-impact contract opportunities. We focus on quality matches, clear communication, and long-term success for candidates and clients.
To apply, submit your resume highlighting banking or lending platform architecture you owned, the integration pattern (API/event), and a legacy-to-custom migration you designed. Generic cloud architects with no lending-system integration will not be considered.