Role: .Net Solution Architect Domain: Insurance Stack - MS Technology, Azure, Full stack etc.. (read below) What we look for? Strong Architecture, Conceptual clarity, problem solving, ability, Leadership quality, Client facing exp, depth in design, integration architecture. Responsibilities: For a change , we are mentioning what can qualify a profile and the depth of architecture required, incumbents may go through the requirements and share us their resume with a separate pg containing details on the asked questions. 1. Scaled Architecture Design Evaluation will be on candidate’s ability to design systems at scale (e.g., NPCI UPI, Uber, ONDC , RedBus): How well do you decompose monolithic systems into scalable components (e.g., ONDC architecture, NPCI as a central switch, geospatial for Uber)? Do you address critical non-functional requirements (NFRs) like latency (<1s for UPI), throughput (10k+ TPS), and fault tolerance? Patterns & Frameworks: Usage of event-driven architecture (Kafka), CQRS, Saga pattern (for distributed transactions), and Circuit Breaker (resilience). Challenges: Assess their approach to interoperability (UPI’s PSP integration), real-time data sync (Uber’s driver tracking), and overbooking prevention (RedBus). 2. Architecture Patterns vs. Styles How do you justify pattern choices (e.g., Bulkhead for RedBus vs. Service Mesh for Uber)? 3. Standards & Governance Compliance: Familiarity with TOGAF, ISO/IEC 42010, or Zachman frameworks. API Governance: Experience with tools like Apigee for centralized API management. 4. Self-Healing Systems Use of Kubernetes (auto-scaling, pod recovery), Chaos Engineering (Chaos Monkey), and observability stacks (Prometheus/Grafana). How do you implement retry mechanisms, circuit breakers, and automated rollbacks? 5. D2C Platform Expertise Proficiency in headless commerce (e.g., Contentful), CDPs (Customer Data Platforms like Segment), and API-first design. 6. Integration Architecture Experience with protocol transformation (REST to SOAP), message queuing (RabbitMQ/Kafka), and ETL pipelines (Apache NiFi 7. Security Architecture Beyond SSO/Auth: How do you implement zero-trust models, WAFs (Cloudflare), and SIEM tools (Splunk)? Do you address OWASP Top 10 risks (e.g., SQLi, XSS) and data encryption (AES-256, TLS 1.3)? 8. Platform KPIs & Metrics Focus on uptime (99.99% SLA), MTTR (<1hr), TPS, and cost optimization. How do you align KPIs with business goals (e.g., user growth vs. infrastructure scaling)? 9. Edge Computing – Edged based Processing Use of AWS Greengrass/Kubernetes Edge for local data processing. How do you address latency reduction, offline capabilities, and edge-node security? Show more Show less