Java Architect

Technical Architect – Integration Platform Location: Pune, India Reports to: PBU Head – Integration Product Business Unit Experience: 10 to 15 years Type: Full time About the Role Anchanto is a global enterprise grade B2B SaaS company powering commerce for brands, retailers, marketplaces, logistics providers, and warehouses across multiple countries. The Integration Platform is one of Anchanto's most strategic engineering assets, enabling scalable connectivity across marketplaces, carriers, ERP, accounting, and enterprise systems. This role defines the technical direction of the platform while transforming engineering through AI-first development, reusable platform capabilities, and engineering automation. Why This Role Exists Today, too much integration engineering depends on custom implementations, repeated design decisions, and manual development effort. This role exists to build a reusable, scalable, and AI-enabled Integration Platform, enabling engineers to spend more time solving business problems than repetitive engineering tasks. What You Will Own The role owns eight areas. The list is deliberately broad because this is the platform owner, but the bar is the same throughout: reusable systems over repeated effort, clear technical ownership, and reliable engineering execution. 1. Integration Platform Architecture Own the long-term architecture across sales channels, carriers, ERP, and enterprise connectors. Outcome: A scalable, reusable, and resilient platform supporting rapid customer onboarding. 2. Platform Engineering and Reusable Capabilities Build reusable frameworks, connector templates, canonical models, and engineering standards. Outcome: Platform capabilities replace repeated custom implementations. 3. AI-Driven Engineering Transformation Lead AI-assisted architecture, coding, testing, documentation, code reviews, prompt libraries, agentic workflows, and engineering productivity improvements. Outcome: Engineering teams consistently deliver faster with higher quality while reducing manual effort. 4. Engineering Excellence and Architecture Governance Define engineering standards, design reviews, observability, resilience, and security. Outcome: Consistent engineering quality across all initiatives. 5. Product Engineering Collaboration Partner with Product Managers, Business Analysts, Engineering Managers, and QA. Outcome: Strong alignment between business goals and engineering execution. 6. Platform Reliability and Scalability Drive resilience, scalability, and production observability. Outcome: Enterprise-grade reliability. 7. Innovation and Platform Evolution Lead technology modernisation and proof of concepts. Outcome: Continuous platform evolution. 8. Technical Leadership and Capability Building Mentor architects and senior engineers while fostering an AI-first engineering culture. Outcome: A high-performing engineering organisation. Cross Functional Operating Model Partner On what Product Managers Product vision and roadmap Business Analysts Business processes and requirements Engineering Managers Delivery execution QA Quality engineering DevOps / Platform CI/CD, cloud, and observability Product Leadership Technology roadmap What Good Looks Like After 12 to 18 Months Leadership should be able to say: Integration Platform becomes a strategic product capability. Engineering teams reuse platform capabilities. AI becomes a standard engineering capability. Engineering productivity improves measurably. Platform reliability and observability improve. Technical debt is proactively managed. Skills and Experience 10–15 years of software engineering experience with at least 3 years in an Architect role. Expertise in Java (Java 17+ preferred), Spring Boot and Microservices. Strong knowledge of Kafka/RabbitMQ, REST APIs, distributed systems and event-driven architecture. Experience with AWS, Docker, Kubernetes, PostgreSQL/MySQL and Redis. Strong understanding of integration patterns, API versioning, idempotency, retries,…