Job Purpose Translate enterprise direction into executable end-to-end solution designs across one or more PODs and provide hands-on technical governance.

Duties and Responsibilities | Responsibility Area | Detailed Responsibilities | Key Deliverables | Success Measures / KPIs | Cadence / Trigger | |-------------------------------|---------------------------------------------------------------------------------|--------------------------------------------|----------------------------------------------------------|-----------------------------------| | Solution Architecture | Create end-to-end solution designs covering application, integration, data, infrastructure, security, and operations. | HLD; solution diagrams; architecture decisions | Design approval first-pass rate; delivery adherence to design | For every initiative | | Detailed Technical Design | Guide or review LLDs, component boundaries, data models, API contracts, error handling, and deployment topology. | LLD review; API specifications; data and sequence diagrams | Design defects; rework caused by unclear design | Before build starts and during refinement | | Non-Functional Requirements | Define measurable performance, scalability, availability, security, supportability, and observability requirements. | NFR catalogue; capacity assumptions; acceptance thresholds | NFR test pass rate; performance and availability targets achieved | During discovery and before release | | Engineering Standards | Define and enforce coding, integration, logging, exception handling, configuration, branching, and review standards. | Engineering standards; checklists; reusable templates | Code-quality trend; standards compliance; escaped defects | Continuous | | Technical Leadership | Provide design guidance, mentor developers, unblock complex technical issues,



and facilitate technical spikes. | Technical recommendations; spike outcomes; mentoring notes | Blocker resolution time; reduced rework; team capability uplift | Daily / sprint cadence | | Cross-POD Dependencies | Identify interface and shared-service dependencies, agree ownership, sequencing, versioning, and backward compatibility. | Dependency register; interface agreements; migration plan | Dependency delivery on time; integration defect reduction | Program increment and sprint planning | | Security by Design | Complete threat modelling, review identity and access, data protection, secrets, vulnerabilities, and security controls. | Threat model; security control mapping; remediation actions | Security findings closed; no critical release blockers | Design and release gates | | Performance and Reliability | Review sizing, caching, concurrency, failover, retries, monitoring, and operational recovery patterns. | Capacity model; resilience design; observability design | Load-test success; incident reduction; MTTR improvement | Design phase and pre-production | | Technical Assurance | Review code and implementation evidence for critical components; verify alignment between approved design and deployed solution.



| Assurance checklist; implementation deviations; technical sign-off | Fewer production defects; controlled deviations | Each release | | Vendor and Product Assessment | Evaluate vendor designs, licensing constraints, product fit, extensibility, support, and integration impacts. | Technical evaluation; gap analysis; recommendation | Fit-to-requirement; vendor issue closure; cost-risk balance | Procurement and change cycles |

Key Decisions / Dimensions

- Technical architecture decisions and HLD sign-offs.
- Standard definitions for engineering practices, patterns, and component boundaries.
- Vendor/product technology stack fitment recommendations.

Major Challenges

- Managing cross-POD dependencies and ensuring standard compliance across agile teams.
- Balancing quick-paced delivery schedules with strict non-functional and security standards.
- Evaluating complex vendor products to ensure architectural fitness and extensibility.

Required Qualifications and Experience a) Qualifications

B.E. / B.Tech / M.Tech / MCA / Post Graduates with 8-12 years of salesforce technology and architectural experience.

b) Work Experience

- Proven experience as a Technical/Solution Architect in a high-scale financial services or enterprise domain.
- Deep understanding of end-to-end architecture (Application, Integration, Data, Security, and Infrastructure).
- Expertise in designing resilient, highly available, and scalable microservices architectures.
- Strong technical leadership, mentoring abilities, and experience driving engineering governance.
- Excellent communication and collaboration skills to manage cross-POD dependencies effectively.

Locations Job Level: GB06

Job Title: Lead Software Architect - IT, SFDC B2B & TWF, SFDC B2B & TWF

Job Location Country: India

State: MAHARASHTRA

Region: West

City: Pune

Location Name: Pune Corporate Office - Mantri Tier Megapolis

📌 Lead Software Architect (India)
🏢 Bajaj FinServ
📍 India