About the Job: The Solution Architect for Banking & Financial Services serves as the technical bridge between privacy platform and the complex application landscape of banking clients. The role requires deep integration architecture expertise combined with an understanding of banking technology ecosystems — core banking systems, middleware, regulatory frameworks, and enterprise change management. The SA designs integration solutions for Banking applications, navigates banking CAB processes, and translates regulatory requirements (DPDP Act, RBI guidelines, PCI-DSS) into technical implementation. This individual works daily with client application teams, DPOs, and IT leadership while providing structured feedback to Privacy Engineering on product gaps and field learnings. Responsibilities: 1. Design integration architecture for privacy tools across multiple client applications in banking environments. 2. Review application assessment reports and determine integration approach per application — API, SDK, webhook, DB connector, or middleware-mediated. 3. Navigate banking-specific integration patterns: core banking systems (Finacle, Flexcube, T24), middleware (MQ Series, Oracle ESB), batch processing, and legacy interfaces. 4. Design consent SDK integration for React/Next.js frontends, Django/Python backends, and CMS driven content pages. 5. Design multi-property consent architecture — unified consent across news sites, job portals, classifieds, automotive, health, education, and streaming platforms with different data collection patterns. 6. Integrate consent signals with Google Consent Mode v2, Google Ad Manager, and programmatic advertising stack. 7. Troubleshoot integration issues in CDN-cached environments — consent banner rendering, cache invalidation on consent change, and geolocation-based consent requirements. 8. Integrate consent signals with Google Consent Mode v2, Google Ad Manager, and programmatic advertising stack. 9. Design solutions for consent lifecycle management within banking workflows — branch, mobile, internet banking, and third-party channels. 10. Troubleshoot integration failures across network, authentication, data format, and configuration layers in highly regulated environments. 11. Produce architecture documents, integration playbooks, and wave-by-wave rollout plans. 12. Work daily with client app-owners, DPO, and IT teams to unblock integration and manage dependencies. 13. Navigate banking CAB (Change Advisory Board) processes and production change management for go-live. 14. Provide structured feedback to Privacy Engineering via Deployment Learning Reports, Integration Feedback Reports, and Architecture Decision Records. 15. Evaluate Privacy platform releases for compatibility with active customer deployments and manage upgrade paths. Requirements: 1. Bachelor’s or Master’s degree in Computer Science, Information Technology, or related field. 2. 14–15 years of experience in software engineering / solution architecture, with at least 3–4 years working in or for banking / financial services technology. 3. Hands-on experience integrating with core banking systems (Finacle, Flexcube, T24, or BaNCS) — not as a developer, but as someone who has designed integrations against these platforms. 4. Strong expertise in REST API design, consumption, and security (OAuth2, API keys, mutual TLS, SAML). 5. Experience with banking middleware and ESB layers (MQ Series, Oracle ESB, or equivalent). 6. Database connectivity expertise (JDBC/ODBC, Oracle, PostgreSQL, MySQL, SQL Server, MongoDB) for Privacy X-Ray connector configuration. 7. Deep JavaScript expertise — not just awareness; must understand execution order, async loading, tag management, and how consent scripts interact with ad-tech tags in the browser. 8. Strong experience with React / Next.js for frontend consent SDK integration and Django / Python for backend integration. 9. REST API design, webhooks, and event-driven architecture for consent signal propagation across microservices. 10. Working knowledge of Kubernetes and container architecture for understanding Privacy deployment topology. 11. Cloud services experience (AWS preferred: EKS, RDS, S3, API Gateway). 12. Experience with multi-property web architectures — shared login, cross-domain consent, and federated data management. 13. Excellent communication skills — ability to present to client DPO, CTO, and app-owner audiences in language each understands. Good to Have: 1. Understanding of cookie mechanics: first-party vs third-party cookies, SameSite attributes, Secure flags, cookie consent propagation to third-party scripts. 2. Knowledge of ad-tech ecosystem: Google Ad Manager, programmatic advertising (DSPs, SSPs, header bidding), Google Consent Mode v2, and TCF (Transparency and Consent Framework). 3. CDN and caching understanding: CloudFront, Akamai, how cached pages interact with dynamic consent state. 4. Understanding of banking regulatory landscape: RBI IT guidelines, PCI-DSS, data localisation directives, and now DPDP Act 2023 is preferable. 5. Working knowledge of DPDP Act 2023 and Rules — consent lifecycle, data principal rights, and how they translate to technical integration requirements, would be an added advantage. 6. Understanding of encryption, masking, and anonymisation trade-offs for PET tool configuration decisions. 7. Experience navigating banking CAB processes, production change management, and enterprise security review cycles. 8. Understanding of CMS architectures (headless CMS, WordPress, custom CMS) and how privacy controls integrate into content pipelines. 9. Professional certifications such as TOGAF, AWS Solutions Architect, or privacy certifications (CIPP/CIPM/CIPT) are preferred.