Important Note - please do NOT put “Synpulse” or “Synpulse8” in your code or documents

Interview Case: Designing a Digital Onboarding Platform in Financial Services

Domain Options: Banking, Wealth Management or Insurance Duration: 90–120 minutes Format: Presentation + Deep Dive Discussion

Objective

Evaluate the candidate’s ability to design and communicate an end-to-end solution architecture that solves a real-world problem in the financial services domain, with core system integration, modern technology design, and pragmatic trade-off thinking.

Case Background

Synpulse has been engaged by a Tier-1 financial services provider (you choose, Banking, Wealth Management, or Insurance) to design a new digital onboarding platform. The goal is to streamline the onboarding experience for new customers or clients through seamless digital journeys, reducing friction, improving time-to-value, and increasing conversion.

Depending on the business line, onboarding may include: • Banking: Personal account creation, KYC, product recommendation. • Wealth: Risk profiling, document collection, investment preferences. • Insurance: Policy selection, e-signature, health questionnaires.

The platform must integrate with: • Core System (e.g., Core Banking, Policy Admin System, or Wealth CRM). • Identity verification (eKYC/eID) services. • Internal systems (CRM, IAM, notification engines). • Frontend channels (web and mobile).

What You Need to Do

Part 1: High-Level Architecture (Context & Container) Present the high-level architecture for your selected domain using C4Model: • Key systems, actors, and responsibilities • Logical breakdown of the solution into containers/services • Alignment with business goals (e.g., efficiency, scalability, security)

Part 2: Low-Level Design (Component or Sequence View) Zoom into one core service in your architecture (e.g., orchestration engine, product recommender, core system adapter) and: • Describe its internal components or service interactions. • Show API designs or key data exchanges. • Explain how it handles exceptions, performance, and monitoring.

Part 3: Core/Legacy System Integration • How would you architect interaction with the core system in your selected domain? • What are the sync/async considerations? • How would you abstract, secure, and monitor this integration layer?

Part 4: Scalability & Observability • How does your solution scale as onboarding demand grows? • How would you enable observability (logs, metrics, traces)? • How would you ensure business continuity and incident visibility?

Part 5: Security & Compliance Considerations • How do you secure sensitive data and ensure privacy? • How do you handle domain-specific compliance (e.g., GDPR, FINMA, MAS, HIPAA)? • How is identity and access managed?

Tools & Inputs

• Use any diagramming tool of choice (Miro, Lucidchart, draw.io, etc.) or draw by hand. • You may assume your cloud provider is AWS, Azure, or GCP. • State your assumptions clearly.

Pro Tips for Candidates

• Choose a domain you are most familiar with: Banking, Wealth Management, or Insurance. • Focus on storytelling: we’re as interested in why you made certain decisions as what you designed. • Think like a consultant, technically sound, but client-conscious.