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

PartnerOn whatProduct ManagersProduct vision and roadmapBusiness AnalystsBusiness processes and requirementsEngineering ManagersDelivery executionQAQuality engineeringDevOps / PlatformCI/CD, cloud, and observabilityProduct LeadershipTechnology roadmapWhat Good Looks Like After 12 to 18 Months

Leadership should be able to say:

1. Integration Platform becomes a strategic product capability.

2. Engineering teams reuse platform capabilities.

3. AI becomes a standard engineering capability.

4. Engineering productivity improves measurably.

5. Platform reliability and observability improve.

6. Technical debt is proactively managed.
   Skills and Experience

1. 10–15 years of software engineering experience with at least 3 years in an Architect role.

2. Expertise in Java (Java 17+ preferred), Spring Boot and Microservices.

3. Strong knowledge of Kafka/RabbitMQ, REST APIs, distributed systems and event-driven architecture.

4. Experience with AWS, Docker, Kubernetes, PostgreSQL/MySQL and Redis.

5. Strong understanding of integration patterns, API versioning, idempotency, retries, fault isolation and high-throughput platforms.

6. Experience building enterprise integrations across ERP, WMS, OMS, marketplaces, carriers or similar domains.

7. Hands-on experience with AI engineering tools such as Cursor, Claude, GitHub Copilot or equivalent.
   Leadership Behaviours We Expect

Architects at Anchanto are expected to operate with high ownership, use data over opinions, adopt an AI-first mindset, drive continuous improvement, and collaborate without bureaucracy.

What This Role Is Not

To be clear about scope, this role is not:

1. Not a coding only architect.

2. Not a delivery coordinator.

3. Not a maintenance only architect.

4. Not a customer-specific solution architect.

This is a technical leadership role responsible for building a scalable, reusable, and AI-enabled Integration Platform.

Engineering Philosophy

1. Engineers should solve business problems, not repetitive tasks.

2. Automate wherever possible.

3. Build reusable capabilities.

4. Use AI to improve productivity.

5. Strengthen the platform with every architectural decision.
   Success Measures

Indicative KPIWhat it measuresPlatform ReuseAdoption of reusable platform componentsEngineering ProductivityReduction in effort through AIArchitecture GovernanceCompliance with architecture standardsPlatform ReliabilityAvailability and resilienceTechnical DebtReduction in architectural debtDelivery VelocityFaster delivery without quality regressionAI AdoptionUsage across the SDLCEngineering CapabilityGrowth in architectural maturityClosing

At Anchanto, we believe the future of software engineering is platform-driven, AI-enabled, and outcome-focused.

This role offers the opportunity to shape the architecture behind global commerce and establish the Integration Platform as a strategic capability for Anchanto's next phase of growth.