Role Purpose (Summary)
We are looking for a FenX Solution Architect with deep expertise in FenX core APIs and platform capabilities to design and govern end-to-end solution architecture for client onboarding/KYC use cases. The role will define reference frameworks, lead client architecture setup, and ensure delivery of secure, scalable solutions across infrastructure, cloud, environments, CI/CD, and deployment.
This individual will act as a bridge between business stakeholders, engineering teams, cloud/platform teams, and vendors, ensuring architectural consistency, regulatory compliance, and reliable production operations.
Key Responsibilities
1) FenX Solution Architecture & Framework Design
Own the end-to-end architecture for FenX-based solutions (onboarding, KYC, CLM journeys) across applications, integrations, data, and security.
Define and maintain the FenX solution framework:
-
Reference architectures, reusable patterns, standards, guardrails
-
API integration patterns, eventing patterns, error handling standards
-
Logging/monitoring approach, resiliency patterns, and deployment blueprints
-
Lead architecture reviews and provide design authority and governance for new initiatives and change requests.
2) FenX Core APIs & Integration Leadership
Design API-led integration for FenX using core APIs, ensuring:
Proper authentication/authorization models (e.g., OAuth2/JWT, mTLS where applicable)
Versioning strategy, backward compatibility, throttling, and performance SLAs
Reliable error handling, idempotency, retries, and auditability
Create integration specifications for upstream/downstream systems:
Channels/portals, CRM, AML screening, document management, workflow, data lake/MDM, reporting
Partner with engineering teams to implement API governance, interface contracts, and test strategy (contract testing, performance testing).
3) Infrastructure, Cloud & Environment Architecture
Define target infrastructure architecture for FenX deployments (non-prod & prod):
Network segmentation (VPC/VNet), routing, DNS, ingress/egress
Security controls, secrets management, encryption (at rest/in transit)
Resilience (multi-AZ / DR strategy), capacity planning, scaling approach
Collaborate with Cloud/Platform/SRE teams to ensure:
Environment build-out and readiness (DEV/SIT/UAT/Perf/Pre-Prod/Prod)
Standardized environment configuration and baseline policies
Observability foundations (metrics, logs, traces) and production readiness
4) Deployment, CI/CD & Release Architecture
Own deployment patterns and release architecture for FenX implementations:
CI/CD pipeline strategy (build/test/security scans/deploy/rollback)
Release governance (change management, freeze planning, release notes)
Blue/green, canary, rolling deployment approaches (as applicable)
Define deployment runbooks, cutover plans, rollback strategies, and BAU handover processes.
5) Non-Functional Requirements (NFRs) & Security
Translate business needs into NFRs and architecture decisions:
Performance, scalability, availability, maintainability, recoverability
Ensure compliance with internal security standards and regulatory expectations:
Data residency considerations, audit trails, access controls, risk assessments
Perform technical risk assessments and drive mitigation plans.
6) Stakeholder Management & Delivery Enablement
Act as the single architecture point of contact for the program:
Business, compliance, engineering, vendors, platform ops, security
Support implementation teams with:
Solution walkthroughs, design clarifications, and troubleshooting
Architecture documentation and decision logs (ADRs)
Mentor engineers/tech leads on FenX patterns and best practices.
Deliverables & Outputs
1. Solution Architecture Document (SAD) / High-Level Design (HLD) / Low-Level Design (LLD)
2. API Integration Specifications (contracts, payloads, error codes, flows)
3. Reference Architecture & Reusable Frameworks (patterns, templates, standards)
4. Deployment Architecture & Runbooks (CI/CD, monitoring, cutover/rollback)
5. NFR & Security Architecture Packs (threat model, compliance mapping, risk mitigation)
6. Architecture Decision Records (ADRs) and governance signoffs
