Solution Architect - Lending Platform

• Own the lending domain model - define bounded contexts, aggregate boundaries, and domain event taxonomy across LOS, LMS, collections, and digital channel systems; ensure all three squads build against a shared, coherent domain language

• Design and own the API contract standards for all business-facing APIs - OpenAPI specifications, versioning strategy, backward compatibility guarantees, and the API review process that all squad Senior Engineers follow before shipping

• Define event-driven architecture patterns for lending workflows - which domain events flow between which services, event schema standards, and the choreography vs orchestration decisions for complex multi-step processes like loan origination and collections escalation

• Establish data ownership boundaries across squads - which service owns which data, how cross-domain queries are resolved, and how the lending domain model is kept consistent as the codebase grows

• Produce and maintain the lending domain Architecture Decision Records library - every significant design decision documented with context, options considered, and rationale; the living technical memory of SarvaGram's lending platform

• Design the integration architecture between the Analytics squad's ML models (EWS, credit scoring, collection propensity) and the business squads' operational systems - clean API contracts, model versioning strategy, fallback handling, and explainability output design

• Architect the collection strategy intelligence layer - how EWS model outputs translate into actionable collection workflows in Vanguard; the design that connects data science outputs to field officer actions

• Design the AI-assisted underwriting architecture in Vertex - how thin-file credit scoring models integrate into the LOS decisioning flow, with RBI-compliant reason codes and audit trail requirements built into the design from the start

• Pioneer the use of agentic AI platforms in lending operations - explore and design how autonomous AI agents can assist with loan processing, collections communication, and customer support workflows

• Use Claude as a core architectural tool - generate ADR drafts, explore system design trade-offs, produce API specification first drafts, and accelerate architecture documentation

• Own the architecture review process for all significant system designs across Nexus, Vanguard, and Vertex - review proposals from Senior Engineers and PMs, provide structured feedback, and sign off before implementation begins

• Define and enforce cross-squad engineering standards for the Business POD - error handling conventions, API pagination patterns, financial calculation standards, audit logging requirements, and domain event schema governance

• Identify and eliminate duplication across squads - where Nexus, Vanguard, and Vertex are solving the same problem independently, the Architect proposes a shared solution and drives adoption

• Resolve technical conflicts between squad Senior Engineers - when two squads have incompatible design decisions that affect shared systems, the Architect is the tiebreaker with documented reasoning

• Ensure every lending system design is RBI-compliant by construction - audit trail requirements, data localisation constraints, and regulatory reporting needs are architecture inputs, not post-launch additions

• Design the audit logging architecture for lending operations - loan state transitions, credit decisions, collection actions, and data access events must all be logged with sufficient detail to satisfy RBI examination requirements

• Work with the CISO on application-level security architecture for lending systems - data encryption at rest and in transit for PAN, Aadhaar, and credit bureau data

• Design financial calculation standards - interest accrual, EMI rounding, penal charge computation, and prepayment adjustment algorithms that are mathematically precise, consistently implemented across squads, and auditable to the rupee

• Mentor Senior Backend Engineers across Nexus, Vanguard, and Vertex - structured architecture reviews, domain knowledge transfer, and deliberate growth toward Staff Engineer level

• Lead the Backend Guild for the Business POD - fortnightly sessions on domain-driven design, lending system patterns, AI integration architecture, and API contract design

• Collaborate with the Cloud-Native Platform Architect on shared concerns - API gateway configuration, observability standards, and infrastructure decisions that affect lending services; consult the Platform Architect for infra needs rather than owning infrastructure decisions

• Engage directly with PMs and BAs during feature design - review BRDs for technical feasibility, surface hidden complexity early, and ensure architecture implications are understood before sprint planning

• 12 to 14 years in software engineering with at least 4 years in an architect or principal engineer role - mandatory prior experience at an NBFC, bank, or lending-focused fintech

• Demonstrable ownership of lending system architecture - has designed LOS, LMS, or collections systems from the ground up, not just contributed features to an existing platform

• Deep API contract design experience - has owned an OpenAPI standard across multiple teams, managed versioning over time, and dealt with the real-world consequences of breaking changes

• Experience with domain-driven design in a complex financial domain - bounded contexts, aggregate design, and domain event modelling in a system where business rules are the primary complexity driver

• Active AI tool user - uses Claude, ChatGPT, or equivalent tools in their architecture work today; not interested in learning about AI, but already doing it

• Exposure to ML model integration in lending - has either built or reviewed the integration of credit scoring models, EWS outputs, or behavioural analytics into operational lending systems