Technical Architect

Job Description: Technical Architect at Anchanto India

Location: Pune, India  | Experience: 10 to 15 years | Seniority:  Senior Individual Contributor / Architect

Industry: Enterprise B2B SaaS / Global Commerce / Supply Chain  Technology

About the Role

We are looking for a Technical Architect who can own the technical architecture across two of Anchanto's most critical products  OXM (Order Experience Management) and OMS (Order Management System). This is a senior individual contributor role with deep ownership of system design, scalability, reliability, and AI-powered capability delivery. You will be the technical authority across both platforms, ensuring architectural coherence, engineering standards, and a clear path to scale as Anchanto grows globally. This is not a hands-off advisory role. You will be deeply involved in design decisions, code reviews, incident resolution, and driving the engineering teams toward better patterns, faster delivery, and higher quality with AI as a force multiplier across the SDLC.

 

Anchanto is a global B2B SaaS company powering commerce for brands, retailers, logistics companies and enterprises. Our customers rely on it to realize 100% of their revenue on a daily basis. The platform is used by 300+ customers brands, retailers, and logistics providers,  processes 150M+ orders annually, and serves thousands of users across operations teams in 12 countries including France, UK, Singapore, Malaysia and UAE.

What Will Your Day Look Like?

1. Own architecture across OXM and OMS - lead system design for new capabilities, define integration patterns, and ensure both platforms evolve coherently as business requirements change.
2. Design and evolve event-driven, distributed systems - ensure scalability, fault tolerance, multi-tenant isolation, and idempotency across AWS (SQS, SNS, EventBridge, Lambda, ECS/EKS, Aurora, DynamoDB, Redis).
3. Lead AI capability architecture - design the technical foundation for AI-powered features inside OXM and OMS intelligent order routing, anomaly detection, demand forecasting, agentic workflows and ensure they meet enterprise-grade reliability, security, and cost standards.
4. Partner with Engineering Managers and Tech Leads - translate product requirements into technical blueprints, unblock design bottlenecks, and ensure engineering teams have clear architectural guidance before execution begins.
5. Own cross-platform integration standards - define API versioning, contract testing, rate limiting, and deprecation policies so OXM and OMS interoperate cleanly and third-party integrations are reliable at scale.
6. Contribute to engineering productivity - identify and eliminate architectural toil, reduce system complexity where it creates delivery friction, and drive DORA metric improvement through better system design

Skills and Experience needed for this job

1. Deep expertise in Node.js - async processing, high-throughput APIs, event-driven microservices at scale
2. Strong working knowledge of Ruby on Rails - MVC patterns, ActiveRecord, background jobs (Sidekiq), API design, and performance optimisation
3. Hands-on experience with AWS- EC2, SQS, SNS, EventBridge, Lambda, ECS/EKS, Aurora/PostgreSQL, DynamoDB, ElastiCache/Redis, S3, API Gateway, CloudWatch
4. System design depth - multi-tenant architecture, idempotency, retries, backpressure, failure isolation, and distributed transaction patterns
5. Proven track record of designing systems with 99.9%+ uptime and sub-200ms P95 latency
6. Strong API design - RESTful, GraphQL, contract testing, versioning, and integration reliability
7. Database expertise – MySQL, PostgreSQL, Aurora, DynamoDB, Redis; query optimisation, indexing strategies, schema design for high-throughput workload.
8. Familiarity with AI coding tools - Claude Code, Cursor, Copilot as productivity multipliers in the SDLC
9. Secure SDLC, SAST/DAST, secret scanning, dependency audits, OWASP Top 10, threat modelling

How you will build at Anchanto

1. You will be the technical conscience of OXM and OMS - the person engineering teams come to when they need to make the right call, not just the fast one.
2. You will make AI a real part of how we build not a side project by architecting AI-powered features inside our products and enabling engineers to use AI tools as a default, not an exception.
3. You will treat scalability, reliability, and cost as first-class design constraints not afterthoughts across every system you touch.
4. You will work with Engineering Managers to ensure teams have clear technical direction before they start building, reducing mid-sprint surprises and rework.
5. You will hold the bar high every API, every schema, every integration pattern should be something we're proud to still have in production two years from now.

What Success Looks Like

1. Reliability: ≥ 99.9% uptime for owned services.
2. Performance: < 200ms P95 latency for critical APIs.
3. AI Delivery: At least one AI-powered capability shipped inside OXM or OMS within 6 months
4. Quality: reduction in P1/P2 incidents and MTTR; improving DORA metrics quarter over quarter.
5. Platform Standardization: Containerisation and observability standards adopted across both platforms.
6. Cost: No unexpected cost blowouts on architectural decisions include cost modelling

Leadership & Ownership traits you must have

1. Own the technical architecture of OXM and OMS end-to-end from design to production to incident
2. Make technical trade-off calls with clarity and confidence speed vs. correctness, cost vs. scale, build vs. buy
3. Drive architectural alignment across engineering teams without formal authority, influence through reasoning, documentation, and trust
4. Proactively identify and surface technical risk before it becomes a production problem
5. Mentor Tech Leads and Senior Engineers on system design, architectural thinking, and engineering standards
6. Partner with Engineering Managers and Product to ensure roadmap decisions are technically grounded and deliverable

Behaviours / Personal Qualities

1. Outcome Ownership: You don't just design systems, you care whether they work in production, at scale, for real customer
2. Systems Thinking: You naturally consider failure modes, dependencies, edge cases, and second-order effects before they become someone else's incident.
3. Execution Discipline: You follow through. RFCs get written. ADRs get documented. Decisions don't disappear into Slack threads.
4. Adaptability: You can work across Node.js and Ruby on Rails stacks, switching context between two distinct platforms without losing depth on either.
5. Raising the Bar: You set a standard for what good looks like - in code, in design, in documentation and you hold it consistently.